13 Comments

  1. Stephen Vaughan

    Mmmm. Why do I keep sensing a terrible amount of BS around this whole topic regarding the current editor and the fact that we need to use a plugin to keep using it when, in fact, a simple filter in the functions.php file of a theme can be used to keep using the current editor?

    Classic Editor is actually extant in WP 5 and so therefore by extension the filter to turn on and off the block editor to get to it could be controlled by a switch in te writing settings of WordPress. It’s very frustrating as a user with specific requirements to see how clumsy all this is being implemented. I ultimately would like to use the block editor at some stage down the line when it better fits my workflows, but not yet. Not till it is more useable.

    Perhaps somebody from WordPress could illuminate me as to why it is necessary to have to use a plugin to use the current editor. Why do they feel that they have to be so controlling in how, when and which editor should be used?

    Report

    • René Drumanic

      Current phase of Gutenberg – the “editor” – is only the beginning. The later phases of Gutenberg will replace everything in WordPress backend, like widgets, menus, media library, user management, everything. Currently existing custom fields plugins like acf, pods, toolset etc. will become completely obsolete, same for all the current pagebuilders.

      Consider Gutenberg editor as some sort of a trojan horse. The “all is fine” Classic Editor plugin should/will convince many to upgrade to 5.0 “without risks”.

      Once people have upgraded to 5.0 and start using Gutenberg editor, they can not go back to 4.x and also can not simply migrate to other CMS because Gutenberg editor puts all its blocks-markup and parameters etc. as one big “datablob” right in the post_content field.

      Then the other phases of Gutenberg will be announced and merged to core, users are more or less locked in, a new infrastructure with pay-per-blocks will replace most existing themes and plugins and Gutenberg project will look like an huge success (at least in terms of number of websites).

      The trick with Classic Editor is, now it’s a filter, later various functionality including classic editor itself will be moved from core to the plugin, so this functionality will be simply gone as soon as Classic Editor expires, which now has been announced clearly for 31.12.2021.

      The four phases of Gutenberg project, the moving of core code to Classic Editor plugin, the “you can always use Classic Editor for now” talk, all that has been communicated several times at support forums, github issues, slack, twitter and make.wordpress.org/core/ so everybody can read and draw own conclusions.

      Report

  2. Daniel James

    Once again, a super important decision has been made behind closed doors without input from the public. Whilst that does give ‘us’ roughly three years to transition from TinyMCE to Gutenberg I don’t like the fact no one was considered.

    This circles back to the issue around the merge proposal that never happened. I totally get it. At this point any call for opinions on Gutenberg will probably be met with plenty of criticism but let’s be realistic here; Gutenberg project management has been awful.

    I’ve said before via Twitter, I like Gutenberg as a thing. But with all it’s history and being merged in WordPress like it is being it’s destroying what once was an open and collaborative project effort. It’d be great if we didn’t get robot business speak answers from the likes of Matt and Gary trying to do damage control but I fear at this point it’s all we’re ever going to get.

    Just to make myself abundantly clear, if this was managed better, I’d be team Gute all the way but it’s not happened that way and we’re left with this mess of a project rollout. At this point I’ve lost all trust in the WordPress project and Automattic. Business and money has been at the forefront the whole time, not FOSS.

    Report

    • Daniel Olson

      Transparency is definitely lacking and regardless of whether that’s intentional or not, it sure can be frustrating. My best guess is that these conversations do happen in the public forum but they are blips on Slack or a Twitter thread that goes unnoticed.

      When it’s all over, the Gutenberg rollout would make for a great social experiment study.

      I think the reactionary tone by the community is purely because it all feels forced. There’s nothing inherently bad about Gutenberg. When people use it they like it.

      It’s an awesome addition to WordPress and concept and like every new project, it needs work. Most importantly though, you need to compromise early and often.

      For example, this TinyMCE news could have been a part of Gutenberg discussion since Day 1.

      Give people options. If the options already exist, just include them. If you don’t want to use Gutenberg then don’t. If folks want to keep the Classic Editor well beyond 2021 and there is someone brave enough to maintain it, let them.

      Instead, focus on how those parts can co-exist in harmony and give their respective developers as much freedom and resources they require. The community will be better for it.

      Report

      • Stephen Vaughan

        I’m with you in having thoroughly tested Gutenberg I see a lot of things I like. Unfortunately it lacks badly in what it leaves out and where it does not address some fundamental things that should have been dealt with in WordPress years ago, one not having a better code code text editor experience bulit in.

        The other big one is how WP5 will implement the current editor (Classic). Having to use a convoluted plugin to deactivate the block editor is overkill and quite frankly a sledge hammer when a one line filter tied to an on/off switch in writing settings would do the same thing. Only activating the block editor for new installs and leaving older installs would have be better PR for the GB team. Not stating a concrete date for Classic removal would also help.

        Immediately though, Gutenberg’s biggest problem is usability. Trying to locate and manipulate content buried in blocks, especially once you get into column structure and nesting is not fun. If they can crack that usability issue it would be a big step forward. But, until that happens, thinking that that the block editor will be easy for the average user, compared to the current TinyMCE with metaboxes setup, is delusional.

        Report

  3. Michael Walden

    I’m old. I am not a WordPress “Wizard” and a huge portion of the behind the curtain stuff is beyond me. That is why I like WordPress: I do not have to know those things. It’s not that I do not like change, but I prefer to edit posts the way I do now. I’ve looked at several “drag & drop” editors and I just do not like them.

    Personally I would hope that the “Classic Editor” is with us for a very long time to come.

    Report

    • Nyssa The Hobbit

      I don’t like them, either. I also like widgets and clean HTML code. I looked at ClassicPress and it appears they’ve thrown out the baby with the bathwater, getting rid of some of my favorite parts of WordPress. Several of my blogger friends don’t like Gutenberg, either. So I hope we can keep our Classic Editor plugins well past 2021.

      Report

Comments are closed.

%d bloggers like this: