Bug with cover photo size calculation

TalkBug Collectors

Join LibraryThing to post.

Bug with cover photo size calculation

1Sir_Lobster
Apr 13, 7:12 am

There is something wrong with how LT uploads cover photos. When they are under 10MB it lets you go through the whole process without actually uploading the final image. I recently struggled with getting three scans to stick but did finally find what's happening.

What I did:
When uploading there is a popup message if your file is above 10MB, the three scans I tired to upload were all between 6MB and 9MB.
I dragged and dropped them into the upload box, pressed save, the upload progress bar showed up and filled up with no problem at all.
But then the covers just didn't show up for the book.

What I noticed:
The thing I noticed now is that even though the scans were under 10MB, on the progress bar is said they were all around 12000KB for some reason.
This all resulted in them going through the upload process, but falling on the last hurdle and not actually being uploaded.

I replicated this as I'm writing this and have attached three images.
1. Shows the actual size of the scan I tried uploading
2. The upload process lets me do it with no issue
3. The progress bar showing that it almost doubled in size somewhere in the process.

Here is the book I did the test on:
https://www.librarything.com/work/35961617/covers/309916780

Here are the two books I already downsized the scans for when I realised the how to get around the issue:
https://www.librarything.com/work/13086804/covers/311209255 - this scan is now 5,03MB on my computer
https://www.librarything.com/work/15221589/covers/310311471 - this one is now 6,53MB

Finally, just to clarify, personally I managed to find a workaround for the issue. But this will need to be fixed since there is no way for users to know what the real upload size limit is right now.

2kristilabrie
Apr 13, 10:29 am

I'll ask @conceptDawg about this when he's back later this week, thank you for the detailed report!

3conceptDawg
Apr 17, 1:05 pm

This should be fixed. This had to do with the way we were encoding the data to send to our servers. It was causing the file size to be larger than it should have been. I've fixed that so it should be true-to-filesize now.

4kristilabrie
Apr 21, 8:36 am