Last modified: 2013-10-09 15:31:16 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 T57460, 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 55460 - No reliable way to detect when an API edit is disallowed by the abuse filter
No reliable way to detect when an API edit is disallowed by the abuse filter
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-10-08 08:45 UTC by This, that and the other (TTO)
Modified: 2013-10-09 15:31 UTC (History)
2 users (show)

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

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

Description This, that and the other (TTO) 2013-10-08 08:45:25 UTC 
I set up an abuse filter on testwiki that warns the user with the MediaWiki message "snorkel-abuse" and also disallows the action. When triggering this filter using the API (action=edit) I get this:

<?xml version="1.0"?><api><edit code="snorkel-abuse" info="Hit AbuseFilter: TTO&#039;s test filter" warning="Don&#039;t create snorkel pages" result="Failure" /></api>

The only way to test for AbuseFilter being hit appears to be to check whether the "info" parameter starts with the string "Hit AbuseFilter". This seems a bit hackish.

The spam blacklist manages to do better than this, providing its own spamblacklist attribute on the <edit> element. AbuseFilter should be able to do better too.
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