3 Replies Latest reply on Aug 6, 2007 11:47 AM by Peter Grainge

    Merged WebHelp RH6 projects

    factormax
      I have three projects I want to merge, and thought that if I set up my primary file TOC to contain them all, then generated and published them all, and that if one of the secondary projects was not in the \merged projects folder then the TOC simply would not show any TOC entries for that one, but would show the usual TOC for the other projects. However, when I removed one of the merged projects to test this the TOC was entirely blank: nothing.
      Is there a way to do this? the reason is the I will not know ahead of time which of the two secondary projects (if any) are installed (they are installed to the \merged projects folder by Installshield), so I wanted to just include their markers in the primary TOC and then thought their TOC contents would display when the Help is opened on the fly.
        • 1. Re: Merged WebHelp RH6 projects
          Peter Grainge Adobe Community Professional (Moderator)
          It sounds like your parent TOC contains the TOC entries for the child projects instead of references to the child TOCs.

          See the topic on my site about Merged WebHelp and see how I explain creating the TOC.

          • 2. Re: Merged WebHelp RH6 projects
            factormax Level 1
            Thanks for your reply and samples, but after all I had done the merge correctly (separate TOCs in the merged projects). Here was the issue: my default browser if Firefox and it takes from 5 to 10 seconds for the TOC to refresh if one of the child projects is not installed. I was waiting only a few seconds and, not seeing the TOC content, just closed the browser thinking the TOC was broken. I opened your samples in Firefox and IE and see the same slow Firefox refresh. Bad Firefox 2.0.0.6. Have you encountered this before?
            • 3. Re: Merged WebHelp RH6 projects
              Peter Grainge Adobe Community Professional (Moderator)
              Issues with Firefox loading have been reported and are documented on my site under Browsers. There are many workarounds that various people have contributed.

              Not aware of the issue being made worse by not including a child project. Haven't seen reports of that. My own merged webhelp is always delivered in full. We merge because of project size.