Last modified: 2014-06-09 09:50:39 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 T68031, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66031 - AbuseFilter should be able to identify previously-deleted pages
AbuseFilter should be able to identify previously-deleted pages
Status: RESOLVED DUPLICATE of bug 20892
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-02 13:49 UTC by Huji
Modified: 2014-06-09 09:50 UTC (History)
3 users (show)

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


Attachments

Description Huji 2014-06-02 13:49:20 UTC
One of the common maintenance tasks in a wiki is to identify pages that were previously deleted and are now created again. If they happen over short-term, usually the deleting admin will notice. However, if they happen over long-term it may fall below the radars.

For that reason, it would be ideal to have a way to create an AbuseFilter which would apply a tag to any page creation edit that is done on a previously deleted page. Unfortunately, none of the existing variables for AbuseFilter allow capturing that. I propose adding an artcile_has_been_deleted variable which returns true if a page has a history of being deleted before.
Comment 1 Andre Klapper 2014-06-09 09:50:39 UTC
Hi Huji. Thanks for taking the time to report this!
This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.

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

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


Navigation
Links