The file search driven by the user provided URL described in the documentation included in the body of default.settings.php does not appear to be implemented by the code that determines the path to settings.php implemented as conf_path in file bootstrap.inc.

This appears to defeat the implementation of sub-directory multi-site configurations as described in the default.settings.php documentation.

This has previously been raised in http://drupal.org/node/174279 but the documentation still describes behaviour that does not appear to be supported by the implementation.

Comments

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented
Status: Active » Postponed (maintainer needs more info)

Can you please provide more information about exactly what you think is wrong and how it should be fixed? (Or alternatively, maybe just close this issue and reopen the other one you linked to, if there is something more to do there?)

lostchord’s picture

lostchord CreditAttribution: lostchord commented

I think the documentation in default.settings.php (and anywhere else it is duplicated) should be updated to more correctly describe the behaviour with respect to sub-directories.

The material available on this site all seems to point to some sort of 'magic' being required in order to get this feature - subdirectory multisite - to work. This seems to either involve symlinks (which didn't work for me) or Apache Alias directives (which did work for me).

Neither of these approaches can be deduced from the behaviour descibed in the 'documentation' which describes how the user supplied URI is processed to generate the search paths. The code that implements this ignores the URI so you are really mislead by the documentation.

So, can the code and the documentation be made to agree? Or the documentation expanded to more clearly indicate the requirements for getting this feature to work?

I would also suggest that the error returned from the install process when it cannot locate settings.php be expanded to include the locations that were actually searched. This would be a far better diagnostic than the current 'You failed' message.

Cheers.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Issue tags: +Novice

Can someone confirm if the documentation doesn't match the behavior?

If no response in a few months, I think we can close this.

Status: Postponed (maintainer needs more info) » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.