Last modified: 2013-03-08 16:55:17 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 T47901, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45901 - Rolling back IPv6 addresses does not work correctly
Rolling back IPv6 addresses does not work correctly
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
1.21.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-08 16:26 UTC by zeibura
Modified: 2013-03-08 16:55 UTC (History)
3 users (show)

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


Attachments

Description zeibura 2013-03-08 16:26:25 UTC
See this diff: http://en.wikipedia.org/w/index.php?title=Electronica&diff=542828286&oldid=540998447 a user rolled back an IPv6 address who made two edits in a row, but the rollback feature only reverted one of them. The feature seems to work normally in other situations.
Comment 1 Alex Monk 2013-03-08 16:33:07 UTC
A rollback edit summary looks like this:
Reverted edits by Username (talk) to last revision by PreviousUsername
Not this:
Reverted 1 edit by 2600:100e:b002:cd8e:a810:e452:cdff:42b9 (talk) to last revision by 2600:100E:B002:CD8E:A810:E452:CDFF:42B9. ([[WP...
Sounds like a problem with Twinkle, not MediaWiki.
Comment 2 Jesús Martínez Novo (Ciencia Al Poder) 2013-03-08 16:49:25 UTC
Indeed, it seems a problem with Twinkle. That's not the normal revert message summary.

Closing as INVALID
Comment 3 Alex Monk 2013-03-08 16:55:17 UTC
Reported on Twinkle's issue tracker on Github: https://github.com/azatoth/twinkle/issues/145

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


Navigation
Links