Skip to main content
Ioana_St
Inspiring
August 29, 2018
Answered

Merged Projects in RH 2019

  • August 29, 2018
  • 1 reply
  • 1806 views

Has anyone tried to work with merged projects in RH 2019? I am running into some weird issues and I can't get merged help to work regardless of the way I try it.

I tested the following.

  • Creating merged project (a parent with one child) in RH 2019 Classic - OK. Opening index.htm from the parent displays the TOC of the parent and child modules and all their topics.
  • Creating merged project in RH 2019 - NOK, the TOC only shows the current project. If you open index.htm from the parent, you only see the parent topics; if you open index.htm from the child, you only see the child topics. If you open the child project and click a topic different from the default one, the TOC of the parent is automatically loaded and replaces the TOC of the child. This happens when the URL changes from file:///C:/master_new_resp/mergedProjects/child/index.htm#t=First_Merged_Topic.htm to file:///C:/master_new_resp/index.htm#t=mergedProjects%2Fchild%2FSecond%20Merged%20Topic.htm. Other than that, you can navigate without errors among the displayed topics in either parent or child.
  • Upgrading merged project from RH 2019 Classic to RH 2019 - NOK, same behavior as the new project above.
  • Upgrading our existing source files from RH 2017 to RH 2019 - NOK, even weirder. If you open index.htm from the parent, you only see the parent topics and you can correctly navigate through the parent's topics. If you open index.htm from the child, you only see the child topics, but once you click any of the topics you get an error saying that the file does not exist. (All the topics do exist and can be opened standalone, but once you click the link that should show them in context, with TOC, the error appears again.) The problem seems to show up when the URL switches from file:///C:/responsive_new/mergedProjects/child_project/index.htm#t=Child_Topic1.htm to file:///C:/responsive_new/index.htm#t=mergedProjects%2Fchild_project%2FChildTopic2.htm.

All the above happen for both WebHelp and Responsive, using the Azure layout.

I guess that something went wrong in the upgrade, but I can't even understand how merged projects are supposed to work in 2019 to know what I should be aiming for...

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

Best not to test that as Adobe are doing a pretty good job.

Being serious, I just created a 2019 setup and made sure the upgraded source projects followed the same structure as for 2017. That would not be the default upgrade path but that is to be expected and is easily fixed.

I then generated again ensuring the structure was squeaky clean. What I found was:

  1. The redirect in the parent failed.
  2. No TOC was shown.
  3. A search designed to return all topics worked but only some of the results showed a topic.

Adobe then advised me that merging will be fixed in Update 1 in September.


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

@petergrainge

1 reply

Peter Grainge
Community Expert
Community Expert
August 29, 2018

In theory it shouldn't be any different. I'll try later.

The links tell me you are using a responsive layout. Have you tried webhelp as well?


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

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Ioana_St
Ioana_StAuthor
Inspiring
August 29, 2018

Yup, same behavior in WebHelp as well. If you want, I can email you my test projects, but I don't want to abuse your patience!

Peter Grainge
Community Expert
Peter GraingeCommunity ExpertCorrect answer
Community Expert
August 29, 2018

Best not to test that as Adobe are doing a pretty good job.

Being serious, I just created a 2019 setup and made sure the upgraded source projects followed the same structure as for 2017. That would not be the default upgrade path but that is to be expected and is easily fixed.

I then generated again ensuring the structure was squeaky clean. What I found was:

  1. The redirect in the parent failed.
  2. No TOC was shown.
  3. A search designed to return all topics worked but only some of the results showed a topic.

Adobe then advised me that merging will be fixed in Update 1 in September.


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

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.