Enrique Arróniz
Forum Replies Created
-
Hi,
Since you are an Elementor Pro user, you can open a support ticket at my.elementor.com
ref: https://elementor.com/help/how-to-submit-a-support-ticket/I’d also suggest you check out Elementor Community Group on Facebook. We have created it to connect Elementor users together and share knowledge, Global Elementor Community.
WordPress.org rules state that commercial products are not supported here.
Hi there,
Thank you for your patience while we diagnosed the loading issues on your site.
Our analysis of the server logs shows that the Elementor editor is currently unable to load because the server is running out of memory during the “handshake” process. This has caused some of the Elementor core files to become inaccessible or corrupted during the recent updates.
What is needed:
1.- Clear the website’s temporary cache (using a cache plugin or your web hosting provider can do that).
2.- Perform a clean re-installation of the Elementor plugin files to ensure no components are missing.Next Steps:
We recommend reaching out to your webmaster or web hosting provider to ensure your server has enough “headroom” for these tasks.
Add these lines to your wp-config.php file:
/** WordPress memory soft limit*/
define(‘WP_MEMORY_LIMIT’, ‘512M’);/** WordPress memory hard Limit */
define(‘WP_MAX_MEMORY_LIMIT’, ‘512M’);I really hope this solution makes things easier for you!
Kind regards,
Enrique Arróniz.
Thank you for reporting the PHP notices appearing after your recent update.
WordPress 6.9.1 introduced a stricter way of checking website scripts. Because of this change, the version of Elementor currently on your site is trying to load its editor components in an order that WordPress now flags as “incorrect.” This is why you see the notices specifically regarding
elementor-v2-editor.This is a known compatibility gap between WP 6.9.1 and Elementor versions older than 3.35.1.
Recommended Steps:
Update Elementor: Please update Elementor Core to v3.35.1 or higher. These versions contain the specific fix for this WordPress change.
Clear Cache: After updating, go to Elementor > Editor > Tools, click on Clear Files & Data, and clear/regenerate any server-level caching.
It is also advised to log out of your website, clear your browser’s cache, and log in again.
If you cannot update immediately, you can temporarily resolve the “Loading” issue by going to Elementor > Editor > Settings > Advanced and setting “Switch Editor Loader Method” to Enable.
While your cloning script successfully moves the Elementor data, it bypasses the “Activation” sequence required by the Elementor Kits Manager.
In Elementor, a Kit is not just a database entry; it is a system-wide configuration that must be “registered.” Moving forward, your scripts must explicitly trigger the set_active_kit method to ensure the editor recognizes the styles and settings immediately upon cloning.
A note for your webmaster or web hosting provider:
—–
Hosting Provider Note
Attention: System Administrator / DevOps When running programmatic migrations, ensure the PHP process has sufficient memory_limit (256M+) to handle Elementor’s CSS regeneration.After database search-and-replace, the following command/script must be executed to register the Kit: \Elementor\Plugin::$instance->kits_manager->set_active_kit( $new_kit_id ); This ensures wp-content/uploads/elementor/css/global.css is correctly generated for the new environment.
—–