Robohelp 2022 Frameless CSH

[drew_3566]

After a recent upgrade to RH2022 and upgrading our HTML help to Frameless we are no longer able to open help topics to the correct location using context sensitive help.

Originally, users would be directed to the correct section of a topic when opening with CSH. However, with the move to frameless it now simply opens the topic without navigating to the correct section within the topic.

Users are able to navigate to the correct section using the ToC, and manually entering the URL works as well.

[Peter Grainge]

The calls have to change. See https://www.grainge.org/RoboHelp_Tour/rh2022/outputs/calling_csh_help.htm

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

[drew_3566]

I'm assuming that they will need to be changed from URL to Map IDs?

[Peter Grainge]

No. The URLs just need to change as I have described. 

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

[drew_3566]

See additional comment regarding using the suggested URL format. To be clear, it's not enough that it simply open the corresponding topic; there are specific sections in each topic that it should direct to using CSH, not simply open the topic's chapter.

[drew_3566]

I should also add, the dev attempted to use the URL format path/index.htm#t=path/topic_name.htm. However, the CSH simply opened to the index page instead of the topic section.

[Jeff_Coatsworth]

That "path/index.htm#t=path/topic_name.htm" format only works with Responsive. Does your existing URL paths include some bookmark indicator? like #bookmark_name at the end of the path?

[drew_3566]

They do, yes. See additional comment below.

[Peter Grainge]

Yes because that format is wrong for frameless. It's explained by following the link. 

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

[drew_3566]

Forgive me, but could you highlight the specific part? Reading over the link (which I found prior to this post) it seems the suggested URL format (path/index.htm#t=path/topic_name.htm) is the one being used and opens to the index page instead of the appropriate section.

[Peter Grainge]

For bookmarks in a topic, you just add #bookmarkname to the frameless URL. 

For example, https://www.grainge.org/RoboHelp_Gems/RoboHelp_Gems.htm#miscellaneous

________________________________________________________

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

[drew_3566]

That is being done as well.
For example:

We have a "Help and Support" topic with a section titled "Install Task Tray."
path/index.htm#t=path/Help_and_Support.htm#Install_Task_Tray is the format that was used but opened to the index page only.

[Peter Grainge]

Yes because it doesn't understand the rest of that URL in frameless. Look at the link I posted, There is no reference to index.htm or t=path etc.

Responsive =

path/index.htm#t=path/Help_and_Support.htm#Install_Task_Tray 

Frameless =

path/Help_and_Support.htm#Install_Task_Tray 

________________________________________________________

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

[drew_3566]

This format (frameless) is not working either. Still opens to the topic without navigating to the bookmark.

[Peter Grainge]

Show this thread to your developer. They will understand.

________________________________________________________

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

[Peter Grainge]

Patently as the link in this thread works, the construction is correct. You must be getting something wrong. Check the bookmark.

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

[drew_3566]

The bookmark is correct. If outputting to a responsive HTML5 format, all CSH works properly. However, there is some behavior with the table of contents in that format that pushed the move to frameless.

[Peter Grainge]

Generate the help locally and go to the topic. Copy the URL into a new browser tab and add # followed by the bookmark, then press enter. What happens?

Is the topic very short?

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

[drew_3566]

Copy / Pasting the url with the bookmark manually keyed opens the correct section with the help fully displayed.

[Peter Grainge]

So patently the call that isn't working is not the same. 

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

[drew_3566]

Could you provide a bit more clarity on what you mean? Neither the dev nor I have changed anything functionally on either side, outside of upgrading from RH2017 to 2022 and moving to a frameless help. Topics and bookmarks have been untouched.

[Peter Grainge]

I don't know what else I can that hasn't been said. 

When you were using 2017 your developer had links in the app that opened the help to the bookmark. Now the links in the app need to change to the format you have proved works.

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

[drew_3566]

the links are correct, as I posted in another comment, the CSH works properly in an HTML5 output and the topic itself opens with frameless, just not to the correct section. This specific issue only occurs in frameless. There is another issue happening in HTML5 I'd be happy to start a new thread to discuss, but there is some influence to move to frameless already.

[drew_3566]

I should clarify, I understand there are fundamental differences between HTML5 and frameless. However, the URL changes are being addressed by the dev but simply not getting the expected results.

[Peter Grainge]

Please post the developer's call.

Beyond that I think you need to go to Adobe Support. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link tcssup@adobe.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

You proved the construction of the call is what I have given you. When the app calls the topic, is the #part showing in the browser?

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