Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
documentation
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2010 at 10:35 UTC
Updated:
6 Jan 2010 at 09:49 UTC
This is a minor issue, but a little rewording of the install text could save some grief and time for first time drupal users/installers.
I'm specifically referring to the install.txt which is used in 6.15 and I think in 7.x (checked via api.drupal.org) as well...
// $Id: INSTALL.txt,v 1.61.2.4 2008/07/09 19:15:59 goba Exp $
The beginning of part 4 of the install text reads...
To run the install script point your browser to the base URL of your website
(e.g., http://www.example.com).It isn't clear to everyone that what you really mean is point your browser to http://www.example.com/install.php
Going to http://www.example.com during a new install prior to running install.php produces a white screen of death.
Comments
Comment #1
jhodgdonReally? It normally works for me to go to the intended home page directly, without the install.php suffix, prior to a new installation.
Can you give more information about what conditions might have led it to work for most people and not for you, or verify that it doesn't work? For instance, do you have drupal source files installed in a sub-directory instead of at the root, or something like that? What web server are you using (Apache, IIS, ???)?
Comment #2
s4j4n commentedThat is interesting that it works for you and not for me. I am curious what's causing this.
I encounter the behavior mentioned in my first post in MAMP as well as on my production server.
1. My MAMP is version 1.8.3, with...
- Apache/2.2.11
- PHP 5.2.10
In MAMP the directory containing my new drupal installation is a subdirectory within the htdocs directory. In MAMP - the directory htdocs is the DocumentRoot. So for me example.com is served from a drupal installation in a directory named "example", something like:
/Applications/MAMP/htdocs/example
You can navigate to example.com served by MAMP by pointing your browser at:
http://localhost:8888/example/
On my MAMP, prior to installation - navigating to http://localhost:8888/example/ produces a WSOD
The php error log file shows the following warnings/errors:
2. My production server is running OpenSolaris with...
- Apache/2.2.6 (Unix).
- PHP 5.2.4
The DocumentRoot is the /home/user/web/public directory. I extracted drupal in the web directory, renamed the drupal directory to public - so index.php of the drupal install is sitting in the web root.
Let's say that the URL example.com is served from this /home/user/web/public directory. With that assumption, on my production server, prior to installation - navigating to example.com produces a WSOD
More precisely, Safari and Firefox produce a WSOD, while Chrome produces a 404.
Using HTTP Live Headers in Firefox, once can see clearly that a 404 is returned for example.com
If I set PHP to display error messages, the following is displayed (note that ip addresses have been changed):
The database and user/user-privileges have been set up prior to navigating to the front page - and settings.php also has been setup. Navigating to example.com/install.php starts the installation process and the site installs successfully after that.
I hope some of this will be helpful. Please let me know if you need any more info or have further questions.
Comment #3
heine commentedDid you edit settings.php? All you should do is copy the stock default.settings.php to settings.php.
Comment #4
s4j4n commentedThank you Heine and jhodgdon for your replies. Yes I edited the settings.php file prior to loading the site for the first time. I guess I picked up some bad habits.