Day to day
Exclusions and monitoring
Some pages or blocks must never be served from the cache: cart, personalised content, context-sensitive third-party module. The module offers a list of URLs to exclude, a regular expression, and a list of modules or controllers to exclude entirely. A module can also be excluded on one hook only: the page stays cached, only that area reloads live (JS/AJAX, or an <esi:include> tag behind an ESI-capable proxy).
Test mode
In test mode, only administrators logged into the back office get cached pages. A badge at the bottom of each page shows whether it comes from the cache and, if not, why: controller not in the list, excluded URL or module, zero lifetime…
Personal blocks
The « Detect personal blocks » button displays the home page, a category and a product for two analysis customers created and deleted straight away, and lists the blocks that change from one to the other (name, cart…), to add in one click to the list of blocks filled in for each customer.
CDN
If the shop is served behind Cloudflare or Bunny, pages cleared from the cache are also purged from the CDN, and a full flush clears the whole zone. A button checks the zone and the API key.
The Diagnostics tab checks at a glance that the cache directory is writable, that WebP/AVIF are available, that Memcached is loaded if selected, that pages are compressed, that PrestaShop's CSS/JS smart cache is on and that the database tables exist — before you run into a problem in production.