Skip to main content
David Kuhn 5000
David Kuhn 5000
Inspiring
December 26, 2022
Answered

Context Sensitive Help - Marker missing in Javascript CSH file

  • December 26, 2022
  • 1 reply
  • 327 views

I have never worked with context sensitive help. I added some topics OK. 

But now I have one that will not link to the correct place from the software. It just links to the top of the Help file. 

I was told by a previous writer that I should not use the generated H file, but to manually edit the H file that was handed over to me and then replace the generated one in the same location. I am not sure why.

In the Frame file, I added a marker of  Type TopicAlias and Marker Text CSH_AmqpClient. At first, I was put in AMQPClient (maybe with an underscore), but the developer told me it was case sensitive AmqpClient, no underscore, no dash, or anything. So I fixed that, but it still does not work.

But we are also looking at the CSH Javascript file in the whxdata folder and the marker is not being generated in that file. I have no idea why. Any brilliant suggestions?

    This topic has been closed for replies.
    Correct answer David Kuhn 5000

    It was confirmed that placing the manually updated H file in 2 places was the solution: 1 before generating the Help in the FrameMaker Project and after generation in the Help folder. 

    1 reply

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    December 27, 2022

    Maybe see this thread - https://community.adobe.com/t5/framemaker-discussions/context-sensitive-help-in-fm-2017-map-file-and-code/td-p/9210301 ?

    David Kuhn 5000
    David Kuhn 5000Author
    Inspiring
    December 27, 2022

    Thank you. I saw that thread. At first glance, I did not see the solution. I went through it again due to your response. I think that it does contain the answer. I was taking the manually updated H file and putting it in the folder with the help, but I neglected to also put that updated version in the FrameMaker folder as well. This must be why it was not being generated in the Javascript file because now it is. I just need the developer to confirm that the issue is solved now, but I think that it should be.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices