Tickets :: Comment on [#1166] disabling script activation message when altering inactive rules / rules that can't be activated due to other constraints

* Your Email Address
* Spam protection	Enter the letters below: \ /.__ .___.. ,. . >< [ __ _/ \./ \| \| / \[_././__. \| \|__\|
Comment	> Our helpdesk has found the script activation messages confusing in certain > > situations, specifically with messages that a script has been activated when > > altering a disabled rule, or a blacklist / whitelist that's over it's > > maximum number of entries. > > > > Say you've set the blacklist so it can only have 5 entires. When you try to > > add the 6th entry, it gives the "too many entries" error, but then > says "Script > > successfully activated", which our helpdesk finds confusing / misleading. > > > > Similarly, if you alter the search criterea on a disabled rule and save that > > change, Ingo reports "Script successfully activated". > > > > Is it possible to disable the script activation messages when altering a > > rule that won't actually get pushed out to the server? We're using the Sieve > > backend. > >
Attachment
Watch this ticket