eZ Publish handles cache directories inconsistently. Some cache files are stored in both var/cache/ and var/mysiteaccess/cache/ But at least ezcontentlanguage_cache.php is read only from the root level (var/cache/).

This can cause issues with multisite installations. This can be fixed via setting the CacheDir directory, but it would be consistent that the system uses the created directories (underneath var/mysiteaccess/).

The system creates the cache directories, but fails to use them correctly. See the directory structures below (non-relevant lines omitted):

listing of var:

[foo@bar var]# ls -la
drwxr-xr-x 10 apache apache 4096 Sep 24 08:53 cache
drwxr-xr-x  2 apache apache 4096 Sep 24 09:08 cache2
drwxr-xr-x  6 apache apache 4096 Dec 18  2009 mysiteaccess1
drwxr-xr-x  6 apache apache 4096 Sep 24 09:07 mysiteaccess2

listing of cache/mysiteaccess1:

[foo@bar siteaccess1]# ls -la
drwxrwxrwx  4 apache apache 4096 Sep 24 09:10 cache
drwxrwxrwx  2 apache apache 4096 Sep 17 22:23 log
drwxrwxrwx  4 apache apache 4096 Sep 23 17:39 storage

listing of cache/mysiteaccess2:

[foo@bar siteaccess2]# ls -la
drwxrwxrwx 12 apache apache 4096 Sep 24 09:13 cache
drwxrwxrwx  9 apache apache 4096 Sep 24 09:08 cache2
drwxr-xr-x  3 apache apache 4096 Sep 24 09:09 log
drwxrwxrwx  5 apache apache 4096 Jan 25  2010 storage

Steps to reproduce

Setup a site with multiple siteaccesses (with unique vardir)

Fill caches and observe that the system creates the cache directories underneath the siteaccess (cache by default), but fails to use them.

Add a unique CacheDir declaration to the sites and observe that the cache directories are now created in multiple locations, but only the ones in the root seem to be used (at least for ezcontentlanguage_cache.php)