Last modified: 2012-03-12 14:06:30 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 T37170, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35170 - Block message for account creation if central auth autocreation of an account fails on a local project because of an account creation blocked block
Block message for account creation if central auth autocreation of an account...
Status: NEW
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-12 14:03 UTC by Martijn Hoekstra
Modified: 2012-03-12 14:06 UTC (History)
1 user (show)

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


Attachments

Description Martijn Hoekstra 2012-03-12 14:03:12 UTC
per bug 11148

ideally, the message should indicate that SUL autocreating an account failed, rather than the generic account creation blocked message. I set the priority to trivial, but I suppose it could be enhancement too. It's not terribly important I suppose.

Suggested message:

"logging in to <project> failed. An attempt has been made to connect to this wiki with your global username <username>. This global username does not yet exist on <project>, and account creation has been blocked for your IP address <address> on <project>. Information about the block: <info>"
Comment 1 Nemo 2012-03-12 14:06:30 UTC
The user doesn't care about technical details, but the problem is that the user tries to login and receives an error about account creation which is not what was tried, hence the confusion.

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


Navigation
Links