Server error (500 error)

Hello Johan,

We are sorry about the issue with saving Elementor pages. On checking your site, it has the latest version (17.3) of the Yoast SEO plugin.

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.

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.

Can you please inform us of the results, so we can help you figure out what the problem is? We look forward to hearing from you.

Hi,

Yesterday I did all the appropiate debugging. Change theme, deactivate all plugins, activate plugins one-by-one, enable wp_debug in config.php, upgraded php version to 7.4., upgraded memory limit to 1024M.

If I disable Yoast or install 1.4.8.1 the problem is gone. All newer versions of Yoast result in the same problem/issue. So my conclusion is that the change in Yoast (from 14.9) effects the loading of the Elementor editor.

Luckily there is a work-around by changing the setting of Elementor to load the editor in safe mode. It loads the backend without theme/plugins.

Hey Johan,

Thank you for your elaborate reply and testing. Sorry to hear you haven’t found any cause (yet).

I tried to replicate any saving error in Elementor pages with Elementor 3.4.5, Yoast SEO 17.3 and WordPress 5.8.1, but no dice. I can simply add/create/edit Elementor pages. I tried this on a local by flywheel site environment on apache and nginx, as well as a live site I have running with Yoast & Elementor both the latest versions.

As you speak of an error 500, that means that there is a fatal PHP error. This should be logged though in your PHP/server logs though, unless something isn’t working in your logging as well. If you use the debugging lines found on https://www.ads-software.com/support/article/debugging-in-wordpress/ to point the logging to debug.log, does anything get stored?

Apart from the log files – are you able to find any error in the browser console at the moment when you try to save? It could be that the browser console or even in the network tab gives more information to find the culprit.

Hey Jeroen,

If the page becomes large (lots of sections, columns, widgets, widgets from third parties) it throws an error and I can’t save the changes.
Smaller pages – no problemo! So, replicating the issue on a different stack – it’s hard.

Yoast seems to have a big impact on loading large Elementor pages. Maybe you could pass this info to the developers.

Met groet,
Johan

Hope Yoast 17.4 is better.
Just read the changelog.

@johan-stam Thanks for your reply, and pease let us know if the changes implemented in the 17.4 release has a positive impact on your issue.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.