This package provides a Plone UI and default rules for managing HTTP response caching in Plone. It builds on z3c.caching, plone.caching and plone.cachepurging.
Version information:
- Version 3.x requires Plone 6.0 or later. Plone 5.2 with Python 3 should work too.
- Plone 5.2 release uses the version 2.x series.
- Earlier Plone versions: use a release from 1.x series.
plone.app.caching is shipped as a dependency of the Plone package. Caching is not enabled by default. It is highly recommended to configure caching.
When you create a default Plone site, it is available in the Site Setup. Under the Advanced header, look for the Caching control panel. There you can enable caching.
When the Caching control panel is not there, there can be various reasons for this:
- If your buildout does not load the
Plone
egg, but onlyProducts.CMFPlone
, thenplone.app.caching
is not included. - If the package is included, but you add a Plone Site using the advanced form and disable caching, then the control panel is not there.
If you want to install it in an existing Plone Site:
- Make sure the package is available in the Plone instance, by adding
plone.app.caching
orPlone
to the eggs and running buildout. - From the Plone Site Setup go to the ZMI (Zope Management Interface).
- Go to
portal_setup
, and then to the Import tab. - Select the HTTP caching support profile, perhaps easiest by id:
profile-plone.app.caching:default
. - Click 'Import all steps'.
Contributors please read the document Process for Plone core's development
Sources are at the Plone code repository hosted at Github.