In order to speed up the process of adaptation and dynamic generation MWT caches the generated pages and content.
It is therefore important to know when caching occurs and when to pruge the caches.
- Images: all images processed and rescaled by the Image Server
are cached, this also includes external images. The name of the images in the cache is a MD5 hash of their URL, this means that
the only situation when it is necessary to purge the images cache is when an image is changed but its URL is unchanged.
- Pages: all generated pages are cached. A cached page expires when the code of one if its internal
widget or the CSS changes.
- Taglibs:
After a page has been processed by the taglib engine, the generated file is cached so that taglibs are expanded only once. If you
modify the implementation of taglibs but you dont change the widgets code, then you need to purge the taglibs cache in order to
see the changes.
- CSS:
Dynamic style sheet generation produces once CSS file for each screen size and theme. When the structure of the theme changes or
when a change is made on the theme's template.css file all the CSS associated to that theme in the cache
are automatically purged.
You can manage MWT's caches in the Administration panel.