Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
My Unix host does not use localhost to access the database, and I inadvertently overlooked the Advanced settings where the database host can be entered.
Is it not possible to check whether localhost is valid, and if not, automatically open the Advanced setting options?
Comment | File | Size | Author |
---|---|---|---|
#10 | 202775.patch | 2.83 KB | michaelfavia |
#8 | installation_error_handling_regular.patch | 2.82 KB | jabapyth |
#5 | installation_error_handling.patch | 3.32 KB | jabapyth |
Comments
Comment #1
chx CreditAttribution: chx commentedhow could we check that there is a mysql running on localhost? that's impossible.
Comment #2
Damien Tournoud CreditAttribution: Damien Tournoud commentedInteresting idea. Promoting to "Usability".
If no server is running under localhost and you don't change the parameters in the collapsed "Advanced options" fieldset, the installer returns the cryptic error message: "Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'". Maybe we could handle error messages intelligently and form_set_error the relevant fields depending on the error (ie. Host in case of a connection error, User and Password for an authentication error, etc.).
Comment #3
coltraneIdentified at UB Usability Testing: http://www.drupalusability.org/node/12
We get a form set error on the database name if field is empty, but no other field identifiable errors.
Comment #4
Bojhan CreditAttribution: Bojhan commentedThis issue does not correspond to the issue found at UBUserTesting2009, that one was related to wrong password/username (although this one is related - its in the error) - I don't think it is part.
Comment #5
jabapyth CreditAttribution: jabapyth commentedThe two issues are closely related -- as the error for both connection and login are handled as one.
Here's a patch to make things a bit more user friendly :)
[this is a small bugfix patch, just to get things reasonable ;). If it goes through I'll work on making the error handling intelligent and more helpful]
before screenshot
after screenshot
please review?
thanks,
Jared
Comment #6
Dries CreditAttribution: Dries commentedjabapyth, could you roll a 'regular' patch?
Comment #7
BerdirWhen creating patches, please use the options -up.
Comment #8
jabapyth CreditAttribution: jabapyth commentedAh, that's how it's done. sorry, couldn't seem to find the right arguments.
Comment #9
Dries CreditAttribution: Dries commentedThe code comments need some work; better explanation and conform to our coding style.
<b>%error.</b>
should be:<strong>%error</strong>.
-- also note the position of the point.Otherwise looks good to me.
Comment #10
michaelfavia CreditAttribution: michaelfavia commentedUpdated to address Dries code comment style and HTML issues.
Comment #12
lilou CreditAttribution: lilou commentedtestbot failure.
Comment #13
Dries CreditAttribution: Dries commentedThis looks good to me, but I haven't tested it. If someone can try testing this, it should be RTBC.
Comment #14
jabapyth CreditAttribution: jabapyth commentedthanks for doing that, michaelfavia
Comment #15
pp CreditAttribution: pp commentedIt works fine.
I tried it with Mysql and SQLite.
Comment #16
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.