TYPO3 PageTSConfig clearCacheCmd scope for external content dependencies
0 reputation · 24 Feb 2020, 19:36 UTC
Configuring targeted invalidation for TYPO3 page cache entries when a custom extension modifies external data presents a boundary problem. The goal is to clear only the affected rendered pages rather than flushing the entire page cache during high-traffic periods.
In TYPO3 v12 and v13, the Cache Framework supports tag-based invalidation, and PageTSConfig offers clearCacheCmd and clearCachePages for page-ID targeted purges. However, identifying every dependent page ID for a single external record across a complex page tree remains uncertain. Additionally, no_cache prevents new caching but does not retroactively purge stale entries already stored for pages that embed the external content.
Which configuration boundary correctly links external data modifications to page cache invalidation? How should dependent page IDs be resolved when content is embedded across multiple pages? Is there a documented mechanism to register cache tags for external data so that clearCache targets only affected entries?
typo3