7 Comments

  1. Anh Tran

    I saw the WSOD protection on Twitter and was very excited about that. I think this is an important improvement for WordPress as it offers a great user experience when they accidentally install a bad-coded or quick-release-without-testing-plugins. With the access to the admin area, they’re able to see what’s wrong, disable the plugins and get their site back.

    Report

  2. Temitope Awe

    Am waiting for the release. It’s gonna be interesting

    Report

  3. Ramjid Pakishna

    It’s easy to poo on poo things like Gutenberg, but we have to count the hits, too and not just the misses.

    This is awesome, and appreciated. Also, who do I kiss for the code editor checking your code before letting it commit so you don’t go all white screen when people won’t give you FTP access? Literally hours of life and …er…mmHg of blood pressure for every errant semicolon or curly brace that normally would have been a time vampire in the past.

    Report

    • Otto

      A lot of people complained about that particular feature. Because it does not work in some situations, where you have unusual server configurations, or poorly made plugins, or excessive “security” rules in place. In all those cases, it just doesn’t allow code changes to be made, and people got furious about that.

      This is the case with pretty much all new features. It won’t work for some people, and they get super vocal about the perceived loss of functionality.

      Report

      • Ramjid Pakishna

        Ah, interesting perspective. I guess I meant the idea and the intended execution. In my experience, Dreamhost’s modsec overreach makes most things unusable, but that’s less of a reflection on the things themselves than DH.

        The idea of someone’s setup meaning the old editor leaves their editing impeded vs. having a compatible setup but being shot out of the sky for a simple mistake. I make more simple mistakes than I do run into tricky setups, so I definitely am partial =)

        I will say, one thing I noticed with it is, sometimes it just comes up blank even though the resulting pages on the front end look fine, and even though the same file visited through FTP looks fine.

        At the very least, there’s continuing discussion and progress. Is there a way to shut it off for those people, similar to Classic Editor?

        Report

  4. wzy

    That WSOD protection feature plus the push for adopting PHP 7 will do more for WordPress than Gutenberg ever could.

    Report

  5. Hamza

    Ah, interesting perspective. I guess I meant the idea and the intended execution. In my experience, Dreamhost’s modsec overreach makes most things unusable, but that’s less of a reflection on the things themselves than DH.

    Report

Comments are closed.

%d bloggers like this: