As an aside for the plugin to be useful it also needs to convert gutenberg posts to none gutenberg when such posts exists. Not having such an option means that this plugin can be deployed only when setting a new site.
I think the idea is that when Gutenberg rolls out in 5.0, existing sites can install and activate this plugin to prevent all their existing content from being converted into blocks.
Thread Starter
Mark-k
(@mark-k)
@pidengmor, and how will they know about this plugin? The realistic scenario of 5.0 is that people upgrade, go to edit some post which prompts them to convert to blocks (or they create some new content) and after a week they decide that they do not like the experience (for whatever reason, plugin incompatibility, inability to properly edit via xml-rpc, wordpress search is 100% useless instead of only 80%, or just a general dislike) at that point they search the interwebs find this plugin and install it.
And at this point, what exactly gona happen to all that content which was authored and changed with gutenberg? gutenberg is disabled, so the inline styling will not be applied any more, and on the editor side you will see only the text, but to see whatever additional data used with it you will need to go to the text tab and guess how to apply all the json data in the comments, something that will be hard even for technical people.
I 100% agree with the problems that are going to erupt, particularly as most users will be unaware of the implications of converting all their content to Gutenberg blocks. But as the development team are determined to add this to 5.0, it seems that having this plugin installed and activated is the best option at present, along with this function to force the replacement of Gutenberg with the Classic Editor.
-
This reply was modified 6 years ago by
barnez.
Thread Starter
Mark-k
(@mark-k)
@pidengmor, yes which brings the second part of my review. History shows that the wordpress core plugins fall into disrepair and no one feels like he should “own” them. We seee it with the importer breaking on php 7.2.
So what is going to happen is that in the long run there will be changes to “gutenberg editor”, but there might be no one that will be interested in maintaining the “classic editor” plugin. In addition @pento said in a very clear language that moving forward the gutenberg team do not plan to maintain the possibility to run the classic editor at all, which means that more and more hacks will be needed, and maybe at some point it will not be possible at all.
The only true option that can be actually maintained is an official way to turn gutenberg off and use the classic editor. Any thing else is a hack with an unpredictable life time
in https://github.com/WordPress/gutenberg/issues/4409#issuecomment-357118208 @pento said
“So, to get back to the original question, a single code-based option to disable the block editor isn’t a viable long term solution, it can’t expand to give appropriate options for future WordPress Core development, it really does a disservice to everyone here if we were to create this option.”
Therefor the notion that the maintaining the classic editor plugin is going to be harder and harder.
I think there will be tens to hundreds of 1,000s of users and developers keen to keep this plugin alive (possibly even millions?). If the current authors (WordPress Contributors) stop maintaining the plugin then I imagine (*hope*) it will be forked. Their strategy for Gutenberg isn’t going to change (introduced into core with no filter or toggle to activate or disable), so it seems that our choice as users is to either find a solution (currently the Classic Editor), or look for a new CMS.
@pidengmor, thank you for mentioning my additional function in your comment earlier.
In the meantime we (@gschoppe and myself) have rolled that function in a plugin and released it as Classic Editor Addon.
Please have a look and if you have any suggestions to improve it, we would love to hear!
I just hope that if they continue down this road with the new editor, then someone will fork wordpress with the classic editor, before this plugin stops being updated.
What you guys are mentioning makes complete sense. #wpfork, let’s start the movement now!
