• Resolved born2excite

    (@born2excite)


    For compatibility, Jetpack needs a page rule for /wp-admin* that:

    • disables Security
    • disables Caching, apps, and performance
    • uses Cache Level Bypass

    My nameservers are pointing to Cloudflare directly and I have this page rule already in my CloudFlare setup.

    Please see: Use Jetpack and Cloudflare on your WordPress site

    When enabling Cloudflare Full Page Caching, the SG Optimizer plugin warns that all existing Page Rules in CloudFlare will be deleted. So, I cancelled and did not enable this feature.

    If Cloudflare Full Page Caching is enabled in SG Optimizer, will the SG Optimiser plugin disable CloudFlare security, Caching, apps, and performance as described in the link above?

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    SG Optimizer uses workers for full page caching. This said /wp-admin should be dynamic. We don’t have issues with jetpack users and full page caches.

    Thread Starter born2excite

    (@born2excite)

    Thanks for your help, Hristo @hristo-sg

    I now have no Cloudflare page rules after enabling Cloudflare Full Page Caching. Can you please tell me, is this what should happen?

    If I understand correctly, SG Optimizer uses workers ONLY for full page caching and does NOT use any Cloudflare page rules. Is this correct?

    Thank you

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    Yes, pagerules and workers can’t work together properly. That’s the way it should be set.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Jetpack Compatibility’ is closed to new replies.