Has anyone iframed a robohelp project? We have a client who needed to put their robohelp project/files behind a login, and share the main website's header and footer.
So we ended up iframing (the already iframed) robohelp project. The print button in the robohelp toolbar isn't working, probably because we're iframing an iframed project. Has anyone had a good workaround for that?
You can put the help in an iframe, but I found that the TOC doesn't load
correctly on IE when the help is placed in an iframe. I've worked around
this by commenting a check in the function ExpandIt in whthost.js:
//if(!gsTP)/* Workaround for not loading in IE11 in iFrame. */
As for the print button, you may need to amend the code of the print
button in the skin editor so that the button points to the correct
frame. top..restofpath or something like it.
There is a workaround. You will have to update the seed file. The seed
files are the templates that RoboHelp uses to generate the output.
You find the seed file for whthost.js in %RH installation
Make a backup of the original file before you change the seed file!
Willam, thanks for the continued support.
Apparently our robohelp author can't locate the seed file you indicated. There are a number of files beginning with whskin_ in the projects that aren't in the template_stock directory.
She was only able to locate whskin_ in the robohelp output folder, which is separate from the folder where the application is.
Sorry about that. It's a little trickier: you must amend the code in
whst_frames.xml for this to work. You can search for the code there and
make the amens. But be carefull: this is a template file and you need to
escape all slashes and single/double quotes.
I hope we're talking about the same file. You can find the scripts and
most files in the folder template_skin and template_stock. Only for the
whskin_frmsetxx.htm files you need to amend the xml.
We tried searching for var printAction = function() in the entire folder/project to modify the target of the print function in the seed file and no luck.
Is there a technical resource at Adobe we can escalate this to?
Just a couple of things.
First, (and this is mostly for anyone finding this thread down the road) I'd like to clarify something. An HTML page may have an Inline Frame inside it. That is referred to as an IFRAME. While RoboHelp produces an output type known as WebHelp, this output is presented using a FRAMESET. A FRAMESET is totally different from an IFRAME. In an IFRAME, the content from a different web page is presented inside a single frame. But a FRAMESET is typically used to divide a HTML page into two or more areas, with each area presenting a different HTML page.
As for the function and the changes you are referring to, Willam advised you to make a tweak to the seed file. That tweak was simply to allow the TOC and other elements to display properly. There was a second bit. The second bit involves the Print function.
Note that the print function is not part of the seed file. It's part of the skin. So it's no surprise whatsoever you aren't finding it in the seed file. It simply isn't there to be found.
You need to be looking at the code inside the skin editor.
Oh, and what you are trying to do is something outside the scope of what RoboHelp is configured to do. So it's doubtful that there is anyone at Adobe to actually escalate anything to.
Perhaps it will help to think of it this way. You purchase a vehicle from General Motors. Instead of driving it on normal roadways as the factory supplied it, you wish to drive it on railroad tracks. The vehicle needs to be modified in order to allow it to be driven on railroad tracks. You will need to find a third party shop to make the modifications as the dealership is only really set up to make repairs to the car as it came from the factory.
Thanks Rick. We ARE the 3rd party shop that the client hired to put a IFRAME around their robohelp project so it could maintain the main site branding and navigation, as well as putting it behind a login.
We'd rather not frankenstein the core code any more than necessary to make it happen. Is there any documentation on integrating a robohelp project with an existing website so it can leverage the same navigation as well as keeping it behind a login? Or, are robohelp projects best suited for "stand alone" applications?
And per your analogy, I'm not requesting Adobe change anything for us, just confirm where the file/code is that we need to change, something more specific than "in the skin editor". We searched outside the seed file too.
There's no documentation as RH was not designed for being iframed. It's
a lot of trial and error. Branding WebHelp beyond the Skin Editor
requires quite a bit of custom coding. Especially when you want
interaction with the parent.