Hi i think that is memory in your server, check logs!
Best Regards
admin panel CSS error
Re: admin panel CSS error
Do you have this code at the top of your stylesheet.php file? It is there to fix exactly this problem!
Zlib output compression uses less network bandwidth, so it makes pages load faster. But it was screwing up CSS intermittently on IE 6, hence the test in stylesheet.php.
Actually, for those people with bandwidth constraints, it might be worth refining that test, as hopefully IE 7 isn't as flaky as IE 6 in that respect. Can you test with IE 7 and tell us whether the problem goes away?
Cheers,
- Martin
Code: Select all
if(isset($_SERVER['HTTP_USER_AGENT']) && preg_match('/MSIE/', $_SERVER['HTTP_USER_AGENT']))
{
@ini_set( 'zlib.output_compression','Off' );
}
Actually, for those people with bandwidth constraints, it might be worth refining that test, as hopefully IE 7 isn't as flaky as IE 6 in that respect. Can you test with IE 7 and tell us whether the problem goes away?
Cheers,
- Martin
-
Pierre M.
Re: admin panel CSS error
Hello,
http://wiki.cmsmadesimple.org/index.php ... quirements
Hopefully Martin is going to change this
Pierre M.
IE6 is not a supported admin browser.secam wrote: I noticed, that in some my pages admin panel ...
It is happening when viewing with IE6, but with firefox everything is Ok.
http://wiki.cmsmadesimple.org/index.php ... quirements
Hopefully Martin is going to change this
Pierre M.
Re: admin panel CSS error
Sorry, my mistake. The ZLIB "fix" only works for public pages, because stylesheet.php isn't called for admin pages.
Secam: you could try disabling ZLIB globally as a test, to check whether compression really is the problem with admin pages in IE 6.
The easy thing to do is to use a better browser, but if you were feeling keen to experiment, you could try and work out where the ZLIB fix would need to for admin pages. You might try adding it to the very start of SendHeaders() in lib/classes/class.admintheme.inc.php and see if that works.
Cheers,
- Martin.
Secam: you could try disabling ZLIB globally as a test, to check whether compression really is the problem with admin pages in IE 6.
The easy thing to do is to use a better browser, but if you were feeling keen to experiment, you could try and work out where the ZLIB fix would need to for admin pages. You might try adding it to the very start of SendHeaders() in lib/classes/class.admintheme.inc.php and see if that works.
Cheers,
- Martin.
Re: admin panel CSS error
Well, SendHeaders() was only a guess, sorry. I don't know the CMSMS source code very well.
The IE6 CSS rendering bug, when compression is used over HTTP, does not seem to be very well known. I only found it by accident (hence the fix in stylesheet.php). Annoyingly, it is very intermittent: it doesn't happen every time, and it doesn't happen on every web page. My guess is that there's a race condition in Microsoft's code, as if they've tried to be clever by rendering content before the download has finished.
It seems to depend on the CSS and HTML content. I chatted with a sysadmin at a large commercial website (not running CMSMS). He didn't know of the problem, despite using a hardware accelerator appliance to compress every file leaving the web farm. So it's probably just luck whether this bug affects a particular website or not, since there's no way to know what type of content triggers the problem.
Cheers,
- Martin.
The IE6 CSS rendering bug, when compression is used over HTTP, does not seem to be very well known. I only found it by accident (hence the fix in stylesheet.php). Annoyingly, it is very intermittent: it doesn't happen every time, and it doesn't happen on every web page. My guess is that there's a race condition in Microsoft's code, as if they've tried to be clever by rendering content before the download has finished.
It seems to depend on the CSS and HTML content. I chatted with a sysadmin at a large commercial website (not running CMSMS). He didn't know of the problem, despite using a hardware accelerator appliance to compress every file leaving the web farm. So it's probably just luck whether this bug affects a particular website or not, since there's no way to know what type of content triggers the problem.
Cheers,
- Martin.
