|
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
|
|
32.
|
|
|
Comcode page cache
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]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
|
|
34.
|
|
|
Template cache
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TEMPLATE_CACHE
|
|
35.
|
|
|
Purge the block caching.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_BLOCK_CACHE
|
|
36.
|
|
|
Statistics cache
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]STATS_CACHE
|
|
37.
|
|
|
Certain statistics, such as total downloads and bandwidth usage are calculated on-the-fly, and/or regularly calculated. If these statistics have become inaccurate, you may wish to recalculate them.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_STATS_CACHE
|
|
38.
|
|
|
Optimise/fix database tables
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]MYSQL_OPTIMISE
|
|
39.
|
|
|
This will tidy up your database tables to make your site run more smoothly.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_MYSQL_OPTIMISE
|
|
40.
|
|
|
Error found on table {1}… {2} = {3}
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TABLE_ERROR
|