Last modified: 2006-12-29 12:00:00 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6449 - Need to validate the database name as part of the pre-install checks
Need to validate the database name as part of the pre-install checks
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Rob Church
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-26 14:46 UTC by Hugh Prior
Modified: 2006-12-29 12:00 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Hugh Prior 2006-06-26 14:46:57 UTC
Normally during installation when an error occurs, the submitted information is redisplayed and the 
user is given a big red message saying something like "Correct the fault below and resubmit", but 
not in the instance when an invalid database name is given.

I tried to call my database "mwdb_1.6.7" but this is invalid (though "mwdb_1_6_7" is OK).  It took 
me a little while longer to figure out what was wrong and how to get back (hitting "back" in the 
browser).  

I suggest that an invalid database name is treated in the same way other errors are treated: 
redisplay the submitted data, give an error message, and point to the field in error.
Comment 1 Rob Church 2006-12-29 12:00:00 UTC
Definitive error message added in r18631.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links