I get the message again: The definition for this element could not be located

[gnomatech]

Good morning,

It happened to me a few months ago and now it happens again.

I have deactivated all the plugins, the child theme and nothing.

Apart from the message The definition for this element could not be located, it does not load any elements either, only the templates

[Ismael]

Hello @gnomatech,

Thank you for the inquiry.

What is the current version of the theme? Please make sure that the theme is updated to the latest version, and then post the login details in the secure note so we can check the issue. Also, provide links to any related pages.

Best regards.

[prakash_s]

Hello @gnomatech,

I checked your site dashboard, you may need to disable the ModSecurity or at least whitelist the following URLs in the secure note. Please note that we use the WordPress Rest API for saving and it looks like your web host does not support it. Please ask your web host to support WordPress Rest API or whitelist the URL in the following screenshot.

Thanks

[gnomatech]

The problem has to be something else.

[Ismael]

Thank you for the update.

The error seems to be random and occurs when this database error happens:

<h1>Error al establecer una conexión con la base de datos</h1>

Please clone the site to a staging environment, switch to debug mode and enable the error logs, then post the WP and FTP details in the secure note.

– https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/

We’ll check the issue again once the staging site is ready.

Best regards.

[gnomatech]

I have activated the debug mode, which in my case is done from the hosting. It doesn’t give any message but it’s curious that it was activated and the conerstone works…

The last warning is from hours ago

[Ismael]

Thank you for the info.

The builder seems to be working correctly when we checked it again today. Unfortunately, we are not sure what that ModSecurity error means exactly, but it seems to be triggered on wp-login.

Have you tried disabling ModSecurity temporarily as suggested by @prakash_s above?