| Summary | disabling script activation message when altering inactive rules / rules that can't be activated due to other constraints |
| Queue | Ingo |
| Queue Version | 1.0 |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | liamr (at) umich (dot) edu |
| Created | 01/14/2005 (7448 days ago) |
| Due | |
| Updated | 10/22/2005 (7167 days ago) |
| Assigned | |
| Resolved | 10/22/2005 (7167 days ago) |
| Milestone | 1.0.1 |
| Patch | No |
State ⇒ Resolved
behaviour is correct in this case. The blacklist/whitelist behaviour
has been fixed.
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ disabling script activation message when altering inactive rules / rules that can't be activated due to other constraints
Queue ⇒ Ingo
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.