Giphy + Thumbnails + ImageProxy = FAIL

[SJ77]

Hi,

If you use small thumbnails for image attachments. (normal for image boards. Folks click for larger image) plus you use image proxy and Giphy, you will find there is an issue.

Turns out Giphy images are saved in the imageproxy folder ONLY at the thumbnail resolution size.  Then they are displayed at the size of the original Giphy. (expanded)

What you end up with is a very low resolution, and quite terrible looking gif image being displayed on your site. Attached is an example of how it should look and what you might end up with.

This is how it should look

Due to the aforementioned, this is what you end up with

Giphy should be saving images in image proxy folder at FULL size (as delivered from Giphy) not Thumbnail size. It should be limited only by the MAX image size in the ACP.
I believe this was setup to use the wrong size limit. The only limit used from the ACP should be the full size image limit not the thumbnail setting.

[bfarber]

Generally speaking, this sounds like a bug rather than feedback or a feature request, and would typically be best handled through a ticket. That said, we can likely reproduce the issue without a ticket if you can confirm the exact settings that need to be adjusted (and the values to adjust them to) in order to reproduce the issue.

[SJ77]

1 hour ago, bfarber said:

Generally speaking, this sounds like a bug rather than feedback or a feature request, and would typically be best handled through a ticket. That said, we can likely reproduce the issue without a ticket if you can confirm the exact settings that need to be adjusted (and the values to adjust them to) in order to reproduce the issue.

Hi, these are the settings to use along with Giphy. The exact error above will happen.

Thank you 🙂

[SJ77]

this is still an issue for IPS software. Just keeping it on the radar.

[Rikki]

21 hours ago, SJ77 said:

this is still an issue for IPS software. Just keeping it on the radar.

A fix for this was actually merged this past week. It should be included in the next major release (not the next 4.4 point release, since it's a higher impact change).