Can’t Edit Pages after Installing Yoast

Hi @hidethegarlic,

Thank you for reaching out. We are sorry you are experiencing this.

An error 500 is most likely a conflict between plugins or themes. Can you confirm that all other plugins, themes, and WordPress is up to date? If not, please update and check if the issue persists.

If it does, we would like to know more details. An error 500 is a PHP fatal error and this should be logged in your server log files. Can you check if you have access to them to see the exact error? If you don’t have access, please ask your host provider to get those for you. If you have the error(s), please get back to us with the information.

Thanks.

Thanks, this is the error message that appeared when I press edit on one of my pages.

There has been a critical error on your website. Please check your site admin email inbox for instructions.

I just asked my hosts to see the error log so I should get that soon.

I have the same Error.
I have found a Workaround by deactivating the Block Editor.
Just install
Classic WordPress Editor
Maybe it will work for you until the Bug is fixed.

The error in the log is

mmap() failed: [12] Cannot allocate memory

I just installed classic editor and issue has gone away. Thanks Joergschoel! Hopefully the error can be solved for others.

@joergschoel @hidethegarlic

Just to clarify, do you have the latest version of WordPress 5.4.1 and Yoast SEO for WordPress 14.3? Also, were you using the Block Editor plugin specifically?

Just to be sure, we would like to rule out any plugin or theme conflicts that may occur that could have caused these errors. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

As we can imagine that 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.

Hello Michael,
in my case it is a complete new WP-Project. Just a few pages with placeholder content. I even try to reinstall from zero. If Yoast is added everything seems ok. But with adding more Plugins the Internal 500 pops up in Admin mode while editing pages or posts.
Yes it seems that the other plugins cause the error. But I tryed to exchange all plugins, but not Yoast and the error comes again.

Here a copy of my WP Settings. Hope you can find the Bug.

### wp-core ###
version: 5.4.2
permalink: /%postname%/
https_status: true

### wp-paths-sizes ###
wordpress_size: 45,08 MB (47271500 bytes)
uploads_size: 31,95 MB (33503612 bytes)
themes_size: 2,88 MB (3016101 bytes)
plugins_size: 76,19 MB (79892523 bytes)
database_size: 2,30 MB (2408448 bytes)
total_size: 158,40 MB (166092184 bytes)

### wp-active-theme ###

name: Twenty Seventeen (twentyseventeen)
version: 2.3

### wp-plugins-active (10) ###

Antispam Bee: version: 2.9.2, author: pluginkollektiv
Broken Link Checker: version: 1.11.13, author: WPMU DEV
Classic Editor: version: 1.5, author: WordPress Contributors
Complianz | GDPR/CCPA Cookie Consent: version: 4.6.3, author: RogierLankhorst, Complianz
Contact Form 7: version: 5.1.9, author: Takayuki Miyoshi
Limit Login Attempts Reloaded: version: 2.13.0, author: WPChef
OMGF: version: 3.7.0, author: Daan van den Bergh
Query Monitor: version: 3.6.0, author: John Blackbourn
Statify: version: 1.7.1, author: pluginkollektiv
Yoast SEO: version: 14.3, author: Team Yoast

### wp-plugins-inactive (3) ###

UpdraftPlus – Backup/Restore: version: 1.16.25, author: UpdraftPlus.Com, DavidAnderson
W3 Total Cache: version: 0.14.1, author: BoldGrid

### wp-server ###
server_architecture: Linux 4.4.0-ui20086.041-uiabi1-infong-amd64 x86_64
httpd_software: Apache
php_version: 7.4.6 64bit
php_sapi: cgi-fcgi
max_input_variables: 1000
time_limit: 30
memory_limit: 300M
max_input_time: -1
upload_max_size: 67108864
php_post_max_size: 67108864
curl_version: 7.38.0 OpenSSL/1.0.1t
suhosin: false
imagick_availability: false
htaccess_extra_rules: true

### wp-constants ###
WP_MAX_MEMORY_LIMIT: 300M
WP_DEBUG: true
WP_DEBUG_LOG: true
DB_CHARSET: utf8

The “mmap() failed: [12] Cannot allocate memory” issue occurs when the server is out of swap memory. Therefore, can you please try increasing the relevant memory by following the steps given here?

If the issue persists, we recommend you please reach out to your web hosting provider and ask them to increase the memory limit for your server and that shall fix the issue for you.

Hello Md Mazedul,
I have allready increased the memory limit to 256M. In WP and in PHP. Same Error.
But in my Logfile there appears a new Error:

Notice: register_rest_route wurde fehlerhaft aufgerufen. Der Namensraum darf nicht mit einem Schr?gstrich beginnen oder enden. Weitere Informationen: Debugging in WordPress (engl.) (Diese Meldung wurde in Version 5.4.2 hinzugefügt.) in /homepages/…/wp-includes/functions.php on line 5167

In English: The function register_rest_route was called with an error. Namespace must not start or end with a slash. (This Errormessage exists since WP 5.4.2)

Maybe this can help.

• This reply was modified 4 years, 5 months ago by joergschoel.
• This reply was modified 4 years, 5 months ago by joergschoel.

Unfortunately, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.