Skip to main content
Participant
December 4, 2006
Question

pdf from WebHelp toolbar no longer opens

  • December 4, 2006
  • 3 replies
  • 663 views
I have a WebHelp file and I have created an additional toolbar button that, when clicked, opens a pdf version of the Help file (so users can easily print all the Help). This has been working fine with IE6 but when it was tested on a machine with IE7 installed, the pdf wouldn't open. Does anyone know if it is IE7 that is causing the problem (seems likely as it is the only variable that has changed) and if there is anything that can be done about it? I have searched Adobe Reader forums and Robo forums to no avail. Any help appreciated.
This topic has been closed for replies.

3 replies

Peter Grainge
Community Expert
Community Expert
December 5, 2006
Can you recreate this in a new one topic project?

If yes, zip it up and send it to me. Go to my site to contact me.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
August 24, 2016

I'm having the same issue, but only with Internet Explorer 11. The PDF files open fine with Chrome and Firefox.

I'm using RoboHelp 2015 and the latest Distiller and Acrobat software. In RoboHelp, I create Baggage Files and link the PDF files to those. I then create a new TOC page for each PDF as a link to these files.

Does anyone know of any resolution for this IE problem?

robowomanAuthor
Participant
December 5, 2006
Peter, thanks for your reply. I have checked my project and the pdf has underscores but no spaces in the name. Any other suggestions appreciated.
Peter Grainge
Community Expert
Community Expert
December 4, 2006
I don't think it is IE7. I just created a test and put on a button as you describe. It failed under IE7 but then I found it also failed under IE6. Tracked it down to having used a PDF with a space in the filename. When I pointed the button to that file, there was a space. By the time RH had put it into the output, the filename had an underscore in. When I changed the source to have an underscore, changed that in the skin editor and regenerated, it all worked fine.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.