Last modified: 2014-11-17 22:52:02 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 T58725, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56725 - CategoryWatch if Enabled in 1.18.1+ Attributes New User With Very Next Edit
CategoryWatch if Enabled in 1.18.1+ Attributes New User With Very Next Edit
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Other (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 16:40 UTC by Lucas
Modified: 2014-11-17 22:52 UTC (History)
1 user (show)

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


Attachments

Description Lucas 2013-11-07 16:40:28 UTC
While not simple to show an example, behavior was noticed as follows since upgrade to 1.18.1:

1. CategoryWatch extension is enabled (either version 1.2.1 or 1.2.2)
2. A new user is created.
3. A different user saves an edit.
4. History indicates the new user (not the editing user) is who made the edit.
5. Subsequent edits behave normally (it only happens for the first edit after creating new user)

Have since upgraded to MW 1.21.2/PHP 5.3.10-1/mySQL 5.5.32-0. 
Behavior remains.

Identified CategoryWatch as the contributor by disabling all extensions and activating one at a time, creating a new user and performing an edit with another user.

Very weird. Will try to duplicate on a test installation.
Comment 1 Andre Klapper 2013-11-08 13:02:08 UTC
Seeing https://www.mediawiki.org/wiki/Extension_talk:CategoryWatch this extension seems to be totally unmaintained. It's code is not on http://git.wikimedia.org/repositories/ and SVN is dead nowadays.
Would you like to try contacting its previous maintainer and maybe take over maintainership? :)

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


Navigation
Links