Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
other
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Mar 2009 at 23:14 UTC
Updated:
3 Jan 2014 at 00:07 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #1
catchNote that if you put any kind of typo for database credentials when you try to install Drupal, that huge wall of red text is what you see.
Comment #2
Bojhan commentedTagging
Comment #3
wretched sinner - saved by grace commentedI think this is due to D7 being in development, and so all errors are displayed, rather than a reduced set. Are you comparing the install errors with D6 -dev or D6.10?
Comment #4
catchThese errors are from install.inc with drupal_set_message() etc., not down to error level settings.
Comment #5
webchickCorrect. This has something to do with DBTNG and lack of error trapping.
Subscribing and promoting to a critical bug. We are not releasing with it like this.
Comment #6
catchAll the messages are defined in:
Abstract class DatabaseInstaller
it's mainly runTestQuery() testConnect() and the $tests array.
I think we'd do fine just showing the message from testConnect() (which looks like the old D6 one) - not sure why runTestQuery() has to do a drupal_set_message() for every fail all at once.
Comment #7
birdmanx35 commentedComment #8
birdmanx35 commentedComment #9
tixilite commentedWe have to get rid of this huge red wall of text. I don't think all the details about which table couldn't be inserted, updated or whatever should be included. It should be more like:
Drupal was unable to insert, update, delete, etc. in the MySQL database.
Are you sure the configured username has the necessary permissions for the above actions?
For more help....(handbook link)
A more details link could also be put which can include all this red text for those who need it.
Comment #10
Bojhan commentedtixilite please read the issue comments.
Comment #11
sirkitree commenteddb_set_active() is not failing - I tried to trace it back through the new classes and methods for DBTNG and it looks like there needs to be some sort of check in
final protected static function parseConnectionInfo()...Comment #12
yoroy commentedbumpscribe…
Comment #13
Bojhan commentedDoesn't seem this issue still exists, can someone verify?
Comment #14
aspilicious commentedThis is fixed!
See attachment, put back on active if you disagree!