Skip to main content
N
nicholasb56967193
Known Participant
September 6, 2023
Question

Broken links in HTML5 TOC

  • September 6, 2023
  • 2 replies
  • 426 views

I have a fairly large book (1500 pages) that I am trying to publish in HTML5. This project is years old, the HTML5 has been working for years, and this bug seems to have only cropped up in the last update.

 

When the HTML5 is published some top level titles in the TOC don't point to the local output folder, but to c:\program files, where obviously the files are not found.

 

In the generated output, which is all where it should be, there is the whxdata folder with all toc*.js files for the TOC and the URLs inside them all have something like this:
url=\"../../../../../../../../c:/program files/adobe/adobe framemaker 2022/filters#7286750bc-500\"

 

Yes, I'm using the latest update.

Dynamic filters are disabled in the STS.

Nothing has changed in the STS file or the TOC file since the last time I generated the HTML5.

There is nothing noteworthy in the log files.

After decades of using FrameMaker, finding myself having to spend hours fighting FM's inconsistencies and bugs in the late delivery stages of a project is getting increasingly frustrating.

This topic has been closed for replies.

2 replies

N
nicholasb56967193Author
Known Participant
September 14, 2023

I "fixed" the issue by removing the TOC file from the book. This at least forces the TOC to generate properly, but loses some folder-level headings that I had in there.

I wish FM would generate the TOC based on a single method rather than trying to guess headings through font sizes, indents, TOC files, folders and chapter levels in the book. 

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    September 14, 2023

    This is where the FM to RH workflow is better than the internal Publish model - in that workflow you choose the FM TOC that you want to create in the RH project.

    F
    Community Expert
    FrameMaker-dkCommunity Expert
    Community Expert
    September 7, 2023

    Have you moved the folder where the project is placed on the local drive? It looks to as if it might have something to to with some url's growing too long for Windows to handle. If you have long file names and long url paths you may eventually exceed what Windows can handle and then errors start happening. Just a suggestion - may not be the solution!

    Bjørn Smalbro - FrameMaker.dk
    N
    nicholasb56967193Author
    Known Participant
    September 7, 2023

    Thanks for your reply. No, I haven't changed the location and the file paths aren't particularly long. The output path is only  "D:\FMOutput" and the project files are in a short path too. In fact the buggy "../../../../../../../../c:/program files/adobe...." path is longer than the correct path.

      W
      Community Expert
      Winfried RengCommunity Expert
      Community Expert
      September 7, 2023

      Could it be that this path is somewhere listed in the sts file? I do not remember, if the sts file is a zip file or a text file. You might have to change the file name extension to open it. Then you can open it with a text editor and check its content.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices