-
Notifications
You must be signed in to change notification settings - Fork 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
Gutenlypso: Opening Media Library Breaks Image Blocks #29557
Comments
Seems to be less of an issue exclusive to Featured Images, but more as Featured Images causing the result due to the actual issue. Opening the "Media Library" in a Block or by setting the Featured Image causes this issue. To recreate:
The same result will occur, images will resize in the actual post but not the editor, and captions will disappear from both. @vindl Due to bug #28893, it's necessary to use the Media Library to upload an image using Gutenlypso. That means adding more than one image to a post would cause a lot of chaos and confusion. May I suggest bumping the priority of this due to how vital images are? |
@torres126 thank you for reporting this and for the suggestion! I'll bump the priority and we'll try to resolve this as soon as possible. |
It seems this is a side effect of using There is a call to If we disable the I think we should pull the current attributes of the image blocks when executing Not sure if any of them are feasible, but I will continue investigating this. cc @Copons since he has been involved in this. |
Looks like the Will open a PR soon exploring this approach. |
Outdated steps: See this comment
Steps to reproduce
What I expected
I expected the post to reflect the changes made in the editor, showing the captions and the image sizing.
What happened instead
In the editor (should show captions beneath image):
In the post:
Browser / OS version
Context / Source
Found when writing a post for my own blog (I've experienced this several times before but I wasn't sure how to recreate it until now)
The text was updated successfully, but these errors were encountered: