0.32.0

• BREAKING: Added users.email_validated_at flag to track deliverability of emails. Flag resets on email change. Changed users.confirmed_at intention. remp/crm#1739 remp/crm#1028
  • The original intention in CRM was to use users.confirmed_at flag to determine both account confirmation and email deliverability. We're splitting this to two different fields.
    • users.confirmed_at now flags the actual account confirmation triggered by clicking on the confirmation link in an email, event-based confirmation, or admin confirmation. Any features dependent on account confirmation should still use this field. To maintain backwards compatibility, we recommend creating event handler listening to the UserCreatedEvent which confirms new users automatically.
    • users.email_validated_at now flags deliverability of email address. Its primary use case is to determine whether systems should attempt to deliver non-system messages to the email address.
  • The migration copies the value of confirmed_at to email_validated_at field to maintain originally stored values. This is a one-time operation.
• BREAKING: Signature of method Crm\UsersModule\Repository\UserEmailConfirmationsRepository::verify was changed and renamed. remp/crm#1739
  • Please change any use to the method to Crm\UsersModule\Repository\UserEmailConfirmationsRepository::confirm.
  • Method now returns instance of the email confirmation row that's being confirmed instead of boolean value.
• BREAKING: Previously, if user signed in with her username and password, she would be automatically confirmed. This has been removed. remp/crm#1739 remp/crm#1028
  • To maintain backwards compatibility, you can create internal event handler listening to the UserSignInEvent and confirm user yourself.
• Added API endpoints users/set-email-validated and users/set-email-invalidated for email address validation/invalidation by external services. remp/crm#1740 remp/crm#1028
• Fixed the issue with the disappearing/hiding buttons in the Basic info panel (UsersAdmin). (Causing problem, if the component is too narrow or the email address is too long.) remp/crm#1838
• Changed Google Sign in user creation flow. We're temporarily generating the user password (it was empty before) until the related trigger in the ScenarioModule supports this scenario and until CRM provides password-less login flow (i.e. magic login link via email). remp/crm#1913
• Fixed invalid use of site_name config option which could cause error if strict check is used by PhpOffice. Replaced with site_title. remp/crm#1921