93291[BUGFIX] Dispatch AfterContentHasBeenFetchedEvent in PageView
Commit message
Review
-
Code review CR 0
-
Verified V 0
- core-ci +1 CI
Issues 2
Files 2
Review log 89
-
Nikita Hovratov uploaded patch set 1 03/20/26, 14:27
-
Oli Bartsch commented on patch set 1 03/20/26, 14:34
-
core-ci voted on patch set 1 V +1 03/20/26, 14:37 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98302
-
Nikita Hovratov commented on patch set 1 03/20/26, 14:45
PageViewContentObject.php:179ReplyYes, is this bad? -
Oli Bartsch commented on patch set 1 04/13/26, 08:00
PageViewContentObject.php:179ReplyI think so. How do you ensure you are not manipulating an already processed content result then? -
Christian Kuhn commented on patch set 1 04/14/26, 12:02
PageViewContentObject.php:179ReplyI stumbled upon this issue as well since I want the fallback to globals TYPO3_REQUEST being deprecated in v14. I solved it differently by handing over $request late: https://review.typo3.org/c/Packages/TYPO3.CMS/+/93654 -
Nikita Hovratov commented on patch set 1 04/15/26, 09:07
PageViewContentObject.php:179Reply Unresolved@bo@cedev.de I think we need then another Event at this point. ResolveContentAreasEvent can only be used internally by TYPO3 to prepare the (lazy) Content Areas Collection, but not for manipulating records, as it is too early in the middleware stack (PrepareTypoScript). -
Christian Kuhn wrote 06/18/26, 23:05
Removed cc Christian Kuhn. -
Nikita Hovratov abandoned the change 10/02/26, 07:52
I'll abandon this approach. So far it hasn't been a huge problem, but we should probably have a look into it in the future.
PageViewContentObject.php:179