-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable/Filter Block Manager #2180
Milestone
Comments
Opened an upstream issue here: WordPress/gutenberg#15265 |
As decided in the current meeting, we should just disable/hide the block manager as a whole. We already provide a trimmed down list of AMP-compatible blocks, so there's not much value in further disabling them. |
Testing instructions
|
This has regressed, see #2904. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently, Gutenberg added a block manager that allows you to disable (unregister) certain blocks completely.
While that might make sense for things like the Verse block, we don't want people to be able to unregister the AMP story, ever.
Either by removing these blocks from the block manager if possible, or alternatively by completely hiding the block manager.
The text was updated successfully, but these errors were encountered: