Skip to main content
Participant
August 9, 2022
Question

RoboHelp adds 'rh_skin=false' for internal link in output

  • August 9, 2022
  • 3 replies
  • 210 views

We wondered why an internal link (from one sub-page to the other) ended in not showing the 'frame' (navigation, header) but just the page content ('Frameless' output profile). We realized that RoboHelp adds a '?rh_skin=false' to the link which has this effect. Why that, how can we avoid that? Accessing the same page via the menu shows the normal page in it's 'frame'.

    This topic has been closed for replies.

    3 replies

    Community Expert
    August 18, 2022

    Argh. I tried sticking a RH2019 frameless in an iframe and it was fine. But I just switched to RH2020 and they changed it - the topicpage.js definitely detects iframes and does stuff. 

     

    You'll need to contact Support for this one. The email address is recommended as it goes to a dedicated Robohelp team. https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp

    Community Expert
    August 18, 2022

    I think the extra code must be a custom script as it's not something I've seen on frameless output hosted normally. Can you  ask the website developers to check for any scripts that might be doing it? Or can you find any script files in your project and see if those could be responsible?

    Community Expert
    August 9, 2022

    Is it only the one link that does this? Have you compared a working link with the this one to see what the difference is?

    Participant
    August 16, 2022

    Dear Amebr, it is the same for all links from page to page. Looks like we found the reason: Our online help is running in an iFrame. There seems to be a mechanism that detects wether the site is running in an iFrame and if it does, it adds '?rh_skin=false' to internal links - maybe this has been carried over from a time when header and navigation were placed in seperate frames to signal that the target page doesn't have to load those frames again, just the pure content. We fixed this issue by giving the outer iFrame a name ('help_frame') and adding a target like 'target="help_frame"' to those internal links - a workaround, not very convenient and bullet-proof. This mechanism is not needed in frameless output any more, please, RoboHelp, remove it. Thank you.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    August 16, 2022

    I think I missed something - what version of RH are you running and what output? It sounds like you are creating frameless output, but hosting it within an iFrame - is that right??