Skip to main content
Known Participant
June 11, 2010
Answered

Hyperlink paths are wrong

  • June 11, 2010
  • 13 replies
  • 1332 views

I am using RH7.03.001

I'm working on a project which consists of a Parent (with 1200-ish topics) and 5 Children (which are optional Plug-Ins for the software) each of about 100 topics .

All the source is stored in SourceSafe.  I generate to a project-specific folder on my desktop, and publish to a project folder in My Documents. I then copy the publish folder to a network location for the Dev team to pick up.

When testing the output, I am having two problems.

First, hyperlinks from a child project are reporting 'invalid link' to the parent project.  On closer investigation, it would appear that RH isn't converting the absolute paths to the correct relative paths. The path is showing as "../../../../../../Desktop/DimX/Appendix/Lists/GenLists.htm", whereas it should be "../../Appendix/Lists/VATRates.htm".  Is this a setting somewhere? I am using Xenu as the link validator.

Second, when testing the context sensitive help - which we do by generating an XML document which maps an app form to a Help topic - if you spawn into a topic located in the parent project, you can see the entire TOC, but if you spawn into a topic located in a child, you can only see the child TOC.

I'm really very confused, and more than a little stressed out with deadlines looming...

    This topic has been closed for replies.
    Correct answer Peter Grainge

    is the child > parent thing a RH issue?  Is it fixed in RH8?


    It's not a RH thing. It's about the path in the source creating the link you need in the output, doesn't matter what you use to edit.

    Fight it if you want or use the method that works.

    Try creating merged help links in Flare if you want some real fun.


    See www.grainge.org for RoboHelp and Authoring tips

    @petergrainge

    13 replies

    RonW63Author
    Known Participant
    June 11, 2010

    sorry, the htm pages used in my example are two different pages.  I have fixed one

    link, but not the other.

    Peter Grainge
    Community Expert
    Community Expert
    June 11, 2010

    1] Take a look at the merged help pages on my site. They cover how I create links between child projects and the method works fine.

    2] If you don't call the help via the parent, you will only see the child project TOC. That is also explained. RoboHelp 8 has an option that overcomes the problem but you can set RH7 to open the full merge. See the Calling Help pages.


    See www.grainge.org for RoboHelp and Authoring tips

    @petergrainge

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    RonW63Author
    Known Participant
    June 11, 2010

    Hi Peter

    Thank you for your advice.  I have followed your instruction in creating the links from child to parent, but the relative path is still going up too far?

    Just to make sure I am following this to the letter...

    • I am opening the child1 source document in RH7 (checked out to C:\Documents and Settings\me\My Documents\WIP\WIP SourceSafe\Help\child1\)
    • Highlight text that will be the hyperlink, and click insert hyperlink
    • drop down 'link to: and choose 'file'
    • browse to the generate folder (the child is generated into 'parent/mergedProjects/child1/' and the link points to 'parent/system/settings/abc.htm)
    • the path is shown as an absolute patch, and on save is converted to relative
    • double-click the link within RH. The destination page is shown in the preview pane correctly.
    • generate the output and test link

    expected outcome:

    ../../System\Settings\abc.htm

    actual: the hyperlink does not work

    ../../../../../desktop/parent/System/Settings/abc.htm

    so it seems that the path is keeping the relativity between the Source projects, not the relativity between the Generated projects? Should I be browsing to the source document for the parent when inserting links?

    Thank you kindly

    Ron