Fix for compression bug in most of version 2 of Xoops.

Enjoy,

ATB

Catz

thanks

Herko

I'm putting in some code in XOOPS 2.1 CVS now. I'd be obliged if anyone could test it with gzip compression and see if it works. As far as I can tell, it does, but I don't know enough about the matter to know for sure.

It'll be in CVS Nightly tomorrow (available from xoops.org front page) - if you want to check the code, it will be in the class/theme.php, XTheme's constructor.

Your Welcome

ATB

Catz

oh yeah - forgot

Thanks, Catz.

hehe!

Np Mith

ATB

Catz

er... where does this code go? I mean, in which file do I insert this to get compression to work again?

Also, shouldn't the compression be done before caching, so that if there's a cache hit, it doesn't need to be compressed again (the compressed content can just be sent out). Will be _much_ more efficient, as the server will be able to handle MUCH more load.

Thanks

Sumit.

Ok this appears to work, yet not as expected (by me), as in before adding this to class/theme.php

I had decided that
.htaccess
php_value output_handler ob_gzhandler
worked better then:
php_flag zlib.output_compression on

Yet as the instructions in php says, if zlib is loaded, so on changing this last night and then visiting my site, there was huge delay after all the work done lately.

So then questioned where, as I had seen bouncing like it before as browsing and realized it was the hack working for gzip of Xoops.
so first removed the htacess ob_gzhandler that was there and this had indeed slowed it.
So then tested does XOOPS now have gzip, yet on a gzip test no ,
yet the site is faster on content, so it looks like this doesn’t compress from the head of the theme, yet the head of the XOOPS content.(there are also references in the file download extensions for gzipping them)

So then as that says if zlib loaded, this I have now added to the htaccess

php_flag zlib.output_compression on

To finish it, so then XOOPS content is gzip (I think) and then files as read, are done via the htaccess.

Sill in testing, yet will see how it handles after a day or so.......