gutenberg

SVG Support & Broken Images If your WordPress website has broken or missing SVG images and you have the SVG Support plugin installed your issue can be quickly solve with the following quick fix. Code to Fix Broken SVG’s Add the following code to your theme’s functions.php file to solve the issue. /* * Correct SVG <img>'s * * SVG Support is adding a width and height of 1 on all SVG images in * the site. */ remove_filter('wp_get_attachment_image_src', 'bodhi_svgs_dimension_fallback', 10); Why You See Broken Images for *.svg‘s The _SVG Support_ plugin has a function in it that will: > Fix for division by zero error for SVGs It specifically sets the width and height attributes to 1 for any SVG’s that don’t provide a set width and height on the <svg> element. It’s not uncommon for this to be the case, many vectors are designed to be flexible and display based on aspect ratio rather than an arbitrary width and height. If you’re having the issue it means that you have SVG’s on your site without these attributes. It’s not an issue though, and the code snippet provided should solve the issue without causing other display issues for you. I’ve also posted this resolution to WordPress.org in the plugin’s discussion area: [All SVGs on site now broken ](wordpress.org) Bug Source Location in SVG Support The bug occurs in the function beginning on line 292 of the functions/attachment.php file in the plugin. Here’s a copy of the code for reference: // fix for division by zero error for SVGs // proposed by starsis // https://github.com/WordPress/gutenberg/issues/36603 function bodhi_svgs_dimension_fallback( $image, $attachment_id, $size, $icon ) { // only manipulate for svgs if ( get_post_mime_type($attachment_id) == 'image/svg+xml' ) { if ( !isset($image[1]) or $image[1] === 0 ) { $image[1] = 1; } if ( !isset($image[2]) or $image[2] === 0 ) { $image[2] = 1; } } return $image; } add_filter( 'wp_get_attachment_image_src', 'bodhi_svgs_dimension_fallback', 10, 4 ); The functionality provided by this chunk of code is based on a recent change to the Gutenberg editor from the core WordPress dev team. It’s reasonable to understand why the plugin author made the change, but regardless it poses issues for many of the websites using the plugin from what I’ve seen around the web. Hopefully this patch helps solve the problem for anyone else experiencing it.

PHPStan just landed in Gutenberg! There are 226 errors initially baselined at rule level 5. Help wanted fixing them: gutenberg#86088

さっき Issue 作成したんだけどもう PR が作成されとる。 早いぞ〜🐘 gutenberg#86019

Want to see the block toolbar in #WordPress being improved? Join the discussion: gutenberg#85204

I see you managed to do wordpress/gutenberg too! It took a bit longer 10 hours over here, but I got @woocommerce up at woocommerce/woocommerce. Also , 100% free and open source.

A PR is in place to fix this issue, and I’m working with the team to test the Table of Contents block in templates. 🎉 gutenberg#85040

Revisiting the 'Browse mode' idea for the WordPress Site Editor: gutenberg#84084 t.co