Last modified: 2014-02-26 15:45:04 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T39830, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37830 - New configuration setting to control whether password confirmation is required for changing an e-mail-address or not
New configuration setting to control whether password confirmation is require...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-22 16:13 UTC by [[kgh]]
Modified: 2014-02-26 15:45 UTC (History)
4 users (show)

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


Attachments

Description [[kgh]] 2012-06-22 16:13:43 UTC
Starting with MW 1.19.x possibly MW 1.18.x it is required to confirm the change of an e-mail-address with a password. This is ok since it assumes that a person logged in into an user account knows the password.

Reality has it that heaps of people create an account, put in the wrong e-mail-address (typo, etc.) and forget about their password after logout. Up till now I was able to sudo these people and help them. Now this is not longer possible.

Thus it would be good to have a way to disable this requirement, something like "$wgUserEmailChangeConfirmation" which defaults to "true"
Comment 1 Sam Reed (reedy) 2012-06-22 16:30:30 UTC
https://gerrit.wikimedia.org/r/12604
Comment 2 [[kgh]] 2012-06-22 17:24:46 UTC
Documented with http://www.mediawiki.org/wiki/Manual:$wgRequirePasswordforEmailChange

Thank you once again for making this possible.
Comment 3 MZMcBride 2014-01-23 20:29:39 UTC
I don't understand this bug. Why is a global configuration needed here?
Comment 4 Andre Klapper 2014-01-24 12:05:48 UTC
MZMcBride: Why did you reopen this?
Comment 5 Andre Klapper 2014-02-26 15:45:04 UTC
No answer - Setting back to RESOLVED FIXED because that is the status of this request.

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


Navigation
Links