-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
β π Console shows missing CSS Stylesheet for the Loop Item template - [ED-13534] #24959
Comments
Hi @samuelmente, thank you for sharing your feedback! π Please Regenerate Elementor's CSS & Data in your WordPress Dashboard > Kind regards |
Hi @nicholaszein |
Thank you for confirming this @samuelmente! π I've escalated this to our QA Team and we will work on a fix if validated. Best regards! |
I'm having the exact same issues with the latest version 3.19.0 on all my websites, which were working fine before updating. A rollback to 3.18.3. fixed the issue as a workaround. |
+1 Same results on my end. |
+1 |
Hello everyone, just an update: While the console will show there are missing styles for Loop Item templates, these are still being loaded but with another file name. So this shouldn't affect anything on your websites and you can update to 3.19.0 securely without any worries. A fix is on it's way! Thank you for sharing your feedback! π |
@nicholaszein Missing css files isn't the only issue as the performance with the latest update is so bad, that all pages with loop or slide items are getting really slow. I doubt the latest Wordpress core update will fix that. |
@nicholaszein It is definitely not only the issue of it being displayed in the console. It also directly affects performance, as the page will wait to continue running js and loading some elements until the stylesheet is loaded (or in this case until the server returns 404) which in case of my test pages can take >1 second. Following is a screenshot for reference. During that "waiting" time all Entrance Animations for example will not run potentially adding a long delay until elements are visible. |
in my case i lost 4s big bug |
+1 page seems suddenly to load forever |
I can confirm the 404 loop error on multiple sites. Seems to occur in 3.18.3 as well. |
When? This is pretty bad as it's slowing down the rendering of pages. |
As of today with the release of Elementor Pro 3.19.1 it seems to be fixed. |
Good job turning this one Elementor team. |
Is nobody else concerned that this wasn't picked up in testing and then took a week to fix with a few lines of code? I mean bugs happen, but it literally took a glance at either the browser console or network tab on a vanilla Elementor/pro install which uses a loop template. |
For me, the Elementor Pro 3.19.1 update solved the problem. Thank you for your prompt work! |
I use the "Dynamic Template Grid" widget from "Unlimited Elements for Elementor" in the Pro version to display loop items. The update to Elementor Pro version 3.19.1 did not solve the problem of large gaps between the loop items or the missing stylesheet. I have restored Elementor Pro version 3.18.3. There are no problems with this version. |
@lachermeierm If you haven't already, you should contact the authors of that plugin with your findings. They may need to make changes to make it compatible with 3.19. |
Hello everyone! We have great news! π π’ We're happy to announce that the issue you raised was resolved in Elementor Core and Pro v3.19.1! π₯³β Feel free to check it out and update both plugins to the new version!
Cheers π₯ |
Please reach out to Unlimited Elements and ask them to fix your issue. |
Prerequisites
Description
Since the Update to Elementor Pro 3.19.0, for loops 2 css-Sheets are included for each loop:
loop-123.css is properly loaded while post-123.css can't be found (404).
I think that you added a change with the update to include the css for loops as "loop-id.css" instead of "post-id.css" to better differentiate them, but somewhere in the code probably forgot to remove the call for the old naming scheme.
Steps to reproduce
Expected behavior
Isolating the problem
Elementor System Info
Click to reveal
Agreement
The text was updated successfully, but these errors were encountered: