[FEATURE] Add possibility to use session data in TS conditions
Since the session API has been adjusted it is no longer possible to access the (now protected) sesData property of the fe_user object. Using TSFE:fe_user|sesData|foo|bar in a TS condition will trigger a deprecation log entry. Instead a cleaner approach is now available: [globalVar = session:foo|bar = 1234567] Resolves: #83506 Releases: master Change-Id: Idbb079334186eac1dfe062a71a601e556a9bd247 Reviewed-on: https://review.typo3.org/55310 Tested-by:TYPO3com <no-reply@typo3.com> Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org>
Showing
- typo3/sysext/core/Documentation/Changelog/master/Deprecation-83506-DeprecateFeUserSesDataCondition.rst 34 additions, 0 deletions...ter/Deprecation-83506-DeprecateFeUserSesDataCondition.rst
- typo3/sysext/core/Documentation/Changelog/master/Feature-83506-RetrieveSessionDataInTSConditions.rst 23 additions, 0 deletions...aster/Feature-83506-RetrieveSessionDataInTSConditions.rst
- typo3/sysext/frontend/Classes/Configuration/TypoScript/ConditionMatching/ConditionMatcher.php 8 additions, 1 deletion...uration/TypoScript/ConditionMatching/ConditionMatcher.php
- typo3/sysext/frontend/Tests/Unit/Configuration/TypoScript/ConditionMatching/ConditionMatcherTest.php 12 additions, 3 deletions...ion/TypoScript/ConditionMatching/ConditionMatcherTest.php
Please register or sign in to comment