Page caching plugins and CDN caching can serve a stale version of your product page that does not include the Chamevo customizer scripts. This makes the customizer invisible to some visitors even when it works for you.

Symptoms

• The customizer loads for logged-in admins but not for logged-out visitors.
• The customizer works after clearing the cache but stops working for new visitors.
• The customizer loads intermittently — sometimes it appears, sometimes it does not.
• After making settings changes, the old behavior persists on the frontend.

Cause 1: Full-page caching serving stale HTML

Full-page caching plugins cache the entire HTML output of the page. If a page is cached before Chamevo's scripts are enqueued, the cached version will not include them.

Fix:

1. Purge all caches in your caching plugin:
   • WP Super Cache: Settings → WP Super Cache → Delete Cache.
   • W3 Total Cache: Performance → Dashboard → Empty All Caches.
   • WP Rocket: Settings → WP Rocket → Clear Cache.
   • LiteSpeed Cache: LiteSpeed Cache → Toolbox → Purge All.
2. Exclude WooCommerce product pages from page caching. Most caching plugins have an exclusion setting:
   • Add /product/* to the "Do not cache" URL list.
   • Or exclude pages that contain the [chamevo] shortcode.
3. Exclude logged-out users from caching on product pages. The customizer loads different scripts based on the product configuration.

Cause 2: CDN caching JavaScript or CSS files

A CDN may cache old versions of Chamevo's JavaScript or CSS files after a plugin update.

Fix:

1. Purge the CDN cache after updating Chamevo.
2. In your CDN settings (Cloudflare, CloudFront, etc.), purge cached assets or set a shorter TTL for JavaScript and CSS files.
3. Some CDNs cache based on URL — after a Chamevo update, the file URLs may include a new version parameter that forces the CDN to fetch fresh files.

Cause 3: Object caching interfering with options

Object caching (Redis, Memcached) caches WordPress options and transients. If Chamevo's settings are cached, changes may not take effect immediately.

Fix:

1. Flush the object cache: