How to Fix Divi 4.0.6 Visual Builder Problems on Hosting

by | Nov 26, 2019 | Hosting, Web Design, Website Security, WordPress | 8 comments

Or, How to Stop The Divi Visual Builder Spinning Dots of Death

Here at Webidextrous, we maintain several websites for our clients who have chosen for its high-quality security and performance for WordPress and Drupal sites. We like so much that we became an agency partner.

For anyone not familiar with it, has rebuilt how hosting works from the ground up to support more robust and secure WordPress hosting. You can read my article about how Webidextrous creates high value for our clients via on their website.

Sometimes with added security and performance come a few inconveniences. About a week ago, as I was editing a few sites that use the popular Divi theme builder by Elegant Themes, I noticed that the Visual Builder was not loading. It would begin to load, and then would get stuck on the “spinning dots” preloader.

I remembered that I had recently upgraded from Divi 4.0.5 to 4.0.6. Usually, a Divi upgrade has at least one bug that can affect most sites. So, I rolled back to 4.0.5 and that solved the issue. It was definitely the Divi 4.0.6 Visual Builder that was having problems.

But that was only a temporary solution. Eventually, I’d want to upgrade to 4.0.6 and beyond. If this issue was something more permanent and systemic, I needed to know.

The Solution (For Now)

Long story short, and after lots of trial and error and testing of the Divi 4.0.6 Visual Builder, plus many rounds with the Divi community and Elegant Themes chat support later, I had a solution in hand. I share it here with you now in case you’re a agency or site owner. It may also be applicable on other hosts that choose to make the live WordPress site more secure from malware injections by making the production site 100% read-only.

  1. Add /files/et-cache/ to the filesystem.
  2. Create et-content symlink pointing to /uploads/et-cache/ in /code/wp-content/ per instructions from “Using Extensions That Assume Write Access” in the Pantheon Docs.
  3. Create /files/et-cache/ via the SFTP client.
  4. Add this to wp-config.php.
if ( ! defined( 'FS_METHOD' ) ) define( 'FS_METHOD', 'direct' );
  1. Update to Divi 4.0.6.
  2. Test and deploy.

Why Did This Happen?

In the updates to 4.0.6, the /cache/ directory that the Divi theme was writing to changed paths. The new path is now /et-cache/. That’s basically it. just needs to know the new path and map it to its writeable, secure filesystem via a symlink.

As to why this happens in general, well, it’s because as awesome as WordPress is, it was built around a hosting ecosystem that is inherently insecure.

Hosting got that way because hosting has largely been an exercise in patching together different bits of software to try to efficiently serve web pages to browsers.

So, WordPress theme and plugin developers have gotten used to being able to write pretty much whenever and whatever they want to WordPress directories. aims to change that default behavior while still accommodating the need for plugins and themes to write somewhere.

This added security results in our needing to do a little extra work to ensure the site remains stable and secure.

What’s Next?

As I discussed this in the official Facebook group for Divi, the community moderator tagged a lead developer/support person at Elegant Themes. This person stated that this issue will be addressed more directly in a forthcoming version of Divi. So, I’m assuming that means that the above workaround might not be necessary from that fix onward. But this fix will return most Divi sites on read-only WordPress sites back to normal working order and can probably remain as-is going forward.

The following two tabs change content below.
Rob Watson is an online business coach and marketing consultant. Beginning in 1996 as a self-taught web designer, he has created websites for everyone from small business owners to multi-national companies. Rob now provides one-to-one coaching for digital business website owners. He is the co-organizer of the West Orlando WordPress Meetup and a WordCamp speaker.


  1. Frank

    This also explained the Pantheon phantom /et-cache/…css etc. changes that were showing up in my Dev even if I didn’t change anything. Thanks for posting Rob! If you hear about a fix for this so I can remove this wp-config.php FS_METHOD direct business, be sure to broadcast it!

    • Rob Watson

      Will do! Glad this was helpful.

  2. Kristi W.

    Thank you! I am having the same problem with Pantheon and Divi. Thanks for sharing your solution. 🙂

  3. Robert

    This also helped us a lot in our own setup, with restricted prod file permissions. Thank you very much Rob for posting this.

    • Rob Watson

      Great! Glad this was helpful.

  4. Jeremy


    What directory are you adding /files/et-cache/ to?

    • Rob Watson

      On Pantheon, the trick is to create a symlink called et-cache in the wp-content/uploads directory and point it to /files/et-cache.


Submit a Comment

Your email address will not be published. Required fields are marked *

Pin It on Pinterest

Share This