Skip to main content
Inspiring
July 20, 2021
Question

PDF publishing from FrameMaker - Links do not work

  • July 20, 2021
  • 1 reply
  • 2616 views

I am publishing two Frame documents that have cross-reference links from one (Owners' Manual) to the other (Sales and Operations Manual).  Currently, both sets of FrameMaker files reside on an internal server in separate folders. The FrameMaker links work on the internal server, but do not work between the published PDFs on our internal or external server.

 

When I publish as a PDF, none of the links work on the source document (Owners' Manual) and the destination document (Sales and Operations Manual).  I have tried publishing as a PDF and also tried File > Publish from the main menu.

 

I get the following error when I edit the hyperlinks and save:

iManage plugin for Acrobat has failed to write the alternative data stream.

 

In my case, I have moved the PDF files into one folder and tried to edit the sourse PDF document's link to point to the topic in the destination PDF.  Haven't found a solution, yet.  Any help would be appreciated. Also, I need to eliminate the path that was used on our internal drive, so that the files can be published from any folder on an external server, similar to HTML, where I can use .../folder_name/filename. As you know, in this path, I can use any folder name to access the root.

 

Thanks!

    This topic has been closed for replies.

    1 reply

    Inspiring
    July 20, 2021

    Another note to add is that I am not accessing the files from iManage.  They are on an internal server only...S:/ drive.

    frameexpert
    Community Expert
    Community Expert
    July 21, 2021

    When you insert your cross-references between the files, make sure they have the same relative location to each other that they will have when you place the PDFs in the final location.

    Bob_Niland
    Community Expert
    Community Expert
    July 21, 2021

    Or use fully qualified URLs that point to where the documents will {always} be served from. This, however, will also always result in use of the link hitting the internet.

     

    Perhaps the ideal relative location is ./ (same directory). This can work for both served and local-copy PDFs.

     

    But pdf-2-pdf links, cannot today be relied on to always work (compared to internal PDF links, which can … if the PDF reader supports them, and not all do, esp. on phones).

     

    Perhaps some future link enhancement will include fall-back:
    primary: ./otherdoc.pdf
    alternate: https://domain.tld/support/manuals/morepaths/…/otherdoc.pdf