Upgrade from RoboHelp 10 to RoboHelp 2020 results in broken links in more than half of toppics

New Here ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

I have for many years worked with RoboHelp 10 in one company. We have now been taken over by another company and have finally invested in a newer version: RoboHelp 2020. 

 

Unfortunately upgrading the project has resulted in extremely many broken topic links. Actually only a few of them have been converted properly. There are about 800 topics needing to get their link fixed and there just MUST be a better way than starting over from scratch. There were no broken links in the project before upgrading. It is only used for online help, not for print.

 

What can have gone wrong? What can I try to do better?

2020-12-07 19_20_43-Microsoft Edge.jpg

 

Views

97

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

I stuck your image back into your post - that's the best way to see screenshots.
What version of RH2020 have you got & upgraded with? You should use the latest build before trying to convert.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

The version is 2020.2.29 and it was just downloaded a couple of days ago.

Thanks for adjusting my post.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

When I saw the email advice that doesn't include screenshots I was going to suggest that often deleting the presets (SSLs in old money) fixes many broken links that show in the Broken Links report.

 

However, now that I have seen the screenshot I can see it's a TOC that is messed up. That is unusual.

 

  1. Any source control involved?
  2. Is the project on a local drive?
  3. Have you tried to run the upgrade process again?
  4. Have you looked in the Broken Links report to ascertain that this is the extent of the broken links?

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

1: The original project was controlled by VSS. The new one will be using another source control, but so far the upgrade was just stand-alone.

2: The project is on the local hard drive C:

3: I have now tried upgrading the already upgraded project. It does not seem to correct anything.

4: The broken links report confirms the extent of the problem.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

The latest version is 2020.3. You do not have the latest version that was released last week. 

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

The new version 2.30.0 does not change anything to the better.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

I have tried upgrading to RoboHelp 2019 Classic. This upgrading process tells that there is a problem with the file root.fpj (actually VSS has reported not being able to check this file in and out).

This XML file misses the last closing tag </rhpml>. 

However, adding this tag does not help. Maybe this file has other errors that should be corrected? 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

The original project was controlled by VSS. The new one will be using another source control, but so far the upgrade was just stand-alone.

Was it fully checked out of source control when you upgraded the first time? Not being checked out seems a likely cause of issues.

 

I have now tried upgrading the already upgraded project. It does not seem to correct anything.

That's not what I meant. I meant starting afresh from the project in Classic.

 

The broken links report confirms the extent of the problem.

Please look at where the broken links are? Are they mostly related to the TOC and the presets?

 

****************************************

 

Also are the topics shown as missing in the TOC also not shown in the Contents panel?

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

Q: Was it fully checked out of source control when you upgraded the first time?

A: No, I copied the project files after checking them in. Thus the files were write protected, but RoboHelp changes that during upgrade. I will try checking everything out and then copy the folder.

 

Q: Please look at where the broken links are? Are they mostly related to the TOC and the presets?

A: I do not understand what you mean by 'presets'. The broken links are lmost entirely related to topics, according to the Broken Links report.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

Checking out before copying does not seem to make any difference.

At least some of the htm-files related to the broken links are simply missing from the upgraded project. Is there a RoboHelp system file that might be responsible for this? If there is, can it be regenerated in the original project, for instance by deleting af file and letting RoboHelp construct it? The files missing in the upgraded project are listed in the "Used file" report in RoboHelp 10.

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

Output presets.

image.png

 

Your image of the TOC shows the topics as missing. My last question in my last post was whether the topics are also missing in the contents panel and you haven't answered that. They could show as missing in the TOC but be present in the contents panel if somehow the link got broken.

 

I suspect the topics are actually missing and whilst you say the upgrade process changed the write protection, I am doubtful that worked.

 

Check out the whole project and then run the upgrade process.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

 

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

The topics are missing in the contents panel, too. 

Checking out everything before copying and ugrading changes nothing.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

If the topics are missing in the contents panel then the upgrade process is failing somehow. Broken links can occur and we have seen that but I wholesale topics missing is not a known issue.

 

What you are upgrading from source control is the project in Classic format, correct?

 

Can you share the Classic project?

  • If you can, then see the Contact page on my site and send the project as instructed there. Do make sure you include a link to this thread and please do not email the project direct.
  • If not then I think on this one you will need to try Adobe Support.

 

