morphiaz
Forum Replies Created
-
Exactly. Now it starts regularly every 12+ hours without any edits at all from our side, logins or even WordPress or plugin updates. Its insane, and there is no way to turn it off – what makes it even more unbelievable. All caching plugins like WP Rocket or WP Fastest Cache that create HTML pages but also if you use CDN, are having this same issue by linking to CSS files, that no longer exist resulting in broken websites for every visitor.
And I actually dont know how to stop this.
@naou there is no need or a reasonable reason to rebuild CSS if nothing has changed, Elementor just has to give us the option to turn this behavior off, if we wish to. Its this simple.- This reply was modified 8 months, 1 week ago by morphiaz.
Sorry Milos, but Nicholas just stated on the facebook forum that Elementor is indeed regenerating the CSS files in /uploads/elementor/css : https://www.facebook.com/groups/Elementors/posts/24377402661958857/
We are experiencing this issue of the deletion of the CSS files in that specific folder even on websites that only have Elementor installed – no other plugins, no updates, no edits, nothing.
This ticket describes it perfectly, but now it happens even if no one makes changes to the website: https://github.com/elementor/elementor/issues/31594
Update:
Image of Nicholas Statement: https://imgur.com/a/cZBVxBF- This reply was modified 8 months, 1 week ago by morphiaz.
Look what I just found:
https://github.com/elementor/elementor/issues/31228
This means, even if Element Cache is disabled, the value is set to 24 hours, meaning that every 24 hours the cache is regenerated. I used ChatGPT Pro to inspect /plugins/elementor/modules/element-cache/module.php and this is what its saying:The “Element Cache” experiment in Elementor is set to inactive, but the code in elementor/modules/element-cache/module.php overrides that setting. Because the module defines the experiment as RELEASE_STATUS_STABLE with STATE_ACTIVE as default, it runs even when disabled, triggering clear_cache() hooks that delete CSS files in /uploads/elementor/css/. In short — the feature can’t actually be turned off, and it keeps wiping generated CSS automatically.
The experiment is marked inactive, but because of lines 41–46 and 131–178 in module.php, Elementor still runs the cache-clearing logic and wipes CSS files.Additionally, when users select “Disable” in the cache TTL setting, the value ‘disable’ is treated as non-numeric, causing Elementor to fall back to 24 hours — meaning it still flushes CSS daily.
In short, the feature cannot actually be turned off and keeps purging CSS automatically every day.
- This reply was modified 8 months, 1 week ago by morphiaz.
This is what the Elementor Admin is answering on the facebook Forum:
“This happens when you use performance optimization solutions such as cache that preload pages directly from the database instead of visiting the pages. Since you’re already caching your pages, you can change the CSS Print Method to Internal Embedding in the Elementor Settings > Performance page. This should prevent your caching plugins from preloading the pages without their styles.“
This cant be the cause, because the issue also happens on sites that have the preloading feature deactivated. Usually we generate the WPFC HTML pages by truly manually visiting the site, when changes were made.
And this doesnt explain at all why the CSS files on /wp-content/uploads/elementor/css/ are being regularly automatically deleted every 12+ hours…
His solution of adding the CSS inline is also absolutely not doable because of performance issues.I can confirm, Elementor keeps deleting / resetting CSS files on /uploads/elementor/css/ thats why WPFC previously created HTML pages cant find the CSS. Only deleting WPFC cache will force a new creation of /uploads/elementor/css/ files and link those to the new created HTML pages.
Its totally crucial to understand, why Elementor keeps deleting those CSS files even though nothing is changed on the website, otherwise it will force anyone to keep deleting the cache manually every 24-48 hours… :((We have the same problem and figured out that the CSS files under /uploads/elementor/css keep getting regenerated and/or deleted even if we dont make any changes to the website. Even though we have Elementor Caching disabled.
It happens all 24-48 hours where we have to login and regenerate the CSS files manually under Elementor > Tools > “Regenerate CSS files and cache” and delete the cache created by WP Fastest Cache.
I absolutely dont understand why Elementor needs to regenerate the CSS files, if no changes are made to the website, auto updates of plugins and WordPress itself are disabled and no one logs into the live website during fixing it and getting noticed that the website is broken again. So, why is this happening?!
EDIT:
I just figured out that the folder /uploads/elementor/css/ keeps getting emptied and thats why our Cache plugin (WPFC) and/or Cloudflare doesnt find the previous cached files in their HTML pages, they generated previously. Thats why the CSS isnt loading and thats why the pages look so awful.
Deleting the cache via Cache plugin will create a new CSS file on /uploads/elementor/css/ and a new HTML file under your cache plugin – in our case WP Fastest Cache – and thats why it fixes the broken website. Nevertheless, it is crucial to find out why Elementor is deleting the CSS files every 24-48 hours – again, on websites that dont change anything and where updates / cronjobs are disabled.I think Elementor keeps regenerating and/or deleting the CSS files under /uploads/elementor/css , thats why the HTML WPFC pages link to older files that dont exist anymore or are newer.
I just dont understand why Elementor is regenerating these files after 24/48 hours even though the website is not updated at all.
And yes, we disabled months ago the caching feature on Elementor as recommended by WPFC, turned off auto updates on all plugins and WordPress itself, disabled cronjobs, etc.- This reply was modified 8 months, 1 week ago by morphiaz.
Ok, thanks anyways and keep up the good work!
Hi Emre,
thanks for your reply.The thing is, we arent using minified files. And, actually no one makes changes to the prod website – where we even stopped all automatic WordPress and Plugin updates, WP cron jobs, etc. Unfortunately this problem started randomly around 2-3 weeks ago; before that we didnt had this problem.
Thanks and best regards,
Morphiaz@madalinungureanu done. Pls check your support tickets.
Exactly.
This partial fix is not resolving the tables being empty. It doesnt import all existing and translated slugs from wp_postmeta. This is a huge issue for someone that translated slugs manually. Actually the big issue is still there, all slugs are being completely translated – again! Existing and already existing slug translations are fully ignored.
- This reply was modified 1 year, 9 months ago by morphiaz.
Forum: Plugins
In reply to: [Cash On Pickup for WooCommerce] HTTP ERROR 500@kamran1331 do you have found some alternative to this plugin?
Any news on this issue? We get this error also with the plugin “Multiple Page Generator”
“2000: Optimization skipped because ‘X-Nitro-Disabled’ header has been detected”
Forum: Plugins
In reply to: [Beautiful Cookie Widget] Connect to existing account doesnt workI also get an error message on console, from the popup:
Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf eval blockiert (“script-src”).