[freeside-commits] branch master updated. eb9148f0ab9aac5e4f89824b7fab6bb9d648e688

Ivan ivan at 420.am
Sun Sep 23 19:19:39 PDT 2012

The branch, master has been updated
       via  eb9148f0ab9aac5e4f89824b7fab6bb9d648e688 (commit)
      from  6868dfdef35b338f5f4f6c0bc9cae535dc344ab9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit eb9148f0ab9aac5e4f89824b7fab6bb9d648e688
Author: Ivan Kohler <ivan at freeside.biz>
Date:   Sun Sep 23 19:18:58 2012 -0700

    rt 4.0.7

diff --git a/rt/etc/RT_Config.pm.in b/rt/etc/RT_Config.pm.in
index bd48b6e..1691820 100644
--- a/rt/etc/RT_Config.pm.in
+++ b/rt/etc/RT_Config.pm.in
@@ -640,6 +640,9 @@ Set($NotifyActor, 0);
 By default, RT records each message it sends out to its own internal
 database.  To change this behavior, set C<$RecordOutgoingEmail> to 0
+If this is disabled, users' digest mail delivery preferences
+(i.e. EmailFrequency) will also be ignored.
 Set($RecordOutgoingEmail, 1);
@@ -897,8 +900,8 @@ Set(@JSFiles, qw/
+    jquery-ui-timepicker-addon.js
-    ui.timepickr.js
@@ -1826,6 +1829,16 @@ If the "RT has detected a possible cross-site request forgery" error is triggere
 by a host:port sent by your browser that you believe should be valid, you can copy
 the host:port from the error message into this list.
+Simple wildcards, similar to SSL certificates, are allowed.  For example:
+    *.example.com:80    # matches foo.example.com
+                        # but not example.com
+                        #      or foo.bar.example.com
+    www*.example.com:80 # matches www3.example.com
+                        #     and www-test.example.com
+                        #     and www.example.com
 Set(@ReferrerWhitelist, qw());
@@ -2279,10 +2292,11 @@ all possible transitions in each lifecycle using the following format:
 =head3 Statuses available during ticket creation
-By default users can create tickets with any status, except
-deleted. If you want to restrict statuses available during creation
-then describe transition from '' (empty string), like in the example
+By default users can create tickets with a status of new,
+open, or resolved, but cannot create tickets with a status of
+rejected, stalled, or deleted. If you want to change the statuses
+available during creation, update the transition from '' (empty
+string), like in the example above.
 =head3 Protecting status changes with rights


Summary of changes:
 rt/etc/RT_Config.pm.in |   24 +++++++++++++++++++-----
 1 files changed, 19 insertions(+), 5 deletions(-)

More information about the freeside-commits mailing list