Enable end user opt-in to generate all sizes in fallback format #1513
Assignees
Labels
Good First Issue
Issue particularly suitable to be worked on by new contributors
[Plugin] Modern Image Formats
Issues for the Modern Image Formats plugin (formerly WebP Uploads)
[Type] Enhancement
A suggestion for improvement of an existing feature
Comments
github-project-automation
bot
moved this to Not Started/Backlog 📆
in WP Performance 2024
adamsilverstein
added
[Type] Enhancement
adamsilverstein
added
the
Good First Issue
|
Hi, I am interested in working on this issue can it be assigned to me. |
|
I was trying to implement the required feature but I am facing confusion about the Currently if I add these custom sizes add_image_size( 'custom_size_1', 400, 400, true );
add_image_size( 'custom_size_2', 800, 800, true );
add_image_size( 'custom_size_3', 1200, 1200, true );When the When the new proposed |
|
@b1ink0 Yes, that's correct. If the new option is enabled, all existing image sizes should receive a converted file in the modern image formats, whereas the default only covers the WordPress Core built-in sizes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
As discussed in #1421 when "generate fallback images" is enabled, we only generate the core default sizes in the fallback format. The reasoning here is that users can have many sizes and generating all of the sub-sizes can require an unexpectedly large amount of storage for users. I am unsure about this so let's give users the option to generate all sizes.
This proposal is to add a checkbox users can check right below the "generate fallback images" checkbox (and it would only be enabled when that checkbox is checked). Similar the the generate fallback checkbox, the note would indicate this requires even more disk space.
Something like:
Ideally when users enable this feature we should notate that in the Generator tag so we can later discover how many sites opt into generating all image sizes.
The text was updated successfully, but these errors were encountered: