Participating Frequently

Question

Broken cross references in FrameMaker Responsive HTML5 output

34 replies
3662 views
Translate

I'm trying to generate Responsive HTML5 output using the Publish command in FrameMaker and some of the cross references are broken. Whether the link works depends on the order of the files in the FrameMaker book. If the cross reference links to a file later in the book, it works. If the cross reference links to a previous file, the link is broken. Has anyone had a similiar issue and found a fix?

Responsive HTML5

This topic is closed to new replies. Start a new post to keep the conversation going.

Matt-Tech Comm Tools

Community Expert

(moved Hyperlink marker comment to a new thread)

Translate

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant

Matt-Tech Comm Tools

Community Expert

I've found that the characters used in filenames and path names can cause EPUB and HTML to fail. Do you have non-alphanumeric characters in file and path names?

I've also found that manual hyperlink markers (using Specify Named Destination) will cause issues when non-alpha characters are used.

If they exist, try renaming files and folders to remedy.

-Matt

Translate

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant

D

defaultmdgbu8fseg0r

Known Participant

Hi,

Thanks for this suggestion. I have now tried removing all hyphens and underscores from the path and filenames:

But I still see the same behaviour in the HTML.

However, after spending some time with Adobe Support we have noticed something: if the target of the link is 'before' the current position but within the HTML output of an *.fm file, they work; whereas, if the target of the link is 'before' the current position and in the HTML output of a different *.fm, they do not work. I have tried to show this using yellow highlights (within an *.fm file) and pink highlights (between *.fm files).

The Database Stored Procedures page opens but the Check the Pods and Check the Logs of the Pods pages do not.

I'm one of three writers, working in different places from each other, and on five products. We are all seeing this issue using FM2020. We are using book-in-book files to publish our document sets. But the problem exists for single guides too.

We don't use manual hyperlink markers. We're fully paid up members of the 'Cross-Reference pod club'.

Translate

C

ch41785421Author

Participating Frequently

Yes, that is the same issue we are facing. If the target link is in the same *.fm file, it works. If the target link is in a different *.fm file "before" the current *.fm file, it fails. If the target link is in a different *.fm file "after" the current *.fm file, it works. Did you get any resolution to the issue?

Translate

pulkitn

Adobe Employee

There are no hidden settings and cross-reference added in standard way should work as is in html5 , If you are facing any kind of issues while generating html5 on latest FM2020 patch , I suggest you to kindly contact Support team at tcssup@adobe.com .They will assist you best there .

-Pulkit Nagpal

Translate

D

defaultmdgbu8fseg0r

Known Participant

Thanks Pulkit.
I have now emailed Adobe Support.

Translate

S

Sabarish Katta

Participant

Even we are facing the similar issue in our project. 😞

Translate

Jeff_Coatsworth

Community Expert

So you're each copying all the FM files locally to work on them (taking turns I hope)

Translate

Jeff_Coatsworth

Community Expert

Is there any source control involved in this? The fact that it worked for someone else sounds like issues with fully checking out the FM files.

Translate

C

ch41785421Author

Participating Frequently

No source control. All files are local to our PCs. I'm wondering if there is some "hidden" setting that is set differently?

Translate

Jeff_Coatsworth

Community Expert

What version of FM? Are you all patched up? I've not heard of that issue occuring, but be warned that there is a limit to how long the path & filename of the resulting HTML file can be without breaking the href= links (discovered that one when I was importing FM content in RH and some xref links on the same topic page would work & others wouldn't - once I shortened up the paths in my FM files, they worked just fine; I mention this because the FM Publish engine is using RH under the hood).

Translate

C

ch41785421Author

Participating Frequently

Thanks! I'm using Version: 16.0.3.979, which I believe is the latest. I'll try shortening the path & filename. But the same cross reference will work or not work depending on the order of the files in the book, I have not changed the path or filename. One of my co-worker's was able to get the cross references to work if the source file is open while generating the Responsive HTML. But this workaround does not work for every book.

Translate

D

defaultmdgbu8fseg0r

Known Participant

Hi,
We are also facing this issue. I've tried the workaround you suggested, of generating the HTML with all the source files open but that didn't help. I realise too that positioning is key; like you found, if the target of the link is 'after' the current position in the HTML it works, and in contrast if the source of the link is 'before' the current position it fails. Have you been able to find a solution for this or have you raised a case with Adobe?

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.