Re: Missing pages
| From: | Gabor Hojtsy | Date: | Tue, 17 Dec 2002 16:49:06 +0000 |
| Subject: | Re: Missing pages | ||
| References: | 1 2 3 | Groups: | php.doc.chm |
| Request: | Send a blank email to php-doc-chm+get-577@lists.php.net to get a copy of this message | ||
> The PHP site says that we should not report missing pages in the
> documentation, because they have software that monitors that, stop
> bothering us, etc. etc. How is that handled in the CHM file?
> I can't open php_manual_en.chm::/function.sizeof.html, in case you're
> wondering. I remember I had that same problem with another function/page
> the other day, but I didn't write it down, so now I don't know what page
it
> was. Sorry about that.
> Well, a quick inspection revealed that I cannot access the Preface,
> Getting Started, What Is PHP, many pages in the "Appendixes", "Streams
API"
> and "FAQ" nodes and absolutely none of the pages in the "HTML Help
Edition"
> node.
> Another glitch I've run into is that when a page cannot be accessed and
> that IE default error page, I have to hit the Back button three times in
> quick succession to go back to the previous page. Is JS really necessary
in
> the navigation functions?
> I'm using CHM version 10, October 25, in Windows ME with IE 5.5.
Yep. We introduced a workaround for IE 6, which works around this behaviour.
The workaround is simply a JS array with all the file names with notes,
so no missing pages are displayed. The error you encounter is a special IE
5.5 / 6 bug, and it is adressed in the latest MS service packs. The time we
discovered this error, we have only known that it is IE 6 related, so the
workaround is only active if you use IE 6. However it turned out after that,
that it also affects IE 5.5.
What you can do about it?
- Upgrade your IE / patch with a service pack
- Apply the IE6fix.reg file which is included in the distribution
to your registry (double click on that), and so all pages will
display correctly. This enables friendly HTTP errors, which are
not ideal in some development situations, but the CHM will work
at least.
The workaround was not active for non IE5 browsers, because the JS array
takes a long time to load into memory, and it may not be cached... Maybe
I'll activate it for all browsers to make sure we never hit this bug
again...
Goba