Are you publishing your content to and delivering it from RoboHelp Server?
No, we don't use RH Server. We generate the help locally and copy it over to our publishing server.
Perhaps therein lies the issue. You said you are creating WebHelp Pro output. That output is specifically designed to work only in conjunction with RoboHelp Server. Try generating WebHelp instead and see if the problem disappears.
Thank you, Rick! We will give that a try.
We had used WebHelp Pro output in the same manner when we had RH9, and used the same process without this issue. Do you know if this is a new specification of WebHelp Pro for RH10?
If by "new specification" you mean that WebHelp Pro should only be used with RoboHelp Server, that would be a NO. It's always been the case that the "Pro" output was intended for use with RoboHelp Server. Now it could well be that RoboHelp 10 Pro output isn't as "forgiving" as earlier versions have been. I'm not sure.
Unfortunately we see so so many folks just gravitate right toward the "Pro" output in the misguided belief that it is somehow better or has more bells and whistles than the basic WebHelp has. But that's never been the case. What HAS always been the case is that the code driving things has been configured to work with the code on the RoboHelp server.
One change that I believe has occurred has been a renaming of the XML files that are created. So that may factor in here. I'm not sure. It might be best for you to just generate WebHelp output, then wholesale delete all the files from the server and publish fresh.