Plan which cache each change needs
No change is called broken when it is only cached.
Life cycle: Plan, example 14 of 35. Worked out on the Fit & Healthy site of Exponential 6.0.15+.
Contents
In the Layouts editor
- Publishing in the Layouts editor and publishing content refreshed the pages by itself on the test copy.
Which cache
- Settings read in templates (menus): Template & content. New templates: Template & content. Stylesheets: Template & content (packed files). Command-line layout imports: none (an import with
--publishpurges the page cache itself).
Which to choose
Keep Caches after a change with the plan.
Check
- The team knows the Clear cache box and
./console exp:cache clear --tag=template,content.
Related pages
- Caches after a change
- Plan examples, every page
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.