TOC not showing up in HTML and Index and Glossary showing up

[bluegiraffe24]

When I publish to Responsive HTML5 in unstructured FrameMaker Version 13.0.5.547 the TOC doesn't come through even though I have it marked as "true" in the settings.

I don't want the Index or Glossary to come through, so I have them set to "false" but the icons for them are still coming through into HTML.

[doug1120]

Are you expecting the TOC to display on on page, like they do in a PDF?  If so, I don't think you can get that in HTML.  The TOC displays on the left in a a column, at least for me.  It never displays on the right.

[Jeff_Coatsworth]

Depends on the layout used and how much you want your web developers to mess around with them.

[bluegiraffe24]

Yes, that's what I was expecting. If it's not possible for the TOC to come through as a page, that's fine.

[bluegiraffe24]

We don't have web developers. I'm it. I chose "false" for Index, Glossary, and Filter, and the icons for them continue to show up so users can click on them and then go to a useless area. That makes no sense. FrameMaker doesn't seem to be working correctly.

[Matt-Tech Comm Tools]

The TRUE and FALSE settings control the visibility of the icons for those components in your HTML output.

When set to TRUE, the icons will take you to those components, which generally get processed into special areas on the output, rather than displaying as actual topics. 

If you don't have a glossary, for example, you should set Show Glossary to False so that your users aren't confused by the icon's inclusion in your output.

[milliee62922081]

I'm pretty sure that a recent Windows update has made my Responsive HTML output get all messed up. Perhaps yours has also fallen foul of something similar? Has this worked before?

[Matt-Tech Comm Tools]

What do you mean by all messed up?

[milliee62922081]

Right after a Windows update my HTML output was showing a cross on some chapters rather than content and other pages that were shown in the TOC were not accessible by clicking on them. Numbering that previously worked started behaving differently too. Yesterday I found out about saving FM files as .MIF then back to FM and that seems to have sorted out most of the issues. I fixed the numbering by taking a different approach with it.