Delete Cache and Prevent CSS & Caching Errors After Pushing – Visual Theme Builder Avada, Elementor, Divi

Did you push your staging website to the production one successfully without any noticeable errors, but the website design resulted in broken or corrupted appearances like missing elements or colors?

Or does the website look good when you are logged in but look broken when you are logged out of the WordPress admin dashboard?

Does it look like some pages were correctly copied while others were not?

If you answer one of the questions above with “Yes” it’s likely that the cache has to be refreshed and deleted to show the pushed changes as expected and as shown on the staging site.

Use these steps to fix the WordPress cache:

  1. Refresh and delete the plugin cache if your site uses a caching plugin like WP Rocket, W3 Total, WP Super Cache, or any other caching plugin. Each caching plugin has a button to refresh and delete the cache. If you are unsure where to find it, read the docs of your caching plugin or ask the support of the caching plugin to learn how to do it.
  2. Refresh and delete the CDN or DNS cache if you use a service like Cloudflare.
  3. Refresh and delete the theme cache! Most visual page builder themes like Avada, Elementor, Divi or any other theme have built-in caching. After a push, you have to refresh the theme cache. Many themes have a special button for doing that. For other themes the cache will be rebuild by saving again the theme settings. If you are unsure about that google for “Theme name + delete cache” or ask your theme’s developer for support.

Updated on February 8, 2024