@tommaso76
Sorry for the delay!
Do you have any other cache plugin installed other than WP-Optimize?
Thanks,
Harshad
Thread Starter
Tom
(@tommaso76)
Hello Harshad,
two websites had a different cache plugin, but I have uninstalled it right before install your plugin.
one website is a fresh install.
I have noticed that everytime there is an auto cache refresh, the DIVI cache css file is missed/deleted.
With manual cache refresh, the DIVI css file shows up again and everything come back to work without any errors.
If you want, I can reproduce this error anytime, just let me know if you need it, thank you for your support,
best regards,
Tom
Thread Starter
Tom
(@tommaso76)
File missing is always this:
/wp-content/et-cache/427/et-core-unified-XXX-XXXXXXXXXXXX.min.css
best regards
Hi Tom,
The issue is that Divi deletes all the assets every time you save a page or post that uses the builder.
WP-Optimize only deletes parts of the cache when saving a page, to save on resources. But Divi requires purging the whole cache.
To remedy to this issue, add add_filter('wpo_purge_all_cache_on_update', '__return_true'); in your theme’s functions.php. Then every time a post is saved, the whole cache will be deleted.
This is unfortunately the only way to go about it, until Divi changes the way they manage their compiled CSS.
Best regards,
Marc.
Thread Starter
Tom
(@tommaso76)
Hello Marc,
thank you very much for your support, now everything is working fine, I will add this filter to all my websites that are using your plugin+divi.
best regards,
Tom
Hi Marc,
I tried adding the code in the child theme’s function.php file, however it is not working.
Anytime I activate WP-Optimize, the theme would lose a large part of the design, especially the images and coloring.
Is there anything you can help with on this?
Thanks,
Nadi
I had this same issue. Some cached CSS files sometimes were not loading. and causing the page to load but a lot of my styling not the be applied.
I had ‘w3 total cache’ installed but not activated. I deleted this plugin and the issue has gone away.
A strange issue…
