Skip to main content
A
Anonymous
January 16, 2019
Question

Broken links created by Robohelp2019 conversion

  • January 16, 2019
  • 5 replies
  • 3751 views

I am running Robohelp 2019.0.4.

Converting a Robohelp Classic project to Robohelp 2019 breaks links in my TOCs.

There are NO broken links in the Classic project, yet the 2019 broken now shows many broken links.

Why is this happening and how can I rectify this without touching every single one of these links?

This topic has been closed for replies.

5 replies

EmanAssem
EmanAssem
Inspiring
August 5, 2019

I was checking Robohelp update 8, and good news is I just found that Broken links issue is now fixed, and managed to generate PDF normally.

EmanAssem
EmanAssem
Inspiring
February 11, 2019

I have the same problem while upgrading from 2015 to 2019, I have many broken links, and couldn't generate PDF due to this issue.

Please any solution has worked with you?

Matt-Tech Comm Tools
Matt-Tech Comm Tools
Community Expert
February 15, 2019

Have you installed Update 5?

I posted a list of features and fixes at https://techcommtools.com/robohelp-2019-update-5-now-available/ and Fix #1 relates to upgrading projects.

-Matt

-Matt SullivanFrameMaker Course Creator, Author, Trainer, Consultant
EmanAssem
EmanAssem
Inspiring
February 17, 2019

Hello Matt, Yeah I did, and still got the same error unfortunately.

isabelleg85447096
isabelleg85447096
Inspiring
January 28, 2019

Hello All,

Problem for me as well. This has only begun happening to my files after downloading update 4.

Projects that were fine under Update 3 are chalk full of broken links. htm/html as well as .pdf/.gif confusion.

Also new with update 4, invalid characters in French text.

A
Anonymous
January 17, 2019

I'll try it a couple of different ways and report back.

Peter Grainge
Peter Grainge
Community Expert
January 18, 2019

2019 will support HTML, the issue was with the upgrade not recognising it. That will be fixed in the next update.

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
A
Anonymous
January 30, 2019

I've decided to just wait until this problem gets fixed, along with whatever else I haven't run into yet. As Robohelp 2019 stands today, I cannot justify using it in production and will continue to use the "Classic" mode until things shake out a bit more. 

    Peter Grainge
    Peter Grainge
    Community Expert
    January 17, 2019

    I see from another post that you are likely upgrading from 2017. I haven't encountered any issues with broken links in the TOC upgrading from 2017.

    1. Is this project one that was worked on in 2017? If not, try upgrading to that first if you can.
    2. Have you tried upgrading it to 2019 Classic first? If not, try that with a copy of the project rather than the original.
    3. Are these all links to topics rather than external links?
    4. 2019 Classic ships with Employee Care 3 as a sample. Try upgrading that.

    See www.grainge.org for free RoboHelp and Authoring information.

    @petergrainge

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    A
    Anonymous
    January 17, 2019

    Thanks Peter.

    1. Yes, this was a project that was converted from 2017. There were no broken links in the project.

    2. Yes, I had converted the 2017 project to Robohelp Classic 2019 and there were no broken links there.

    3. These are all links inside of TOCs to topics inside the project.

    4. I converted the Employee Care 3 project and everything looks fine.

    Ok, I just found out what is going on. During the conversion my .html files are being changed to .htm files while links those files are in still reference the html files. Yeah.

    Is there a way to control this behavior during the conversion?

    A
    Anonymous
    January 17, 2019

    No way that I am aware of. Sounds like a job for a little utility that

    changes file extensions.

    Peter Grainge

    www.grainge.org

    @petergrainge


    I question whether this is a necessary or desirable behavior by Robohelp 2019 and wonder why this isn't documented somewhere. It is certainly something I would warn the user about both in the documentation and the UI. It would be nice if your were warned, then given a choice whether to keep the html extension or not.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices