Hi,
@vmarko
It seems there was something wrong with the file I attached.
Here is my conf screenshot.
Did you find something in the meantime?
@schwipps Do you still run in to this issue if you don’t regenerate Elementor’s CSS as part of your deployment process? For us, this seems to resolve the issue.
Also, Elementor’s CSS is cleared automatically when an Elementor database upgrade happens. This is probably why we see issues more with major Elementor version updates. Perhaps by clearing the CSS manually, and also triggering the database update, this causes issues.
Anyway, I have stopped manually triggering the CSS regeneration and so far so good, except for one issue which is that stylesheets are linked to the bottom of the document the first time the page is rendered. I’m hoping Elementor will fix that.
@jamieburchell
Unless it’s done by the other actions, we don’t regenerate Elementor’s CSS during our deployment process.
By the way, when I run into this issue after a deployement, on specific pagees, and clear all W3TC caches to get rid of these brokenp ages, I still run into the same issues on different pages.
I barely trigger (Elementor’s) CSS regeneration manually since it almost never solve any CSS issue I encounter.
Hi there,
Here’s a surprizing update: W3 Total Cache is officially not be compatible with Elementor anymore.
https://elementor.com/help/elementor-hosted-incompatible-plugins/
>> My bad: this is only for Elementor hosted websites. So I believe those for which Elementor provides the hosting solution. Forget it.
@schwipps Happy New Year 😀
Unless it’s done by the other actions, we don’t regenerate Elementor’s CSS during our deployment process.
Elementor’s CSS is cleared (regenerated) automatically when an Elementor database upgrade happens.
I’m still running in to this issue.
