[documentation] [Documentation bug] Incorrect sites/all documentation

[Crell]

Issue status update for 
http://drupal.org/node/103915
Post a follow up: 
http://drupal.org/project/comments/add/103915

 Project:      Documentation
 Version:      <none>
 Component:    Admin Guide
 Category:     bug reports
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  Crell
 Updated by:   Crell
 Status:       active

Best practice is to keep site-specific files with site-specific code,
not to confuse it with site-generic code.  Yes it will not-break if you
put your files directory in sites/all/files, but it technically doesn't
break if you put it in themes/engines/files either.  That doesn't make
it a good idea. :-)  Encouraging people to keep site-specific everything
together from the get-go is a good thing.




Crell



Previous comments:
------------------------------------------------------------------------

Mon, 18 Dec 2006 03:35:09 +0000 : Crell

The example of the "new 5.0" sites/all support on this page [1] is
wrong.  It says:



/drupal
  /sites
    /default
       settings.php
    /all
       /modules
       /themes
       /files

Which is not correct.  sites/all does NOT provide any magic support for
files, and in fact putting files there is a rather bad idea.  It's for
modules and themes that you want shared only.  A more correct example
would be:



/drupal
  /sites
    /default
       /files
       /modules
       /themes
       settings.php
    /all
       /modules
       /themes

(I'm not sure what the rule is for what counts as "critical" for
documentation, but I figure "incorrect information" is a good guess. 
Please correct if I'm mistaken.)
[1] http://drupal.org/node/53705




------------------------------------------------------------------------

Mon, 18 Dec 2006 03:42:44 +0000 : Crell

It's not just the example, I just realized, but the descriptive text as
well.




------------------------------------------------------------------------

Mon, 18 Dec 2006 12:52:00 +0000 : pwolanin

@Crell - the site works either way if you're doing a single site
installation.  So, there is no real difference unless the user is
transitioning from single site to multi-site.  In that case, the user
would have been best advised to put everything in /sites/sitename all
along (as per the initial example).


So, the real question is simply what do we want to define as the "best"
practice.