Overview
An Overview of how caching works within SugarCRM
What It Does
Much of the user interface is built dynamically using templates from metadata and language string files. Sugar implements a file caching mechanism to improve the performance of the system by reducing the number of static metadata and language files that need to be resolved at runtime. This directory stores the cached template and language string files.
Where is the Cache?
In a stock instance, the cache is located in the sugar root ‘cache’ directory. If you would like to move this directory to a new location, you can update the config parameter ‘cache_dir’ in your config.php or config_override.php to meet your needs.
Developer Mode
To prevent caching while developing, a developer may opt to turn on developer mode.
Admin > System Settings > Advanced > Developer Mode
This is especially helpful when you are directly altering templates, metadata, or language files. The system automatically refreshes the file cache. Make sure to deactivate developer mode after completing customizations because this mode degrades system performance.