Hi im a front end designer who used wordpress and elementor. My company has over 1000 sites hosted through wordpress. So the recent update has caused half of our sites headers to lose the Class tag and has caused other bugs. we were forced to rollback the update and make our own global fix. I was wondering if wordpress is going to address the issue or are they just going to pretend its not there. i'm not sure who to talk to about this. but we as a company can't afford another fuck up like that.
EDIT: I first would like to apologise for the misdirected anger and frustrations,is was unnecessary and uncouth of me. I am aware the company i work for is crappy, i just wasn't aware of how systemic all the issues we have are, multiple things said in the comments has made me aware of just how crummy the business practices are. I also wasn't aware of how little our developer was doing until people brought up multiple things i have never heard him do or try…ever. There is just not a lot of career opportunities near me in my field. idk when i can leave just know i am trying.
WordPress is setting the rules. It’s on Elementor to fix incompatibilities and it’s on you to wait for Elementor version that is compatible with your WP version.
Now would be a great time to move away from Elementor.
Why make global fix instead of report and wait for fix? It happens hence the very large disclaimer to backup. And more importantly you need to understand after that 1000s of sites, that Elementor is not WordPress.
This made me worry and I just quickly checked as I have custom classes on my Elementor and ran an update the other day. No problems at all. Something else is causing the problem in your setup for sure but its not one of them.
Address it to WordPress, see if they’re gonna do something about it
I still can’t believe that anyone that has created more than a handful of sites still uses elementor….
Just curious, what is your job title? I’m wondering about the income potential of being a WordPress developer and the available job opportunities in the field.
Is it a recent wordpress core update that caused it, or a recent elementor update?
I’m still building themes using bootstrap and _S and I’m happy with that.
Elementor needs to release an urgent minor update. That’s how it should be fixed.
First of all, if you’re managing 1000 sites it’s your responsibility to do compatibility tests on a sampling of sites, both in pre-release versions as well as released versions, before updating everyone else. I mean, that’s just basic hygiene.
Incidentally I disagree with others that if a WordPress updated breaks widely-used plugins or themes that it’s automatically not their fault. WordPress frequently issues patches specifically to fix incompatibilities they introduce. Sometimes days after, typically within a week.
Side note: If I was managing 1000 websites I absolutely would not update anything but test sites to new WordPress releases for at least a week. For that matter I wouldn’t recommend it even if I only had a single site. Let other people do live testing for you.
Finally, yeah, Elementor is “special” when it comes to updates. They actually do seem to be getting better (it’s amazing what multiple rounds of investments plus venture capital oversight *plus* selling millions of your software can do to enhance discipline.) But it’s still not the case that they’re on the ball when it comes to compatibility and regression testing. Not for their own releases, not for new releases of core WordPress.
And speaking of discipline and regression testing, let’s get back to your situation: what the heck are you doing letting 1000 sites get updated, with half of them crashing, without taking responsibility for your own regression testing, compatibility testing, rolling out updates rather than updating in bulk, having automated rollback solutions, etc. I mean, even if you’re only charging $10/month for maintenance, with 1,000 sites that’s almost enough to keep a part time developer on retainer to help you avoid exactly this situation.
In the same way as hospitals do not blame the power grid when the power goes out, but implement generators … If you look at the layers, WordPress core, the theme you are using, Elementor, as well as your responsibilities… the buck unfortunately stops with you. Why only some of the sites ? The fact that its erratic seems to point to something which may be outside of the tooling you are using’s default behavior.
You ‘should’ be testing on a staging server to implement any changes, especially at scale like this, you have the obligation to ensure that whatever happens is under your control.
There are tools you can implement to perform automated headless browser testing, I’ve become more of a Laravel developer in recent years, and we have Dusk which is a great way of saying “when I go to this page, I see XYZ”, that you could roll out at scale and start implementing test after test to ensure basic acceptance of how the design should appear / what elements should be present (class tag on header element is a workable test I could write for example).
This will solve the html / markup, but you will need to dig a little deeper to ensure that visual regression testing works as expected, i.e. the CSS is applying itself in a way that you would expect.
Reach out to Elementor support describing the issue you are having so they can add a fix for this on future releases.
If you’re using Elementor Pro you’ll need to contact Elementor through the Elementor site.
Upgrades should be done in a staging environment to test for issues like this. I haven’t encountered any issues with my WordPress + Elementor websites with the latest releases. The latest for WordPress was back in July so I’m not sure why you are blaming them for an issue affecting over 500+ websites. It sounds like a dev issue.
We manage over 6K website and this would never be a problem for us.
Seems like you guys are headed for Disaster at a later time.
We have implementationsamd many safeguards to prevent such things from happening, including update local testing for compatibility.
With great respect, I must tell you that the core team puts out a sequence of beta and then release-candidate releases for every release, and invites everybody to test them. If you tested a release candidate and found a defect that killed 1000 sites, and reported it, they would almost surely fix it.
There’s no magic here. Open source software needs community participation.
1000 sites? You sound like you are fumbling around in the dark. Godspeed to your customers.
Elementor is a great tool, but it’s key to remember it’s not the same as WordPress itself. Backing up is super important! I really think that in the near future, we should stick to using the Block Editor instead of Elementor.
Why was this update not tested in a DEV environment first?
I’m surprised nobody here has said that this subreddit is for [Wordpress.org](http://Wordpress.org) ( which hosts nothing ) not [Wordpress.com](http://Wordpress.com) ( which actually does WordPress hosting ). So writing here about [wordpress.com](http://wordpress.com) issues is useless.