Torben Hansen

[TASK] Hide honeypot field from screenreaders

9

The configured value `new-powermail-hp` for the autocomplete attribute is invalid and fails in the accessibility check provided by accessibilityinsights.io AFAIK, valid values for autofill are: * https://www.w3.org/TR/html52/sec-forms.html#autofilling-form-controls-the-autocomplete-attribute * https://www.w3.org/TR/WCAG21/#input-purposes

Replace: `$parser->parse(...) line in \Tx_SfTv2fluidge_Service_SharedHelper::getContentColsFromTs()` with `$parser->parse(\t3lib_TSparser::checkIncludeLines($typoScript));` Thanks to Leonie Philine Bitto from netcreators.nl

If a virtual host is configured to `SecRuleEngine = DetectionOnly`, those non-blocked attacks should be listed separated from really blocked attacks

See: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76519

Argument annotations can be removed in several classes.

See https://github.com/TYPO3/typo3/commit/77fd49fff2c886eabe243fa404e005002d42afab?s=03 Check, if this has any impact on emails sent by the extension and payment integrations

[TASK] Send emails depending on language setting

3

NotificationService::getNotificationBody() must render the fluid standalone template based on the saved language in the registration (Frontend and Backend)

Work on all phpstan issues (also those excluded in baseline)

The old alias to `sf_event_mgt:cleanup` command must be removed

Due to a bug in extbase, the backend module does not respect the workspace id of records and may show unpublished data to users in live workspace. Forge issue: https://forge.typo3.org/issues/97220