Regenerate CSS & Data: Automatic Regeneration

[ghost]

Prerequisites

• I have searched for similar feature requests in both open and closed discussions and cannot find an existing request.
• I have verified that the feature is still missing from the latest stable versions of Elementor or Elementor Pro.

What problem is your feature request going to solve? Please describe..

As an agency, updating Elementor can be extremely painful. After every update, I must log into several websites to manually regenerate the Elementor CSS and Data to fix design-related issues.

Describe the solution you'd like.

After every Elementor update, automatically regenerate the Elementor CSS & Data.

There's no harm in doing this for us. The alternative is far worse.

Describe alternatives you've considered.

Not using Elementor.

Additional context

No response

Agreement

• I agree that my request may be closed without action if it doesn't meet all the requirements.

[jazir555]

Shouldn't this be the easiest functionality for Elementor to add ever? The functionality to regenerate the CSS already exists, this is essentially just automating it. Can the Elementor devs seriously not bang this out in like 2 hours? @nicholaszein

[jazir555]

@nicholaszein

Thanks, I think making a blog post is a good idea. I can't recommend looking into The Cache Purger enough since this is basically its entire purpose. There are tons of caching systems, and its exclusive focus is clearing every known cache mechanism. I think it would provide a good framework for improving Elementor's cache clearing functions, and the dev is responsive and I'm sure would be happy to collaborate with you guys.

[nicholaszein]

Hey @jazir555!

It seems I completely underestimated the time it would take to write this, and I still haven't finished the text. I think I need to take some real time on it over the weekend. Unfortunately, @wpturnedup has either blocked me or deleted his account, but I hope he can read this later.

[jazir555]

@nicholaszein

It looks like he deleted his account, it displays as "ghost" even in incognito.

It seems I completely underestimated the time it would take to write this, and I still haven't finished the text. I think I need to take some real time on it over the weekend

No worries, I've had the same where I've significantly underestimated the time required to do a thorough write up of something. I'll look forward to the post hopefully sometime this week or next week :)

[nicholaszein]

Thank you @jazir555! 🙏

I'm almost finished with the article, and after that we'll have a period of review from my colleagues. I'm hoping to publish it as an article soon, but I don't have a date yet. If it takes too long I'll share it here. I'll keep you posted! Thank you for being so kind and patient! ❤️

[jazir555]

Sure no problem! Looking forward to it!

[ghost]

It’s not a bug. It’s not going to be a feature. So, file another complaint with tech support.? I’m on it!

Even if this is not Elementor’s “fault,” it needs to be a discussion about why it’s happening, so Elementor’s customers can get to the bottom of it.

I’ll continue to say it. Elementor’s GitHub management needs to be addressed. It’s seriously flawed.

[ghost]

Purging the cache has never worked for me, when it comes to Elementor-based content/design being broken after and Elementor update.

Only the Elementor regeneration process fixes the issues.

[jazir555]

If you're using multi-layered caching that would be why. Object caching, Page caching, CDN cache, Server cache, Varnish, etc could be out of sync. I have to manually purge my nginx cache to fix the issue.

Try The Cache Purger as it will ensure all caches are purged simultaneously.

[ghost]

For fun, I just went to see what Bricks is doing in this area. They made this a feature within their builder over a year ago.

[jazir555]

Still, can you try The Cache Purger to see if it resolved the issue? I'd bet this is it, I've had the same problem with broken styles, which in my case was cache purging related.

[nicholaszein]

@wpturnedup I completely understand your frustration. All I ask is that you don't make conclusions just yet.

You seem to be upset specifically with me, and I understand that. If you ever felt mistreated in any way by me, I sincerely apologize.

Like you, I'm here because I care, but it takes time to make things right, and I cannot yet give you all the attention and care you expect and deserve. I'm not, in any way looking to antagonize and dismiss your submissions and feedback. They are actually of extreme value for mee and for the rest of the team. Like in any big company, we need to organize things, and separate them, so we can address them in an orderly fashion, otherwise we would never be able to address anything. This is why there are procedures, and places specific for each type of communication, and I am required to enforce them for the sake of everyone.

In any way, we do recognize GitHub needs more organization, and we've been working hard for quite some time to achieve this goal. Our commitment is to address each and every message, so everyone can feel heard. Unfortunately, it's not an easy task that can be solved quickly. We're just not there yet. There are quick ways to solve this, but they are not beneficial for users like yourself, and that's not our goal.