Hello Bricks Community,
I am experiencing a problem when using custom thumbnail sizes registered with dynamic crop (e.g., width set and height auto) in Bricks Builder together with Imagify for WebP image optimization.
Version: 1.12.4
The Issue
• I register a custom image size with only the width set and height as auto (e.g., add_image_size('300xauto_thumb_RET', 600);).
• This size appears correctly in both Imagify settings and Bricks Builder image size dropdown.
• However, when selecting this custom size in Bricks, the front end does not display the correct thumbnail image. Instead, it often shows the full-size WebP image or the wrong size.
• If I use a hard crop (both width and height set with cropping enabled), everything works as expected: the correct thumbnail size is displayed and Imagify serves the WebP version properly.
What I Have Found
• This issue seems isolated to dynamic crop sizes (soft crops) where only one dimension is set and cropping is disabled.
• WordPress generates proportionally resized images for these sizes, not hard-cropped images.
• Bricks Builder and Imagify sometimes fail to serve the correct image size or WebP version for these dynamic crops.
• Hard cropped images (with both width and height set and cropping enabled) are reliably served with the correct size and WebP format.
• When setting a source on the image object, it does force the correct image crop, but Imagify then fails to select the webp variant.
Steps Taken
• Registered the custom image size using add_image_size('300xauto_thumb_RET', 600);.
• Verified the size appears in Imagify and Bricks.
• Regenerated thumbnails.
• Cleared all caches.
• Tested with new image uploads.
Request for Help
• Has anyone else experienced this issue with dynamic crop custom thumbnails in Bricks Builder?
• Are there any workarounds or fixes to make dynamic crop sizes work correctly with Imagify and Bricks?
• Is this a known limitation of Bricks or Imagify?
Thanks in advance for any insights or suggestions!