Core

Ok, this one is quite complicated to explain.

In short: The Backend does not work if you use multiple domains with virtual hosts (see screenshot). Using paths relative to TYPO3_site for packages would fix this bug.

I have the following Apache Setup for virtual hosts:

<VirtualHost *:80>
  ServerName local-dev
  ServerAlias *.dev
  VirtualDocumentRoot /var/www/%-2+
</VirtualHost>

This means, when I visit www.example.de.dev Apache looks for files in /var/www/www.example.de/* and when I visit www.example.com it looks in /var/www/www.example.com/*

(Both folders are symlinks to the same folder)

This makes it possible to easily work on different domains in a local setup.

When I now visit the backend via www.example.de/typo3/ the package manager sees /var/www/www.example.de as Document Root and uses it as packagePath.

This information is written to the Cache (cache_core/PackageObjects_HASH)

Then I visit the backend via www.example.com/typo3/. The cache is read and the package paths are /var/www/www.example.de/typo3/sysext/t3skin/ instead of example.com.

This leads to incorrect links to stylesheets (see screenshot).

Using relative paths in the cache would fix this problem. Another fix could be to use different caches based on the hostname or document root.