I have a really strange problem with IE6 and would be extremely grateful for a) opinions, b) a second look and c) any help that can be offered as this thing really has me stumped.
I'm running 4.7 CVS (as of today) and all modules installed are also CVS as of today. Amongst the contributed modules that I'm running are blockbar and controlpanel. I don't think either of these two are the problem but I'm mentioning them because the problem seems to occur round about where those modules kick in.
In FF, Opera, Mozilla and IE7 (beta 2), my site displays fine, every time, every page. But in IE6 (with SP2), it doesn't. Well, not always. And it is the not always bit that has me stumped.
Sometimes pages appear fine. For example, /user nearly always appears fine. Most node pages (as far as I can tell) appear fine. But the home page appears fine only sometimes. As the attached screen_shot shows, /front_page occasionally shows up only partially rendered. The code just stops. Right about the time it starts to display the body of the page. Other times it's fine. And at this precise moment, going to root (www.vcommunity.org.uk) just gives me "Page cannot be displayed". If I attempt to go to /user, I get a similar "weird" page. But /user/register appears fine in IE6 with no problems whatsoever. If I follow a link on there to, say, the events calendar, again, displays fine.
Just what is going on!?!
I have been through every PHP file (.inc, .module) and have made sure that there are no extraneous whitespaces at the end of any file. I've reloaded every file just in case but I still get the same results.
My questions:
a) Does anyone else get this when they visit my site in IE6? Or is it just me?
b) If it is not just me, what is causing it?
I'm very grateful for any help or opinions offered.
Regards
Patrick
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | drupal_screenshot_sample_10.png | 214.41 KB | Patrick Nelson |
Comments
Comment #1
Patrick Nelson commentedSorry forgot to attach screenshot.
Comment #2
markus_petrux commentedI have also observed something similar, even with current HEAD. Only partial page seems to be sent to the browser, and it only happened in IE6.
Disabling page cache solved the problem. Strange.
Comment #3
Patrick Nelson commentedThat worked just fine. It is as if IE6 never knew there was a problem. So, does this mean that the page caching system is buggy?
Comment #4
ebruts commentedI can verify this with IE 6.0 SP2 and drupal cache enabled.
Marked it as critical as it will break many sites.
Comment #5
ebruts commentedActually I did not test it on a clean install but had statistics logging enabled. Here is some debug.
This is what Internet Explorer sends
Notice the Fatal error at the end? This might prevent IE6 to correctly decode the gzip encoded content.
So the next time you try to reload the page, IE sends and receives the following
and thus uses his internal cached site (which it probably is not able to decode).
Whereas other browsers like Firefox or Opera are able to decode it correctly even with the Fatal error in plain text.
Comment #6
ebruts commentedThere seems to be two problems to worry about. The first, rather simple, is about fixing statistics.module.
The other might not because it is a general problem.
*_exit is called even on cached pages, that is good to have for running statistics etc. but as soon as some exit hooks start to actually output content it will cause problems with the caching system as it might (on most systems it will) transfer the cache in gzip encoding -- but the output of the exit hook will be plain text.
Comment #7
moshe weitzman commentedexit hook should not be outputting anything. if it does, it should know that stuff might not always work.
sounds like a statistics bug
Comment #8
moshe weitzman commentedComment #9
ebruts commentedHas been fixed by Dries.
http://drupal.org/cvs?commit=26849
Comment #10
(not verified) commented