Known Participant

Question

Linking topics between different child projects

Forum|Forum|2 years ago
February 13, 2023
7 replies
985 views

Hello,

What is the correct way to link a topic from one child project to a different child project? I tried to link a Topic from Child2 to Child1 by selecting the text in Child1 and clicking Hyperlink > Local Files > MyRobohelpProjects > Child2 > topic. When I generate the Responsive HTML merged output from the Parent, I get a 'page may have been moved or deleted' message after I click the Hyperlink in Child1. Right-clicking the contents pane and choosing Link > Link File linked the topic but none of the images appeared in the merged output.

This topic has been closed for replies.

Peter Grainge

Community Expert

I think i would create a new topic and copy the old content into a text editor and paste it in to the new topic, then format it.

________________________________________________________

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

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

Peter Grainge

Community Expert

You say "When I generate the Responsive HTML merged output from the Parent, I get a 'page may have been moved or deleted' message after I click the Hyperlink in Child1."

Have you then proceeded to generate all the projects and tested whether it is broken there?

________________________________________________________

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

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

S

sprite253Author

Known Participant

I generated all the projects, and there are no issues anywhere else. When I click the linked topic, I see the following error message:

https://tenant.sharepoint.com/mergedProjects/Project_Name/Topic.htm might be temporarily down or it may have moved permanently to a new web address.

I noticed this is the only place where the link shows up as .htm instead of .aspx.

A

Amebr

Community Expert

The paths seem correct as far as I can remember. I can't think of any reason why Peter's link between projects worked when you uploaded it to Sharepoint, but your own test project did not.

The best I can suggest is you compare the output preset settings for Peter's project and yours to see if any of the differences seem relevant.

Otherwise I think you need to contact support. See the following page for options. The email address is recommended as it goes to a dedicated Robohelp team.https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp

S

sprite253Author

Known Participant

Thank you for taking the time to try and find a resolution, Amebr. Have a great rest of the week!

A

Amebr

Community Expert

So Peter's merged project sample worked fine when uploaded to sharepoint? In that case it must be some difference in your project.

Perhaps the publish location doesn't have the right folder structure? Can you share some screenshots of that - the parent project root folder and the root folder of one of the children might be enough to see if that's the case?

S

sprite253Author

Known Participant

Hi Amebr,

Thanks again for taking the time to follow up. I sincerely appreciate it. Yes, Peter's merged project worked on SP and so did my own local output for the sample parent and child projects I created.

I have three folders on the desktop: generate, publish, and source. The source folder contains the Parent project and both the Child projects (children are inside the Projects folder)

The publish folder structure is as below

Inside the mergedProjects folder, I have the output of the Child projects

Below is the folder structure of Child_1 from inside the mergedProjects folder

Thank you!

S

sprite253Author

Known Participant

Update: I linked Child_1_Topic to Child_2_Topic using a hyperlink and published the output to SharePoint. After checking the hyperlink extension in the SharePoint output, I found that it stayed as htm and did not convert to aspx. The rest of the output works perfectly, including hyperlinks between different topics within the same Child project and external links. I am using RH 2022 for reference.

A

Amebr

Community Expert

Can you generate a regular responsive output rather than a sharepoint output and test the local output.

Also can you generate Peter's sample (use Responsive_Azure_Blue output preset) without making any changes except to make sure the Output Path for each project points to the correct folder in the MergedOutputs folder (if you don't add the project directly off C drive (C:\MyMerge) you need to update the path to reflect the new location.)

The sample works perfectly for me with only the output path change, so if we can validate that it also works for you that will narrow down where the issue is.

S

sprite253Author

Known Participant

Hi Amebr,

My local responsive output works as expected. I also generated Peter's sample, and both, local and SharePoint outputs work fine. What else can I try? I appreciate you taking the time to respond.

A

Amebr

Community Expert

You need to set up your source projects with a specific folder structure which is described in Peter's document. That will make it easy to link using the source projects and the links will then work in the output as well. I highly recommend downloading the sample project Peter provides and looking at how that is structured - the simplified content makes things easier to understand.

S

sprite253Author

Known Participant

Hi Amebr, Thank you for taking the time to respond. I made another attempt at recreating the folder structure as follows.

Step 1: I created 3 folders: generate, publish, and source

Step 2: Next, I saved the Parent project inside the source folder, and two child projects inside the Projects folder, Child_1, and Child_2

Step 3: I generated the Parent project Responsive HTML output into the generate folder for local output and publish folder for SharePoint output

Step 4: I inserted a link into Child 2 Topic by choosing the Child 1 topic from the source folder.

The resulting path is visible as an absolute path as below

Step 5: I generated both Child Project outputs into the generate and publish folders for the local and SharePoint output respectively.

Step 6: I published the output to SharePoint. I can view both the Child 1 Topic and Child 2 Topic in the Responsive HTML output on SharePoint. However, when I click on the link inside Child 2 Topic,

I see the following error.

I cannot figure out what I am missing here, I never see the path of the link change to a relative path.

Peter Grainge

Community Expert

See the Merged Help pages on my site. It's all explained there.

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

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

S

sprite253Author

Known Participant

Hello Peter,

I read through the Merged Help pages on your site and have the following question. After I select Local Files, do I choose the topic I want to link from within the child project that is saved locally on my desktop or from within the generated output inside the merged output folder? I tried both and neither is working. As shown below, the Training Resource Center is the Parent project. The outputs for all children are inside the mergedProjects folder. I have a separate folder that stores the SharePoint output labeled Test_RespHTML_SharePoint.

If I choose the topic to link from inside the child project saved locally on my desktop, I get the following error message after I click to access the linked topic

Thank you.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded