mirror of
https://gerrit.wikimedia.org/r/mediawiki/extensions/AbuseFilter.git
synced 2024-11-24 06:03:49 +00:00
Don't use an empty string for block parameters
Follow-up of Iaeae672dca66ffc745054daabd6f0eae7dfbc648. Some actions were still marked with red, specifically the ones with block inside. The reason is that we stored the 'blocktalk' parameter as an emtpy string if false, which wasn't filtered when loading request. Changing the empty string to something different is enough to fix the problem, hopefully without regressions. Note that this isn't retroactive and needs an edit to become effective. Bug: T189681 Change-Id: I7d7f0606fc23bad5ba342076066ab0e935680b3f
This commit is contained in:
parent
913d37eba6
commit
7008de80e6
|
@ -1203,7 +1203,7 @@ class AbuseFilterViewEdit extends AbuseFilterView {
|
|||
$parameters[0] = $specMsg;
|
||||
} elseif ( $action == 'block' ) {
|
||||
$parameters[0] = $request->getCheck( 'wpFilterBlockTalk' ) ?
|
||||
'blocktalk' : '';
|
||||
'blocktalk' : 'noTalkBlockSet';
|
||||
$parameters[1] = $request->getVal( 'wpBlockAnonDuration' );
|
||||
$parameters[2] = $request->getVal( 'wpBlockUserDuration' );
|
||||
} elseif ( $action == 'tag' ) {
|
||||
|
|
Loading…
Reference in a new issue