Bug #22967
closed
Backend not properly formatted when compressionLevel has been set
0%
Description
Not sure if it occurs in the RC1 candidate (wasn't able to select final release from dropdown box)
With $TYPO3_CONF_VARS['BE']['compressionLevel'] = '5';
in the Install Tool and having added the lines (according to the Install Tool):
<FilesMatch "\.js\.gzip$">
AddType "text/javascript" .gzip
</FilesMatch>
<FilesMatch "\.css\.gzip$">
AddType "text/css" .gzip
</FilesMatch>
AddEncoding gzip .gzip
to the .htaccess file, the backend looks weird (see screenshot). Even after deleting the temp_CACHED_* files in typo3conf. Tested with Safari 5 and Firefox 3.6.3 on MacOSX.
(issue imported from #M14828)
Files
Updated by Mark Kuiphuis over 14 years ago
Found the solution :-)
The release notes (http://typo3.org/download/release-notes/typo3-44/) didn't say anything about deleting the files in typo3temp, but the NEWS.txt file in the introduction package did)
So after deleting them and deleting the temp_CACHED_* files in typo3conf the backend appeared normally with compressionLevel set.
Updated by Steffen Gebert over 14 years ago
There should be no need to clear typo3temp/ because of the compressionLevel.
You said clearing typo3conf/temp_CACHED* is the solution. I doubt that the error was caused by compressionLevel, but more because of the setting $TBE_STYLES['skins']['t3skin'], which is new, but required for all skins in 4.4.
This is in ext_tables.php of EXT:t3skin, temp_CACHED* is a merged file of all ext_tables.php, so this cache has to be cleared.
Clearing typo3conf/temp_CACHED* is also done by clearing All caches or just the Configuration cache (as it is the Configuration cache).
To be honest, I have no idea, whether the Upgrade Wizard triggers a cache clearing. I assume the verisonNumber-Update does, as it writes to localconf.php, which is also cached in the configuration cache.
The gzip compression feature should work directly, when compressionLevel is set and the required RewriteRules are configured IIRC.
Updated by 