Bug #72703
openFlash message caching has changed in TYPO3 7.3
0%
Description
Flash messages rendered by EXT:fluid VH are cached and rendered from cache on page access. This was not the case before TYPO3 7.3 and is not the case when using TYPO3 6.2.
Example
User creates an object, a flash message is added and the user is redirected to the list view.
The flash message will be cached and displayed to any user until the cache of the page is flushed somehow.
Previously the page cache was disabled whenever the flash messages VH was used within a cached plugin.
Cause of this is a removed no cache config in the flash message VH, see marked line:
This behavior change is undocumented and should be considered breaking.
LinksUpdated by Riccardo De Contardi almost 8 years ago
- Status changed from New to Needs Feedback
Hi. does this issue still occur in 7.6.6 or the latest master? Thank you!
Updated by Felix Nagel almost 8 years ago
Hey, I've tested this in TYPO3 7.6.7 and 8.1.0. It's still an issue.
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Needs Feedback to New
Updated by ondro no-lastname-given over 7 years ago
- Description updated (diff)
Can confirm
same behaviour on Typo3 v 7.6.11
Updated by Felix Nagel over 7 years ago
- Description updated (diff)
@ondro no-lastname-given
Please do NOT remove useful information from the description.
Updated by Susanne Moog over 4 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Stefan Froemken about 2 years ago
As persistence.enableAutomaticCacheClearing is activated by default you only need to add TCEMAIN.clearCacheCmd = [pagesWithYourPlugin] into PageTSConfig of your storages pages.
Extbase itself contains mechanisms in CacheService to interprete this PageTSConfig and clears cache for you.
The old solution with $GLOBALS['TSFE']->no_cache = 1 will only render the page uncached, but IMO the old page cache is still valid. So if you or another visits the list page again, your new created record is still missing.