HTML doc opens on local device, but not on Web server

[keuler]

Hi. New issue where HTML docs won't open correctly. Plz assist.

Scenario:

1) I have a project that publishes to a HTML5 target in tri-pane format. (Windows 7, Flare 11).
2) The HTML docs are test-published to my company's linux based web server (Apache, I think).

After publishing, when I go to bring up the output in a web browser, the TOC the topic area aren't populated with content. Also, nothing happens when I try to search for something.

Odd thing is, the HTML docs appear fine when launched from my the main output file (eg, via the View option). Search doesn't work on the local copy either, although it does show a spinner indefinitely.

My IT guy suspects there's a javascript error somewhere. However, I've done nothing fancy since the output worked a couple days ago. (I just added a few divs for formatting.)

Thanks in advance if you can help.

[Mike Kelley]

I personally haven't encountered your issue, so I would need more information. Bring up both instances of your output (local and server) in Chrome, and then open Developer Tools for both tabs (F12, or right-click anywhere on the page and select 'Inspect Element'). In the console you'll probably see some error-based red text. If you could report that it might help someone figure out the issue.

[Nita Beck]

What browser does this happen in? All? Some, and which?

I've seen this in IE and, in my case (your mileage may vary), it was solved by making sure, in the target on the Advanced tab, to select "Add meta tags to content", which enables the meta tag reading "<meta http-equiv="X-UA-Compatible" content="IE=edge" />" that is already populated in the field. According to the Flare 11 documentation, "This tag tells Internet Explorer to render with the latest version."

[Feebeegeebee]

Hi,
I've experienced similar problems when viewing output on a non-Microsoft (Linux) web server.
The output launches but everything (toc, index, main window) appears blank.

There is a bug if you enable the "Do not use Content folder" option AND you are outputting to HTML5.
There are two 'Resources' folders at the root level of the project. One is for the HTML5 code and is required and the other is the 'resources' folder for the project. However, in Windows you cannot have two folders with the same name so they get merged. Project files need 'resources' and HTML5 code is looking for 'Resources'. Both are required.

If you rename the Resources folder in your Content Explorer to something else (e.g. "properties"), rebuild your help and re-publish it to your webserver, this might just solve your problem.

I hope so. I fell over this issue yet again only recently with a legacy project.
Regards,
Feebeegeebee

[keuler]

All- Thanks for your comments.I took a look at in Chrome.

One interesting thing: In all builds that are failing as described, the build includes a "Service" directory. Older builds (that don't include this directory) work fine.

In some (but not all) cases, the Chrome Developer Tool reports this error:

http://intranet/keuler/MinMain_Working_ ... Subsystems

The actual Service directory does contain a Service.asmx item in the path, but it's a file, not a directory.

Do any of you know what this service directory is all about?

Looks like this could be a job for tech support.

[keuler]

MadCap tech support fixed this one. Issue was that I accidentally checked the option "'Include server-side Help engine". (I don't publish to an IS Server.)