Large Image

Sorry, was that supposed to be helpful in some way? My Media settings show that Thumbnail is 150×150, Medium is 300×300 and Large is 1024×1024.

Again, when I upload a featured image for a post that is 1024×1024 or larger (a square), it generates a large variant that is 1024×1024. However, when I do the same for a GD post, it will not generate a large variant if the image is a square. If the image is not a square and exceeds 1024 in height or width, it will generate a large variant. Let me know if I’m not making the issue clear and I’ll do my best to clarify.

If I upload an image to GD listing that is 2000×2000, it resizes the image to 1024×1024 and sets that as the default image. It also generates 150×150 thumbnail, 300×300 medium, and 768×768 medium-large. But it doesn’t generate a large image of 1024×1024. If I upload an image that is 2000×2001, however, it will resize it something close to 1024×1024 and also generate a large image that is close to 1024×1024. It seems like a perfect square image will not generate a large image, under any circumstances. This doesn’t happen if I upload a featured image to a regular post. In that case, I get thumbnail, medium, medium-large and large.

The reason this is a problem is that AppPresser requires a large image URL for displaying in certain ways.

I’ve already done that, no change.

But that’s not true. It does create the large image if the image exceeds 1024 in height or width and is not a square. If the image is a square, it does as you suggest. Which makes no sense.

Stiofan, you’re killing me man. Hopefully, fourth time is the charm.

You’re right, if I upload a 1024×1024 image to a GD post, it will use that as the default image size and not generate a large image. While acceptable, WordPress itself doesn’t behave this way. It will create a duplicate large image if you do the same thing with a post. But that’s fine, no big deal. My issue is that if I upload a 2000×2000 image to a GD post, GD will create a default image sized 1024×1024 (it does NOT keep the original size) and does not generate a large variant. If I upload an image that isn’t square, say 1026×1024, GD will resize it to 1024×1022, set that as the original, and generate a large variant. I don’t understand why it would not do this consistently for any image exceeding 1024 in width or height.

Let’s talk about standard WordPress behaviour. I’ve attached a 2000×2000 image. When I upload this image as a featured image for a WordPress post, I end up with a thumbnail image, 150×150, a medium image, 300×300 and a large image, 1024×1024, in addition to the original image at 2000×2000 which is also in the uploads folder. Perfect.

Now, if I do the same thing with GD and upload this exact same image with a GD post, what happens? I end up with a thumbnail image, 150×150 and a medium image, 300×300. The original image is resized to 1024×1024 and I have no large image. This presents a problem with the API because it means there is no large size variant of the featured image.

It’s not standard WordPress behaviour. So why is this happening? And again, why is it only happening with perfectly square images?

Oh I see. So you resize my 2000×2000 image to 1024×1024 and then tell WordPress to do its thing. WordPress sees the 1024×1024 image and doesn’t generate a large image. Sorry Stiofan, I didn’t fully understand your explanation before.

Is there a way to disable that? The reason this presents a problem is that AppPresser is looking for the large image variant for it’s featured listing slider that uses the WordPress API for content. This is so the image doesn’t appear pixelated on higher resolution devices, like retina iPad’s. When we provide instructions for listing submissions, I can tell people “make sure your featured image is at least 1025 in height or width to be compatible with the app”. That’s easy. But because of what you guys are doing, I have to tell them “make sure your featured image is at least 1025 in height or width but is not a square to be compatible with the app”. That will be much harder to explain.