We are seeing the same thing. The custom CSS for the page is being included in the json response from the server – so the publish action succeeds but the response is malformed so the javascript handler shows an error.
Hi @martinmoustgaard and @hutman
Thanks for opening the issue. I have tried to edit/publish some pages using Elementor v4.3.2 and Yoast SEO v28.5; however, I am not able to replicate the error or see anything in the debug log. So, can you please confirm whether you have already performed the conflict check with default theme to narrow down the issue?
Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty-Five.
Please test this on your development or staging site if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.
Also, can you confirm whether you can replicate the issue on a new site using Yoast SEO v28.5 and Elementor v4.3.2, with the default theme like Twenty Twenty-Five?
Looking forward to hearing from you.
Dear @josevarghese,
We discovered the same issue on several of our sites running Elementor v4.3.2 and Yoast SEO v28.5.
Downgrading Elementor to v4.2.x resolves the issue, as does deactivating Yoast SEO while keeping Elementor v4.3.2 (including Pro). As @hutman correctly pointed out, the root cause is a malformed JSON response returned by the server, which unexpectedly contains inline CSS.
We initially tried to replicate this on our staging environment without success. It turned out that Yoast SEO’s Indexables/SEO Optimization process is automatically disabled in non-production/staging environments, which is why staging wasn’t affected.
Based on this, we bypassed the issue on LIVE by temporarily disabling the Indexables/Optimizer via PHP:
PHP
// Temporary deactivation of Yoast SEO indexables optimizer
add_filter( 'Yoast\WP\SEO\should_index_indexables', '__return_false' );
With this snippet active on LIVE, we can save pages in the Elementor Editor again without needing to perform a full rollback or deactivate Yoast completely.
However, a proper bug fix in an upcoming release would be greatly appreciated. If left unaddressed, more sites will likely run into this issue as they attempt to run the background SEO optimizer.
My colleague discovered this reported issue which seems to be related to our problem:
https://github.com/elementor/elementor/issues/37468
Switching to External File instead of Internal Embedding seems to solve the problem for us.
Regards, Martin
I have exactly the same problem. It’s a choice between disabling Yoast or switching to external CSS, but the latter causes recurring display issues.
Do you have any other solutions?
Hi there
Thanks for the comments. I understand how frustrating it can be to encounter this issue, especially when the changes appear to be saved, but you still see a server error. Although we are unable to reproduce the issue on our end, the Elementor support team has confirmed in this thread that they are working on a fix, which is expected to be included in an upcoming version.
Temporary workaround:
Until the Elementor team releases a version containing the fix for this, they recommend temporarily rolling back Elementor to version 4.2.4. This should help avoid the ‘Server Error’ from showing while you wait for the official fix. Once a newer Elementor version containing the fix is released after ensuring it from the changelog, you can update Elementor from 4.2.4 to the latest version again.
You can find the steps to roll back Elementor to a previous version in this help article
