[BUGFIX] Lift restriction for restricted records in Routing Aspects
Since TYPO3 v9.5.16 it is not possible anymore to resolve URLs with an Aspect that contains records with fe_group restrictions. This is due to a legacy solution that the Frontend User is actually initialized early enough but the groups are resolved within $TSFE->determineId() at a later point. For this reason, Routing does not handle fe_group restrictions, but the plugin should take care of that for the time being. Future TYPO3 versions can decide to resolve the fe_group restrictions earlier, but this would be a breaking change of behaviour of the Frontend Request Workflow for TYPO3 v10 + v9. Resolves: #91049 Releases: master, 9.5 Change-Id: I0e57768f5358dc06101acdca374b9c872a65c865 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64408 Tested-by:TYPO3com <noreply@typo3.com> Tested-by:
Krystian Szymukowicz <k.szymukowicz@gmail.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
Showing
- typo3/sysext/core/Classes/Routing/Aspect/PersistedAliasMapper.php 4 additions, 0 deletions...sext/core/Classes/Routing/Aspect/PersistedAliasMapper.php
- typo3/sysext/core/Classes/Routing/Aspect/PersistedPatternMapper.php 4 additions, 0 deletions...xt/core/Classes/Routing/Aspect/PersistedPatternMapper.php
- typo3/sysext/core/Tests/Functional/Routing/Aspect/PersistedAliasMapperTest.php 4 additions, 2 deletions...ts/Functional/Routing/Aspect/PersistedAliasMapperTest.php
- typo3/sysext/core/Tests/Functional/Routing/Aspect/PersistedPatternMapperTest.php 4 additions, 2 deletions.../Functional/Routing/Aspect/PersistedPatternMapperTest.php
Please register or sign in to comment