Possible conflict with Divi 3.25.2 builder/theme

Hello,
Thank you for the information.
Can you please share more details? Also can you please disable W3 Total Cache settings one by one and see which one is causing the issue.

Will do Marko, but not at the moment due to time constraints. Do you suggest starting at the top or are there areas within W3 I should hone in on first to save time?

After upgraif to Divi 3.25.2 I could not use the Divi wireframe or front end builder for editing all all – non responsive. Actually thought I had lost an internet connection. OK, cleared all caches, rechecked host’s PHP version (7.1), etc. So I rolled back to the previous Divi build version (all was OK with 3.24.1), then reinstalled the latest version again (3.25.2) and went through the limited plugins I use, deactivating/ activating one-by-one withe the Divi builder. Only W3 seemed to cause the conflict.

Thank you.

Hello,
You should try with Minify. I presume it’s on Auto. Disable the Minify and see if the issue persists?

HI,
How can I unsubscribe from this thread?
Thanks!
BM

Hello @beatrizmendoza,

Just deselect “Notify me of follow-up replies via email” checkbox in the bottom of the page.

Hi Marko,
Divi handles minify. Minify is was NOT checked in W3, though radio button has Auto selected.

I cleared the W3 caches as well as my browser’s cache, but the unresponsive Divi builder persisted. So, I unchecked Page Cache in W3. Then the Divi builder worked, but that defeats the purpose of using the cache.

Hmmm.

Hello,
Have you tried updating to 3.25.3?
If so does the issue persist after that?

Yes, I updated today and the issue is still present.

Hello,
It appears that they’ve changed something in their code that causes this conflict. Have you tried reaching out to their support for assistance?

Yes, I’ve contacted Elegant Themes and we have tried various changes. Their latest reply is as follows:
——————————————–
It is definite that the plugin is conflicting with the theme – I suggest you to discuss with the W3 Cache plugin developer about this issue for a resolution.

Please let me know if there are any other questions.
———————————————

Hello @everanomad,

I spoke with the team and unfortunately, as this is the first and the at the time being the only issue of this kind, the only way that we can check this is to offer you our professional support to investigate the issue.