Copy link to clipboard
Copied
I have generated webhelp using a trial version of RH11. When the webhelp is deployed to the web server the navigation buttons (browse sequence) do not work with Google Chrome. The buttons work correctly when the webhelp is installed on my local machine. I experienced this same issue with RH10 and was hoping that RH11 corrected the problem. Any ideas?
Copy link to clipboard
Copied
First, did you update your version with any patches? Next, is JavaScript enabled in your browser?
Copy link to clipboard
Copied
I have updated RH10 with the patch from the following web page: http://helpx.adobe.com/robohelp/kb/webhelp-issues-robohelp-versions-10.html
I have not applied any patches to RH11.
JavaScript is enabled.
Copy link to clipboard
Copied
Try updating RH11 and regenerate the help
Copy link to clipboard
Copied
Updating RH11 and regenerating help did not correct the issue. The browse sequence buttons are not enabled (i.e. when I place the cursor over the buttons, the cursor does not change from a pointer to a hand/finger).
Copy link to clipboard
Copied
Hmm, that’s really strange – you say it works if the WebHelp is local, but not if it’s on a web server? If anything, I would expect the reverse with Chrome and its paranoia over local HTML files. I don’t remember if any of the sample projects that ship with RH have browse sequences, but you could try playing with them to see if the effect is “project-specific” or something that’s busted. If the sample behaves the same way, then you need to report it to Adobe using the http://www,adobe.com/go/wish form.
Copy link to clipboard
Copied
The samples do have browse sequences.
Click Open on the RoboHelp Starter page and then click Samples in the ribbon on the left.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
I tried several of the Robohelp sample projects and found that the browse sequence buttons worked when deployed to the webserver.
I then created a new project with just a few topics, created the browse sequence, and then deployed to the webserver. Still had the issue with the browse sequence navigation buttons not being enabled.
Hmmmmmm......so I then had a look at the Generate webhelp settings....comparing the sample project with my project. After a bit of fiddlilng, I found that the issue is with the "Add Breadcrumbs Links" under the Navigation folder for the Webhelp Settings. When I enable breadcrumbs, the browse sequence buttons do not work. I tried this with one of your sample projects and got the same results.
So now I know what is causing the issue, but I don't know why.
Copy link to clipboard
Copied
LOL – the samples are Adobe’s, not Peter’s ;>)
Now that you’ve isolated the cause, make sure you report it as a bug.
Copy link to clipboard
Copied
When I said "your", I meant Adobe's not Peter's. Great idea, BTW, Peter....to try one of the sample projects with browse sequences. I thought it was possibly something weird that had inadvertently creeped into my project.
Copy link to clipboard
Copied
Umm, @AltairLiz, it was actually me that suggested using the sample project to test the issue – Peter just confirmed that they have browse sequences to play with in them. Good work in isolating the issue ;>)
Copy link to clipboard
Copied
@AltairLiz
I finally got to set up a test for this. I generated the Employee Care 2 webhelp on a new installation of RoboHelp. I have not applied the recent updates referenced in Announcements on the forum.
The browse sequences and breadcrumbs were enabled and the browse sequences and breadcrumbs both worked just fine in Chrome.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
Nice detective work on that.
As a further test, let's try this. Assuming you want breadcrumbs to be a part of the project, does the same behavior manifest if you add a Breadcrumbs placeholder to a Master Page and associate the Master Page with the desired topics? If taking this approach, you would turn off Breadcrumbs in the Single Source Layout recipe.
I'd also hope you would take a few moments and report the issue to Adobe as a bug using the link below:
Cheers... Rick