Pavel Dosev

Hello Mark,

I checked the site, and the issue probably comes from the way the stylesheet is included on the page.

<link rel="stylesheet" href="https://hivefitnessbristol.co.uk/wp-content/uploads/2022/02/hivefitness-gymcatch.css">

In their documentation (p.4 below) they specify that the CSS can be included there however it needs to be wrapped in <style></style> tags:

https://www.divithemeexamples.com/add-custom-css-to-divi/

Please try using one of the methods described in their documentation and it should be working correctly.

• This reply was modified 2 years, 9 months ago by Pavel Dosev.
• This reply was modified 2 years, 9 months ago by Pavel Dosev.

Hi @pearsey,

Please open a new post for this and provide us with more details about the errors you are receiving you try to turn on the options you mentioned.

Hello @iarovuo,

Thank you for the suggestion. We will consider it being added in a future plugin release.

Regards,
Pavel Dosev

Yes, you can remove the sg_worker. It is part of the full page caching, and it is automatically created in Cloudflare upon activation.

Hello @bspaceships,

The content of the page was still cached. I purged the website’s cache and the about-us page loaded correctly.

To avoid this in the future, you can purge the cache before deactivating the plugin and/or purge the dynamic cache from Site tools after disabling it.

Hello @mickhele,

We have an option to disable images based on CSS class and image type. Unfortunately, we don’t have one for stopping it on a per-page URL basis for now.

Hi @jairoochoa,

The plugin should create those tables for all subsites when it’s activated. We are aware that it currently doesn’t add them. We are already working on a fix that we will deploy with one of the following versions of the plugin that will address that.

In the meantime, you can follow the workaround we described in the previous reply to add those database tables for your subsites.

I was able to recreate the problem through the admin page. The dynamic cache is actually working correctly for the website. Only the checker through the admin page shows a failed result.

The checker fails as additional cookies are passed by one of your website’s plugins, which conflicts with the plugin’s checker. The plugin in question is:

woocommerce-payments

You can test it by temporarily deactivating the plugin and checking the results.

Otherwise, you can disregard it as the dynamic cache is working correctly, and only the checker is showing an incorrect result. You can verify this by purging the cache and then opening your browser’s developer tools >> Network and looking for the header below. The first time the result should be MISS and refreshing the page will change it to HIT:

x-proxy-cache: HIT