Copy link to clipboard
Copied
Hello,
when generating HTML5 in the current version 16.05.1096, the generated TOC navigation bar no longer works. The faulty link does not lead to the .htm or the scripted ID, but to the programme folder:
file:///C:/c:/program%20files/adobe/adobe%20framemaker%2020/filters?rhtocid=_4#998464bc-3
How can this be fixed?
I think the problem is in my scripted files and it's not a FrameMaker or publishing problem.
Copy link to clipboard
Copied
I wasn't seeing any code in @techwrite 's TOC - just looked like some German words pointing to a topic from what I could see.
Copy link to clipboard
Copied
I do not use any code in the FrameMaker document, only texts and images. The double c: in the path specification in the TOC makes me a bit suspicious: file:///C:/c:/... Or does that have no meaning?
 
Copy link to clipboard
Copied
Well, that TOC item shouldn't be trying to point to anything in that C:\program files folder - that's the mal-formed part we're trying to figure out how it ended up like that - it should be pointing to your index page and the path to the topic.
Copy link to clipboard
Copied
You can't get what you need from the Fm side of the equation.
Copy link to clipboard
Copied
I am currently using the default.sts supplied. But the error is the same. Is this the desired HTML code?
 
Copy link to clipboard
Copied
If that's from the output, then yes, that's what Matt wanted to see. Clearly it's got a messed up href= part to it. The question becomes - "where is it getting that from from?"
I'd be tempted to create a new settings file and see if it generates the correct link. You haven't got any conditional text or anything applied to that TOC destination in FM?
Copy link to clipboard
Copied
I'm with @Jeff_Coatsworth on this one. The settings files are not very robust and a change of FM versions may easily break one. Absolutely worth a try.
Copy link to clipboard
Copied
Yes, this is directly after publishing when displaying the generated HTML text. I have not applied anything to the TOC target. It is a normal, automatically generated FM TOC.
Copy link to clipboard
Copied
I created new settings with New, did not change the default settings and saved them. But unfortunately the error remains the same.
Copy link to clipboard
Copied
Wow - bizarre. I'd suggest it's time to contact the FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.
Copy link to clipboard
Copied
Has the HTML5 publishing worked formerly at the same location on the harddrive? I have sometimes experienced that the generated url's became too long. Meaning that if you have a url like this c:users/user/documents/jobname/folderthisandathat/folderthatandthat/andohter/foldernames/ ..... You may end up havin too many characters for Windows to handle in the resulting HTML5 url.
Copy link to clipboard
Copied
I created HTML5 for the last time in April 2020. That worked without any problems. Since then, hardware and the FrameMaker version have changed. But PDF creation has been sufficient since then. But now HTML5 is also desired.
The path to one of the generated HTML files is, for example: "C:\Users\123456789\FMOutput\archivelink_filechecker_tec\Responsive HTML5\archivelink_filechecker_tec\archivelink_filechecker_tec_changes\archivelink_filechecker_tec_changes.htm"
Copy link to clipboard
Copied
That's really long - I'd look at creating into a C:\FMOut\ folder directly (and maybe even shorten up my FM content location too).
Copy link to clipboard
Copied
Output path "C:\h5" results in files like "C:\h5\tst_html_int\Responsive HTML5\tst_html_int\tst_html_int_howto\tst_html_int_howto.htm" with the same error.
Copy link to clipboard
Copied
Does FrameMaker actually generate any files in the chapters directories? If you use File Explorer and navigate to the output dirctory "Responsive HTML5\". That directory is supposed to hold the hierarchy of your FM books chapter. So you will have a folder, with a number of other folders inside - each folder havin the name of the FM chapter. Please check whether the chapter folders look allright. They are supposed to contain an html file each.
Copy link to clipboard
Copied
All chapter folders look allright and contain an html file each.
Copy link to clipboard
Copied
... and if you open the html files - do they look right? I have a bit of trouble understanding how the main HTML5 site looks for you... If you click the index.html in the "Responsive HTML5" folder - what happens?
Copy link to clipboard
Copied
All looks fine. Clicking an index item works fine and display the correct html file:
Clicking an TOC item shows the "wrong" path below and causes the error:
 
Copy link to clipboard
Copied
The long path in the html is the key. Are your books , chapters or output path pointing to a server location? Is there some sort of CMS in use?
Copy link to clipboard
Copied
There is no CMS in use. The files are stored in directories on a file server.
Copy link to clipboard
Copied
As a test, try taking a copy of the FM files and putting them on your c:\ drive preserving their internal folder structure & then generate from there to that shortened C:\FMout\ location.
Copy link to clipboard
Copied
I copied the FM book to c:\h5\fm_h5\h5_int.book with output on c:\h5... It returns the same error.
(PDF generation continues to work with correct TOC links.)
Copy link to clipboard
Copied
If you copied it like that, it should have broke all the links inside FM when you updated - wasn't your FM content a long string of German text??
Copy link to clipboard
Copied
I have copied the book with all the files. The book update was correct, PDF is correct, only HTML5 still returns the same error.
Copy link to clipboard
Copied
Let's figure out if it is the files or the Publish process...
Go to Help > Samples... and copy the UserGuide(Arabic,English,Hebrew) directory to a writeable directory on your local machine.
Will that publish successfully to HTML5?
If yes, the issue is with your files or their location.
If no, it's with FrameMaker and/or your Publish config.
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more