There is already a preference whether scripts should be activated 
immediately on a rule change.

Here's a related suggestion:

For  Vacation, and the other special sections, have a 'Save and 
Enable' button.



Many users will save their vacation message, but think this is enough 
to _enable_ the vacation message as well.  "DISABLED" wouldn't have to 
be so loud if we were deflecting this mistake.

I've change this in CVS HEAD. Let's see if we get any positive or 
negative feedback. Probably not.

Changing the wording like this sounds good to me. I can see how the 
all-caps "DISABLED" could throw people off.

I have no strong opinion about this, anyone else?

I changed the [DISABLED] section in templates/filters/filter.html to



[<tag:filter.enablelink /><font color="red"><gettext>disabled - click 
to enable</gettext></font></a>]



that would probably sate my users.. is it good enough?

I personally don't care if it's "disabled" or "inactive", but making 
the link clickable makes sense to me.

This is not my first bug complaining about stupid users, but I refuse 
to believe mine are worse than anyone else's.



The big red "DISABLED" that appears next to "vacation" indicates to 
several of my users that vacation messages are disabled systemwide, 
prompting them to contact our helpdesk to ask if they can be enabled.



I'll be glad to hack up a patch, but I'm not sure which way to go on 
this.  Options include:



1) changing [DISABLED] to [inactive - click to activate]

2) removing the [DISABLED] entirely (as there is no corresponding 
[ENABLED], and it's redundant with the check/X column to its right) 
and possibly automatically enabling vacation messages when they are 
configured

3) removing the [DISABLED] entirely and displaying a page of 
instructions after users configure vacation



thoughts?