-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
InnerBlocks shows inline-image block, when not allowed #11621
Comments
(Out of curiosity) how do you know when the inline images are and aren't supposed to appear. Is that something you see by reading the code or that you know from elsewhere? (Note: I don't know how to look that up in the code but would like to learn!) |
I tested using the Media & Text block with WordPress 4.9.8 and Gutenberg 4.3 using Firefox 63.0.1 on macOS 10.13.6 and found that I was able to insert an inline image into an inner block (10s), however, now I am thinking that the following means that you are using custom code:
Are you able to provide a code example for how you've used |
Thanks for the reply. If you are able to provide a code example and tell me exactly where to place it (or maybe make a very small plugin that includes your custom block that can be installed for testing?), then I can help test. Otherwise, I've added the |
I am not able to reproduce this issue on the current version of Gutenberg. So it seems fixed, as I have not seen other people having this issue. Therefore I will close this issue, thanks for your help anyway! |
Describe the bug
When a new block is inserted with the 'InnerBlock' component, and 'allowedBlocks' is used, the 'Inline-Image' block still shows, even when it's not allowed.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
The 'allowedBlocks' should appear, but if 'inline-image' is not allowed, it should not appear.
Screenshots
Before saving the post:
After saving the post and reloading the page:
Desktop (please complete the following information):
Additional context
Gutenberg 4.2.0
The text was updated successfully, but these errors were encountered: