Merging FlashHelp/FlashHelp Pro

Question

I have published a mergedproject in the FlashHelp output
using RH7 to the RHServer 7. It merges the TOC seamless for all
projects listed in the mergedproject folder. The master is a shell
only. The html topic in there simply redirects to an intro topic
(located in a child project). The Index works fine and you can see
all the index terms regardless of the child project where they are
located. I only have 2 issues at this point:
1) The glossary term displays 2-4 definitions. It's like if
the term is found in all 4 child projects, it lists them all. Each
child project has it's own glossary. Anyone know why? I don't want
to merge the glossary to one as the child projects will continue to
be added.
2) The search function does not seem to be working. I had it
working once, but then I turned off all the glossaries
to see if I could get the duplicating definitions to stop.
When I reactivated them, the search still does not work. So not
sure there is a correlation there.
I found this thread that talked about 3 files that need to be
in the FlashHelp output:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=65&catid=447&threadid =1324503&highlight_key=y&keyword1=merged%20projects
In this thread it states that the output should have these
folders and associated file:
whdata
whgdata
whxdata
I have the last 2 in the list but not the first one whdata.
How do I get the whdata folder/files to generate (I looked in the
SSL output folder, but it's not there either for any of the
projects? And does anyone know what these files are for?
Peter -- thanks for your topic on Merging WebHelp, works for
FlashHelp 7 too. I created a master project with multiple masters
and multiple children. This is soo cool. The Parents_Project has 6
masters (containers) and 4 (and growing) children projects. The
only difference is that I had to point to the mastername.htm versus
the index_childname.htm. However, the mastername.htm calls that
index page and other than the glossary and search issues listed
above, things work wonderfully.
Sorry, I digressed again. Now back to our regularly schedule
issue.
Cindy

Answer 1

Peter -- let's drop the whole FlashHelp Pro for the moment.
Yes, I understand the different outputs. I am outputing FlashHelp
to our internal server which just also happens to have Server 7 on
it. I don't know that the server piece is or is not interferring
with FlashHelp. All I know is this is how we have always published
our FlashHelp to the server and that server has always had RH
Server on it. The only way we have ever gotton FlashHelp to work is
to publish it to the server in this path Adobe\RoboHelp Server
7\Servers\1\Projects.
Now maybe FlashHelp shouldn't be here, but like I said it was
the only way that we could deploy the help where everyone could see
it. Before merging we hade 4 different modules and you would just
select the module you wanted (i.e., HR or Payroll). Now we've
conditionalized by audience and merged the help. So a call rep can
see what they do both in the HR and Payroll system without having
to go out and select the other project.
So should the FlashHelp be somewhere else? I suppose, but the
most logical place was in the path listed above. Near as I can tell
there wasn't any issue with doing it this way and the help worked
without any problem. So when we upgraded to 7 we just kept it the
same way.
The only difference now is that I am merging the FlashHelp
and using the conditionalize build tags. Yes, I have published
locally (FlashHelp). There are no issues publishing, and the search
works, but the glossary does not work locally or on the server.
Cindy