|
|
12.
|
|
|
The website software associates on-disk files (stored in the <tt>uploads/</tt> subdirectories) with content. This tool will list all the files the website software believes are on-disk, but not actually used. Please do not delete them without giving each individual consideration: it is possible that someone has manually placed them (or an unofficial addon has made them) and referenced them in a non-standard way.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_ORPHANED_UPLOADS
|
|
|
13.
|
|
|
This tool is the opposite to the orphaned-uploads tool: it will find references to on-disk files for content where the files do not actually exist. The database records of the content will be detailed in a coded format, from which you can determine the resource type and the resource ID. This tool will also test non-local URLs for ‘404’ errors.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_BROKEN_URLS
|
|
|
18.
|
|
|
Choose what you would like to clean-up from the list. It is advised to only tick (check) the options you need – indiscriminately running all tools will not likely result in any net benefit, and will cause a temporary load-increase on your server.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CACHES_PAGE
|
|
|
19.
|
|
|
You may wish to rebuild caches after editing content outside the official website interfaces, or if cache files are lost or corrupt – however you should not ever need to rebuild caches if you have only been administering the website normally.<br /><br />If you regularly make manual changes to files outside website interfaces, you may find it useful to know that you can automatically regenerate any cache used in the generation of a page by clicking the web browser refresh button whilst holding the <tt>ctrl</tt>+<tt>alt</tt>+<tt>shift</tt> keys down together.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CACHES_PAGE_CACHES
|
|
|
21.
|
|
|
De-cachers
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CACHES_PAGE_EXP_CACHES
|
|
|
26.
|
|
|
Comcode fields are cached in a pre-calculated format which is a cross between Comcode and <acronym title="HyperText Markup Language">HTML</acronym>. In theory this should mean that changes to site configuration shouldn't damage the validity, but some changes may do so.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_COMCODE_CACHE
|
|
|
29.
|
|
|
Any mapping in the theme image mapping which is not a specially uploaded user-image. This will allow re-searching for URLs for theme images that have not been explicitly overridden in the image manager.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_THEME_IMAGES_CACHE
|
|
|
31.
|
|
|
Enable Comcode page caching. It is highly recommended this option is left on for a production website, but whilst you are setting up a site you may wish to disable it so you can directly edit Comcode pages as text files on the server.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CONFIG_OPTION_is_on_comcode_page_cache
|
|
|
33.
|
|
|
Enable template caching. If you are editing templates manually (without the aid of the website software) and do not want to manually empty the cache for every change, this option should be turned off.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CONFIG_OPTION_is_on_template_cache
|
