RH2022 output generation changes hyperlink from upper to lower case, breaking link

Forum|Forum|1 year ago
November 12, 2024
3 replies
206 views

We converted from RH2015 to RH2022. In RH2015, a generated link ends with "RF/rf1111," which is also how it appears in the Source file prior to being generated. In Robohelp 2022, the same generated link ends with "rf/rf1111," even though it is "RF/rf1111" in the Source file. Consequently, the link does not work in RH2022 generated help.

We are using the HTML5 preset, and cannot find any field or control that would change the path from upper to lower case. Is there anything we can do to stop this from happening? We have numerous broken links throughout the help.

This topic has been closed for replies.

Peter Grainge

Community Expert

Checking a merge demo that I have, the check box is strictly file names only and in a simple test, the case of the folder was not changed. The mystery is thus why is it changing in the new UI when it worked in Classic. To the best of my knowledge nothing changed and I have been working with merged help for twenty odd years.

The folders in mergedProjects get their case from the RHPJ folder when you add the project to the parent TOC. Is the case correct there?
You say In Robohelp 2022, the same generated link ends with "rf/rf1111. Exactly where are you seeing that.
The problem is not with links in a specific child but does also occur with cross child projects. Correct?
Is the issue only with calls to the screens, not within the output?
Have you tried simply renaming the folder in the output?

This issue is precisely why in my Merged Help instruction pages I advocate always using lowercase for everything.

Let me know about the above but if all else fails, then a case sensitive find and replace operation should fix things.

________________________________________________________

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.

Peter Grainge

Community Expert

As you are new to 2022, you may find the RoboHelp Tour on my site useful. See the 2022 pages.

________________________________________________________

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.

Peter Grainge

Community Expert

I think this is what you have missed. What surprises me is that RoboHelp does not change this during the upgrade. Your Classic project still exists as the upgrade creates a new project rather than changing the old one. Did you perhaps create a new preset and miss the setting?

________________________________________________________

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.

J

jas35401Author

Known Participant

No, we are actually very aware of that setting. Our path is /Company Name/help/mergedProjects/RF/rf1111. We have checked that flag so that "rf1111" is generated in lowercase. However, the "RF" before that should not be in lower case, but the generation is making it so. In RH2015, we also checked that flag, and the "RF" remained in uppercase.
You might say the simple solution is to rename our "RF" folder where the generated files are sent to "rf," but doing this would break the connection between the screens and the help. We have approximately 3,000 screens.

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