Issue with Drupal multisite

[davem]

It would appear something has changed so that Civi no longer wants to install in a Drupal multisite tree...

We've done a manual install just to test 4.4.6 and it will not install without installing in sites/default even if the drupal is installed in sites/site_name then CiviCRM still needs write access to sites/default and generates a civicrm.settings.php in there.

Moving it out afterwards and changing the paths in the config file results in a working CiviCRM in every respect except when using kcfinder in the WYSIWYG in mailings and external url tracking (and probably some others too). It seems to be fine on sites we've upgraded to 4.4.6 but not on a new install.

Is this a change we missed or not intentional?

Thanks

Dave

[circlebails]

Just to clarify this:

Vanilla drupal-7.31 / CiviCRM-4.2.17 drupal not installed in sites/default  sites/all/modules/civicrm/extern/url.php "could not load settings file:"

Vanilla drupal-7.31 / CiviCRM-4.3.8 drupal not installed in sites/default  sites/all/modules/civicrm/extern/url.php "could not load settings file:"

Vanilla drupal-7.31 / CiviCRM-4.4.6 drupal not installed in sites/default  sites/all/modules/civicrm/extern/url.php "could not load settings file:"

Vanilla drupal-7.31 / CiviCRM-4.2.17 upgraded to 4.3.8 drupal not installed in sites/default  sites/all/modules/civicrm/extern/url.php "Missing input parameters" So after an upgrade CiviCRM magically works in a multi site setup.

What mysteriously happens during an upgrade to suddenly make this work?

We are asking as we host many (150+sites) as multi site but fail to see why CiviCRM

1: Will not install as a multisite (civicrm.settings.php is always created in sites/default regardless of site it is being installed on in multisite).

2: Will not operate correctly in Multisite until it has been upgraded.

Thanks

Bails