Skip to main content
Inspiring
April 28, 2022
Question

Publisher hypertext and cross-reference links not working

  • April 28, 2022
  • 6 replies
  • 2974 views

I am using FM 16.04 to create HTML5 help. Although hypertext and cross-reference links work in FM and PDF output (via Publisher), they are often broken in the OLH.

As far as I can tell there is nothing wrong with the links when I examine the HTML in Notepad.

    This topic has been closed for replies.

    6 replies

    Community Expert
    July 10, 2023

    I have just made a quick test with two types of links. 

    1.  A cross reference from the main textflow of chapter 1 to a text frame inside an anchored frame in chapter two. PDF works fine - HTML5 is broken
    2.  A hotspot inside an anchored frame in the main textflow of chapter 1 linking to a textframe insiden an anchored frame in chapter two. PDF works fine - HTML5 is broken.

    If this is a case similar to yours, I would consider it a bug. This kind of error makes i impossible to, for instance, have hyperlinks in bubble texts on technical drawings.

    Bjørn Smalbro - FrameMaker.dk
    Inspiring
    August 4, 2023

    I guess this problem still persists... I've been trying to fix links in my HTML5 output which seem to be working perfectly in the PDF file. In the HTML5 output, the links disappear entirely... A very annoying problem!

    Jeff_Coatsworth
    Community Expert
    Community Expert
    August 4, 2023

    Did they contain any of the funky text characters that Matt mentioned?

    Matt-Tech Comm Tools
    Community Expert
    Community Expert
    May 4, 2022
    • what are examples of the hypertext markers and the xref-ed headings?
    • what is the html code produced in the output?
    -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
    Inspiring
    May 4, 2022

    I have cross-references to headings and table titles only. I have "gotolink" hypertext markers jumping to named destinations within the same book. Everything works within FM and the PDF created by Publisher.

     

    Community Expert
    May 3, 2022

    I believe the feature is broken. I have had the same problem and the conclusion was that hypertext just did not pass over into HTML5. I may be wrong though.

    Bjørn Smalbro - FrameMaker.dk
    Inspiring
    May 4, 2022

    Wow! That's quite a bug if true! I'm about to call Adobe TCS support to help sort this out. I am running way behind on my project.

    Community Expert
    April 30, 2022

    Can you post some of your broken links and if possible also, how they should look like?

    And as a comparison also the same for a good link?

    Inspiring
    May 3, 2022

    Unfortunately the content is proprietary. However, I'll create a new file and post that soon. Is it possible for TOC markers to "mask" the cross-ref markers? I am also finding that some index markers are also coincident, position-wize, with cross-ref markers.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    April 29, 2022

    Another thing to check is the total path + filename length of the link targets - FM doesn't have an issue but the RH publish engine certainly does. You can test by moving a copy of your FM content to a nice short path off your C:\ drive and looking at the links that were "bad" before.

    Inspiring
    April 29, 2022

    I moved the source files to the C: drive but unfortunatly got the same result.

    Even within the HTML5 output of the same FM file, I get a "Page Not Found" error even though the target topic does exist.

    Community Expert
    April 29, 2022

    Hi CaptLauren,

     

    Are the targets of these cross-references and hyperlinks in the same book? Or do they point to other books? This would not work.

     

    Best regards

     

    Winfried

    Jeff_Coatsworth
    Community Expert
    Community Expert
    April 29, 2022

    They should work (I think) if you employ the "book of books" strategy.

    Inspiring
    April 29, 2022

    On a related issue, when I added a book as a sub book, none of the links from the sub book to the parent book files worked. I believe that Adobe recognizes this as a problem.

    So, in Explorer, I created a child of the folder that contains the main book source files. Then I added each of the FM files in the child folder to the book individually.  The links worked in FM and in PDF, but not when run through Publisher.

    I will now try to shorten the paths to the source FM files and see what happens. At the moment they are a bit "deep" in the directory structure.

    I appreciate all your suggestions and will keep everyone posted about the results.