#104809Exception in BE login notification with f:translate in custom SystemEmail layout
Description
Similar to #104461 an error occurs if a custom SystemEmail layout is registered which uses the <f:translate/> Fluid viewhelper and a user logs into the TYPO3 BE having the emailMeAtLogin option enabled:
> No valid attribute “applicationType” found in request object
This happens because the EmailLoginNotification is processed within a BE middleware but the request applicationType attribute is set after middleware request processing by the BE application.
Reviews 2
Related issues 4
- Bug #99864Notify by email on login not working after user activates MFA
- Bug #100128AdminLoginWarning email not sent when MFA is activated
- Feature #100307Use PSR-14 Events instead of hooks for logout in AbstractUserAuth
- Bug #104461"Test Mail Setup" cannot send mails if System HTML mail layout uses <f:translate>