Is this a good idea? only if it is backwards compatible.

  • I’m worried about this feature and how it will impact on all the live wp sites of my clients. In all projects I have Custom fields, custom post types, Yoast SEO, woocommerce, not sure how this Gutenberg thingy will impact on all the sites, on my tests it really disrupts and destroys everything.

    If I want to maintain the current WordPress editor and look and feel, will I be able to do it , by deactivating the guttenberg editor?

    I don’t think that it was necessary such a change, there are much more important and urgent features to introduce to core than this..

    I understand the need to go JS but only this can be a good idea when it doesn’t break all the old websites. that is causing harm to the developer community that has trusted this CMS for years. but who will be more affected are the small-medium businesses that will need to pay to developers to fix the compatibility issues. I think that it will be a great thing to consider all these issues… I personally feel that this pushes me to move to to static site generators or directly the Jamstack.

    • This topic was modified 6 years, 8 months ago by gaucho code.
    • This topic was modified 6 years, 8 months ago by gaucho code.
    • This topic was modified 6 years, 8 months ago by gaucho code.
Viewing 2 replies - 1 through 2 (of 2 total)

  • You will be able to use https://www.ads-software.com/plugins/classic-editor/ to disable Gutenberg if you wish. I believe WooCommerce are updating the plugin to be more compatible with Gutenberg (this might have already started) so it’s worth keeping an eye on that.

    Moderator Marius L. J.

    (@clorith)

    Hiya,

    Thank you for taking the time to test Gutenberg, and share your experiences!

    Lynqoid already shared the step for retaining the current classic editor once WordPress 5.0 is released (when this is depends on when we feel Gutenberg is finished, so no ETA yet), I’d love to address your other concerns.

    You are right that some custom fields plugins may not work well with Gutenberg right away, we do believe that most of them will work (and looking at my own projects, I see that they do so far work quite well in Gutenberg as well). What is likely to happen is that they may not all work during the plugin beta period which is going on now, but any serious plugins will be doing their own updates to be compatible when that time comes. The plan is to also fall back to the old editor if we detect conflicts with metaboxes introduced by plugins, this to avoid breaking your site. This mechanism is not something that is in the beta plugin as this time because we want to actually detect such conflicts at this time.

    Custom post types, which is what WooCommerce uses (I’ll use that as an example here) will be able to say they don’t use Gutenberg, and then you’ll have the screen you see today. They are experimenting with some very interesting things for Gutenberg though, judging by their blog posts, so I’m personally very excited to see what their plans are.

    At the end of your first paragraph you wrote that it destroyed everything, what did Gutenberg destroy? In general, all your content should remain the same even with Gutenberg enabled so I would love to hear some more about this.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Is this a good idea? only if it is backwards compatible.’ is closed to new replies.