OnePay wrote:
In our implementations "$xoopsConfig['gzip_compression']" returns NULL (it is turned on in the admin), so it would not even try to use ob_gzhandler. However, when I remove the complete if-statement and just put "ob_start('ob_gzhandler')" there is no "Content-Encoding: gzip" in the headers. Only after placing the "ob_start('ob_gzhandler')" on the very first line (in the first else-statement) in the "common.php" file it outputs the site using gzip compression.

Note: I have added this to the bug list.

ackbarr wrote:
since XOOPS already uses smarty for content caching, I wouldn't think it to be desirable to switch to or add a different caching engine.
Until this bug is fixed, if you want to ensure that your pages are gzip encoded you can disable the "Use gzip compression" setting in System -> Preferences -> General Settings and add the following to XOOPS_ROOT/.htaccess

le="color: #000000"><?php php_flag zlib.output_compression on php_value zlib.output_compression_level 5

zlib.output_compression_level can be from 1 to 9, with 9 being the highest compression. Normal settings are usually between 3 and 6.

Please note that your host must be using Apache and has to allow you to create .htaccess files for this workaround to function.

Jan304 wrote:
If people now want to enable gzip they can try out a lot of codes...