Content Encoding Error in parts of the manager after upgrading to Evolution?

I am having the same issues. Can´t access manager frontpage neither the whole configuration section.

Besides this the installer is having problems when you choose a different language than english (image dir not writeable...).

Would be nice to get a solution soon, because i want to upgrade all of our modx systems.

The content compression issue is definitely due to having zlib compression running - as soon as I enabled that on my local install, I managed to replicate the reported issues. What puzzles me is why it only affects a few manager pages - very strange!

@slackstar: What are the permissions on your image directory? Does this error only get reported when you choose a language other than english? I’m not sure how the language change would affect the pre-install checks to be honest.

Quote from: garryn at Aug 03, 2009, 11:27 AM

The content compression issue is definitely due to having zlib compression running - as soon as I enabled that on my local install, I managed to replicate the reported issues. What puzzles me is why it only affects a few manager pages - very strange!

@slackstar: What are the permissions on your image directory? Does this error only get reported when you choose a language other than english? I’m not sure how the language change would affect the pre-install checks to be honest.

I had just tried with english, and zlib running, and the problem exist there also.

Quote from: slackstar at Aug 03, 2009, 08:59 AM

Would be nice to get a solution soon, because i want to upgrade all of our modx systems.

Slackstar,

Current workaround is posted in this thread: http://modxcms.com/forums/index.php/topic,38262.msg230789.html#msg230789

Disabling Zlib compression will work during the interim...

Aha, just tried a few things - it would seem the problem could be related to the buffer size being used when zlib compression enabled. Altering my .htaccess as follows seems to solve the issue for me:

Anyone wanna try this fix out?

An alternative that should work is probably to disable output comrpession for the manager completely. Try putting the following in your htaccess inside your /manager directory:

Quote from: rthrash at Aug 03, 2009, 11:58 AM

php_flag zlib.output_compression Off

Ryan, I had thought about this as well. Does anyone know what commit in the SVN could possibly lead to this behavior?

Quote from: garryn at Aug 03, 2009, 11:45 AM

Aha, just tried a few things - it would seem the problem could be related to the buffer size being used when zlib compression enabled. Altering my .htaccess as follows seems to solve the issue for me:

php_flag zlib.output_compression 8192

Anyone wanna try this fix out?

After inserting this, I got a error 500...

Mysql version: 5.0.32-Debian_7etch8-log
PDO Driver for MySQL, client library version: 5.0.81
PHP Version: 5.2.9-0.dotdeb.1
Memory size: 128 mb.
Apache: 2.2.3
Suhosin Patch 0.9.7 and Zend Scripting Language Engine installed.

Not sure if this has anything at all to do with the issue, but I remember seeing that error message in a post on php.net the other day in reference to text editors adding characters to the files.

http://us2.php.net/manual/en/function.ob-start.php#91963

Maybe it helps, maybe not

I suspect Suhosin is to blame there for that one Henrik.