Last modified: 2009-01-31 19:51:02 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 7480 - Un-hardcode (or at least internationalize) database error message
Un-hardcode (or at least internationalize) database error message
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Normal minor with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-03 21:22 UTC by jaroslaw lipszyc
Modified: 2009-01-31 19:51 UTC (History)
2 users (show)

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


Attachments

Description jaroslaw lipszyc 2006-10-03 21:22:00 UTC
Message "Wikipedia has a problem  Sorry! This site is experiencing technical
difficulties. Try waiting a few minutes and reloading. (Can't contact the
database server: Unknown error (10.0.0.101))" is in english only. This is major
bug: this message shows regardless of which wikipedia you want to see: spanish,
french, german, polish... Error message in language our users don't understand
is not helpfull at all.  It must be localised, or - if this is impossible -
given in all major wikipedia languages (as on wikipedia.org web page)
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-10-04 02:10:48 UTC
The problem is apparently that if you localize the message, you have to get the
localized message from the database.  But you can't access the database, which
is why you get the error message.  According to an anonymous developer in
Database.php lines 96-7:

# I give up, Brion is right. Getting the message cache to work when there is no
DB is tricky.
# Hard coding strings instead.

Of course, this could probably be worked around somehow, but there's a reason
for it.  Still, as an interim matter it would certainly make sense to hardcode
in translations for the major languages.
Comment 2 Dan Li 2006-10-04 04:55:11 UTC
Isn't that what wfMsgNoDB is for?
Comment 3 jaroslaw lipszyc 2006-10-04 15:48:54 UTC
maybe this will be helpfull: in the same time wikipedia logo appearing with this
message IS localised (ie. it's polish wikipedia logo if you attempted to see
polish wikipedia) 
Comment 4 Jimmy Collins 2006-10-04 17:42:50 UTC
(In reply to comment #1)
> The problem is apparently that if you localize the message, you have to get the
> localized message from the database.  

Only the default language of the wiki is read from the database. If you change
your language in preferences the translation is (mostly) read from
languages/messages/Messages**.php (except of additional customizings by the admins).
Comment 5 Rotem Liss 2006-10-05 15:58:42 UTC
(In reply to comment #2)
> Isn't that what wfMsgNoDB is for?

Right, I think it should be used. (Maybe wfMsgNoDBForContent instead.)

(In reply to comment #3)
> maybe this will be helpfull: in the same time wikipedia logo appearing with this
> message IS localised (ie. it's polish wikipedia logo if you attempted to see
> polish wikipedia) 

The logo is set by $wgLogo in LocalSettings.php, and is used from the servers,
without using the DB; the messages are used from the DB.
Comment 6 Rob Church 2006-12-09 10:51:17 UTC
(In reply to comment #1)
> is why you get the error message.  According to an anonymous developer in
> Database.php lines 96-7:

It was Tim. :)
Comment 7 Niklas Laxström 2009-01-31 19:51:02 UTC
I18n (not customisation) possible after r46653.

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


Navigation
Links