Page Builders Integration

ZiziCache provides automatic compatibility for common page builders and WordPress FSE. It focuses on safe caching and optimization around editor sessions and template updates.

What it does

• Bypasses HTML optimization when a builder editor/preview is detected.
• Bypasses page caching when known builder query parameters are present.
• Purges and preloads cache when builder templates (specific post types) are saved and published.
• Adds safe exclusions:
  • JS delay exclusions for Elementor frontend scripts.
  • CSS minify exclusion for GeneratePress off‑canvas/offside menu CSS.

Editor detection (examples)

The bypass list includes common parameters such as elementor-preview, bricks, et_fb, fl_builder, ct_builder, breakdance, vc_editable, brizy-edit, and WordPress FSE parameters. The full list can be extended via zizi_cache_page_builder_params.

Template post types monitored

Cache purge/preload is triggered for template post types from builders such as Elementor, Divi, Bricks, Breakdance, Oxygen, Beaver Builder, WPBakery/Visual Composer, Thrive Architect, Brizy, GeneratePress, Astra, OceanWP, Avada, and WordPress FSE (wp_template, wp_template_part, wp_block).

Configuration

• No dedicated UI; the integration is automatic when the plugin is active.
• Extend or override detection:
  • zizi_cache_page_builder_params — add query parameters that should bypass caching.
  • zizi_cache_page_builder_detection — override the detection result.

How to verify

1. Open a builder editor/preview URL and confirm x-zizi-cache-cache is BYPASS or no cache file is created.
2. Save a builder template and confirm its URL is purged (and preloaded if preloading is enabled).

Disable the integration (optional)

add_filter('zizi_cache_disabled_integrations', function($integrations) {
    $integrations[] = ZiziCachePluginsIntegrationsPageBuilders::class;
    return $integrations;
});