passlee.com runs a three-layer caching stack: FastPixel caches full-page HTML, ShortPixel CDN caches static assets, and Avada compiles its own fusion-styles CSS separately. All three must be understood together when diagnosing why a change isn’t appearing live.
Known issue and fix
The staging environment’s FastPixel advanced-cache.php had hardcoded paths pointing at the production directory – a leftover artifact from cloning production to create staging. This was fixed by resolving paths dynamically via WP_CONTENT_DIR on both staging and production, rather than hardcoding either path.
Operational notes
- Correct FastPixel purge method: FASTPIXELFASTPIXEL_Backend_Cache::get_instance()->purge_all().
- Cached files live under the fastpixel-website-accelerator directory; there is a separate index_local.html specifically for local-cache.
- The ShortPixel CDN’s cdn_purge_version integer should never be bumped manually – doing so causes 404s on CDN-proxied CSS URLs.