[Rt-commit] r13004 - in rt/branches/3.8-TESTING: . etc

[sartak at bestpractical.com]

Author: sartak
Date: Fri Jun  6 19:20:14 2008
New Revision: 13004

Modified:
   rt/branches/3.8-TESTING/   (props changed)
   rt/branches/3.8-TESTING/etc/RT_Config.pm.in
   rt/branches/3.8-TESTING/lib/RT/Date.pm

Log:
 r61814 at onn:  sartak | 2008-06-06 19:20:04 -0400
 Add an AmbiguousDayInFuture option, and make neither Past nor Future the default. The old default of Past screws up 12/12/09 fabulously. rt3.fsck.com #7201.


Modified: rt/branches/3.8-TESTING/etc/RT_Config.pm.in
==============================================================================
--- rt/branches/3.8-TESTING/etc/RT_Config.pm.in	(original)
+++ rt/branches/3.8-TESTING/etc/RT_Config.pm.in	Fri Jun  6 19:20:14 2008
@@ -718,9 +718,11 @@
 # past value? For example, should a date of "Tuesday" default to mean
 # the date for next Tuesday or last Tuesday? Should the date "March 1"
 # default to the date for next March or last March?
-# Set to 0 for the next date or 1 for the last date.
+# Set AmbiguousDayInPast for the last date, or AmbiguousDayInFuture for the
+# next date. The default is usually good.
 
-Set($AmbiguousDayInPast , 1);
+Set($AmbiguousDayInPast, 0);
+Set($AmbiguousDayInFuture, 0);
 
 # }}}
 

Modified: rt/branches/3.8-TESTING/lib/RT/Date.pm
==============================================================================
--- rt/branches/3.8-TESTING/lib/RT/Date.pm	(original)
+++ rt/branches/3.8-TESTING/lib/RT/Date.pm	Fri Jun  6 19:20:14 2008
@@ -197,7 +197,7 @@
             GMT           => 1,
             UK            => RT->Config->Get('DateDayBeforeMonth'),
             PREFER_PAST   => RT->Config->Get('AmbiguousDayInPast'),
-            PREFER_FUTURE => !RT->Config->Get('AmbiguousDayInPast')
+            PREFER_FUTURE => RT->Config->Get('AmbiguousDayInFuture'),
         );
         # apply timezone offset
         $date -= ($self->Localtime( $args{Timezone}, $date ))[9];