Start with a brand new copy of cvs.
cd drupal/sites
cp -a default www.example.com
chmod -R a+w www.example.com
You will not pass the install requirements because I did not "chmod -R a+w default".
Also if you create the www.example.com directory but forget to chmod it. Then you follow the onscreen instructions it will fail, because it does not have write to sites/www.example.com/settings.php
Why do we need both directories to be writable by the webserver. I believe that we are just missing another "conf_path()" for the checking of the permissions, but I can not find where.
Also the notice message that you need to remove permissions does not say anything about removing permission from the "default" directory, it only tells you about www.example.com.
Comment | File | Size | Author |
---|---|---|---|
#7 | 209240_conf_path_bug_7.patch | 2.46 KB | gopherspidey |
#5 | 209240_conf_path_bug_5.patch | 2.77 KB | soxofaan |
#3 | dir-install.patch | 1.46 KB | gopherspidey |
Comments
Comment #1
gopherspidey CreditAttribution: gopherspidey commentedComment #2
Gábor HojtsyHm, how is this critical?
Comment #3
gopherspidey CreditAttribution: gopherspidey commentedThis seems to fix the problem. I do not know if I have it in all the right places. It fixed my problem
Comment #4
mike stewart CreditAttribution: mike stewart commentedHad the same issue. Applied this patch and it resolved my problem. The patch seems to make sense. It appears there was an API change between Dr5 conf_path vs Dr6 conf_path, and the install script was not updated.
Note:
It appears the that this patch fixes install "Parameters" [conf_path(FALSE,TRUE)]. They are inverse of the "default" parameter value.
In fact, at first glance it seems odd that the script worked in non multisite installs. According to the API $require_settings should be set FALSE during an intial install... yet the install script without this patch does not pass an explicit value, and the function default suggests it won't otherwise work. hmm. dunno. will look into if I get a chance.
Comment #5
soxofaan CreditAttribution: soxofaan commentedI got bitten by this issue too with a white screen of dead twist:
* multi site install: created empty directory /sites/www.example.com, not webserver writable
* /sites/default was webserver writable (leftover from previous tests), so I passed the requirement check
* after submitting database username/password I got WSOD message that the settings file (/sites/www.example.com/settings.php) was not writable
cause as mike noted: install script was not updated to new conf_path behaviour: install script fails to recognize that /sites/www.example.com/ is a configuration directory because there is no settings.php file (yet)
patch solves the problem
for reference: the issue that introduced the new conf_path() behaviour for Drupal 6: http://drupal.org/node/147324
in attachment: code style clean up of patch #3 + fix for forgotten update of related message string
Comment #6
coltranePatch failed to apply cleanly but fixed the issue.
patching file install.php
Hunk #4 FAILED at 916.
1 out of 4 hunks FAILED -- saving rejects to file install.php.rej
patching file includes/install.inc
Steps:
Checkout CVS
cp -a default localhost
chmod -R a+w localhost
Requirements problem not received.
Not sure why the patch failed on that chunk for me but the code changes work correctly.
Comment #7
gopherspidey CreditAttribution: gopherspidey commentedI would say that this is a confirmed fix. I have rerolled the patch to remove the hunk problem.
Comment #8
gopherspidey CreditAttribution: gopherspidey commentedPlease commit this patch, This bug is already causing confusion. http://drupal.org/node/210238
Also does anyone know where the getting started page/documentation is for drupal 6 (like http://drupal.org/getting-started/5) . I would like to review the install documentation.
Comment #9
Gábor HojtsyIndeed, I checked the API, and we should not look for the settings.php just yet, before it is actually there. This lets multisite setup directories to be found as well. Committed #7, thanks. Still to be committed to 7.x.
Comment #10
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.