CreativePro Forum

Return to Member Forum

• Author
  Posts
• • March 18, 2015 at 8:34 am #74014
    Margaret Hunter

    Participant

    Similar to another poster’s TOC problem, I am getting an error message about a Page Anchor not found when exporting to epub. I know it’s something to do with the index because if I delete the index it exports without errors. It’s always the same page anchor (number 94) but if I look at the link of hyperlinks there’s nothing with that number.

    Annoyingly, I can’t see any problem with the links that are exported as everything seems to be there.

    Is there any way I can find where the source of that no. 94 anchor is?

    Thanks!

    InDesign CC 2014, exporting to epub 3.0

  • March 19, 2015 at 2:31 am #74033
    Margaret Hunter

    Participant

    Edited

  • March 27, 2015 at 2:01 pm #74209
    Christine Glade

    Member

    I’m getting a similar error in my document can can’t seem to find any such reference. The epub still validates ok but it’s driving me nutz.

  • August 4, 2015 at 11:15 am #77134
    Ryan Scheife

    Member

    Too bad there as not been a solution to this. I have the same issue with my index causing the same error message during the output to ePub. The file validates fine, though some of the vendors are kicking the file back to me because of this. Ugh.

  • September 3, 2015 at 5:38 pm #77875
    Lisa May

    Member

    Have any of those who posted to this thread found a solution yet? I have the same issue 200 times over. I have a 240 page book (30 plus files compiled into a book file) with hundreds of index entries. The very last thing I did to this book was to update the index. Then I export to ePub. The exporting process informs me of over 200 “page anchor not found” errors. When I try to validate, I get over 200 “referenced resource missing in the package” all referring to the index. There is no way I can fix these one by one and I wouldn’t know where to start since InDesign built the index from the index markers minutes ago, then after exporting, InDesign cannot find those very same markers that are still in the very same place. Sounds like a bug. But I can’t deliver a file to a client if it won’t validate. Anyone with ideas?

  • September 4, 2015 at 6:06 am #77884
    David Blatner

    Keymaster

    What version of InDesign?

  • September 4, 2015 at 6:21 am #77885
    Lisa May

    Member

    I am using CC 2015. One of the fixes I tried was to update the software. I just downloaded the latest version of ID and still have the same problem. I think I might have found a clue though. I discovered in the ePub with the errors that wherever there is a page range for an index entry (66-67, rather than just 66), clicking on the first page in the range (66) is a working link but clicking on the second page (67) is not. Out of curiosity I counted how many entries in the index list a page range. Right around 200. I will be editing those in the index panel to see if that fixes the issue. Unless there is a way to tell InDesign to generate an index with only the first page in a range?

  • September 4, 2015 at 8:18 am #77888
    Michael Grossman

    Member

    I’m using Indesign CC 2015 to create epubs, then Kindle Previewer for a mobi file.
    There surely is a TOC issue when ID exports. The closet I came to solving it was by creating a new TOC via Layout->Table of Contents, the dropping the actual new page frame with TOC contents into the book’s page. It won’t anchor, but it will at least get a TOC to show up in the Kindle Previewer. If you try to anchor the page, it will rasterize, show up as art, and fail as a TOC. The problem I have with this Rube Goldberg bandaid procedure is that the TOC, since it’s not anchored, shows up as the book’s last page. I love InDesign and Adobe product. However since they stopped updating the Export to Kindle, all kinds of issue appear. Hey Adobe, get with it. Like it or not, Amazon’s Kindle format accounts for a majority of ebook sales. The epub conversion at the KDP Publish site is imperfect. Yet Amazon seems unwilling to update the Export to Kindle patch.
    Oh well. If anyone has experience this same issue and succeeded, I’d sure appreciate your help. Thanks – Michael

  • September 8, 2015 at 7:48 am #77965
    Kevin Callahan

    Participant

    MIchael, you’re halfway there using the method you describe to create the TOC.

    You can insert the created TOC text in place in the InDesign document. I often add it as a standalone, unthreaded page, after the Title Page. If the Title Page and TOC are the first, unthreaded, pages in the document, the EPUB export will make those 2 the first pages of your EPUB. (The reason your TOC is showing up at the end of the EPUB is probably because your whole book is threaded EXCEPT for the TOC; InDesign exports the first text box it finds moving in from the top left corner of a page, and includes that box’s entire thread of text, even if it’s 300 pages, until it moves on to the next text box on the page).

    There’s another approach: when exporting a document in which you’ve let InDesign create a TOC, point to that TOC in the export to epub dialog box. It’s in the first screen of the export process; in CC2015 it’s under Navigation TOC. This will generate the toc.xhtml, which is used for device navigation. But, you can also use it as your live, in-book TOC if you add it in order to the spine in the content.opf.

    Whichever method you use, make sure you have Landmarks designated in the toc.xhtml. Here’s a link explaining them: https://ebookflightdeck.com/handbook/landmarks

  • September 8, 2015 at 4:21 pm #77977
    Lisa May

    Member

    For anyone following this conversation now or in the future, I would like to provide at least one help on InDesign 2015 CC’s problem with index entries not found. My problem that I described above was entirely about the fact that the export to ePub does not seem to support index entries with a page range. In other words, when you create an index entry in ID and specify anything other than “Current Page” as the type, it works great for the index generated for the print version. But when you export that book to ePub, ID seems to be confused by the fact that there are two page numbers listed (for example, 14-16), but only one index marker (on page 14). So it generates an error “page anchor not found” for every one of the entries with the page range. In my book with the problems, I opened all of the book files and the index panel and I had to go through every entry in the index panel, double-clicking every entry with a page range and editing it to just “Current Page.” Then I was able to generate the new index and export to ePub and all 200 errors vanished. Unfortunately, I could not find this behavior described anywhere online, including Adobe’s help pages. It took me over 2 hours to trouble-shoot and another hour to individually edit 200 index entries. It would be really nice if Adobe found a work-around for this problem. A simple solution would be to give us a check box in the generate index dialog box that would override all individual index types to be “Current Page.” Then, at least the index entries would not have to be edited individually. And it would be great if this was documented in Adobe’s help.

  • August 12, 2016 at 7:20 am #87373
    Bob Doyle

    Member

    Lisa May,

    You have identified the problem perfectly. And I have the simple solution for you and others who have fixed the missing anchors one at a time.

    First, this is a only a problem when exporting a Reflowable EPUB. Indexes for Fixed Layout EPUBS have both ends of the page range as active links!

    The solution is to use BBEdit or Text Wrangler to do a search and replace in the index.xhtml file using a GREP expression.

    Here is the problem line in my book index.
    <p class=”Index-Body”>abduction 132–137

    Page 137 has an empty href=””.

    Here is the GREP expression

    Find: ([0-9]*)

    Replace: \1

    And here is the new line

    <p class=”Index-Body”>abduction 132–137

    The page range still has the 137, it still won’t be an active link, but it won’t throw an error in epub validation.

    To show you how the Fixed Layout does not have this problem, here is the code generated by InDesign.

    <p class=”Index-Body ParaOverride-1″><span id=”_idTextSpan130758″ class=”CharOverride-7″ style=”position:absolute;top:1146.24px;left:0px;letter-spacing:-0.23px;”>abduction </span>

    <span id=”_idTextSpan130759″ class=”CharOverride-7″ style=“position:absolute;top:1146.24px;left:927.39px;”>132</span>

    <span id=”_idTextSpan130760″ class=”CharOverride-7″ style=“position:absolute;top:1146.24px;left:1224.03px;”>–</span>
    <span id=”_idTextSpan130761″ class=”CharOverride-7″ style=”position:absolute;top:1146.24px;left:1331.15px;”>137</span>

    Both ends of the page range are active links in FXL EPUBS.

    My index had 598 missing page anchors, all repaired in a few seconds.

  • December 1, 2016 at 2:48 pm #90228
    Anonymous

    Inactive

    I found another solution.

    My document had some kind of glitch. So when I began pasting content into a new document, the hyperlinks palette went from empty to full. So, I deleted all the hyperlinks and my EPUB document outputted without the “Page Anchor not found” error message.

  • July 8, 2019 at 2:56 pm #117540
    Christine McNaull

    Member

    Thank you Lisa and Matthew McCullough (from another thread). You both provided clues that solved my problem. I do believe since then the updates have solved the range link problem.

• Author
  Posts