Website Editor Compatibility Issue

  • yashwagh1

    (@yashwagh1)


    2 days, 10 hours ago

    We are currently investigating a compatibility issue affecting the Elementor page editor on our WordPress website.

    The editor works normally before certain security configuration changes are applied. However, after these changes, Elementor stops opening, preventing us from creating or editing website pages.

    Our objective is to maintain the website’s existing design, CSS, and JavaScript functionality while ensuring that the security configuration is properly implemented.

    • This topic was modified 2 days, 10 hours ago by yashwagh1.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Mubashir Ali

    (@technifysol)

    2 days, 9 hours ago

    Hello @yashwagh1,

    Since Elementor works before the security changes and stops loading after them, one of the new security rules is almost certainly blocking something the editor needs.

    Elementor loads inside an iframe, runs inline scripts, and relies on the REST API and admin-ajax.php, so strict security settings can break it without affecting the front end.

    I suggest disabling your security rules one at a time to find which one breaks the editor. Once you identify it, adjust that rule to be compatible with Elementor rather than removing it.

    Feel free to share more details about the security rules, I would be more than happy to guide you.

    Plugin Support Milos

    (@miloss84)

    2 days, 8 hours ago

    Hi there,

    Thank you for providing the details regarding the issues you are experiencing with the Elementor page editor.

    Based on the information provided, since the Elementor editor was functioning normally prior to the recent security configuration changes, we can confidently conclude that the new security settings are the direct cause of the issue.

    To give you a bit of technical context, Elementor is a highly dynamic page builder that relies heavily on continuous background communication. When you launch the editor, it actively uses the WordPress REST API and admin-ajax.php to save and retrieve data, while also executing inline JavaScript and dynamically generating CSS. When strict security measures are applied, such as aggressive firewall rules, restricted Content Security Policies (CSP), or blocked API endpoints, they frequently interpret Elementor’s standard background processes as malicious activity. This blocks the editor’s essential scripts from loading, which prevents the interface from opening.

    We completely understand your objective to maintain the website’s existing design and functionality while ensuring the new security configuration is properly implemented. Resolving this typically requires identifying which specific rule is blocking the editor and explicitly “whitelisting” Elementor’s processes within your security plugin or server firewall.

    Unfortunately, as these specific security configurations fall outside of our scope of support, we are unable to assist further with adjusting those rules. We sincerely apologize that we cannot be of more help in directly resolving this matter.

    We highly recommend sharing this context with your system administrator, hosting provider, or the team responsible for the security updates, as they will be able to adjust the firewall or security settings to safely accommodate Elementor’s requirements.

    Thank you for your understanding.

    Best regards,

    • This reply was modified 2 days, 8 hours ago by Milos.
Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Tags