RH 2022 Webhelp output links format

[christele15]

Good afternoon, 

I really wished I was done with all our issues but this one is yet another major issue. Our output/hmtl files are referenced in several internal application and link are not to be updated unless previous approval because it impacts several projects. When deploying the output to a test environment, the links implemented in other applications returned 404 errors. After further review I noticed that if you click the link from the TOC the backslash is replaced by %2F,  URL Encoded value of the Forward Slash (/). and #t= was also added appending the start page. I included below examples and really hope someone has a solution for this issue because this was not happening in Classic.

Right clicking the link from the TOC: file:///D:/outputs/Claims/pagehelp/Adjust_Claim_-_Claim_Detail_help_realtime.htm
Clicking directly from the TOC: file:///D:/outputs/Claims/oconlinehelp.htm#t=pagehelp%2FAdjust_Claim_-_Claim_Detail_help_realtime.ht...

Thank you in advance, 

CHristele

[Peter Grainge]

When you generate the output I suspect you are seeing a dialog that says something along the lines Generated With Errors. If you click the link in that dialog I think you will see some yellow warnings.

What they are telling is that the link is to something on your hard drive rather than within the project. You need to find and correct those links. Do not search on the absolute path shown as that is what the report shows but in your topic it will be a relative link. Search on the end of the path, try Adjust_Claim_-_Claim_Detail_help_realtime.htm.

Try creating the link using the webpage option and entering the path as it will be on the server.

________________________________________________________

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

[christele15]

What if I did not get any errors? 

If I click from the TOC this is the link I get:

file:///D:/outputs/Edits/edits.htm#t=Benefit_Processor_Edits%2FBP1.htm

If I right click> open new tab or window:

file:///D:/Edits/WebHelp/html/Benefit_Processor_Edits/BP1.htm

And this is for all my 8 projects? Am I missing out a configuration on the TOC?

Thank you 

Christele

[Peter Grainge]

Well either you are or you are not getting error warnings, which is it? 

In the TOC are you pointing to a topic that is in the same project? 

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

[christele15]

I did not get an error. It said successful.

[Peter Grainge]

That answers the first question. 

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

[christele15]

Good afternoon again Peter, 

I double check the WebHelp log as well and there no warning as well.

Thank you 

Christele

[Peter Grainge]

The question I meant was "In the TOC are you pointing to a topic that is in the same project?" 

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

[christele15]

Yes it is in the same project. 

[Jeff_Coatsworth]

I'm not so sure of that - you mention you have file:///D:/outputs/Edits/ and file:///D:/Edits/WebHelp/html/ - those don't look like they are in the same ouput folder.

[christele15]

so sorry Jeff, copied the wrong information... I have been starring at this for now 18 hours:

Click from toc format: file:///D:/outputs/Edits/edits.htm#t=Benefit_Processor_Edits%2FBP1.htm

Right Click > open window or open tab: file:///D:/outputs/Edits/Benefit_Processor_Edits/BP1.htm

[Peter Grainge]

Looking again, am I right in understanding if you open the output directly it works fine. The issue is when the help is called from an app? 

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

[christele15]

No Peter , the issue is the format of the url itself when clicking from toc, this was not happening in Classic:

Click from toc format: file:///D:/outputs/Edits/edits.htm#t=Benefit_Processor_Edits%2FBP1.htm

Right Click > open window or open tab: file:///D:/outputs/Edits/Benefit_Processor_Edits/BP1.htm

[Jeff_Coatsworth]

That %2F HTML should be interpreted by your browser just fine - what version of RH2022 are you running? I don't think you mentioned your point version.

[christele15]

I am running Robohelp 2022.2.22.

Thank you 

Christele

[Jeff_Coatsworth]

How does the sample project behave if you generate locally?

[christele15]

To clarify Jeff, this is the issue:

We have an application to which you log in and when using FN+f1 the previous url which pointed to our project output was: (this was in rh 2017)

https://url.com/fep/realtimeclaims/help/html/oconlinehelp.htm#fieldhelp/Total_Charges_help.htm 

in the test environment, with the rh2022 version we receive a 404 error because RH 2022  link format is:

https://url.com/fep/realtimeclaims/help/html/oconlinehelp.htm#t=fieldhelp%2FTotal_Charges_help.htm 

I tested the link to that page directly and  was able to isolate the problem to be htm#t

I need to find a way to have the url to be updated to htm# instead of rh htm#t
I hope I make sense because I am exhausted... 

christele

If I go directly to the link without the above url format it revert to the homepage.

[Amebr]

Note that Webhelp does not exist in RH2022. When you upgraded from RH2017 your webhelp output was converted to Responsive HTML5. You can tell from the icon next to the preset name - if it's a shield with a 5 inside, it's Responsive. If it's a globe, it's Frameless. When you try to add a new output preset, you will not find an option for Webhelp.

If you have linked to the help from an application (context sensitive help) the link format is different and your developers will need to change their help calls.

Peter's site has information on the differences between webhelp and responsive CSH links.

[Peter Grainge]

This is the page @Amebr is referring to. RH2022 Calling Context Sensitive Help (grainge.org)

________________________________________________________

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

[christele15]

Good morning Jeff and thank you!  

After one night of sleep , I can now clarify. I migrated 9 projects from RH 2017 to RH2022  using the Responsive HTML5 output preset. This is when I discovered that the links format was updated from htm# to htm#t . So you are saying that this cannot be solved via RH, the developers will have to update the link for all 9 applications?

Thank you 

Christele

[Jeff_Coatsworth]

Check out Peter's page for the explanation - basically the call command to specific topics in the help (known as Context Sensitive Help or CSH) changed when Responsive HTML5 came in.

[christele15]

Thank you so much Jeff, this is so helpful and again sorry about the confusion , many sleepless nights 😞 

[christele15]

Good afternoon all, 

I reached out to adobe support because if RH content management system main purpose is to be used as an online help and referenced by companies’ applications, updating the way links are parsed on the output should have been flagged as a major issue to your existing clients...

I will keep you posted, 

Christele

[Jeff_Coatsworth]

Not sure what you expect to happen - RH isn't changing back to the older way of calling the help topics. I'm sure it's not that difficult to adjust the call from the application to the content. I know it certainly wasn't in my company's case (I actually made the changes myself to make it happen & I'm no programmer).

[Amebr]

It can be quite hard, particularly if you have users on different version of the software and have a modular product. I had a many months long process to roll out updates with conditional context calls, so that the old help would be called until all installed products were updated to a version with the new context call built in. (I'm astonished I managed to get the thing live, to be honest. 😛  )