Hi Al.
I am still struggling to follow this. Can we step back to
some basics.
In a merge you have a parent and any number of children. The
parent can have content but if you look at the merged webhelp topic
on my site, I recommend that contain is just another child project,
a sort of big brother if you like. The parent is then just a shell.
However that's not essential if you don't have many parent / child
links and can live with the false broken link reports you will get
in the parent.
That's the source material. Now let's look at how you output
it.
You point the parent to a folder we will call WebHelp. It can
be within the !SSL! folder where it is by default but as Leon
pointed out, it can be anywhere. When you generate the parent to
that it also creates folders for each child project.
You then output each child to its folder and end up with a
complete output. At that point you can copy that to a server and
everyone sees everything. However you can also put on the server a
setup with the parent and just some of the children and it will
work fine.
Are you perhaps using conditional tags to create different
mixes rather than just not delivering one or more children?
Also you are talking about buttons. What buttons? These are
something you have added?
It sounds like you are providing some buttons to access
different things whereas you could allow access via the TOC and
that would only contain whichever children you have assembled for
that build.
Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.