Last modified: 2011-05-06 10:25:06 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 T27950, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25950 - Link to the edit in the warn-log if user saved anyway.
Link to the edit in the warn-log if user saved anyway.
Status: RESOLVED DUPLICATE of bug 18374
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-16 13:24 UTC by Krinkle
Modified: 2011-05-06 10:25 UTC (History)
3 users (show)

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


Attachments

Description Krinkle 2010-11-16 13:24:50 UTC
When a filter is set up to warn but not to prevent the edit, it would be nice if when viewing the hits of a filter on the AbuseFilter-page or on Special:Log for a particular page or user, when examining the details to have the information: "Did the user save anyway after the warning ? If yes, a link to the diff would be handy".

Without this it means we have to go into the user's contributons page and page back to around the time the abusefilter was logged and go through the edits.

The side-case is that when the user made a lot of edits but works in tabs, there can be a delay of several minutes between the warning and the actual edit making it even harder to trace.

When submitting the edit-form to be saved after a warning I think it's fairly simple to pass the log-id like  is done with timestamp for edit conflicts. Once saved the log-id is looked up and a diff-field is populated or something like that so that when examining the abusefilter hit the diff can be found directly.
Comment 1 John Mark Vandenberg 2011-05-06 10:25:06 UTC

*** This bug has been marked as a duplicate of bug 18374 ***

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


Navigation
Links