Last modified: 2014-09-23 19:47:40 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 T32024, 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 30024 - AbuseFilter: per-filter customizable block settings
AbuseFilter: per-filter customizable block settings
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Normal enhancement with 7 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 22523 29739 (view as bug list)
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-07-23 08:32 UTC by MA
Modified: 2014-09-23 19:47 UTC (History)
11 users (show)

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

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

Description MA 2011-07-23 08:32:12 UTC 
Currently AbuseFilter uses a default block expiry time defined by the variable $wgAbuseFilterBlockDuration in the configuration file. 

It would be good if the settings of the block and its expiry time could be configured locally for each filter when creating one (or modifying it) so we could use different block settings for different filters rather than only one expiry time/settings for all of them.

Thank you.
Comment 1 Mayur 2011-08-25 05:28:38 UTC 
+1, Another problem is that in case of Range block this parameter doesn't work.It blocks a range indefinitely.
Comment 2 unanswers 2013-01-27 16:52:39 UTC 
+1 for this. Also, a way to specify a different block setting for a user and an IP address would be handy.
Comment 3 MA 2013-02-03 21:44:10 UTC 
*** Bug 29739 has been marked as a duplicate of this bug. ***
Comment 4 MA 2013-02-03 21:45:14 UTC 
*** Bug 22523 has been marked as a duplicate of this bug. ***
Comment 5 MA 2013-02-03 21:49:16 UTC 
Importance changed to normal:normal. Several users have expressed that this would be useful.
Comment 6 Andre Klapper 2013-02-11 09:19:38 UTC 
(In reply to comment #5)
> Several users have expressed that this would be useful.

Still it's an enhancement (new functionality).
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