I am working in a RH 10 project upgraded from a RH 9 project. When generating Webhelp, local output displays fine, but after compiling and uploading to our online app, the TOC and Index do not display - what I mean is that the tabs exist, you can click them, but they are empty. Search doesn't work either, plus the logo in the header doesn't appear, though it is in the images folder that is uploaded.
Some more details:
I'd be glad to provide any other details if needed.
It sounds that way. Have you checked that:
If the answer to both these questions is Yes, it is time to suspect the application build process.
I could check in the full project folder, minus the RH file itself, which is quite heavy, and have the application load the main HTM in the !SSL! folder. Would that be a possible solution? I'm not sure why the app would need the whole folder structure, but I suspect that it may be missing a file in the main project folder.
New discovery: If I compare the wxdata folders of the current and a previous, working version, all XML files seem to be missing from the current folder, except for synonym.xml and whfts.xml. The old folder includes package files (for example, package_25.xml) and 'wh' files, as shown in the attached screenshot. To clarify, I am now missing most of the XMLs in the screenshot.
I suppose that it wouldn't be correct to copy those over to the new folder, because RH is supposed to be generating them automatically. My questions are, if anybody knows:
Unless your project references these package_xx.html files in some way I have no idea whart they are. They are certainly not part of the normal webhelp output. Try this:
Thanks for these suggestions.
I tried Republish All, plus turning on Mark for the Web, which seems to have been turned off. After uploading and compiling, I still see the same - empty TOC/Index tabs and missing logo.
The only thing I haven't tried is switching from DHTML to Pure HTML, however, I'm not sure if this is even related.
I think it's definitly an issue to investigate with the development team to see if something is happening when the files are being compiled.
Just a side note. The option for Mark of the Web is only going to apply when you view content from your local hard drive and you are using Microsoft Internet Explorer as your browser. If you are uploading this content to a server, the option may as well not exist. So it won't matter if it's enabled or not and would have no bearing on this situation.
Changing the option from DHTML shouldn't really affect it either.
@Colum - The package_xx.html files are certainly part of RoboHelp output. After you generate WebHelp, you should see them in the whxdata folder.
I think we have established that the files display fine immediately after generating, no? That would then suggest that the issue is entirely in the lap of perforce and what the development team is doing. (or, more accurately, NOT doing)
Thanks, Rick! I hope you're right and that we'll find the culprit.
Regarding the package_xx files, the only suspicious thing I found was that in a previous RH project with the same content (more or less), these were outputting as .xml files, and in my case they were .js files. Could this have anything to do with the issue?
I do suppose it's possible. But I don't think it's likely. Adobe simply changed the file naming conventions of those small chunks of data that make up the TOC and Index and Search. It's possible that your dev team may not know to include them in the build. And if that's the case, it would certainly explain why it works for you locally immediately after you generate but not after the dev team puts their hands on it.
Essentially you just need to show one of them that it works on your PC before you commit the files to source control, and ensure ALL the output files are actually being uploaded to Perforce.
I suppose one test would be to just grab a copy of all the files you are placing into Perforce and plop them on a machine. Try to open WebHelp. If it works, you know beyond a shadow of a doubt that your developers are doing something wrong or not managing to get all the files. But if it fails for you, I'd suspect that you aren't managing to get all the content uploaded properly into Perforce.
Eurika! One of the developers simply helped me upload the folder holding the output files to Perforce, and after compiling the last application build, the help is displayed perfectly.
So, I guess it really was a Perforce-related issue. Either something to do with how my workspace is configured as opposed to that developer's, or the fact that he didn't only override the files in the relevant folder, but also deleted the extra files that were probably there from previous versions (I didn't do this because I was afraid to lose data, etc., when in fact the old XMLs and JSs may have been the culprits).
If anyone encounters this problem, think the best practice is to clear the entire folder on Perforce and replace it with the last version of fresh output every time a live update is needed for the help.
Thanks for the help, @Column and Rick .
Did you hear that sound?
That was the sound of applause coming from Kansas City, MO!
Pleased ti see that you got it sorted! And thanks for posting back what the issue was. It may help someone down the road!