Captiv8r I was experiencing the same problem as thread #TOC Navigation pane doesn't show in WebHelp Rh2015 , however, when I generate my WebHelp (in RH 9), "....index.html" isn't trucated on my start page file name, and appears correctly prior to publishing. Only when I publish to SharePoint 2013 does it hide the TOC pane. The "Show" link isn't visible on the start page - just the start page that doesn't have any links for the user to navigate. Can you perform your magic for this one?
Can you post us a screenshot of what you're talking about? Maybe a shot of your SSL WebHelp layout screens? Use the forum's web interface to post images.
Here you go, Jeff. Thank you!@
So what happens when you open up that TM_System_Updates.htm file? We kind of need to see what you've got indicated in Content Categories page and what it appears like in your browser (BTW - RH9 will be totally incapable of displaying WebHelp correctly in new versions of browser due to changes in browser security - you need to either manually apply some hacks or move up to RH2015).
When I click on the link, this page opens up:
these are my settings for the Content Categories:
What are the hacks you speak of? Thank you. 🙂
Hmm, so it looks like you've got your index page and your default topic pointing to the same file. I'm not sure if that's having an impact or not - I've never tried that; my projects are usually "project_name_index.htm" and "Welcome" or some other default landing page. Do you have a TOC created? I see you've told the SSL recipe to use the default one, but if it's empty, I'm not sure what you'd get. Try loading one of the sample projects included with RH and generate it to see if its TOC is showing up..
[Edit] - re:hacks - see https://www.wvanweelden.eu/articles/robohelp-patches-and-updates
Bit of a backstory on this. I'm not sure what version of RoboHelp changed the behavior, but earlier versions of the product would create WebHelp output where the start page was named identically to the project. So perhaps you created a new blank project named Foo. When you went to create WebHelp, the start page for the WebHelp would be Foo.htm.
I remember suggesting to anyone that would listen, that index.htm would be much better. Through the years I noticed a fair number of people that would do as you are suggesting. They would create a topic in their system named Foo.htm and then nominate that topic to be the Default Topic.
As you might imagine, this would cause a conflict because when WebHelp was generated, you had a Foo.htm that is supposed to be the name of the WebHelp start page, and another Foo.htm that is supposed to be the name of the default topic. And because it is impossible to have two files using the same exact file name, RoboHelp would typically rename one of them.
If memory serves, RoboHelp modified the file name of the Default Topic, because the name set in the WebHelp recipe seemed to supercede it.
So this likely explains part of what you are seeing. Personally, I'd suggest changing the WebHelp start page name to index.htm. Certainly won't hurt anything. But I'm also very skeptical that it will also resolve the issue here. My gut says they need to bite the bullet and upgrade. And really, if you are generating browser based help, it's only logical to keep up with all the latest changes.
I figured out the problem -- for some reason a copy of all the web help SSL files existed outside of the SSL folder and that is what I copied to the FTP server. Once I copied the contents of the SSL folder, everything worked. Thank you all for your help.