Torben Hansen

The current price option feature is not flexible enough to allow mutliple prices for an event. It is not possible to name the price options and it is currently always...

TYPO3 `list_type` will sooner or later be removed. Therefore, all plugins should be migrated to `CType`. A update wizard must be available to migrate existing content elements. Migration: https://github.com/TYPO3/typo3/commit/f471d667bed295e71bded70c4e687b31099fa5fc

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.0/Breaking-102605-TSFE-fe_userRemoved.html Most occurencees can be replaced with User Aspect. ViewHelpers are not so easy, since we must access `$GLOBALS['TYPO3_REQUEST']`. Change is considered breaking, since some functions returning`FrontendUserAuthentication` will vanish

[FEATURE] Always show top events first

1

Add an option in the event list and search plugin, so it is possible to show top events in the result list on top. Example for Repository: ``` $orderings['top_event'] =...

This change fixes the range string calculation, so items for the given date are included until 23:59 of the target end date. Fixes: #4087

[BUG] Wrong range string generation in DateRange facet

1

**Describe the bug** The range string in the `DateRange` facet is generated, so that the time of the start- and enddate is 0000 (00:00). For the enddate, this is wrong...

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

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

In order to cleanup the `EventController`, some methods will be moved to `EventEvaluationService` Public methods: * `evaluateForDetailAction` * `evaluateForRegistrationAction` The class will contain the following methods from `EventController`: * `evaluateSingleEventSetting`...