Remove /sites/all in favor of top-level directories [#2209283]

Background

Since #1724252: Allow and encourage top-level directories instead of /sites/all/* directories, site-agnostic extensions can be placed into top-level directories.
#1757536: Move settings.php to /settings directory, fold sites.php into settings.php is about to move /sites/default into the top-level directory.

Problem

The /sites/all directory duplicates the top-level directory.

Proposed solution

Remove support for /sites/all.

Upgrading

People can simply move their files:

$ git mv sites/all/profiles/* profiles/
$ git mv sites/all/modules/* modules/
$ git mv sites/all/themes/* themes/

If that makes any sense in the first place → with Migrate in core, users might not actually upgrade within the same repository/code-base at all.

Comment	File	Size	Author
	drupal8.sites-all-kill.0.patch	2.25 KB	sun

Comments

Comment #1

catch

he/him

English

commented 3 March 2014 at 12:05

The thing I don't like about the top level directories, is that I've worked on some projects where the sites/all/* directory was kept separately from the core checkout, which you can't really do with three top level directories. In that case I guess you could just use multisite instead but not really seeing the benefit of removing the option.

Comment #2

longwave

he/him

English

commented 3 March 2014 at 13:33

Also not sure I see the benefit in this. None of the "problem" items are actually problems?

Comment #3

tstoeckler

he/him

German

Essen, Germany

commented 3 March 2014 at 13:38

This is not an argument either way, but once #1757536: Move settings.php to /settings directory, fold sites.php into settings.php has landed it will also be possible to specify a custom conf path in your top-level settings.php. I.e. people could still declare $conf_path = 'sites/all' or whatever which would then work similar (but for settings.php) to D7.