[TYPO3-dev] problem with compressed CSS: SOLVED!

[bernd wilke]

On Tue, 04 May 2010 03:36:24 +0200 Steffen Gebert wrote:

> Am 04.05.2010, 01:52 Uhr, schrieb Steffen Gebert
> <steffen at steffen-gebert.de>:
> 
>> Am 04.05.2010, 01:49 Uhr, schrieb bernd wilke <t3ng at pi-phi.tk>:
>>
>>> Content-Encoding: gzip
>>> Content-Length: 14827
>>> Content-Type: text/css
>> looks good
>>
>>> the 'content' is the same still compressed file.
>> So you see weird characters when displaying the file in FF, and not the
>> stylesheet?
> 
> I just had a look at Bernd's PC.
> He had mod_deflade and mod_mime active, we deacticated both, but nothing
> changed. Headers are correctly sent, but all browser simply show the
> encoded version.
> 
> Lars mentioned that he had problems with the order of rules in
> .htaccess. Please always use the order from misc/advanced.htaccess! He
> also mentioned that - after fixing this - the browser cache has to be
> cleared (esp. safari seems to be very stubborn on using the wrong
> versions..)
> 
> Hope somebody has better ideas to solve the issue..
> 
> Steffen

After a lot of tries activating and deactivating different modules: 

my .htaccess was ignored in default-configuration!

my solution:
in /etc/apache2/sites-available/default chaneg from:
        <Directory /var/www/>         
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None                       <======
                Order allow,deny                         
                allow from all                           
        </Directory>  
to:
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride All                        <=====
                Order allow,deny
                allow from all
        </Directory>

so keep in mind, that .htaccess must be computed at all!

can TYPO3 test this and deactive compression done by TYPO3 instead of 
configured compressionLevel?


the compression of all files by apache2 worked by default. so for me just 
a merging of all CCS/JS would result in compressed transfers with less 
requests.


should this give an additional configuration-switch in install-tool?
[ ] merge all CSS / JSS

or depend on compressionLevel?
merging is done if compressionLevel > 2
zip is done if compressionLevel > 4


bernd
-- 
http://www.pi-phi.de/cheatsheet.html