Oneboxing large images fails with no visual cue

If you upload the image, it will be optimized before the upload happens.

image

Also, you can see the limit in the browser console

image


Let’s forget what you see here; it’s misleading with your issues.

From what I tested on your forum, posting an image link works well.
That would be welcome if you could provide another concrete example.

One thing that bothers me is why this image, for example, https://dronescene.co.uk/images/uploads/fullsize/20230227161106_DJI_0087_1.jpg is still failing on your forum (and I can’t reproduce it elsewhere)

From what I see, the cache is only 1h.

3 Likes

There are two ways images can be oneboxed and unfortunately, only one was handled correctly. This should be fixed in:

4 Likes

Thanks for looking in to this Bianca :smiley:

images can be oneboxed by the AllowlistedGenericOnebox or ImageOnebox and only AllowlistedGenericOnebox was handled correctly

Are you able to tell if this bug was a regression? :thinking:

1 Like

Hi Richie :slight_smile:

Please tell us if this change fixes your issue when it’s live.

2 Likes

I’ve looked at the code changes in the commit from Bianca, looks promising :crossed_fingers:t2:

1 Like

The fix has been merged, updating should resolve the issue on your site as well.

I think this has been a bug from day 1.

2 Likes

The fix was merged and this is what will be displayed now when we link a remote image too large to be downloaded to Discourse when download remote images to local is set to true.

2 Likes