Subsequent uploads produced no resized images. The first time it worked at all produced a useful m size but no true t size. The first image (last successfully uploaded) took dozens of tries. Notice though that they only have t versions - the m versions generated are still uselessly full-sized. The first two images in that post that I uploaded (the second and third in the post) came back without resized versions being generated, but both worked on a second try. There’s something wrong with their code or their infrastructure, and it’s failing for a high percentage of uploads, but not all of them. I just finished successfully embedding three images with thumbnails in this post. Imgur still does the resizing, but very unreliably. Here is the HTML source that created the previous 3 images: Ĭonfirming this is still broken, and sharing my workaround. to create these 3 variations (sizes) of an image: Note: Similar to what is mentioned in another answer, make sure to respect some specific HTML formatting syntax, in order to be able to use the img HTML tag. the spacing between the image and text can only be set using.the vertical alignment of the text is always at the bottom of the image.cannot have text that spans more then a single line.Some examples of using such query string in an image, for xyz = 16, 32, 64, 128:ītw, the above also shows that you can even insert some text in between 2 images, though such text seems to have these limitations (at least I have no idea yet how to get around those): Attention: sometimes part of the top and bottom are not shown (I think it depends a bit on the actual image you're using). I.e I just added the query string ?s=128 right after. Yet another workaround might be adding a query string like ?s=xyz (with xyz = 16, 32, 64, 128, 256 or 512) after the name of the image to change it from gSpBi.png to (eg) gSpBi.png?s=128. There's also Huge (h) but it looks just like the full size because the image is big. Thanks to the users who caught this here on our various meta sites and to Geoff for knowing who to contact. We're sorry for the delay but glad that it's up and running now. This error has reduced the number of images I personally added to posts so I'm particularly glad that it's fixed. Thanks for participating in the public inquiry part of that process. ~Douglas Adams, The Hitchhiker's Guide to the Galaxy Signed in triplicate, sent in, sent back, queried, lost, found, subjected to public inquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters. Before finally getting sent to imgur, the task ended up being: We really appreciate their effort! You may ask, "why did it take nine months to fix, then?" - to which I'll say, it unfortunately and unintentionally went through something similar to the Vogon bureaucracy to get to imgur. Within 24 hours of notifying them, they identified and fixed the issue. The team over at imgur were amazingly helpful in getting this done for us quickly. Because some of the servers were working correctly, this made the occurrence incredibly random. There was a problem with a few of the servers that had autolaunched using the wrong IAM profile in AWS, resulting in their not being able to properly write to S3 as expected. Any images uploaded during the outage (7 August 2018 until 19 April 2019) will need to be re-uploaded to imgur for the resizing to work correctly as the additional image sizes weren't created and there's no way to fix this.įrom the imgur response to our bug report: Moving forward, all images uploaded to the Stack Exchange imgur will be sizable using the URL adjustments indicated in the question (see below for examples). Thank you so much for your patience with this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |