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

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1166
-----------------------------------------------------------------------
 Ticket     | 1166
 Created By | liamr at umich.edu
 Summary    | disabling script activation message when altering inactive rules / rules that can't be activated due to other constraints
 Queue      | Ingo
 Version    | 1.0
 State      | New
 Priority   | 1. Low
 Type       | Enhancement
 Owners     | 
-----------------------------------------------------------------------


liamr at umich.edu (2005-01-14 15:20) wrote:

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.