We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
I know the issue about an HHComponentActivator message appearing when trying to preview a topic has been previously discussed on the forum, but the solution offered only solves half of the problems that I am having.
Copying the eHlpDthm.js file from a blank project as suggested resolves the issue with the message appearing, but as one other user indicated in their post, any link in the topic that should display in an auto-sizing popup window does not appear. Copying the file does not resolve this problem for me. I used the View Source option when previewing a topic to look at the html code and noticed that the topic name in the path for the popup is replaced with an another name such as "rlt1F76" instead of "print_option." The name changes each time I preview the topic. Selecting the topic to display in a frame does not have the problem, only auto-sized and custom-sized popups.
I am using RoboHelp 10, specifically version 10.0.1.292.
Thanks in advance for your help.
When you preview from RoboHelp the process creates a temporary version of the topic. Each of these is assigned rlt as the first three letters and the others seem to be arbitrary and random.
As for the popup issue, you are on version 10 of the application and that means you are two versions behind. Have you ensured that you have applied any updates? Check the link below for updates.
Thanks for the reply Rick. I just find it odd that popups worked fine and then one day they didn't, likely the same day I got the HHComponentActivator message.
I had no idea the patches weren't installed when I clicked Updates on the Help menu. Applying the applicable updates had the following results:
I'll have to work on getting the company to update my RoboHelp, until then I'll limp on.
I just find it odd that popups worked fine and then one day they didn't, likely the same day I got the HHComponentActivator message.
Indeed, such is the oddness encountered when a browser update suddenly changes that playing field and the RoboHelp code no longer knows how to handle the changes!