search

Automattic / gutenberg-ramp

Control conditions under which Gutenberg loads - either from your theme code or from a UI
https://wordpress.org/plugins/gutenberg-ramp/
76 stars 15 forks source link

Does not support 'fallback' mode #65

Open Ipstenu opened 5 years ago

Ipstenu commented 5 years ago

I use the Classic Editor as a fallback. That is, I check this option:

Use the Gutenberg editor by default and include optional links back to the Classic editor.

This (1) lets me have an "Edit Classic" link and (2) Allows me to pick, when I create a new post, to use the classic editor.

When I activate RAMP and flag it to allow Gutenberg on a post type, it removes that create option.

This means I cannot use Gutenberg as "Recommended but yeah, use the Classic editor if you've gotta" scenario, which is currently the default behaviour with Gutenberg. I know it's not preferable, but in order to on-ramp users more granularly, this allows me to steer them towards Gutenberg while still giving them a comfortable fallback.

Would it be possible to support that?

https://wordpress.org/plugins/manager-for-gutenberg/ does this by making heavy use of removing filters, which I know isn't optimum, but provides a better balance for my medium to advanced technical users who are in the process of ramping up :)

dartiss commented 5 years ago

Totally agree with this. Due to Jetpack's lack of GB support, I have to drop back to the classic editor on posts just to change the Publicize text.

dartiss commented 5 years ago

I also made mention of this in a recent blog post, as the lack of a fallback prevented me from using Ramp on a site, and I had to use a rival product instead.