Last modified: 2010-05-19 20:39:35 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 T25598, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 23598 - Log contradictions
Log contradictions
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Victor Vasiliev
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-05-19 18:16 UTC by MA
Modified: 2010-05-19 20:39 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description MA 2010-05-19 18:16:33 UTC 
Please see:

[1]: http://meta.wikimedia.org/wiki/Steward_requests/SUL_requests/2010-05#SKbot
[2]: http://meta.wikimedia.org/w/index.php?title=Steward_requests/SUL_requests&oldid=1976825#SKbot-2
[3]: http://meta.wikimedia.org/w/index.php?title=User_talk:Werdna&oldid=1963698#Unified_login

The account SKbot is SULed since 10:28, 12 September 2009 (8 months ago) however it seems that we have a bug because despite having a SUL account he keeps creating accounts unnatached <http://toolserver.org/~vvv/sulutil.php?user=SKbot> BUT local logs says they are automatically created <http://gl.wikisource.org/w/index.php?title=Especial:Rexistros&user=SKbot&uselang=en> but they do not even appear on CentralAuth <http://meta.wikimedia.org/w/index.php?title=Special:CentralAuth&target=SKbot>

I'm afraid I do not know what's happening with this so before usurping accounts I'd like to know why this is happening.

Regards.
Comment 1 MA 2010-05-19 20:39:35 UTC 
Forget this, the user was able to recover them via password reset. Strange those entries on the logs/centralauth, but fixed now.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links