About: Admin Tools Wiki:Edit filter/Instructions   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

This section explains how to create a filter with some preliminary testing, so you don’t flood the edit filter history page. You must strictly adhere to the following: * Read the documentation at mw:Extension:AbuseFilter/RulesFormat * Test some expressions at debugging tools: * for example, evaluate 'some string' rlike 'myregexp' to test your regexp; * true expression evaluates to 1, false shows nothing * Manually test your code at batch testing page: * find someone who recently made an edit of the type that you’re trying to target, * put that username in “Changes by user” field and click “test” button; * if you don’t see positive triggers: * check “show changes that do not match the filter” and click “test” again * find the edit that you targeted an

AttributesValues
rdfs:label
  • Admin Tools Wiki:Edit filter/Instructions
rdfs:comment
  • This section explains how to create a filter with some preliminary testing, so you don’t flood the edit filter history page. You must strictly adhere to the following: * Read the documentation at mw:Extension:AbuseFilter/RulesFormat * Test some expressions at debugging tools: * for example, evaluate 'some string' rlike 'myregexp' to test your regexp; * true expression evaluates to 1, false shows nothing * Manually test your code at batch testing page: * find someone who recently made an edit of the type that you’re trying to target, * put that username in “Changes by user” field and click “test” button; * if you don’t see positive triggers: * check “show changes that do not match the filter” and click “test” again * find the edit that you targeted an
dcterms:subject
dbkwik:admintools/...iPageUsesTemplate
abstract
  • This section explains how to create a filter with some preliminary testing, so you don’t flood the edit filter history page. You must strictly adhere to the following: * Read the documentation at mw:Extension:AbuseFilter/RulesFormat * Test some expressions at debugging tools: * for example, evaluate 'some string' rlike 'myregexp' to test your regexp; * true expression evaluates to 1, false shows nothing * Manually test your code at batch testing page: * find someone who recently made an edit of the type that you’re trying to target, * put that username in “Changes by user” field and click “test” button; * if you don’t see positive triggers: * check “show changes that do not match the filter” and click “test” again * find the edit that you targeted and click on “(details)” * check the variables and maybe return back to debugging tools * Create idle (logging only) filter * in the notes field add something like “Testing phase, will add a warning” * let the idle filter run for a while to test for false positives and negatives * Post a message at the edit filter discussion page, so other Administrators have a chance to fix your code or improve the warning * Finally, fully enable your filter: e.g., add warning, prevention, tagging, etc.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software