Assistance Required – Errors in Dev Tools for Responsive HTML5 Output

[sidwrites]

I am using RoboHelp to create online help files and generate Responsive HTML5 output presets. To continue the project previously managed by another writer, I imported the HTML files from the output folder, as no .rhpj files were available. Additionally, I do not have information on the exact RoboHelp version used by the previous writer.

I use SourceTree to push help file changes to the repository, and the help files are displaying correctly within the application. However, when inspecting the output in Developer Tools, multiple errors appear in the console (please refer to the attached screenshot).

Could you please assist me in resolving these errors? Let me know if any additional information is required.

Thank you.

[Jeff_Coatsworth · Accepted solution]

Let's get this straight - you have RH (what version? always mention that in a thread), but you have lost the source RH project that created Responsive HTML5 output previously, so you have created a new project and imported the output files into it - correct?
Ok - I would strongly try to find the source RH project - the approach you are taking (called reverse engineering - see https://www.grainge.org/RoboHelp/Reverse_Engineering/Reverse_Engineering.htm for Peter's advice on your situation) is going to mess up your project up and produce nothing but tears going forward.

[sidwrites]

Thank you Jeff! RH Version is 2022.5.28. Yes you are correct. But unfortunately, the previous writer system was flashed without backing up the files when he left. Any suggestions?

[Jeff_Coatsworth]

Peter spells it out on his page:

If frameless or responsive help was your only output, then I am sorry to say you are stuck. The best you can do is a manual rebuild.

1. Access the output and copy the text into a new project via a text editor. What you don't want is the code behind the content. Yes that does mean you have to then apply the styles, rework tables and so on.
2. Dropdowns and Expanding Text will need to be copied in separately.
3. Snippets and Variables will just be text.
4. See also "What Will Be Lost" below.

By now you will see why locating the source files is worth the effort.

[Peter Grainge]

Are you 100% sure that your predecessor did not have any backups on a server? Check with IT. I have seen scenarios where someone in your situation has had to get their line manager apply pressure on IT to help. Otherwise it is a long a painful process. IT should not flash a drive without taking a copy first. 

Use something like Pure Text (Microsoft Store - free) and you can paste in the output without the code. Images will have to come in separately. Any dropdowns must be expanded and their text copied in as well. Links will have to be created. @Jeff_Coatsworth was not exagerating.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[sidwrites]

Thank you so much Peter! I will do!

[Amebr]

You also mention Source Tree which I believe is a frontend for GIT source control. Double-check with the git admin that there is not a repository that contains the source files somewhere.

Usually only the source is kept in source control, not the output, although this is not an absolute rule - just that devs often get cranky about output clogging their nice clean source 🙂