Critical error when adding or editing WordPress blog posts

  • ryeduck55

    (@ryeduck55)


    1 month ago

    Hi WordPress Support,

    I’m reaching out for help with a recurring critical error in our WordPress admin console.

    Whenever I try to add a new blog post or edit an existing one, WordPress redirects me to an error page stating:

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

    The rest of the website appears to be functioning normally, and the issue seems specifically related to creating or editing posts within WP Admin.

    I’ve attached a screenshot of the error for reference.

    Could you please help us investigate what may be causing this? In particular, it would be helpful to know whether this could be related to WordPress itself, a plugin or theme conflict, PHP/server configuration, or another issue within the post editor.

    As this is currently preventing us from updating our website and publishing new content, we’d really appreciate your support in resolving it as soon as possible.

    Please let me know if you need our site URL, WordPress/PHP version, error logs, plugin information, or any other details from our end to troubleshoot this.

    Thank you very much.

    Best,
    Ryan

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator threadi

    (@threadi)

    1 month ago

    The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.

    Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.

    In both cases you should be able to see what the cause is in the logfile.

    Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    1 month ago

    Hi @ryeduck55,

    As stated you’ll need to enable debug mode in order to have a better idea what’s causing the issue.

    In order for you to investigate it, you’ll need to open your wp-config.php file located in your root directory, and look for
    define(‘WP_DEBUG’, false);.

    Change it to:

    define('WP_DEBUG', true);

    In order to enable error logging to a file on the server you need to add:

    define( ‘WP_DEBUG_LOG’, true );
    define( ‘WP_DEBUG_DISPLAY’, false );
    @ini_set( ‘display_errors’, 0 );
    define( ‘SCRIPT_DEBUG’, true );

    After making the above changes, please try to replicate the issue. The related errors will be saved to a debug.log file inside the /wp-content/ directory.

    You can find more details about debugging here:
    https://learn.wordpress.org/tutorial/debugging-in-wordpress/

    Please let us know how that goes, have a nice day.

    Kind Regards,
    Nithin

    adnanparvaiz760

    (@adnanparvaiz760)

    1 month ago

    Hi Ryan,

    I understand how frustrating it is to be locked out of creating or editing posts, especially when the rest of the site is running smoothly.

    A “Critical Error” inside the post editor (often tied to the block editor/Gutenberg or autosave REST API requests) is usually triggered by one of three things: a plugin/theme conflict, a PHP memory limit exhaustion during content processing, or a corrupted database table/transient.

    To help us narrow this down, could you please provide a few additional details?

    1. Error Logs (Debug.log): Since you mentioned checking your inbox, could you share the exact error text from the email you received, or enable WP_DEBUG in your wp-config.php file to paste the specific error traceback?
    2. Recent Changes: Did this start happening right after updating a specific plugin, theme, or your PHP version?
    3. Active Plugins: A quick list of your installed plugins (especially SEO plugins, security tools, or page builders that hook into the post editor) would be very helpful.

    Quick Steps You Can Try Right Now:

    • Check the Browser Console: Open your browser’s Developer Tools (F12) and go to the Console or Network tab while trying to save a post. Look for any red 500 Internal Server Error or failed AJAX/REST API (wp-json) requests, as these often point directly to the culprit plugin.
    • Test in Incognito / Different Browser

    Whenever you have a moment to share the error log or debug details, let me know, and we’ll dive right in to get your publishing workflow back online!

    Best regards,

    Adnan

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.