Last modified: 2010-05-15 15:42:48 UTC
This will inevitably be something basic to resolve, but for the life of me I
can't figure out what it is. I've also looked for similar reports (to avoid
duplication) and haven't found any.
In Firefox v2 the dev wiki I'm setting up displays/renders properly every time.
However in both IE v7 and v6.0.29 there are intermittent display problems
occurring. Initially a generic error appears indicating "Internet Explorer
cannot display the webpage" however if you refresh the page enough times it will
This happens most frequently on log-in.
I've also just installed this yesterday, so aside from the installation settings
I haven't customised much.
Problems *had* been occurring in which the page would not load completely.
However as per another bug report here, I've included "$wgNoOutputBuffer =
true;" in LocalSettings and this issue doesn't seem to be occurring anymore.
The server specs we're using are:
IIS (I believe version 5)
Probably unrelated to the issue, but this doesn't belong:
PHP Warning: Module 'mysql' already loaded in Unknown on line 0
PHP Warning: Module 'mysqli' already loaded in Unknown on line 0
You might want to try installing 1.9.0 before continuing debugging attempts; a
number of compatibility issues were resolved in 1.9.
Thanks, I'll give them a shot. Will let you know what happens. Cheers :)
Update: I've upgraded to MediaWiki version 1.9.0 and am still experiencing the
same problems. In fact the issue with truncated pages has returned - including
true;" no longer seems to resolve the problem (may have been a coincidence
previously), and page refresh no longer works either.
As before, Firefox version 2 is not experiencing any problems.
I'll attach a screenshot depicting the extent to which the page loads in case it
helps. Would you like the code too?
Created attachment 3045 [details]
Screenshot depicting truncated page in Internet Explorer
I located the source of the problems. The solution is outlined here:
<strong>Bug 3000: REQUEST_URI is not set under IIS</strong>
Thanks for your help everyone.
*** This bug has been marked as a duplicate of 3000 ***