Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #55443, comment 167


Ignore:
Timestamp:
09/01/2022 01:37:04 AM (20 months ago)
Author:
eatingrules
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55443, comment 167

    v1 v2  
    1616So at least if it's off by default and has a toggle, we can say "Hey, there's this new feature, it's has these benefits, but just be aware of XYZ potential downsides" then they can choose to turn it on and try it.
    1717
    18 I am still certain that there will be a significant number of problems down the right (most acutely due to future thumbnail regeneration) -- and, as currently proposed, it will be particularly bad because site owners won't have a clue as to why their site's disk usage has skyrocketed sometime in the future.
     18I am still certain that there will be a significant number of problems down the road (most acutely due to future thumbnail regeneration) -- and, as currently proposed, it will be particularly bad because site owners won't have a clue as to why their site's disk usage has skyrocketed sometime in the future.
    1919
    2020> The other idea, default to "off", makes this useless imho. Usually 95% of options are never changed from their default values. This is a new feature that would enhance millions of web sites and bring this part of the WordPress image handling to 2022. Why would it be potentially enabled on only 5% of sites? Makes no sense to add to core at all in that case.