I create epub files by php. When I upload them by API I get:
"Your EPUB contains unmanifested files." error.
I get same error if I try to upload manually.
I checked my book localy with epubcheck-1.0.5 and on http://threepress.org/document/epub-validate/
Both checks say it is valid epub.
Also, checked files within epub (zip). All files there are within manifest tag in book.opf
Is this lulu bug, or you do some extra check then epubcheck? What should I look for?
Message edited by TuckDesign 3 years ago
3 years ago
just tried to upload one free epub book from epubbooks site. Get the same error. This looks like lulu bug....
3 years ago
There are two possible issues. First, Apple validation includes more than just ePub 1.0.5 check. See full requirements below. Second, validation is working properly in the on-site wizard, but we have not done much live testing of ePub validation in the API, so there could be a bug.
Can you try uploading your ePub in the new wizard? http://www.lulu.com/publish/ebooks. If this works, it's likely an API bug and I'll have a developer look into it Monday. If it fails in the wizard, make sure you're meeting the requirements below:
Validation. All ePubs converted through Lulu's ePub conversion service are guaranteed to pass Apple's ePub validation process. If you're creating an ePub yourself, keep in mind that all ePub files submitted to the iBookstore must pass Apple’s strict validation requirements. We automatically validate your file in our eBook wizard at upload time, and provide feedback and options for fixing the file if there are any errors.
At a minimum, your file must pass epubcheck 1.0.5. Many third-party sites provide tools to validate ePubs, here's one. Lulu is not responsible for the accuracy or security of third-party sites and tools. As a word of warning, simply passing epubcheck 1.0.5 does not guarantee your file will pass all of Apple's validation requirements. There are a few additional gotchas commonly encountered with ePubs that prevent them from importing into the iBookstore system:
1) All characters in the URIs must be valid with non-alphanumeric characters properly encoded (for example, space should be encoded as '%20'). This problem most often surfaces in URIs in the NCX files. For best results, do not use filenames in the ePub that have spaces or other characters that are not safe for use within URLs; this avoids the need to URL-encode them at all, thereby reducing the chances of error and delay.
2) All files included in ePubs must be listed in the ePub manifest (OPF file). ePubs containing unmanifested files will fail import.
3) Only UTF-8 and UTF-16 encodings are allowed in ePubs. Any ePubs that are improperly encoded will fail import, so it is important to use the correct character encodings.
If you can't get it fixed, please email the file in question to firstname.lastname@example.org. This will help us get a jumpstart on looking into the issue on Monday.
Last thought for now: double-check the directory to make sure it's clean and doesn't contain any stray unnecessary files (i.e. Thumbs.db, etc.).
Ok, resolved it.
File names can't start with numbers, not only in manifest ids, but in filenames also!
Please sign in to add a post.