See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your support contact options. If you do go to Support, please post back what the problem was as that will help anyone else who may encounter this. My gut feel is this is somehow related to source control but I don't know how.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

 

 

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

I think the problem here is that all your topics and images in Classic are in the root folder. That has never been good practice and is behind the problem here.

 

You reported "I have tried upgrading to RoboHelp 2019 Classic. This upgrading process tells that there is a problem with the file root.fpj (actually VSS has reported not being able to check this file in and out)".  That file is a listing of all the files in the project so without that present I expect you got the same problem that I did in Classic, it is showing no files when I tried to open the project in Classic 2019.

 

It would seem that the core of the problem is this root.fpj file. What I have found though is if you import the topics that didn't make it through the upgrade process, they are OK in the new version. The Broken Links report lists them for you.

 

Importing them will be easier than you are expecting as you can multi-select the files. 

 

image.png

 

I suspect the reason behind this working in RoboHelp 10 for you and not upgrading to 2019 Classic for me is somehow linked to source control. When I opened the project you sent in 2019 Classic I got the same root.fpj dialog and I had no option but to tell RoboHelp to stop trying as I could not of course access that. I think if you disconnected a copy from source control you would see the same problem.

 

On upgrade the process is I believe looking at the root.fpj file and I suspect that is corrupt. Thus while I see the topics in File Explorer when I extract your zip file and can import them, opening the project in 2019 Classic does not see any of them. I haven't tried upgrading after opening the project in 2019 Classic but I suspect that would be a complete fail.

 

Sorry it's not better news.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

The above is not the full reply I posted. Please ignore for now while I edit the reply.

 

It has now been edited.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

Just to add after opening the project you sent in 2019 Classic and the upgrading to 2020, all topics are missing. That reinforces the issue is the root.fpj file. It would seem importing the missing topics is the only solution although I guess you could try creating folders in RoboHelp 10 and then upgrade. It might be worth a try.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

You could try to use the VSS version history to get a working copy from before the root.fpj file was corrupted. Although any changes made after that version would need to be redone (easy enough to get the content using source control, but time consuming to verify which topics need to be updated). So if the corruption happened some time ago, it might be easier just to import the topics and recreate the TOC, Index, etc in a brand new project, as Peter suggested.

 

(Also, for anyone following along later, you can remove the source control link from a copy of the project by clicking the Wayback Machine link at the bottom of this thread, then following the instructions to edit the .xpj file. This will remove the link to source control from the copy of the project.
https://community.adobe.com/t5/robohelp/remove-a-robohelp-project-from-source-control-without-openin...

 

Don't forget to delete the cpd file before opening the project after making the changes.)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

You could also try replacing just the root.fpj with a copy from before the corruption. In theory only topics added or deleted since the date of that root.fpj would need to be resolved, but that might involve manually editing the fpj and you might not be comfortable with that.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

I am now working my way through importing the files shown in the Broken Link report.

Unfortunately there are two issues with this procedure (so far):

  1. The report only shows a couple of hundred files at a time. After I add these files, the report shows another set of broken links, and I then continue adding those. So far I have repeated this procedure five times, and the number of red crosses in the TOC is not overwhelming anymore. It seems like the original files are all there now (five of them still appear as broken links, though they are actually present). I intend to fix the TOC by moving the imported topics to the books where they are missing (old language - I have not yet worked with the new user interface.
  2. The Broken Link report shows an increasing number of files from the upgraded project. Is that a problem?
    2020-12-09 08_02_56-Hjælp til LUDUS Web - Adobe RoboHelp.jpg

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 09, 2020 Dec 09, 2020

Copy link to clipboard

Copied

I have now decided to start over. The soultion will be to import all of the topic files and recreating the TOC and the conditions manually. Monotonous work, but better than chasing strange errors.

Thanks to those who tried to help.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 09, 2020 Dec 09, 2020

Copy link to clipboard

Copied

LATEST

When you import the first topic with links you will see some broken links reported as the target will not have been imported. That is going to continue as you import each topic but it will also fix some links. What I am getting at is I can't see the advantage of your approach.

 

I think I would take a screenshot of the TOC or make a copy of the TOC file so that you have something to work from. Then I would trash the TOC and the presets. I think those two things will remove a lot of broken links. Then judge the best way forward.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Please use the Blue reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
RoboHelp Documentation