Previously working now won’t let Divi builder load
-
Hello,
Several months ago, I finally found the right cocktail of Async Javascript,Autoptimize,WPRocket, and Critical CSS to speed up my site as much as possible without breaking it. Whew!Today, however, I have another issue. The Divi builder will not load. I am getting timeouts. I have changed NO settings in Autoptimize except for testing and then changing them back and I have also optimize for logged in users unchecked.
I am sure this is an Autoptimize issue as when I temporarily disable autoptimize, the problem is solved.
I moved my website to cloud hosting very recently but the builder was working fine until this morning, however, the problem seemed to occur before I updated the theme because I pulled back to a previous version of the theme and was still having the issue.
In Autoptimize I have js/jquery/jquery.js excluded optimize Javascript checked, aggregate JS checked, aggregate inline JS unchecked as it was making the cache size grow quickly, CSS optimization is all checked except for aggregate inline css and inline all CSS and I’m using the critical CSS powerup (which I note that ALL rules disappeared when I moved the site). HTML code is optimized. And I have Save aggregated script/css as static files? checked.
In Async Javascript I have it enabled async method set to defer jquery excluded, and autoptimize support turned OFF. The above settings worked well until today. If I turn autoptimize support on it breaks some of the Divi builder modules and if I exclude my theme and child theme in theme exclusions all content disappears for some posts/pages that were created with builder modules. If I don’t exclude that it works fine.
I don’t want to stop using autoptimize and I can work around this for just a bit by going into “Safe Mode” if I want to use the Divi builder…but it would be nice to solve this problem which occurred just today.
Any ideas?
The page I need help with: [log in to see the link]
- The topic ‘Previously working now won’t let Divi builder load’ is closed to new replies.