[wp-trac] [WordPress Trac] #47873: Introduce handling of "Big Images"

[WordPress Trac]

#47873: Introduce handling of "Big Images"
-------------------------+---------------------
 Reporter:  azaozz       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  high         |   Milestone:  5.3
Component:  Media        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+---------------------

Comment (by azaozz):

 Replying to [comment:12 mikeschroder]:
 > I think we should store the original in all cases, and default to that
 behavior to help users generate larger sizes, if/when they need them, in
 the future.
 >
 > This would also allow WordPress to create these larger (or other dynamic
 sizes) for users' sites in high quality when as WordPress gets better at
 handling images. It's never a good idea to resize from an already resized
 image when it's possible to work from the original.

 Completely agree!

 Thinking that deleting the original image should be left for plugins, and
 should not happen immediately after uploading an image. We still need the
 original to make all the image sub-sizes (which can be slow process over
 several requests).

 The current patch stores the original image's file name in another array
 key in the image meta array: `original_image`. It is trivial for a plugin
 to check for its existence, remove the key, and delete the original file.
 In that case the resized image will be used instead when creating new sub-
 sizes in the future, but the quality will be reduced and the size will be
 restricted to the "big image threshold" value from the time the image was
 uploaded.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47873#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform