Last modified: 2010-05-15 15:38:19 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 3293 - Inconsistent (double) textstring Special:Confirmemail and Special:Preferences
Inconsistent (double) textstring Special:Confirmemail and Special:Preferences
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-08-28 18:13 UTC by T. Gries
Modified: 2010-05-15 15:38 UTC (History)
0 users

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


Description T. Gries 2005-08-28 18:13:34 UTC
In SpecialPreferences lines 287-289, currently text strings 

- mailerror, $1 and 
- eauthentsent, $1

are used; they have an additional $1 part. These parts are used, when a user
changes the stored e-mail address and the wiki automatically sends out the
confirmation e-mail.

In SpecialConfirmemail lines 55-57 a similar construct is used, when the user
explicitly requests e-mail confirmation. You can see the very similar code
construction. But they used strings are here 

- confirmemail_sendfailed and 
- confirmemail_sent

Due to a different program structure, wfMsg is not used here.

The target of this bugzilla is to show that an improved code (of text handling
in Confirmemail.php) could save two of the four text strings, becauses they have
essentially the same meaning.

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