Skip to main content
A
amie68
Inspiring
September 17, 2025
Answered

Invalid url in merged help toc entry

  • September 17, 2025
  • 2 replies
  • 164 views

I have a merged help, frameless output help file. One parent / 55 child projects.

 

Some child projects have TOC entries that point to web pages. In those cases, the URL in the published file includes the path to the child project added to the URL of the intended page. Example:

https://help.oursite.com/parent_project/mergedProjects/child_project/https://url_of_intended_site.htm 

 

If I look at the files locally on my PC, the TOC entries are correct - only including the path to the web page. It is after these files are copied to the production server that I see this error. They are copied using an FTP client.

 

Any idea why that happens or how I can correct?

 

As info, I'm using RoboHelp Version 2022.4.179.
    Correct answer Jeff_Coatsworth

    I would suspect that the fact that they work locally, but not on the server means that there's something extra hanging around on the server. Have you tried a test where you FTP it to a completely empty folder and test it from there?

    2 replies

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    September 17, 2025

    Look at your link. It has HTTPS twice.

     

    Is the link to something not in the merge? I'm not clear if that is what you are saying.

    ________________________________________________________

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

      

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    A
    amie68Author
    Inspiring
    September 17, 2025

    Yes, https being there twice is the problem.

     

    https://url_of_intended_site.htm  represents the path entered in the TOC entry.

     

    https://help.oursite.com/parent_project/mergedProjects/child_project/  represents the path that is being added to that URL when the file is published.

     

    The URL points to a topic not in the child project with the TOC entry. It references a topic in a different child project.

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity ExpertCorrect answer
    Community Expert
    September 17, 2025

    I would suspect that the fact that they work locally, but not on the server means that there's something extra hanging around on the server. Have you tried a test where you FTP it to a completely empty folder and test it from there?

    A
    amie68Author
    Inspiring
    September 17, 2025

    Good idea. I'll try that and see what happens.

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