It is great that the installer notices that you do not have a 'files' folder... However best practices suggest 'sites/default/files' as a prime choice. Is this really something that should be an installation blocker? Is there reason we don't check the entire sites tree for a writable 'files' folder as well as /files?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 195033.patch | 573 bytes | dopry |
| #3 | 195033.patch | 573 bytes | dopry |
Comments
Comment #1
kbahey commentedI agree we should move the default 'files' to 'sites/default/files', as per best practices.
Since there is already an issue on this, #194860, I am marking this as a duplicate.
Comment #2
dopry commentedThis is not a duplicate. This issue is specifically an unnecessary installer requirement. #194860 is about making the example.com/files map to sites/*/files. Not in my interest.
Comment #3
dopry commentedhere is patch that uses conf_path() in file_directory_path.
Comment #4
dopry commentedhere is patch that uses conf_path() in file_directory_path.
Comment #5
catchhttp://drupal.org/node/191310
Comment #6
catchRequirement was added here: http://drupal.org/node/191310
This is a patch.
Comment #7
robloachAnother similar issue made to move the files directory to sites/*/files.
Comment #8
catchedit: ignore me, the other issue was the one you linked to :|
Comment #9
moshe weitzman commentedComment #10
lilou commentedAlready committed.