Last modified: 2014-02-12 23:38:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 19606 - filter rule seem to have maximum length
filter rule seem to have maximum length
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2009-07-08 21:39 UTC by seth
Modified: 2014-02-12 23:38 UTC (History)
1 user (show)

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


Description seth 2009-07-08 21:39:28 UTC
Goto [[w:de:Spezial:Missbrauchsfilter/test]], use rule #17 with "changes by user" =
This will trigger some edits.

Now add the line
   | (rcount("something",added_lines) < rcount("something",removed_lines)) 
somewhere in the rule. Then it will fail.
Maybe there is a maxmum length of filter rules?

(Filter rule #3 at w:de was very long (> 1000 chars). A work-around was to move a part of the rule to #17.)
Comment 1 Andrew Garrett 2009-07-16 17:07:59 UTC
(batch change)

Minor bugs that nevertheless need looking into
Comment 2 Andrew Garrett 2009-07-17 16:51:42 UTC
The maximum length is 65, 536 characters. I don't think it's likely that you're hitting it, though.

The filter seems to not match, rather than throwing a syntax error.
Comment 3 Andrew Garrett 2009-08-07 16:07:29 UTC
Problem may be the max URL length.

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