[Rt-commit] rt branch, 4.2-trunk, updated. rt-4.2.6-50-g063094f

[Wallace Reis]

The branch, 4.2-trunk has been updated
       via  063094fed59d09598a8aaf05392ca1079c877058 (commit)
      from  8a23441b2c757f76f97ac92b60777723f58c5f7c (commit)

Summary of changes:
 etc/RT_Config.pm.in | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)

- Log -----------------------------------------------------------------
commit 063094fed59d09598a8aaf05392ca1079c877058
Author: Wallace Reis <wreis at bestpractical.com>
Date:   Mon Aug 18 09:36:42 2014 -0300

    Switch from saying "true/false" to "1/0"
    
    People try to put the bare word true or false into the config setting
    with horribly results.

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index ae22eb8..bb9bb22 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -1674,7 +1674,7 @@ Set($MessageBoxIncludeSignature, 1);
 =item C<$MessageBoxIncludeSignatureOnComment>
 
 Should your users' signatures (from their Preferences page) be
-included in Comments. Setting this to false overrides
+included in Comments. Setting this to 0 overrides
 C<$MessageBoxIncludeSignature>.
 
 =cut
@@ -1866,8 +1866,8 @@ Set($QuoteFolding, 1);
 =item C<$AllowLoginPasswordAutoComplete>
 
 Allow browsers to remember the user's password on login (in case the
-browser can do so, and has the appropriate setting enabled). Defaults
-to false.
+browser can do so, and has the appropriate setting enabled). Default
+is 0.
 
 =cut
 
@@ -1969,7 +1969,7 @@ defaults alone.
 
 =item C<$DisallowExecuteCode>
 
-If set to a true value, the C<ExecuteCode> right will be removed from
+If set to 1, the C<ExecuteCode> right will be removed from
 all users, B<including> the superuser.  This is intended for when RT is
 installed into a shared environment where even the superuser should not
 be allowed to run arbitrary Perl code on the server via scrips.
@@ -1980,7 +1980,7 @@ Set($DisallowExecuteCode, 0);
 
 =item C<$Framebusting>
 
-If set to a false value, framekiller javascript will be disabled and the
+If set to 0, framekiller javascript will be disabled and the
 X-Frame-Options: DENY header will be suppressed from all responses.
 This disables RT's clickjacking protection.
 
@@ -1990,7 +1990,7 @@ Set($Framebusting, 1);
 
 =item C<$RestrictReferrer>
 
-If set to a false value, the HTTP C<Referer> (sic) header will not be
+If set to 0, the HTTP C<Referer> (sic) header will not be
 checked to ensure that requests come from RT's own domain.  As RT allows
 for GET requests to alter state, disabling this opens RT up to
 cross-site request forgery (CSRF) attacks.
@@ -2001,9 +2001,9 @@ Set($RestrictReferrer, 1);
 
 =item C<$RestrictLoginReferrer>
 
-If set to a false value, RT will allow the user to log in from any link
+If set to 0, RT will allow the user to log in from any link
 or request, merely by passing in C<user> and C<pass> parameters; setting
-it to a true value forces all logins to come from the login box, so the
+it to 1 forces all logins to come from the login box, so the
 user is aware that they are being logged in.  The default is off, for
 backwards compatability.
 
@@ -2071,7 +2071,7 @@ Set($WebRemoteUserAuth, undef);
 
 If C<$WebRemoteUserContinuous> is defined, RT will check for the
 REMOTE_USER on each access.  If you would prefer this to only happen
-once (at initial login) set this to a false value.  The default
+once (at initial login) set this to 0.  The default
 setting will help ensure that if your webserver's authentication layer
 deauthenticates a user, RT notices as soon as possible.
 
@@ -2344,13 +2344,13 @@ used. Use the C<Outgoing> option to set a security protocol that should
 be used in outgoing emails.  At this moment, only one protocol can be
 used to protect outgoing emails.
 
-Set C<RejectOnUnencrypted> to true if all incoming email must be
+Set C<RejectOnUnencrypted> to 1 if all incoming email must be
 properly encrypted.  All unencrypted emails will be rejected by RT.
 
-Set C<RejectOnMissingPrivateKey> to false if you don't want to reject
+Set C<RejectOnMissingPrivateKey> to 0 if you don't want to reject
 emails encrypted for key RT doesn't have and can not decrypt.
 
-Set C<RejectOnBadData> to false if you don't want to reject letters
+Set C<RejectOnBadData> to 0 if you don't want to reject letters
 with incorrect data.
 
 If you want to allow people to encrypt attachments inside the DB then
@@ -2389,7 +2389,7 @@ L<RT::Crypt::SMIME>.
 
 =item C<%SMIME>
 
-Set C<Enable> to false or true value to disable or enable SMIME for
+Set C<Enable> to 0 or 1 to disable or enable SMIME for
 encrypting and signing messages.
 
 Set C<OpenSSL> to path to F<openssl> executable.
@@ -2444,7 +2444,7 @@ be found by running the command `perldoc L<RT::Crypt::GnuPG>` (or
 
 =item C<%GnuPG>
 
-Set C<Enable> to false or true value to disable or enable GnuPG interfaces
+Set C<Enable> to 0 or 1 to disable or enable GnuPG interfaces
 for encrypting and signing outgoing messages.
 
 Set C<GnuPG> to the name or path of the gpg binary to use.
@@ -2736,8 +2736,8 @@ For example:
 
 Unless there is an explicit mapping between statuses in two different
 lifecycles, you can not move tickets between queues with these
-lifecycles.  This is true even if the different lifecycles use the exact
-same set of statuses.  Such a mapping is defined as follows:
+lifecycles -- even if both use the exact same set of statuses.
+Such a mapping is defined as follows:
 
     __maps__ => {
         'from lifecycle -> to lifecycle' => {
@@ -2859,7 +2859,7 @@ which asks the administrator's browser to show an inline page from
 Best Practical's website.
 
 If you'd rather not make this feature available to your
-administrators, set C<$ShowRTPortal> to a false value.
+administrators, set C<$ShowRTPortal> to 0.
 
 =cut
 

-----------------------------------------------------------------------