.. include:: ../Includes.txt


.. _breaking-changes:

Breaking Changes
================

2022.01.01
''''''''''

Interface Evoweb\SfRegister\Interface\FrontendUserInterface is renamed to
Evoweb\SfRegister\Domain\Model\FrontendUserInterface

2021.12.31
''''''''''

Validator configuration is changed. As long as your custom validator has no
injected classes like repository or likewise, you do not need to change anything.

If you need something in your validator, you need to use to constructor
injection, add an implements of InjectableInterface, make the validator a public
service via Services.yaml and need have a way to get
the options set.
Options can be set by your own method or by using the AbstractValidator of
sf_register.

So if you need a class in your validator in code this changes are needed:
* Add your validator to Services.yaml:
* Add ```implements InjectableInterface``` to your validator
* Use \Evoweb\SfRegister\Validation\Validator\AbstractValidator as validator base
* Add the repository in constructor

**Services.yaml**::

   Evoweb\SfRegister\Validation\Validator\UniqueValidator:
     public: true


**Class definition**::

  use Evoweb\SfRegister\Validation\Validator\AbstractValidator;
  use Evoweb\SfRegister\Validation\Validator\InjectableInterface;

  class UniqueValidator extends AbstractValidator implements InjectableInterface, ...


**__construct**::

   public function __construct(FrontendUserRepository $userRepository)
   {
     $this->userRepository = $userRepository;
   }


2020.04.29
''''''''''

The hole extension was refactored to make best usage of TYPO3 10 changes. Namely

* constructor DI
* exchange Signal/Slot dispatcher with PSR-14 events, have a look in extendability at :ref:`PSR-14 events<Psr14Event_>`
* refactor to fully match the PSR-12 standard
* rename TypoScript setting processInitializeActionSignal to processInitializeActionEvent
* rename TypoScript setting redirectSignal.* to redirectEvent.*
* reorganize TypoScript setting createDefaultSelected etc to defaultSelected.create etc
* reorganize TypoScript notifyUser* and notifyAdmin* setup and constants to notifyUser.* and notifyAdmin.*
* modify Mail service to have better controller and action assignment
* replace switchableControllerActions with individual plugin per controller
  check what elements with list_type sfregister_form are present in table tt_content
  and replace them with their corresponding new plugin
* change how TS names, templates, mail subject and PSR-14 event name are build based
  on controller and action name in combination with notifyAdmin and notifyUser
  * TS name is build notifyAdmin.{ControllerName}{ActionName} notifyAdmin.createSave
  * Template name is build NotifyAdmin{ControllerName}{ActionName} NotifyAdminCreateSave
  * Mail subject is build subjectNotifyAdmin{ControllerName}{ActionName} subjectNotifyAdminCreateSave
  * Event name is build NotifyAdmin{ControllerName}{ActionName}Event NotifyAdminCreateSaveEvent
  * PostCreateSave replaced with CreateSave
  * PostCreateConfirm replaced with CreateConfirm
  * PostCreateRefuse replaced with CreateRefuse
  * PostCreateAccept replaced with CreateAccept
  * PostCreateDecline replaced with CreateDecline
  * PostDeleteSave replaced with DeleteSave
  * PostDeleteConfirm replaced with DeleteConfirm
  * PostEditSave replaced with EditSave
  * PostEditConfirm replaced with EditConfirm
  * PostEditAccept replaced with EditAccept
  * SendInvitation replaced with InviteInvite
  * PostResendMail replaced with ResendMail

2019.02.03
''''''''''

Drop custom form styles in favor for Bootstrap 4.2 styles. Be aware, to get the styles.css
from older releases if you depend on it. If you use the Bootstrap 4.2 form styles you are
good to go.



2019.02.02
''''''''''

The password strength meter got replaced with the <meter> element. If you still need the old
iframe variant for old browser or for the looks, please override the file
EXT:sf_register/Resources/Private/Partials/Form/Password.html in your sitepackage and replace

Before:
::
   <meter min="0" low="20" optimum="30" high="40" max="50" id="bargraph"></meter>

After:
::
   <iframe id="bargraph" frameborder="none" scrolling="no"
      src="/typo3conf/ext/sf_register/Resources/Public/Images/progressbar.svg"></iframe>



2019.01.17
''''''''''

The core changed away from saltedpasswords towards integrated passwordHashing in EXT:Core (see
Deprecation: #85804 - Salted password hash class deprecations)

By this its always possible to properly hash passwords.

Due to this shift the support for md5 and sha1 configuration is dropped in
EqualCurrentPasswordValidator::isValid and FeuserController::encryptPassword.



2019.01.13
''''''''''

Changes in validation were done to match the new pattern used since TYPO3 9. To ensure that the user/password model
still validates you need to check whether you changed rules in plugin.tx_sfregister.settings.validation.*.*

Here are some examples how old rules need to be converted:

Before:
::
   Evoweb\SfRegister\Validation\Validator\RequiredValidator
After:
::
   "Evoweb.SfRegister:Required"

Before:
::
   StringLength(minimum = 4, maximum = 80)
After:
::
   "StringLength", options={"minimum": 4, "maximum": 80}

Before:
::
   Evoweb\SfRegister\Validation\Validator\UniqueValidator(global = 1)
After:
::
   "Evoweb.SfRegister:Unique", options={"global": 1}

In general 'Evoweb\SfRegister\Validation\Validator\' needs to be replaced with '"Evoweb.SfRegister:' and the
ending 'Validator' with '"'



2015.11.15
''''''''''

* Method 'changeUsergroup' got pulled up from FeuserCreateController to FeuserController. If a controller extends
  FeuserCreateController the change in changeUsergroup needs to be copied.
* Method 'changeUsergroup' got the parameter '$usergroupIdToBeRemoved' removed. This is because all known usergroups
  previously set get removed now. So only the '$user' and '$usergroupIdToAdd' need to be provided. All usage of this
  method needs to be changed accordingly.

* Drop mailhash, setMailhash() and getMailhash() from frontend user model as it was deprecated since 2014.