[wp-trac] [WordPress Trac] #48522: Attachment size not generated when large images uploaded
WordPress Trac
noreply at wordpress.org
Wed Nov 27 21:14:22 UTC 2019
#48522: Attachment size not generated when large images uploaded
-------------------------------------------------+-------------------------
Reporter: vanyukov | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.3.1
Component: Media | Version: 5.3
Severity: normal | Resolution:
Keywords: 2nd-opinion has-patch needs-testing | Focuses:
needs-unit-tests |
-------------------------------------------------+-------------------------
Comment (by vanyukov):
Replying to [comment:19 azaozz]:
> Looking at 48522.diff again, it changes the behaviour in
`_wp_make_subsizes()`. Until now errors while creating a particular sub-
size were silently ignored. As the sub-sizes are created in a loop, that
allowed the loop to continue and (attempt to) create the next sub-size.
Yes, I did see that part. That's why I said it was not a patch. I believe
you were planning, at some point, on having WordPress auto regenerate
attachment sizes during a theme switch, for example? There would have to
be a way to continue on if one of the attachment sizes is not generated
for some reason.
Regarding 48522.diff. Won't that seriously limit the capabilities of hosts
that are not able to accommodate the heavy lifting of ImageMagick? With
the patch, I'm getting no images at all and am required to downsize the
original. What if that's not an option? I can see so many scenarios that
would make me want to upload attachments as large as possible. I'm fine
with a host not being able to generate the largest attachment sizes.
That's my concern. But I don't want WordPress to make that decision for
me.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/48522#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list