Closed (won't fix)
Project:
Drupal core
Version:
6.x-dev
Component:
other
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Mar 2007 at 05:33 UTC
Updated:
9 Aug 2013 at 23:33 UTC
Jump to comment: Most recent
jd4x4 (http://drupal.org/node/106216#comment-208257) points out a piece of information that should be added to the Multisite section of the INSTALL.txt file.
+After the new directory is set up, the new database (if required) is created
+and the settings.php is correctly edited. Point your browser at:
+new.site.name/install.php. Note that it is not necessary to move settings.php
+into the new directory. Doing so will actually prevent this from working.
+
| Comment | File | Size | Author |
|---|---|---|---|
| install.txt_0.patch | 770 bytes | ehowland |
Comments
Comment #1
webchickThis actually goes against core, since it's altering a core file. I also moved the version to 6.x because it should be fixed in HEAD first and then back-ported to 5.x.
A couple of nit-picks:
1. You're using double-spaces after periods; they should be just single spaces.
2. Instead of new.site.name, use "example.com" -- that's a standard for documentation.
3. Also should only be a single empty line between paragraphs, rather than two.
Now about this:
+After the new directory is set up, the new database (if required) is created
+and the settings.php is correctly edited. Point your browser at:
+new.site.name/install.php.
Why would you need to run install.php if the database was already created and settings.php was edited..?
Comment #2
Anonymous (not verified) commented5.x is approaching end of life. Is this still an issue?
Comment #3
jkingsnorth commentedClosing old issue