Which actions are required to activate caching in a newly installed TYPO3 instance? (1)
The “Enable Cache” check box has to be activated during the installation.
The “Enable Cache” setting in the “Install Tool → All configuration” section has to be selected.
Nothing needs to be done. TYPO3 caching is activated by default.
The installation has to be called up once using a special URL: http://example.com/index.php?no_cache=0
Caching has to be activated in the “Caching” module in the backend.
Page generation takes a long time. Why could this be? (3)
The website is too large – TYPO3 only runs efficiently with up to 100 to 150 pages.
One or more extensions loaded disable caching.
The URL contains the parameter &no_cache=1.
The server has already been running for too long and has to be restarted to free memory.
The page contains too many COA_INT elements.
How can you measure the time taken to generate a page in the frontend? (2)
The “INFO → Rendering” module in the backend provides detailed statistics.
If the TypoScript config.debug = 1 option is set in the setup, the rendering time is written into the source text as a comment.
If the TypoScript mod.debug = 1 option is set in the Page TSconfig, the rendering is written into the source text as a comment.
The Admin Panel allows you to check rendering times.
Page rendering times are stored in the database table pages with every request.
What is cached in TYPO3? (4)
Compressed versions of .docx and .xlsx files.
The HTML output of static pages.
The thumbnails of files in the fileadmin/ directory that can be displayed in the Filelist module.
Configuration settings.
TypoScript templates.
Files that are loaded onto the server using a backend form.
Where exactly are cached pages saved by default? (2)
In the typo3temp/ directory, if the pageCacheToExternalFiles option is set.
In the typo3conf/ directory.
In the cf_cache_* tables in the database.
In the cf_cache_* fields of the respective table in the database.
In the location configured by the following key (to overwrite the default): ['SYS']['caching']['cacheConfigurations']['cache_pages']
What happens if you enter the following code in the User TSconfig? (1) options.clearCache { all = 1 pages = 1 }
All caches are deleted automatically every time a page is called.
The TYPO3 cache is activated.
It allows the administrator to delete the cache.
It allows the user to delete the cache.
All page caches are deleted.
You have written a new news entry using the “news” extension, but the article is not displayed in the frontend. What can you do in this situation? (2)
Restart the web server.
Add the following TypoScript in the root template: config.page.clearCache = true
Add the following TypoScript to the Page TSconfig of the root page: TCEMAIN.clearCacheCmd = all
Delete all files in the typo3temp/ directory.
Delete the page cache.
TYPO3 caches all pages by default. How do you deactivate this option for individual pages? (1)
That is not possible – caching can only be deactivated or activated for all pages.
By making the following entry in the TypoScript setup in a global context: config.no_cache = 1
Caching can be deactivated in the page properties.
By adding the UID of the page you do not want to cache to the pagesNoCache option in the Install Tool.
You want to cache the contents of a specific page for exactly 7 days. How can you achieve this? (2)
By installing and configuring the extension cache_expiry.
TYPO3 does not support cache expiration for specific pages - only globally.
Set caching to 7 days in the page properties.
An option is available for this purpose in the Page TSconfig (time is given in minutes): page.cacheExpires = 7*24*60
In TypoScript setup, use the option (time is given in seconds): config.cache_period = 604800
