"Speaking URL fragments" 5.0.0 and 4.3.0 (EXT:content_slug)

Only minor adjustments were necessary to support TYPO3 v14 with this extension.

To use Sebkln\ContentSlug\Evaluation\FragmentEvaluation->sanitizeFragment as a userFunc in TypoScript, the new PHP attribute #[\TYPO3\CMS\Core\Attribute\AsAllowedCallable] must be applied to this method (Changelog #108054).
The call as a userFunc is useful for sanitizing the fragment string if other or additional database fields are used as a source.

The new PHP attribute has also been backported to TYPO3 versions 13.4.21 and 12.4.41 to avoid breaking changes in extensions. These versions are therefore the new minimum requirements for this extension.
This also means that version 5 can support three TYPO3 major versions at once.

I released this version at the beginning of the week to fix a potential problem in the redirects module of the TYPO3 backend: If a redirect target points to a content element (i.e., has a fragment), in some cases, the redirects module could no longer be accessed. The issue occurred depending on whether the content_slug extension was loaded in the first site in the page tree. From now on, the extension checks in the event listener whether a valid frontend request is given.

As a small improvement, it is now also possible to use the FragmentIdentifierProcessor with its alias fragment-identifier in TypoScript, which eliminates the need for the FQCN:

// Process 'fragmentIdentifier' variable in section menus:
tt_content.menu_section.dataProcessing.10.dataProcessing.20.dataProcessing.5 = fragment-identifier
tt_content.menu_section_pages.dataProcessing.10.dataProcessing.20.dataProcessing.5 = fragment-identifier