When I enable the W3 Total Cache plugin the ability to edit pages with Beaver Builder breaks, I can open the editor and make changes to the various modules but when I click “Save & Finish” or “Save & Preview” the update bar appears but freezes and never completes. If I click cancel, nothing happens. Disabling W3 Total Cache immediately resolves the issue until it is enabled again.
I’m sure the answer is simple but I found nothing on the support forum or documentation, so hopefully you can help me to resolve this issue.
Hi,
I just had the same issue last week with BulletProof Security and Billy was very responsive and helpful with this. Deactivating the plugin (or changing some of it’s parameters) solves the issue.
During the weekend I experienced the same with W3 Total Cache. The same happens with WP Super Cache. It all depends on JS indeed. Obviously minifying put’s the BB neded JS files in the wrong place.
Perhaps you could add this info to your observations the coming week, Billy.
There aren’t any known issues at the moment with W3 Total Cache. If you are having issues, would you mind shedding more light on what might be going on in your situation?
The moment I activate minifying JS, Billy, the accordion doesn’t work anymore and the BB interface behaves strange. If I uncheck that and leave the rest of W3 Total Cache alone everything works fine.
Meanwhile I’m testing Quick Cache from the guys who made S2Member. This works without any problem together with BB and is nearly as fast as W3 Total Cache on my site. But this site only has 40 pages and just a few posts. So Quick Cache might no be as good on typical blogs. Subject to test.
Basically, Page Builder is not usable (for me) if W3 Total Cache is active. On a couple sites, I can’t open up Page Builder at all. On another site I can open it up, make changes, but cannot save.
As soon as I disable W3 Total Cache everything works perfectly again.
I’d be happy to provide access if you’d like to try and troublehsoot.
I did not read every thread about W3C and BB but in my case I found out that for example making a gallery crippled the layout in a way I could not get to the media.
Disabling the minify settings in W3C resolved the conflict. The rest of the caching system is still doing it’s job as advertised.
That’s what I said at February 9, 2015 at 10:47 am. W3 Total Cache works fine with Beaver Builder as long as minifying is deactivated. But that’s not the goal because minifying is a very important part of site speed and rating.
Billy, we had that conversation already with regards to Bulletproof. Did you find out anything meanwhile?
Sorry. I already confessed I did not read all the posts. I was looking for an answer after a lot of switching plugins.
This works for me:
Disable from logged in users in W3C works fine. But that seems to be a bit to wide, since every logged in user on a site with a lot of logged in users will get the penalty.
Adding /?fl_builder to the list of Never minify the following pages: is also doing the trick. I don’t know yet how robust this setting is but on all the pages I want to edit it seems to work.
Unfortunately, I did some testing and it appears that W3’s JavaScript minification is breaking the WordPress editor on the front-end which is causing an error and bringing down the entire builder. There’s not much we can do about that as that code is out of our hands.
It also looks like there is an issue with the core WordPress media uploader and W3 minification on the front-end. I’ve filed a ticket here to hopefully get some traction on this issue.
However
I did some digging in W3’s code and it looks like we can force it to not minify while the builder is in edit mode by defining the constant DONOTMINIFY. This will be available in the next update and should solve many of the issues people are having with W3 and BB.
Tnx Justin, for taking the time to analyze. It’s like in real life: Some things you can influence and some not. So we focus on the things we can change. Not minifying of course is a solution. From my experience I can tell that Quick Cache is doing a good job as well and is not conflicting with BB so far in my installations.
You’re welcome, Leo. We’ve actually started using QuickCache for clients as well. W3 is great and can do amazing things but we find it’s a bit overkill for smaller sites.
I stopped using W3C. It’s the most complete but also most complex plugin. I experimented wit a few other other plugins but no one worked as good as W3C. Until I discovered the (paid) plugin WP-Rocket (http://wp-rocket.me)
I don’t want to get everybody paying for this plugin but it’s dead easy to configure and works like no other plugin. And it is very active supported and developed.
And: it works very well wit BeaverBuilder. I had no issues whatsoever.
I’m not sure if the issue is as much with W3C specifically or minification. I’m using W3C but with minification turned off, using a different plugin for that. Beaver Builder is broken if that plugin is activated.
So basically, if Beaver Builder’s scripts get minified then it breaks. I’m not sure if that’s on Beaver Builder though since minification can cause issues if implemented incorrectly. And there’s usually a way of excluding.
So question, when js is BB loading in the page builder?
