I just started to use Gutenberg in my projects. A feature i always used with the old WordPress Editor was “Hide on screen” and i mostly removed the defautl editor and just added an a specified field-group to manage the content on the page.
When i use the Gutenberg editor and select the not to show the “content editor” the default Gutenberg-Editor is still available.
Is this currently possible?
This does not work with and is a known issue. You cannot hide the new editor. If you don’t want to show it on a specific post type you need to disable it completely for the post type.
Hey John thanks for your answer.
Im not happy that the backend then looks like before Gutenberg. It is quite disturbing for the backend-user to have two different views. Is there a roadmap to solve this issue?
Most of the issues are because WP has not provided any way to accomplish the fixes. Start here https://github.com/WordPress/gutenberg/issues/12692
I found the following method to hide the Gutenberg editor. (the solution at the bottom) https://github.com/AdvancedCustomFields/acf/issues/112
If there was a way to access the checkbox value for the Content Editor “Hide on screen”, then we could adapt the code to look for that value, instead of having to put in page names, but for now, I am Just hiding it on the home page.
That method does change the edit page back to the classic editor, so it hides the Content Area.
Unfortunately, the field groups are loaded after the point where you can add or remove editor support, so there isn’t a way to switch between classic/block editor based on ACF field groups. The closest you might be able to come to this is to use a custom template and remove editor support for any page using that template.
I discovered an answer to this at https://www.billerickson.net/disabling-gutenberg-certain-templates/. It does not use the “hide on screen” settings, but it did accomplish what I was trying to achieve.
