#93887Ext:Form Caching Determination breaking Ajax Request
Description
With Typo3 10.4.14 was a new method “isRenderedCached()” introduced in TYPO3\CMS\Form\Domain\Runtime. This method returns true on:
“$contentObject->getUserObjectType() === ContentObjectRenderer::OBJECTTYPE_USER”
We use an Ajax call for our Form Requests and the Extension helhum/typoscript_rendering for rendering a typoscript path. This extension uses a USER object. The above comparison statement determinates therefore our call as cached while it is not.
While this might be an issue with the helhum/typoscript_rendering extension and needs a change there, we find that comparison suspicious. Can anyone please explain why a USER object should always be cached?
Reviews 8
- 10.4 70513[BUGFIX] Ensure uncached forms in case of POST requests
- main 70460[BUGFIX] Ensure uncached forms in case of POST requests
- 11.5 75447[BUGFIX] Do not hide ContentObjectRenderer on form rendering
- main 75247[BUGFIX] Do not hide ContentObjectRenderer on form rendering
- 10.4 75326[TASK] Add functional tests to test the caching behavior of ext:form
- 11.5 75013[BUGFIX] Ensure uncached forms in case of POST requests
- 11.5 75082[TASK] Add functional tests to test the caching behavior of ext:form
- main 73722[TASK] Add functional tests to test the caching behavior of ext:form
Related issues 6
- Feature #91419Disable caching on a per form basis
- Bug #98084Honeypot not working anymore?
- Bug #98222Inconsistent form rendering after #93887
- Bug #98336Revert modified cache handling in form framework
- Bug #97977New EXT:form request handling hides current ContentObjectRenderer
- Bug #98023custom prototypes cannot be applied