Op vrijdag 06 januari 2006 01:31, schreef Larry Garfield:
/sites /all /modules /themes /theme-engines /default /modules /themes /theme-engines /files /example.com /modules /themes /files ...
That way stuff that people used to put in /modules or /themes would go under /sites/all instead, but otherwise functionality is the same. Nothing outside of /sites is ever edited by a user (unless they're being silly and hacking core). Backup is then cp ./sites /my/backup/directory and you're done, and a .htaccess rule to hide ./sites/* is trivial.
Thoughts?
I like this, but the security part should get some attention too. Here is my shot: /public index.php xmlrpc.php /stylesheets /javascript /images /icons /sites /all /modules /themes /example.com /includes /database /public contains all the web accessible stuff. /sites/all contains the default settings.php and default stuff as well as the the Bèr