ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

[sebdea]

Hi there,

Book done in InDesign CC, exported as pub, formatted with Sigil, checked with Sigil and Calibre. Everything is fine and no errors found.

Until I tried to upload it on lulu.com. Horror!

It started raining with errors:

ERROR: bad CRC checksum for entry OEBPS/image/Cover.jpg: 18279d2b instead of dbc55f4
ERROR: Publisher value is missing in OEBPS/content.opf
ERROR: Unable to locate a valid publication date. A date with the event attribute publication (opf:event=publication) is required in OEBPS/content.opf
ERROR: Unable to locate a valid creator. A creator with the author role (role=aut) and the file-as attribute is required in OEBPS/content.opf
ERROR: Unmanifested file: META-INF/com.apple.ibooks.display-options.xml
ERROR: IOException: Unresolved external XML entity: 'http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd' in OEBPS/Perfect_Pilates_Digital.xhtml
ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

....

ERROR: Unable to locate element with id '_idParaDest-74' in OEBPS/toc.ncx

Some of them can be done. I hope. I am unable to solve the mystery of that:

ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

Since _idParaDest-X is a MUST in order to connect the TOC to the appropriate heading I see no point in making an error of it.

Same book was uploaded as ePub without errors and same ePub was used to generate a Kindle version which also passed the verification of Amazon checking system.

Ohh. Yes. The cherry on the top of the cake:

ERROR: Fixed layout EPUB.

What on Earth is wrong with their system? Indesign has an option to export a file as fixed layout ePub but I am 100% confident I didn't used it.

Can anyone help me to solve this puzzle?

Kind regards,
Sebastian

[HarryT]

The fact that you posted your message in the "Upload Help" forum suggests that you intended to upload it to the MobileRead library, that being the purpose of this forum. Had you been asking for help with uploading it elsewhere, you would presumably have posted in the "ePub File Formats" forum.

I shall move your post to the correct forum, but you've been a member for over three years, so you really should know what the correct place to post messages is by now.

[Hitch]

Originally Posted by sebdea

Hi there,

Book done in InDesign CC, exported as pub, formatted with Sigil, checked with Sigil and Calibre. Everything is fine and no errors found.

Until I tried to upload it on lulu.com. Horror!

It started raining with errors:

ERROR: bad CRC checksum for entry OEBPS/image/Cover.jpg: 18279d2b instead of dbc55f4
ERROR: Publisher value is missing in OEBPS/content.opf
ERROR: Unable to locate a valid publication date. A date with the event attribute publication (opf:event=publication) is required in OEBPS/content.opf
ERROR: Unable to locate a valid creator. A creator with the author role (role=aut) and the file-as attribute is required in OEBPS/content.opf
ERROR: Unmanifested file: META-INF/com.apple.ibooks.display-options.xml
ERROR: IOException: Unresolved external XML entity: 'http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd' in OEBPS/Perfect_Pilates_Digital.xhtml
ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

....

ERROR: Unable to locate element with id '_idParaDest-74' in OEBPS/toc.ncx

Some of them can be done. I hope. I am unable to solve the mystery of that:

ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

Since _idParaDest-X is a MUST in order to connect the TOC to the appropriate heading I see no point in making an error of it.

Same book was uploaded as ePub without errors and same ePub was used to generate a Kindle version which also passed the verification of Amazon checking system.

Ohh. Yes. The cherry on the top of the cake:

ERROR: Fixed layout EPUB.

What on Earth is wrong with their system? Indesign has an option to export a file as fixed layout ePub but I am 100% confident I didn't used it.

Can anyone help me to solve this puzzle?

Kind regards,
Sebastian

I haven't looked over your ePUB, but if memory serves, Lulu uses a much, much older version of ePUBcheck, something like...1.1? I am reminded by looking at the error message you have about "creator" versus "author" roles, and recall having this issue a few years ago with a book for a big author of ours. Therefore, you may have to invest a fair amount of time in making the book compatible with a MUCH older ePUBcheck, which can be a real pain in the ass.

Vis-a-vis the FF: did you use any type of precise vertical or horizontal positioning? A much older ePUBcheck could be interpreting that in that fashion. Plus, you'd have to pull it out, even for a newer ePUBcheck, if you did, as most won't pay a gnat's worth of attention to it.

You also won't be able to get the xml file for the Apple fonts to pass.

HTH,
Hitch

[dgatwood]

Originally Posted by Hitch

You also won't be able to get the xml file for the Apple fonts to pass.

Is there a reason you couldn't add it to the manifest?

[Hitch]

Originally Posted by dgatwood

Is there a reason you couldn't add it to the manifest?

Yes, because it "lives" outside of the scope of the manifest. If you try to add it to the manifest, you'll get an error as well. I haven't made an ePUB with the xml file in some time (risking that a first-gen will display whatever is needed), but I do recall this problem.

The rest of the issues can't be addressed without additional data.

Hitch

[DiapDealer]

Originally Posted by sebdea

ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

ERROR: Unable to locate element with id '_idParaDest-74' in OEBPS/toc.ncx

ERROR: Unable to locate element with id '_idParaDest-1' in OEBPS/toc.ncx

Since _idParaDest-X is a MUST in order to connect the TOC to the appropriate heading I see no point in making an error of it.

Correct me if I'm wrong, but surely you mean that "_idParaDest-X is a MUST in order to connect the HTML TOC to the appropriate heading"?

The wording of the error makes it sound as if the href in your chapter heading links are trying to point to an id in the ncx file instead of an html toc. And that id is (of course) not being found in the toc.ncx file (not that things would work that way even if it were found).

I could be all wet though ... as I can't make EPUBCheck 3.0.1 produce that same exact error (and am not going to try and get the older 1.1 version working locally).

I can verify that Sigil's Flightcrew validator won't make a peep about linking to the ncx file in the manner I believe you may have mistakenly done.