Breaking: #82878 - Removed field “no_cache” in database table “pages”¶
See Issue #82878
The database field
pages.no_cache has been removed from TYPO3 Core. This option allowed editors
to completely disable all frontend caching functionality of a specific page.
Having this option previously set on a specific page will now use caching when rendering this page.
Existing installations having this option set in their database.
This can easily be checked via a SQL query:
SELECT uid, pid, title, FROM pages WHERE deleted=0
AND pid>=0 AND no_cache=1;.
The “no cache” option which should be avoided or otherwise used carefully by integrators via
config.no_cache = 1 in conjunction with a condition on a per-page basis.
However, it is better to set a very low cache timeout, or investigate why caching is configured wrongly in an extension or plugin.
Also, use the following SQL query to quickly check if your installation is even using this option at all. If not, it is not necessary to migrate anything:
SELECT uid,title FROM pages WHERE no_cache = 1