Project

General

Profile

Actions

Bug #97977

closed

New EXT:form request handling hides current ContentObjectRenderer

Added by Elias Häußler over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2021-04-12
Due date:
2021-04-12
% Done:

100%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.1
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

#93887 and #92406 introduced a new request handling for EXT:form forms. However, the new implementation hides the current ContentObjectRenderer instance since it always creates a new instance:

https://github.com/TYPO3/typo3/commit/9f933f2cf1c05709962c9efa2dd1951e7ad9a6a7#diff-4bbbe7629411df04b5f476caca764d500f1f55134e061c4533fe80bac36f9393R78

This no longer allows form finishers to retrieve the current content object data. For example, the current content object element ID is stored in EXT:form_consent when a new consent is created, see https://github.com/eliashaeussler/typo3-form-consent/blob/0.6.0/Classes/Domain/Factory/ConsentFactory.php#L121-L130.

Re-using the current ContentObjectRenderer via the ConfigurationManager solves the problem.


Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Bug #98336: Revert modified cache handling in form frameworkClosed2022-09-12

Actions
Follows TYPO3 Core - Bug #93887: Ext:Form Caching Determination breaking Ajax RequestNeeds FeedbackRalf Zimmermann2021-04-09

Actions
Actions

Also available in: Atom PDF