Copy link to clipboard
Copied
We recently upgraded from RH8 to RH10, and almost immediately encountered (what appears to be) an old issue.
Using Adobe TCS 4.0, we create our content in FrameMaker 11, then link to Robohelp. After generating Webhelp, we tested the output from a local machine. Everything worked as expected.
We then checked the files into Microsoft TFS and hosted the Webhelp on an HTTPS server. However, when we tested the output using Internet Explorer 9 and Chrome 23, we found that:
We don't use an index, but I assume that would not work either. I've attached screenshots so you can see the problem:
Adobe previously released a fix for the whutils.js file for RH8 and RH9, which used to be hosted here: https://acrobat.com/#d=WqbdTq-2R79ToU08-zfBEw (link now broken). I am assuming it is a similar issue with a similar fix. I will file a bug report, but I wanted to see if the community had any quick fix since we're on deadline.
You can see the full forum history here: http://forums.adobe.com/thread/822754?tstart=0
So after engaging our development team, we have resolved the issue for the present.
We had two new variables with our process for this release:
As it turns out, the second variable is the culprit here. RH is off the hook for now. For reasons yet unknown, Visual Studio was excluding files (without notice)
...Copy link to clipboard
Copied
I'll first identify myself as Michael's colleague, and then add two more things:
Copy link to clipboard
Copied
So after engaging our development team, we have resolved the issue for the present.
We had two new variables with our process for this release:
As it turns out, the second variable is the culprit here. RH is off the hook for now. For reasons yet unknown, Visual Studio was excluding files (without notice) from checkin. Once we performed an additional step (right click Visual Studio directory > Add Items), it picked up the missing files and everything worked as expected in the staging / QA environment.
The missing file was WebHelp > resource > resource_.xml.js.
Next step on our end is to test the integrated RH > TFS Source Control. We didn't (thought we didn't) have enough time to test publishing WebHelp directly to TFS using the RH 10 plugin - not sure if it would make a difference or not. We'll test that properly between releases and see if it works or not.
Very, very strange though that Visual Studio would behave that way over such a simple, every day version control procedure. My dev team is flummoxed - and these guys are good enough for that to be a genuine rarity.
Copy link to clipboard
Copied
Thanks for the update Daniel. Feel free to update this thread if you find anything esle out with the RH / TFS integration testing.