Rica

Hi @slickmoos,

Thank you for sharing your site details, I understand how frustrating it can be when high CPU usage impacts the editor’s performance.

Since you’re using Elementor Pro, we’d be happy to take a closer look at this for you. Please log in to your my.elementor.com dashboard using your registered email address and submit a support ticket there. This will allow our team to investigate your site more thoroughly and provide more advanced troubleshooting.

Kind regards,

Hi @visedfaq,

I consulted with our developers and they confirmed that we are indeed experiencing a bug related to the issue you described.

This has been reported to our developers, and they’re working on implementing a fix in one of the future updates. You can also follow updates and future fixes through our official Elementor Changelog here: https://elementor.com/help/elementor-products-changelogs/

Thank you for your patience while our team works on this. We continuously strive to improve Elementor’s functionality and resolve known issues as quickly as possible.

Please don’t hesitate to reach out if you need anything further.

Kind regards,

Hi @bigdmoney,

Currently, Elementor’s core and free plugins do not include a feature for creating nested photo albums with backend management. However, you can use third-party free plugins like ‘Photo Gallery by 10Web’ or ‘Envira Gallery Lite’ from the WordPress plugin repository. These plugins let you create albums and manage photos from the backend, but advanced nesting (albums within albums) may require a premium upgrade. Always check for compatibility with Elementor before installing.

Kind regards,

Hi @majito,

To remove leftover Elementor Pro widgets and settings after deactivating and deleting the Pro version, you’ll need to manually edit your pages and remove any Pro-only widgets or features. Since the free version locks these widgets, you may see broken elements or leftover code affecting your site’s speed and appearance. Here’s what you can do:

1. Edit each affected page with Elementor and delete any Pro widgets (they’ll usually show as ‘Unavailable’ or ‘Locked’).
2. Remove any custom code or CSS related to Pro features.
3. If you have many pages, consider recreating them using only free widgets to ensure no Pro code remains.
4. After cleaning up, clear your site and browser cache.

Unfortunately, there isn’t an automatic way to reset only Pro settings while keeping free settings. You’ll need to manually remove or replace Pro elements.

Kind regards,

Hi @ahmad3275,

Thank you for sharing the details and screenshots regarding the form issue. I understand that when a wrong email is entered, an error appears saying “This field is required,” even though the field is not empty. Additionally, upon submission, another error appears: “Your submission has failed because of an error.”

Since you are using the Form widget, that indicates you have Elementor Pro installed. This gives us access to advanced form features, but for a deeper investigation of this behavior and to provide the most accurate assistance, it would be best to open a support ticket with Elementor. Our support team can examine your setup, replicate the issue, and identify why two errors are appearing simultaneously instead of a single, specific validation message for an invalid email.

Opening a ticket will ensure your issue gets proper tracking and resolution. You can also include your screenshots and details in the ticket to help speed up the investigation.

Kind regards,

Hi Luke,

Thank you for reaching out and for sharing those details.

You’re absolutely correct that when plugins update automatically especially after major updates cached files may still serve outdated resources. In setups using caching plugins such as W3 Total Cache, the cache is not always automatically flushed when another plugin like Elementor updates. As a result, previously cached CSS or Post-CSS files may still be referenced, which can lead to 404 responses and pages appearing broken until the cache is cleared.

At the moment, Elementor does regenerate its own CSS files during updates, but it does not automatically trigger cache-flush commands for third-party caching plugins. Because caching plugins manage their own caching layers (page cache, object cache, CDN, etc.), they typically require their own purge process to run after updates.

Your observation about the WP-CLI command wp w3-total-cache flush all resolving the issue aligns with this behavior, since it forces the plugin to regenerate and serve fresh cached files.

Your suggestion about Elementor triggering cache purges for major updates is definitely a thoughtful one. Since this would involve coordinating with third-party caching plugins, it would likely require dedicated integrations. If you’d like, I can also help submit this as a feature request to our product team for consideration. You can submit this as a feature request on GitHub: https://elemn.to/gh-new-feature-request

Thank you so much for your kind understanding.

Have an amazing day!

Regards,

Due to inactivity, this ticket has been closed.