Bug #90162
openFlexform caching problems with (nested) site config
0%
Description
I encountered multiple issues with updated flexform data having no effect in FE.
While developing a plugin with a flexform, changes made to the flexform data weren't reflected in the FE output. After debugging the application and checking the saved flexform data in tt_content, it had to be some kind of caching problem. I tried "Flush frontend caches": no effect. I tried "Clear all caches": no effect. I then tried "Flush TYPO3 and PHP Cache" in Admin Tools/Maintenance: finally, the changed data was showing in the FE.
I noticed the same flexform had no problems with updating values on a different page, where the same plugin was in use. But that page was within the default site. The page with the flexform caching problems had its own site config, nested within the main/default site. When I removed the site config for the nested site (so that the page was part of the main site config), all updating problems were gone. A simple reload of the page in the FE was enough, no cache clearing required at all.
To sum up:- There seems to be some caching problem with flexform data and nested site configs
- "Flush TYPO3 and PHP Cache" in Admin Tools/Maintenance doesn't do the same thing as "Clear all caches" (even though it says so: "This utility is also present in TYPO3’s backend: Top Bar > Clear Cache > Flush all caches")
This is obviously a serious problem, since regular BE users might have the right to change flexform data, but can't access the cache clearing in Maintenance.
Updated by Benni Mack about 4 years ago
- Status changed from New to Needs Feedback
Hey Michael,
thanks for you report. This sounds very interesting - can you let us know if this happens ONLY with flexforms or with regular content within nested sites as well?
Thanks.
Benni.
Updated by Michael Stopp about 4 years ago
It seems to happen with regular content as well. I could reproduce it with a content element of type 'Text & Images'.
I had a very limited use case (just a single plugin with a large flexform as page content) when I ran into this problem, so I didn't notice the more fundamental nature of the problem...
Updated by Christian Kuhn about 2 years ago
- Status changed from Needs Feedback to New