Support » Plugin: Gutenberg » Broke my ENTIRE business, thanks!

  • Isn’t there a way to give it ZERO stars?

    This is the worst thing that’s ever happened since I started using, building with, and developing WordPress back in 2005.

Viewing 3 replies - 1 through 3 (of 3 total)
  • wow, i’m sorry to hear that. I’m happy I was laid off shortly before the plugin came out.

    Bianca

    (@bianca205)

    Sorry you feel frustrated with Gutenberg.
    But would you care to fill us in on how Gutenberg exactly broke your ENTIRE business? You can install and enable the Classic Editor plugin if you prefer to keep using the classic editor instead.

    I totally sympathise with you @codymckibb. My business is based around web design, programming, and in particular writing custom plugins for unique businesses. Since the experimental inclusion of the Gutenberg editor I kept returning to it when I had a new site to build, but always ended up reverted back to the Classic Editor.

    There is no way my customers would be able to easily write content using the current default Gutenberg editor. The support time I would have to devote to teaching them how to use it would be enormous. It is like nothing they have used before. Simple tasks like typing a passage of text results in a new floating blocks for each paragraph, every time they hit enter. Then clicking on one of these blocks causes tool bars to appear that hide the previous paragraph contents. It seems to make no logical sense. Users want something easy, flexible and familiar which works like MS Word or Google Docs. You had this with the Classic Editor.

    I’ve also looked at the tutorials for writing plugins to make my own custom block types and I am afraid this too seems horrific and bizarrely complex. If I had a few months to sit and pull the code apart I may make some headway but I have to earn a living. Please, for the love of all things WordPress, NEVER remove the Classic Editor plugin as it will kill the product.

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