Books, Topics Missing from TOC

[Cape_Ops]

Why when publishing and merging 2 projects, one of the projects does not completely publish?  When I publish each as a standalone project they each publish completely.

Additional Info - Using RoboHELP Server Web Administrator, if I uncheck the "Automatically merger projects of the same type" and then View each project seperately each Project is complete (the TOC for each is complete).  If I check the "Automatically merger projects of the same type" and view the merged Project one of the Projects is only partially viewable.  In other words the TOC does not contain all the project books and pages.  Unchecking the "Automatically merger projects of the same type" and the TOC is once again complete.

I applied a fix suggested by Adobe support and now I am getting the following message whenever I click on a Book in the TOC at any level, "Loading, click to cancel..."  BTW, clicking on the message does nothing.

[Peter Grainge]

I have moved this thread to the RoboServer forum hoping that someone here can help.

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

[RoboColum_n_]

Can we check whether the projects are merged before your publish or published separately and merged on the server. I always do the former and it works just fine. Also can you confirm what version of RH Server you have.

[johndaigle]

Hi, Cape Ops

As Adobe support probably indicated to you, this is a known issue and I am working with several other folks on a similar fix. Please email me off-forum at my profile address which can be found by clicking on my forum picture. I'd like to know more details so I can consolidate my support requests. I'll let you know what solutions Adobe is working on and post them here at that time. I would particularly like to know how many levels your TOC has (i.e. what level of "nested" books do you have?)

Thanks

John Daigle

Adobe Certified RoboHelp and Captivate Instructor

Evergreen, Colorado

www.showmethedemo.com

[Cape_Ops]

A new bug was found in RoboHelp 9 Server and the Adobe Support Team created a patch.  See Case #0185222590.