@sunstate Apparently the PR has been successfully cherry-picked for release in the next point version of 6.4, but so far the point versions that have gone out have all been maintenance releases.
As far as I can tell, the next non-maintenance point release will include this fix and other Gutenberg bug fixes, though I’m not sure when that will be yet.
@sunstate I just tested in WordPress 6.4.2 and indeed, it seems the issue is still present. As far as I can tell though, the fix was supposed to be merged.
I’m currently checking on this to see what happened. Thanks for following up!
@diebornmans I’m sorry to hear this happened to you, and pardon for the late response — I needed to step away from the forums for a bit.
I’m still foggy as to what could have caused you to lose administrator access in the first place. Perhaps there was a plugin conflict or a bug with the user registration logic that caused this to happen. I’ll take a look to see if I can create a new user and replicate the issue.
In any case, I wish you the best of luck on your next steps and hope that you can find something that suits your needs 🙏
@jfans8yg19 Ok I’ve been able to take a closer look at this. Are you by chance using a block theme with full site editing? If so, you could give this approach a shot:
First, give the cover blocks you’d like use object-fit: contain a custom CSS class like cover-contain by clicking on each block in the editor, then going to Advanced under block settings:
The caveat is that the cover will still retain its height, so additional space may be present on the top and bottom of the images at smaller resolutions.
Beyond that, the best way I know how to get this right would be to create a child theme and create a custom template to have more granular control over the markup and display of the images, probably using display: flexbox.
Alternatively, you could explore creating a custom block that would overlay an image with text and retain aspect ratio while resetting its height dimension whenever the window resizes.
How does all of that sound? Perhaps that can give you some ideas or point you in the right direction 😄
Hello! Are you comfortable using custom templates and code? If so, I may be able to assist you.
If you’re otherwise looking to use the Storefront interface to create the layout, this sounds like a theme-specific issue, and I recommend going to the Storefront theme support forums to receive better assistance.
Hi all, I’ve created a Github issue to discuss this bug more in depth, along with a proposed fix here.
Please feel free to chime in with any additional thoughts on the issue or pull request. We can hopefully get a fix in for the next minor release, WordPress 6.4.2.
In the meantime, as a temporary fix, you can add the following code to the image block’s v8 migrate function in one of two places. If taking this approach, please make sure to create a backup of your files and note that any changes here will be overridden when you update Gutenberg or WordPress.
if ( ! attributes.behaviors?.lightbox ) {
return attributes;
}
if you have Gutenberg installed and activated, you can add the code to packages/block-library/src/image/deprecated.js around line 1049.
If you’re running WordPress without Gutenberg, you can add the code to wp-includes/js/dist/block-library.js around line 23678
Thank you!
This reply was modified 2 years, 6 months ago by Artemio Morales.
This reply was modified 2 years, 6 months ago by Artemio Morales.
This reply was modified 2 years, 6 months ago by Artemio Morales.
This reply was modified 2 years, 6 months ago by Artemio Morales.
@sunstate I’ve taken a closer look at this and indeed, modifying the meta attributes appears to cause the migration function to run unexpectedly, causing the error.
I’m currently consulting with some other contributors to find the best path forward.
Are you able to check permissions on the files before and after you apply the crop? Perhaps the images get uploaded with one set of permissions, but those change when the image is modified.
This may have to do with the image’s deprecated.js — that’s the link to the file in Gutenberg, but I’m not sure where it ends up in WordPress core. Am looking now.
The fact that the error message mentions migrate and that a native lightbox was just added to core is tipping me in this direction, though am not sure.
