...
- Template cache. For better front-end performance, PrestaShop caches your HTML pages.
- Never compile cache. Only enable this if you are making edits theme, and need to see your changes every time you reload your page.
- Compile cache if templates are updated. PrestaShop is able to see when a theme file has changed, but this might not always work as expected.
- Force Compile. The normal behavior: HTML pages are compiled and cached, even if the theme has changed.
- Cache. This option makes it possible for you to disable all file caches, and not just the one pertaining to template files. Only disable this if you debugging a theme or a module for PrestaShop. Otherwise, you should leave it enabled.
- Debug console. New in 1.5. PrestaShop enables you to display the Smarty Debug Console, which gives you valuable information on a template page. Read more about it at http://www.smarty.net/docsv2/en/chapter.debugging.console.tpl. Note that the console opens in a pop-up window: make sure to make your browser allow them for your shop's domain name. Because the debugging console might display private information, make sure only to use it when in maintenance mode, or with the URL parameter.
- Do not open console. The default setting. No one sees the console, not even you.
- Open console with URL parameter (SMARTY_DEBUG). The console is only displayed if you add
?SMARTY_DEBUGat the end of the URL. This is great, but once your tests are done, do revert to the default setting, as this "trick" is known and some hackers could make use of it. - Always open console. The "full on" setting. Everyone who has access to your shop can see the console. Therefore, keep it for maintenance sessions.
| Note |
|---|
Because the debugging console might display private information, make sure to only enable it when in maintenance mode. Do not keep it enable on a production store. |
Optional features
New in 1.5.
...