Replies: 1 comment 3 replies
-
|
Not by design, ebooks are supposed to come across too. Bindery reads the ebook off the ABS item's media.ebookFile field, and when that's set it creates an ebook edition right alongside the audiobook one. Your layout (epub next to an [Audio]/ subfolder in the same item) is exactly the "both" case that should work, so the fact that only the audiobook landed means Bindery isn't seeing media.ebookFile on those items. Two things would let me pin it down. First, what ABS version are you on? Second, if you're up for one API poke, hit GET /api/items/?expanded=1 on your ABS server (any book that has both formats) and tell me whether there's a media.ebookFile block with a path in the response. That tells me instantly whether ABS is reporting the epub and Bindery is dropping it, or ABS isn't attaching it in the first place. Either way I'll open an issue to track combined audiobook plus ebook import. Structure isn't the problem, yours is fine. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have all of my audiobooks/ebooks combined in the following structure:
I have them as 1 "Books" library in Audiobookshelf, and they all display properly, showing options for reading, listening, or both when applicable.
However, when trying to import the library using the Audiobookshelf option in Bindery, it only imports the audiobooks, and not the ebooks.
Is this by design? Or is it something that could be added in a future update? I was under the assumption that Bindery preferred this file structure...
Beta Was this translation helpful? Give feedback.
All reactions