i agree. the error message is a *******.
Two questions so people can sort out your problem:
(1) Are you using InDesign CC or InDesign CC 2014?
(2) If the latter, are you creating Reflowable EPUB or Fixed Layout EPUB?
CC indesign2014 trial
Yes, that is a frustrating problem. Since you're rebuilt your TOC then the other possible explanation is that you've either built more than one TOC Story which you've failed to update and it was part of the export, or you've copied contents from the TOC Story and pasted it into a non-TOC Story which is part of the export.
What is happening behind the scenes is this - prior to CC when InDesign generated the TOC it merely had to attach a hyperlink to the page number in the TOC - that was sufficient for PDF hyperlinks to work. More specifically, there was no backlink to the SOURCE of the TOC entry, just a reference to the page it was on.
In the CC update (I forget which one now) we added more information when generating the TOC entry - in addition to the hyperlink to the page that was there before, we also add some special information that allows us to get back the source paragraph. It is the lack of this information on an older TOC page number that triggers the error string.
You are fine to ignore it, with the outcome that you'll find a page number entry that is not emitted as an hyperlink. Unfortunately there is no easy way to try to track this errant entry down other than to try to keep trimming your export Story(s) down until you isolate which Story/Content is culprit.
Now the idea that the CC updates with respect to EPUB represent a downgrade is ludicrous! Clearly you have no idea of the two years of work that have gone into moving EPUB from where it was in CS6, but why should you? Certainly we don't make it very easy to find.
You've given me a good excuse, thank you, to remind folks about 3 papers I've written which outlines all the changes made in each update since CS6 which should put the rest any idea that CS6 is a safe harbor, with respect to EPUB work at least.
We've been on a regular cadence of two updates a year which would place the next update..very soon.
The team is earnest about improving the EPUB export so we are interested in hearing about problems and suggested solutions. We've got a lot of things to worry about on our list already but knowing what the common pain points are really helps us set priorities.
Architect, InDesign Engineering
Preach it, brother!!!! ;-D
Myron: FWIW, just regenerating (updating) the TOCs in our converted docs, with "Add anchors" turned on in the TOC dialog box first, has fixed the problem with no ill effects in our EPUBs.
1 person found this helpful
I think the Adobe InDesign team is doing a FANTASTIC job with their CC updates, especially in regards to EPUB. Each update has made my workflow significantly easier. I'm absolutely thrilled each time an update is released.
That said, I've also noticed some strange behavior with the TOCs in my EPUBs. I use multiple TOCs, and when I click "Make Text Anchor in Source Paragraph" everything works fine. The EPUB has a perfect TOC with links that work. BUT, if I then click "Sort Entries in Alphabetical Order" (and yes I update the TOC and save) the resulting EPUB does not generate TOC links at all. The TOC is just regular text. A quick look at the EPUB's code reveals that the alphabetized TOC does not include any TOCAnchors.
I have the same rather urgent problem, too. Need TOC links for epub asap. How soon will this be added to InDesign CC 2014? My epub export is Fixed.
"Sort Entries in Alphabetical Order" in TOC should work the same way. The TOC should be generated in this case as well in alphabetical order.
Could you send me your InDesign file where this problem is reproducible? You can upload it to dropbox and share the link with me: firstname.lastname@example.org.
The hyperlink limitations (okay, the lack of support for) in Fixed Layout have been resolved for the fall update.
I took a look at Jame's files. Since Articles Panel is being set as Content Order while exporting EPUB, the workaround is to arrange the text frames in the Articles panel in the same order as your alphabetical TOC entries. This is feasible in this case since each text frame is a separate entity with just the names of flowers.
Updating the TOC after this step and then exporting should generate the TOC fine.
I received this message from Kindle Direct:
Your wrote: "Myron: FWIW, just regenerating (updating) the TOCs in our converted docs, with "Add anchors" turned on in the TOC dialog box first, has fixed the problem with no ill effects in our EPUBs"
Actually AnnMarie, with Indesign CC 2015 we still have an important problem related to the "TOC isn't anchored error message". Here's the issue:
Yes, even though you get the error message, the TOC still fine when exported as an epub. But when you covert the epub to a mobi file via the Kindle Previewer, you'll see that in the Kindle, when you tap for the TOC, it doesn't open to the TOC page. It opens in NeverNeverLand...and is therefore of no value to the reader.
I hope InDesign will solve this problem since, Like it or not InDesign, Amazon is the big Elephant in the room for ebook sales.
So Douglas Waterfall and anyone else at Adobe, we really need your help for a solution for this.
(Note: "Make Text Anchor in Source Paragraph" is definitely turned on but it still isn't working.
Now I would think it is some time ago and in the 2015 issue so many great new improvements have been shown, but...
I still can't find a solution to this.
And, fine if it still doesn't work as desired, but how to solve the situation and create the e-pub with a proper working TOC?
Even if I have to make the TOC by hand...
Please, has anyone come up with a solution please!!!
"Even if I have to make the TOC by hand..." You can try cross-references.
Douglas, don't think I don't appreciate the improvements made in all iterations of InDesign, but I'm now in CC 2018, a print designer working for the first time creating epubs, and the idea that three years ago, folks were complaining about something that still isn't working for me tonight is just crazy! I have created .... and created ... and created .... my InD TOC, following all the steps very, very carefully, and I ALWAYS have checked "Make Text Anchor in Source Paragraph." Upon export, this does not happen. In fact, upon export, an HTML TOC does not appear anywhere in the document! The Nav TOC is there but no internal TOC, which I'd really like to have. If Adobe hasn't fixed this since 2014, 2015, 2016, 2017, or 2018, I can't help but get the feeling that someone over your way is sitting on their hands and laughing at us designers out here. But if it HAS been fixed, or if there is a magic trick I can read about somewhere (though I have scoured the 'net for a solution and found none as yet), I'd really like to know.
One more thing: Every post I HAVE found about the TOC functions -- even inside the Adobe site itself -- seems to refer to TOCs that are being generated from InDesign books (.indb). The manuscript I'm working with is all in one single InD file, not in separate chapters (I did try that method and for reasons I won't go into, it didn't work well with this manuscript). So what little I AM finding about the TOC situation isn't even applicable to what I'm doing!
Please tell me there is some help for this problem. Four or five years is way too long to wait with this many people in need. We all pay our $60 bucks each month. I feel like I'm paying for a headache!
I believe Douglas Waterfall has moved on within Adobe. This thread is three years old, maybe you should start a new one and explain again what your issue is.
Thank you, Derek. I'll do that.