Moez Tharani
Forum Replies Created
-
Posts
-
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.
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.
Updated, no change.
I’ve already done that, no change.
This reply has been marked as private.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.
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.
This reply has been marked as private.This reply has been marked as private.Stiofan,
I have another site doing the same thing, but it’s not running Autoptomize, only GD Booster. I’ll give you access in the next post, but it’s vital you not save anything or make any changes to it as it’s a client production site. Thank you.
Moez
Stiofan,
Can you disclose the changes made to Autoptomize? I have 3 other sites displaying similar issues.
Moez
This reply has been marked as private.This reply has been marked as private.Unfortunately, that doesn’t seem to address my issue. I’m more than happy to go digging through the code to change the default sorting, if I have to. We use a slightly modified version of your API to feed content to our mobile app (it doesn’t modify your code as it’s registered as a separate endpoint). The problem is that the data appears to be sorted by post_date. So /events?event_type=upcoming&page=1&per_page=10 shows me 10 event instances with the first two in August, the third in October and the fourth in September, because that’s the order I added them. The second page of results might show something completely different. So when our app pulls down that data, it will show 10 events and then when you scroll to get the next page, it adds events above. We’re working around this by pulling all events down at once, but that brings it’s own set of issues.
The schema parameters for orderby for events shows that post_date is the default and nothing else (whereas the same thing for places shows more options). Is there a hidden way to sort by event_startdate? Because that would resolve all of our issues.
Do we have to do anything to let WP Easy Updates know we are licensed?
