FlashHelp deployed in RH7 displays 404 page error instead of topic

Report · May 27, 2009

I upgraded some help projects from RHX5 to RH7.

In MAC (OS 10.5.x) Safari (3.2.1), when the application calls the FlashHelp authored in RH7, the Help opens, but the Help topic does not display. Instead, a 404 Page not found error is displayed. If you click a topic in the TOC the HTML content is displayed - so the Help does work after you select a topic.

From the same application, if you call a Help project that was not upgraded to RH7 (but was still authored in RHX5) the topic content opens as expected (you do not get the 404 Page error).

Has anyone else experienced this problem?

Report · May 27, 2009

Hi there

What happens if you configure a different topic as the default?

Perhaps you should try that.

Cheers... Rick

Report · May 28, 2009

At this point, I'll try anything. But, no, even if I make the default topic the same as the topic I am trying to call from the application I still get the 404 error. Everything is working fine in IE so I am afraid it is something new in the RH js that Safari doesn't like. I even tried switching the call from HH_HELP_CONTENT to HH_DISPLAY_TOC - but the 404 error is still there.

Report · Jun 29, 2009

The only resolutions I found so far are:

- replace RH js call to direct call to topic URL

- switch to WebHelp

When I submitted this issue to Adobe support I received a call stating that they do not support JS application calls to Help systems generated in RH. If you can open the topic (that is an individual html topic file) independently using the browser, apparently they consider that generation successul and the browser to be supported.

Report · Jun 29, 2009

JulieCarr wrote:
The only resolutions I found so far are:
- replace RH js call to direct call to topic URL
- switch to WebHelp
When I submitted this issue to Adobe support I received a call stating that they do not support JS application calls to Help systems generated in RH. If you can open the topic (that is an individual html topic file) independently using the browser, apparently they consider that generation successul and the browser to be supported.

Just musing over the reply here. It's odd that they would say that, giiven the fact the WebHelp API *IS* a JavaScript application call, is it not?

Cheers... Rick

Helpful and Handy Links