Support » Plugin: Classic Editor » Blank screen after updating or publishing post

  • Resolved tomango

    (@tomango)


    Over the last couple of days a number of our sites have been going to a blank screen when a post is published or updated. I have disabled all other plugins and themes and can confirm it is caused by Classic Editor plugin. There is nothing listed in the log related to this. The issue only occurs on PHP 7.4 and below, upgrading to PHP 8 prevented the issue.

Viewing 14 replies - 1 through 14 (of 14 total)
  • I am encountering the same thing. It just started this week. It happens when I try to have more than one statement. One and it posts. Two and it does not post, but gives me a blank screen with the URL https://mydomain.com/wp-admin/post.php

    I have deactivated all other plugins and even switched back to the block editor, which has no problem with more than one image.

    I have the same issue. Just started 2 days ago. Upgrading php from 7.4 to 8.0 did the trick. But now I get the message module imagick is missing:

    “The WordPress Hosting Team maintains a list of those modules, both recommended and required, in the team handbook (opens in a new tab).

    Warning The optional module, imagick, is not installed, or has been disabled.”

    Thread Starter tomango

    (@tomango)

    @miwalther Imagick is only supported on 7.4 at this time. I would suggest moving back to 7.4 if you need it and waiting for the plugin authors to fix this.

    I am not sure if I need it. The Site Health Status in wordpress tells me it’s “recommended and required”.
    But I need PHP 8.0 so I can save pages and posts again. It’s not just the Classic Editor plugin causing the problem of not saving. It’s also WPBakery Page Builder which I use and need through the theme.

    So are you saying that Classic Editor doesn’t work with PHP 8.0, or is it possible that there’s some kind of clash with some other plugin?

    Thread Starter tomango

    (@tomango)

    It does work with PHP 8, there is a bug on PHP 7.4 and PHP 7.3 where if you update a post it can result in a white screen. I have tried on a new install with default theme and no other plugins and it still happens. Upgrading to PHP 8 fixes it.

    • This reply was modified 2 months, 3 weeks ago by tomango.
    Thread Starter tomango

    (@tomango)

    @tobifjellner I have had quite a few more reports of this issue today. How do we raise this as a bug to get fixed ASAP?

    Acutally very weird. When I tried and tested today now saving worrked again using PHP 8.0. On all my domins. It defenitely did not work last Thursday and Friday. Now I canged back to 7.4. for all my domains and no problems anymore. And my ISP just told me they did not change anything on the server since. Very weird.

    @tomango
    Where I’m using Classic Editor, things are still working normally (PHP 7.4), so it would be good if you manage to figure out more specifically what is clashing. Do you all have some other third plugin, or are you using some specific theme?

    Anyway, when you’ve got enough information for a reproducible bug, the best place to file it would be https://github.com/WordPress/classic-editor/issues

    Thread Starter tomango

    (@tomango)

    I have set up a clean download of WordPress, using default theme and only 1 plugin, ‘Classic Editor’. I have narrowed it down to hyperlinks. Including a hyperlink triggers the error. Here is a video https://youtu.be/RAn5E091e8Q. I will create an issue on git now.

    Plugin Author Andrew Ozz

    (@azaozz)

    Cannot reproduce here either (PHP 7.4).

    Including a hyperlink triggers the error.

    Sounds like the PHP 7.x server/install may have some sort of (overly eager) anti-exploit checks. What happens if you post a long comment with links from wp-admin (/wp-admin/comment.php?action=editcomment&c=####)? How about a longer category or tag description?

    In any case there must be an error message in a log somewhere. Also, what’s the HTTP error in the server response (from the browser’s dev. tools).

    • This reply was modified 2 months, 3 weeks ago by Andrew Ozz.
    Thread Starter tomango

    (@tomango)

    @azaozz Thanks for your suggestions. The page server response is normal – 200.

    I tried posting a comment with a link to ‘/wp-admin/comment.php?action=editcomment&c=####’ like you suggested and you’re right, this triggers it too.

    A long category name yields ‘Could not insert term into the database.’, as expected.

    Thread Starter tomango

    (@tomango)

    I managed to solve the issue by disabling the extension ’20-monarxprotect.ini’. Many thanks to all who helped me get here.

    Plugin Author Andrew Ozz

    (@azaozz)

    @tomango I’m glad you fixed the problem. Thanks for posting about it.

Viewing 14 replies - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.