-
Notifications
You must be signed in to change notification settings - Fork 73
Errors in Thumbnail creation #24
Comments
No, that is a new problem. BBS looks for Calibre-made pictures called "cover.jpg" in the book folders. You could check if that file exists for book 335. If it exists it would be interesting what kind of picture it is. Maybe PHP has limits there. Look at it with exiftool or a similar tool. The result for a Calibre-made cover should look like this:
|
Yes, there is an image "cover.jpg" for the book 335 in the book folder. This is what exiftool puts out:
This happens only with 4 books out of hundreds, so I could live with that. But I want to know why this happens ;-) The only difference I see, is the file permissions: rw-rw-rw- (your example: rwxrwxrwx) |
It's not the permissions because I have test files with different permissions (rw-r--r--), and they work. And I checked the -- strange -- dimensions. That was also ok. |
In the meantime I did the following: I deleted the book in Calibre. Imported the ePub file and tagged it again with meta tags and a different cover image. Now the book has a different ID and.....it works. Well, maybe the bug was Calibre itself, I don't know... As I said, this happened with under 1% of all my books, so maybe the "cover.jpg" was corrupted during synchronization with my Sanology... I think this issue can be closed, but we should keep an eye on this. |
ok, thanks for checking this out. |
Hi,
I encountered an error in the creation process of the thumbnails:
In admin section, the "Clip thumbnails" button is set to "yes":
The Bug:
Here's a screenshot of the different views:
In the folder "data", no thumbnail for the relevant book (this case ID 335) exists.
The original cover image in the Calibre Library is an ordinary jpeg file.
Even changing the cover image in Calibre, doesnt affect BicBucStriim!
It's just not created....
Did you encounter this behaviour before, or could you give me some hints how to test this further... ?
Thanks,
BuzzDee
The text was updated successfully, but these errors were encountered: