Exponential CMS caches content, templates, and configuration aggressively for performance. If your changes aren’t showing up, clearing the cache is the first thing to try. Exponential 6.x has more than one cache layer — here’s what each does and how to clear it.

Method 1: Symfony/Application Cache (Command Line)

With SSH access, from your installation directory run:

1. php bin/console cache:clear — clears the application cache.
2. Add --env=prod to clear the production environment cache specifically: php bin/console cache:clear --env=prod

Method 2: Legacy Content Cache (Command Line)

The legacy content and template caches are cleared via legacy scripts run through the console:

1. php bin/console ezpublish:legacy:script bin/php/ezcache.php --clear-all — clears all legacy caches.
2. For content-only cache: php bin/console ezpublish:legacy:script bin/php/ezcontentcache.php

Method 3: From the Legacy Admin Panel (No SSH Needed)

1. Log in to the legacy admin interface (the classic admin panel).
2. Go to Setup → Cache management.
3. Choose Clear all caches, or clear specific caches — content, template, or INI — individually.

Still Seeing Old Content?

• HTTP cache / Varnish: Exponential uses an HTTP cache layer for published pages. Publishing content purges affected pages automatically, but if a reverse proxy (Varnish/Fastly) is configured it may need purging too.
• Browser cache: hard-refresh with Ctrl+Shift+R — your browser may simply be holding the old page.
• Permissions: after clearing cache on the command line, make sure the var/ directory stays writable by the web server user or you’ll get errors.
• Cronjobs: some content (searches, notifications, workflows) updates on a schedule — if stale data persists, the cronjob may not be running: php bin/console ezpublish:legacy:script bin/php/runcronjobs.php