Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

generated TOC navigation bar no longer works in Responsive HTML5

Community Beginner ,
Oct 26, 2023 Oct 26, 2023

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?

4.6K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , May 15, 2024 May 15, 2024

I think the problem is in my scripted files and it's not a FrameMaker or publishing problem.

Translate
Community Expert ,
May 14, 2024 May 14, 2024

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 14, 2024 May 14, 2024

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?

html_toc_link.png

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 14, 2024 May 14, 2024

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 14, 2024 May 14, 2024

You can't get what you need from the Fm side of the equation.

  1. Go to your HTML5 output.
  2. Use the INSPECT (in Chrome) or similar feature to display the code associated with the TOC.
  3. Reply and paste the specific HTML code associated with the link here.
-Matt Sullivan
FrameMaker Course Creator, Author, Trainer, Consultant
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

I am currently using the default.sts supplied. But the error is the same. Is this the desired HTML code?

html_toc_item.png

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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? 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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.


Bjørn Smalbro - FrameMaker.dk
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

I created new settings with New, did not change the default settings and saved them. But unfortunately the error remains the same.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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.


Bjørn Smalbro - FrameMaker.dk
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

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"

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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).

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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.


Bjørn Smalbro - FrameMaker.dk
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

All chapter folders look allright and contain an html file each.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

... 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?


Bjørn Smalbro - FrameMaker.dk
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

All looks fine. Clicking an index item works fine and display the correct html file:

techwrite_0-1715782151155.png

Clicking an TOC item shows the "wrong" path below and causes the error:

techwrite_1-1715782228998.png

html_error.png

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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?

-Matt Sullivan
FrameMaker Course Creator, Author, Trainer, Consultant
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

There is no CMS in use. The files are stored in directories on a file server.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

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.)

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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??

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2024 May 15, 2024

I have copied the book with all the files. The book update was correct, PDF is correct, only HTML5 still returns the same error.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 15, 2024 May 15, 2024

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.

-Matt Sullivan
FrameMaker Course Creator, Author, Trainer, Consultant
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines