[BUGFIX] Ensure pageUid of RedirectFinisher can be parsed correctly
With #92112, parsing of the pageUid option of the RedirectFinisher has been restricted to accept only strings as option value. Prior to this change, one could also define integer values. The previous behavior has now been restored by explicitly parsing the option value as string and then parsing it back to an integer. Resolves: #92800 Related: #92112 Releases: master, 10.4 Change-Id: I88992b309e09757ae24348c6066294effb209505 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66620 Tested-by:TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
Showing
- typo3/sysext/form/Classes/Domain/Finishers/RedirectFinisher.php 1 addition, 2 deletions...sysext/form/Classes/Domain/Finishers/RedirectFinisher.php
- typo3/sysext/form/Tests/Unit/Domain/Finishers/RedirectFinisherTest.php 118 additions, 0 deletions...form/Tests/Unit/Domain/Finishers/RedirectFinisherTest.php
Please register or sign in to comment