You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
96px x 96px is the default size used by the function get_avatar(), and the size used by Largo's author bio widget, but that 96x96 size is not registered by default in WordPress or in Largo. Here's the list of image sizes in Largo that are registered as of the current 0.5-dev:
add note to changelog that this will require regenerating thumbnails (recommend a plugin) or re-uploading avatars.
Largo does define the thumbnail image size to be 140x140, though, so we may be able to add image srcsets to get_avatar via wp_get_attachment_image_srcset as an argument onget_avatar as the fifth parameter array( 'extra_args' => '...' ) but that seems very extra, and only worth implementing as part of a comprehensive srcset review in #1577
The text was updated successfully, but these errors were encountered:
Largo defines a lot of image sizes:
https://github.com/INN/largo/blob/17caa1eadcc889b19af8047d6369428fce8e7823/functions.php#L253-L261
But it doesn't define the one that we use in a lot of places for thumbnails:
https://github.com/INN/largo/blob/7e7b4cd65105c5dab3d5ea9f6dc4bce957d2a7e0/partials/author-bio-description.php#L14-L20
96px x 96px is the default size used by the function
get_avatar()
, and the size used by Largo's author bio widget, but that96x96
size is not registered by default in WordPress or in Largo. Here's the list of image sizes in Largo that are registered as of the current0.5-dev
:Fix:
add_image_size( '96x96', 96, 96, true );
Largo does define the thumbnail image size to be 140x140, though, so we may be able to add image srcsets to
get_avatar
viawp_get_attachment_image_srcset
as an argument onget_avatar
as the fifth parameterarray( 'extra_args' => '...' )
but that seems very extra, and only worth implementing as part of a comprehensive srcset review in #1577The text was updated successfully, but these errors were encountered: