the following docs from default.settings.php don't seem to match the behaviour of the installer:
* For a single database configuration, the following is sufficient:
*
* $databases = array(
* 'driver' => 'mysql',
* 'database' => 'databasename',
* 'username' => 'username',
* 'password' => 'password',
* 'host' => 'localhost',
* );
*
* That is equivalent to:
*
* $databases['default']['default'] = array(
* 'driver' => 'mysql',
* 'database' => 'databasename',
* 'username' => 'username',
* 'password' => 'password',
* 'host' => 'localhost',
* );
when i use the following in settings.php for a fresh install of HEAD:
$databases = array(
'driver' => 'mysql',
'database' => 'databasename',
'username' => 'username',
'password' => 'password',
'host' => 'localhost',
);
i get the following error:
In your ./sites/default/settings.php file you have configured Drupal to use a server, however your PHP installation currently does not support this database type.
so, is the code wrong or is the doco wrong?
Comments
Comment #1
Anonymous (not verified) commentedclosing this, as it seems to be a duplicate of Select MySQL as default database driver, and fix a E_ALL warning during install.
sorry for the noise.
Comment #2
damien tournoud commentedThis has nothing to do with the other one.
Comment #3
Crell commentedThat looks like a bug in the code, because that fallback logic is supposed to work.
I have actually been pondering removing the fancy-schmancy fallback nesting. It just burns cycles on bootstrap, and with the installer 95% of users will never write their own settings.php file anyway.
Would anyone object greatly if we just got rid of the crazy fallback stuff? I don't think it serves any purpose now that we have an automated installer.
Comment #4
damien tournoud commentedCrell: the fallback logic does not work in the installer, there is a:
in install_verify_settings()...
Comment #5
Anonymous (not verified) commentedi had a look at this, its not a trivial fix. i'm totally fine with removing/simplifying the fallback code.
EDIT: and i'd be happy to supply a doc fix patch if that's the way we decide to go.
Comment #6
oadaeh commentedI think this problem can be fixed with a simple if/then conditional.
(I'm tempted to mark this as critical, because I wasted over an hour on it when attempting to do a "quick" 15 minute patch review and update.)
Comment #7
oadaeh commentedOkay, that wasn't enough. I'll see if I can find where else this needs to be corrected and upload a new patch.
Comment #8
oadaeh commentedThe patch I provided (in #6) fixes the install problem, but doesn't fix the bootstrap problem that happens after Drupal is successfully installed. I've spent quite a bit of time following threads and have not yet been able to locate where it strays. I will have to come back to this later, as I need to leave for out appointments, unless the consensus is to just remove it.
Comment #9
oadaeh commentedI finally got back to this. (I actually forgot about it.) After rereading this thread and reliving my experiences, I agree with Crell on this issue.
Comment #10
oadaeh commentedComment #11
smk-ka commentedLet's get rid of it. The reason has been named before: manual editing isn't required anymore, which means this feature will be hardly ever used.
Comment #12
dries commented+1 for removing and optimizing the hell out of the bootstrap process.
Comment #13
Crell commentedOh that is so much prettier! I just ran the Connection tests and clicked around a bit and everything runs fine. #11 is RTBC. Thanks, smk-ka!
Comment #14
dries commentedCommitted to CVS HEAD. Thanks for the review, Crell.
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.