Copy link to clipboard
Copied
We are using RoboHelp 9 on a Windows 7 platform.
We are seeing what appears to be inconsistent behavior from RoboHelp when setting up a RoboHelp project.
These are the steps we follow:
Sometimes the Content Categories node has a child node called Content <Default>, and sometimes that child node is not there.
As far as we know, we are following the exact same steps either way.
I am hoping someone who knows RoboHelp can tell us a simple fix to see the Content <Default> child node every single time.
Thank you in advance!
Tim
Copy link to clipboard
Copied
Never seen that, but are you all up to date on RH 9 patches?
Copy link to clipboard
Copied
Hi Jeff, thanks for the swift response.
We have implemented the Adobe Technical Communication Suite 3.5, which came with RoboHelp version 9.0.2.271. When I look for RoboHelp patches on the Adobe Web site, there is no patch for that version.
In RoboHelp, when I select Help > Updates, the Adobe Application Manager window appears, and tells me there is an update available for Photoshop Camera Raw, which I don't know anything about. RoboHelp does not show up as having an update available.
So, to answer your question, I have not taken any updates.
Tim
Copy link to clipboard
Copied
Hi Tim
I'm aware that RoboHelp team did issue a recent update. But like you, I was shocked to find that it wasn't listed when I clicked Help > Updates from the menu. That certainly seems the logical approach, no?
I know sometimes updates are released that require you to download and replace specific DLLs and whatnot. Hopefully this one isn't that way, but it may well be.
I'll ask Peter to confirm.
Cheers... Rick
Copy link to clipboard
Copied
Rick
This poster is on Rh9. No recent patch for that.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
Then you're up to date; maybe your WebHelp SSL is damaged? Try creating a new one (don't copy an existing one) and using it to see if it's fixed.
Copy link to clipboard
Copied
Hi Jeff,
We were creating a new project for every product. So...we were already creating a new WebHelp SSL for each product.
Your post gave me an idea for a work-around, and this is what I did:
Everything is looking good! Thank you again.
Tim