Forum Replies Created

Viewing 15 replies - 1 through 15 (of 1,999 total)
  • The block editor has over a million sites using it already, so not worried about test or usage coverage. We made the Classic Editor plugin to give people a choice to hold back even while the default experience moves forward.

    Forum: Reviews
    In reply to: [Gutenberg] awful plugin

    Very sorry that you had that experience. Looks like Spacious Pro is a commercial theme, assuming you paid for it definitely contact ThemeGrill and let them know that Gutenberg compatibility is important for you as a customer and future purchases. They may also already have an update for Gutenberg compatibility!

    You will not be forced, you can install the Classic Editor plugin (which we also made) and when you update to 5.0 you’ll stay on the same editing experience you have today.

    It must be coming from one of the other plugins that updated, if we can track down which one we can help them update and fix the bug.

    Thank you for your feedback, and I appreciate you giving it a try and taking the time to share your experience. We’re working hard to make it both a powerful and intuitive experience, but obviously haven’t made it there yet for you. We also hope that Gutenberg can provide a base the page builders you mention can build on in the future, so for example you would be able to switching a site between Elementor and Visual Composer without having to redo it from scratch.

    Did anything change on your site in between when it was working and then stopped working?

    We’ve announced that the plugin will be officially supported until at least 2022.

    It is not supported to stay on 4.9, and I would highly recommend against it, however you can install the “Classic Editor” plugin and you will stay on the old editor in 5.0 and beyond. We have announced the classic plugin will be officially supported until 2022.

    That’s an excellent suggestion, will look into it. Thank you!

    Classic editor leverages the TinyMCE bundled with WP, which Gutenberg also uses, so that’ll get updates as new versions of WP come out.

    I have read this, and thank you for your feedback.

    In addition to being a more intuitive, user-friendly interface for people to write and create pages, Gutenberg is also:

    1. A framework for plugins and themes to register and provide interactions in blocks. Right now every plugin and theme does this differently, there are no common patterns or language.
    2. Phase 2 of Gutenberg replaces widgets, menus, and allows for theme layout in the customizer. This means that users can learn things once, and developers can write things once, and have them work all over the site instead of (for example) creating a shortcode for the editor, a TinyMCE plugin to have an interface for it, and a completely separate widget to do the same thing, and a separate interface for that.

    Forum: Reviews
    In reply to: [Gutenberg] Just No!

    @healthy-lawn-dude: Mr Dude, we would love for your site to be as healthy as your lawn!

    As Tammie said, the Gutenberg team has created a plugin that will keep you on the current editor even after your site upgrades to 5.0:

    https://wordpress.org/plugins/classic-editor/

    So you can use that, get many of the benefits of a new core release, and then switch the editor when it suits you. You could wait a week, a month, or all the way to when it’s time for the ryegrass again.

    I’ll also add that Gutenberg is going to be completely free, open source, and bundled with core, so it’s hard to draw a line between it and making money.

    If you mean that it’ll allow less technically able or proficient users to be able to create a site using WordPress than could before, that is definitely a goal. Part of the hope in investing so much time in Gutenberg is it does bring us closer to our goal of “democratizing publishing” and encourages more people to join the free and open web that WordPress enables instead of publishing on platforms like Facebook, Twitter, Medium, or one of the proprietary site builders that are out there.

    To the extent more WP users means more money inside the community, that’s probably true to the extent it drives adoption in countries with more disposable income, but the great news is that will flow to all corners of the WordPress ecosystem and create new opportunities for everyone from developers to agencies to add-on sellers to hosts.

    Gutenberg is informed by everything that’s been tried (and largely hasn’t worked) so far, such as the Front end editor, other plugins, page builders, even our own attempts to evolve or replace TinyMCE in the past.

    You do illustrate the difficult tightrope between improving functionality and maintaining backwards compatibility. If we took the approach you advocate for, keeping “terrible UX solutions” just because a plugin used them or people are used to them, we’d still look like this:

    https://matt.files.wordpress.com/2017/08/img_0315.jpg

    The key to breaking backwards compatibility is to make sure what’s on the other side is #worthit. Gutenberg is very much in beta and evolving rapidly, but later in the year I hope you’ll see what we think will be worth it to cause some code to need updating but will usher in a new era of democratizing publishing on the web.

Viewing 15 replies - 1 through 15 (of 1,999 total)