-
Hello!
I am having this issue: the overlay panels are not accessible when W3 Total Cache is active. I suppose it could be a setting of the cache plugin.
What could it be that interfere with the overlay and conditions pages? -
Hi there,
This is most likely caused by W3 Total Cache’s JavaScript minification. When JS files are combined or reordered, it can break the overlay panel’s trigger and open/close logic.
To narrow it down, try disabling these W3TC features one at a time (testing after each):
- JS Minification — Should be at Performance → Minify → uncheck “JS minify” (this is the most likely culprit)
- CSS Minification — same area, uncheck “CSS minify”
- Page Cache — temporarily disable to rule out stale cached markup
If disabling JS minification fixes it, you can re-enable it but add GenerateBlocks Pro’s scripts to the exclusion list instead of disabling minification entirely. The script handles to exclude would typically start with
generateblocks-pro.Let us know how that goes!
-
Hello George, and thanks for the support.
I don’t use minification, but I did use page cache. Disabling it, though, didn’t solve the issue.
-
the overlay panels are not accessible when W3 Total Cache is active
I assume this happens in the front end? Can we see a URL?
-
No, it’s happening in the backend. The overlay are visible in frontend, but I cannot edit them in any ways on the backend.
-
That’s weird, cache plugin should not affect the admin area, can you check with the cache plugin’s support?
-
That’s what happened,
I switch to WP Rocket and the issue was resolved.
When I tried, in a staging copy of the site, to switch back to w3 total cache, the overlay panels where accessible in the backend.
So, I close the ticket, maybe it was just some settings which I didn’t deactivate in the first few tries.
Thanks
- You must be logged in to reply to this topic.