If you have a big pagetree with many TypoScript +ext Templates, then the same pageTSConfig is added over and over again for each page containing an +ext template.
In our case this resulted in 4.6 mb entry in cf_fluidcontent, which in turn caused the live DB to reject the entry resulting in fatal error in the backend.
As the method name suggests, it should be enough to add this pageTSConfig only to pages where the TypoScript template has the root flag.
A workaround we successfully used was to activate compression for the cache backend cf_fluidcontent.
NamelessCoder
commented
7 years ago
If you have a big pagetree with many TypoScript +ext Templates, then the same pageTSConfig is added over and over again for each page containing an +ext template. In our case this resulted in 4.6 mb entry in cf_fluidcontent, which in turn caused the live DB to reject the entry resulting in fatal error in the backend. As the method name suggests, it should be enough to add this pageTSConfig only to pages where the TypoScript template has the root flag.
A workaround we successfully used was to activate compression for the cache backend cf_fluidcontent.