Themeisle Docs

Appearance

Fix: Front-End Editor or Page Builder Keeps Reloading with Super Page Cache ​

When Super Page Cache is active, a visual editor or page builder that runs on the front end of your site can get stuck in a reload loop or fail to load entirely. This guide explains why it happens and how to fix it.

In this article

Why This Happens ​

Super Page Cache caches public pages by default. When you launch a front-end editor, Super Page Cache treats that URL as a normal public page and serves a static cached snapshot instead of letting the editor load dynamically. The editor then detects that the page is not in the expected state and reloads — often triggering the same cached response again, creating a loop.

Front-end editors, visual design tools, and page-builder previews depend on dynamic loading. Their URLs should not be served from the Cloudflare cache or the disk-based fallback cache.

Affected editors ​

This issue can affect any editor or design tool that runs on the front end of your site, including:

  • Yellow Pencil — live CSS and styling editor (loads via query parameters such as ?yellow_pencil=true or ?yp_rand=)
  • Elementor — front-end page builder preview (?elementor-preview=)
  • Divi Builder — front-end visual builder (?et_fb=1)
  • Beaver Builder — front-end page builder (?fl_builder)
  • WPBakery Page Builder (formerly Visual Composer) — front-end editing mode
  • Brizy — front-end editor
  • SiteOrigin Page Builder — front-end editing view
  • Customizer previews — any theme or plugin that opens a front-end customizer or design panel

The fix is the same regardless of which tool you use: exclude the editor's URL pattern from caching.

How to fix it ​

  1. Open the affected editor on your site and copy the URL shown in your browser's address bar — including any query string (e.g. https://example.com/my-page?yellow_pencil=true).

  2. Go to Settings > Super Page Cache and stay on the General tab.

  3. Scroll to the Prevent the Following URIs to Be Cached field.

  4. Add the editor's URI pattern on its own line. Use * as a wildcard to cover sub-paths and query variations. Common patterns:

    *yellow_pencil*
*yp_rand*
*et_fb=1*
*fl_builder*
*elementor-preview*

    If the editor loads on a dedicated path (e.g. /my-editor-page), you can also add the path directly:

    /my-editor-page*

  5. Click Save Settings.

  6. Purge your Cloudflare cache and disk cache so any already-cached version of the editor URL is cleared.

  7. Reload the editor to confirm it now opens normally.

📝 Note: These exclusions apply to both the Cloudflare CDN cache and the disk-based fallback cache.

For the full rules on URI patterns and wildcards, see Excluding URLs from Cache in Super Page Cache.

Editor still reloads after adding the exclusion ​

If the problem persists after adding the exclusion and purging the cache:

  • Check other caching plugins. Disable page caching in any other performance plugin active on your site so that only one cache is involved.
  • Check for a server-level or host-level cache. Some hosts add their own caching layer that is independent of Super Page Cache.
  • Check for a leftover Cache Everything Page Rule. Current versions of Super Page Cache use a Cloudflare Cache Rule and do not create a Page Rule. Any Cache Everything Page Rule in your account is left over from an older setup or was added manually and can keep caching the editor URL even after you add an exclusion. Go to your Cloudflare domain, open Rules → Page Rules, and delete any rule that caches all URLs without exceptions.

Still having issues? ​

If the editor still keeps reloading, contact Themeisle support for further help.

Was this helpful?