If you do not want to use the block editor, install the “Classic Editor” plugin.
I actually had to do two things: install the “Classic Editor” plugin AND delete the “Gutenberg” plugin. With those changes everything went back to normal.
How am I to handle this if Gutenberg becomes mandatory on WordPress Release 5.0?
When 5.0 comes out, go to the settings for Classic Editor and make it the default editor.
Gutenberg (the “block editor”) will be the default editor on WordPress 5.
As I said above, I could not fix the layout problem until I deleted the Gutenberg plugin. When Gutenberg becomes mandatory, will I be able to delete it?
Stop using the word “mandatory”.
In WordPress 5.0, the Gutenberg plugin will deactivate itself because the what *was* Gutenberg is part of WordPress core. If you don’t want to use that editor, use the “classic editor” plugin.
But it wasn’t enough to deactivate it here. Even when it was deactivated and the “Classic Editor” was installed, pages were improperly formatted. I had to actually delete the Gutenberg plugin. So my question is: When Gutenberg is part of the WordPress core in 5.0, will it disrupt formatting even when deactivated?
If you’re not using it, no.
Good answer. Thanks for taking the time.
It turns out that the solution is to wrap the entire page (or portion) with the tags <!– wp:core/text –> <!– /wp:core/text –>. This will prevent the insertion of any extra tags in wrapped code.
