Issue status update for http://drupal.org/node/23467 Post a follow up: http://drupal.org/project/comments/add/23467 Project: Drupal Version: cvs Component: file system Category: bug reports Priority: normal Assigned to: killes@www.drop.org Reported by: killes@www.drop.org Updated by: killes@www.drop.org Status: patch (code needs review) Attachment: http://drupal.org/files/issues/file-default_0.patch (7.23 KB) I#ve updated the patch and added some blurb to the general file setting path. I agree with Dries that we should force the people to use a file patch that contains their domain name. Not sur how to do that, though. killes@www.drop.org Previous comments: ------------------------------------------------------------------------ Mon, 23 May 2005 20:07:40 +0000 : killes@www.drop.org Attachment: http://drupal.org/files/issues/file-default.patch (4.98 KB) Currently the defautl for the file storage directory is /files. This is a problrem if you should later decide to setup more than one site from the same source code. The attached page changes the default to be /sites/default/files (defautl is replaced by the site url if the default directory is renamed). ------------------------------------------------------------------------ Tue, 24 May 2005 20:22:17 +0000 : Dries The fact that the different files-directories are potentially shared in a multi-site setup probably needs to be documented in the form description. I suggest you update the form descriptions too so the user understands why we are suggesting to store files in that particular directory. I guess it would be even better to _force_ files to be stored in the proper sub-directory of the sites-directory. I see two problems with that though: legacy code will stop working, and URLs to static files become longer/uglier. It does get us a step closer to the proposed separating of 'system files' and 'local files'. Thoughts? ------------------------------------------------------------------------ Wed, 25 May 2005 02:47:45 +0000 : moshe weitzman i'm curious how the bryght folks do this. they run a large mutli-site install. you could work around this by setting a $conf['file_directory_path'] n a site's settings.php. ------------------------------------------------------------------------ Wed, 25 May 2005 06:55:39 +0000 : singularo I discovered this with the image module, and worked around it by using files/www.whatever.com in the file system path setting, but I think it would be better to have seperate "files" directories for each site.