Saving/publishing changes in Avada Live editor does not purge cache

Hi @kizinko,
Unfortunately, nothing can be done in that case. If Avada is not calling the default WP hooks on page update, then the plugin has no way to know that the page content has been updated and it’s time to purge the cache.

Generally when a page’s content is updated one the the following WP actions are fired:

• deleted_post
• wp_trash_post
• clean_post_cache
• edit_post

But it seems Avada is not doing that, and following the WP post update process. So, there is nothing that I can do from here. I think they should run the proper actions on content update.

Understood! Thank you for your response. I will send them a ticket asking them to fire one the following WP actions on Save in the Avada Live editor:

• clean_post_cache
• edit_post

I sent a ticket to Avada asking them to fire one or both of the following WP actions.

• clean_post_cache
• edit_post

“Both of the action hooks that you have shared are being fired when the content is saved using the live editor. I have tested and confirmed that as well. It must be something related to your cache system. We are not removing these hooks from the live editor and they are being fired just like in the back-end. We are also using the “clean_post_cache” hook to clear Avada caches in some cases.”

is there anything else you can do on your end to see why the cache may not be clearing?

Hi @kizinko,
Unfortunately no. The plugin is not removing any calls whatsoever. It simply look for the action to be fired and then do it’s work. It doesn’t have any capability to remove anything. If those actions are fired then the plugin would definitely purge cache.

Found the solution! Sharing this here in case you have anyone else with the same problem.

I did some more tests with another site that I control and figured out that the issue was with a plugin conflict between the ‘WP Rocket’ and ‘Super Page Cache for Cloudflare’ plugins. Removing the caching from WP Rocket resolves the issue. In my case, I replaced the WP Rocket plugin with the Perfmatters plugin (because it does not do any of the caching – thus no cache conflict).