Skip to main content
September 16, 2013
Answered

New books and topics don't appear in the ToC after generated in DHTML (RoboHelp v8)

  • September 16, 2013
  • 1 reply
  • 785 views

Until recently, when I wanted to add a topic to a book in the Table of Contents, I just dragged it from the Project Manager into the Table of Contents.  I'm not sure what is different now, but the new topics appear in the Table of Contents pod but not in the generated DHTML.  To make it more confusing, to me anyway, some newly added topics DO show.

This topic has been closed for replies.
Correct answer Captiv8r

In the Project Manager pod under Table of Contents, I have only one entry.  I cleared the cache and then copied the !SSL! folder to the server. 

The topics and book marked "not included" above still do not appear.  The topic marked "included" still appears.

I recently did a massive search and replace.  Could have anything to do with my current problem?


Hi there

I do suppose "massive" searches and replaces could affect things. But we need to check a few other things first.

When you examine the SSL recipe, are you using any kind of a Conditional Build Expression? If so, perhaps you have tagged the content and it's not appearing for that reason.

Cheers... Rick

1 reply

Captiv8r
Legend
September 16, 2013

Hi there

How do you get the content from the output folder to the server? Do you manually copy it or are you using the Publishing feature? For that matter, where exactly *IS* the content when you are trying to view it?

Perhaps you need to clear the browser cache?

Cheers... Rick

September 17, 2013

After I generate WebHelp, in RoboHelp a box pops up, "Result: WebHelp has been successfully generated".  I click "View Result", but I don't see some of the newly added topics.  Because I don't see the new things in the preview, I haven't copied the files to the server yet.

Captiv8r
Legend
September 17, 2013

@Rick - I did say "may get" not "will get" - YMMV ;>)


True that, but you were suggesting that this is a "preview", when it isn't. It's actually viewing the output in pretty much exactly the same way you were suggesting. Hence, the clarification.