diff options
Diffstat (limited to 'rt/etc/RT_Config.pm.in')
| -rw-r--r-- | rt/etc/RT_Config.pm.in | 97 |
1 files changed, 36 insertions, 61 deletions
diff --git a/rt/etc/RT_Config.pm.in b/rt/etc/RT_Config.pm.in index ea64a2e01..1755f5455 100644 --- a/rt/etc/RT_Config.pm.in +++ b/rt/etc/RT_Config.pm.in @@ -284,11 +284,6 @@ regular expression that matches all addresses used by your RT. This lets RT avoid sending mail to itself. It will also hide RT addresses from the list of "One-time Cc" and Bcc lists on ticket reply. -If you have a number of addresses configured in your RT database already, you -can generate a naive first pass regexp by using - - perl etc/upgrade/generate-rtaddressregexp - =cut Set($RTAddressRegexp , undef); @@ -320,6 +315,24 @@ F<RT/User_Local.pm> Set($CanonicalizeOnCreate, 0); +=item C<$SenderMustExistInExternalDatabase> + +If C<$SenderMustExistInExternalDatabase> is true, RT will refuse to +create non-privileged accounts for unknown users if you are using +the C<$LookupSenderInExternalDatabase> option. +Instead, an error message will be mailed and RT will forward the +message to C<$RTOwner>. + +If you are not using C<$LookupSenderInExternalDatabase>, this option +has no effect. + +If you define an AutoRejectRequest template, RT will use this +template for the rejection message. + +=cut + +Set($SenderMustExistInExternalDatabase , undef); + =item C<$ValidateUserEmailAddresses> If C<$ValidateUserEmailAddresses> is true, RT will refuse to create users with @@ -375,11 +388,6 @@ or 'qmail'. Note that you should remove the '-t' from C<$SendmailArguments> if you use 'sendmail' rather than 'sendmailpipe' -For testing purposes, or to simply disable sending mail out into the world, you -can set C<$MailCommand> to 'testfile' which writes all mail to a temporary -file. RT will log the location of the temporary file so you can extract mail -from it afterwards. - =cut Set($MailCommand , 'sendmailpipe'); @@ -399,11 +407,8 @@ Set($SetOutgoingMailFrom, 0); =item C<$OverrideOutgoingMailFrom> C<$OverrideOutgoingMailFrom> is used for overwriting the Correspond -address of the queue as it is handed to sendmail -f. This helps force -the From_ header away from www-data or other email addresses that show -up in the "Sent by" line in Outlook. - -The option is a hash reference of queue name to email address. +address of the queue. The option is a hash reference of queue name to +email address. If there is no ticket involved, then the value of the C<Default> key will be used. @@ -611,7 +616,7 @@ Set($UseFriendlyToLine, 0); =item C<$FriendlyToLineFormat> -C<sprintf()> format of the friendly 'To:' header; its arguments +C<sprintf()> format of the friendly 'From:' header; its arguments are WatcherType and TicketId. =cut @@ -841,6 +846,9 @@ RT ships with several themes by default: 3.4-compat A 3.4 compatibility stylesheet to make RT look (mostly) like 3.4 +This bundled distibution of RT also includes (enabled by default): + freeside2.1 Integration with Freeside + This value actually specifies a directory in F<share/html/NoAuth/css/> from which RT will try to load the file main.css (which should @import any other files the stylesheet needs). This allows you to @@ -849,7 +857,7 @@ option can be overridden by users in their preferences. =cut -Set($WebDefaultStylesheet, 'web2'); +Set($WebDefaultStylesheet, 'freeside2.1'); =item C<$UsernameFormat> @@ -860,7 +868,7 @@ EmailAddress. =cut -Set($UsernameFormat, 'concise'); +Set($UsernameFormat, 'verbose'); =item C<$WebDomain> @@ -982,7 +990,7 @@ login if you change it. =cut -Set($WebNoAuthRegex, qr{^ (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x ); +Set($WebNoAuthRegex, qr{^ /rt (?:/+NoAuth/ | /+REST/\d+\.\d+/NoAuth/) }x ); =item C<$SelfServiceRegex> @@ -1097,16 +1105,6 @@ displayed in kilobytes. If set to C<'b'>, then sizes will be bytes. Set($AttachmentUnits, undef); -=item C<$EditCustomFieldsSingleColumn> - -When displaying a list of Ticket Custom Fields for editing, RT defaults -to a 2 column list. If you set this to 1, it will instead display the -Custom Fields in a single column. - -=cut - -Set($EditCustomFieldsSingleColumn, 0); - =item C<$RedistributeAutoGeneratedMessages> Should RT redistribute correspondence that it identifies as @@ -1287,29 +1285,6 @@ search results in RT. Choose from [0, 120, 300, 600, 1200, 3600, 7200]. Set($SearchResultsRefreshInterval, 0); -=item C<$ResolveDefaultUpdateType> - -Set the default Update Type when clicking the Resolve link in the Ticket -links tab. - - Comment Comments (Not sent to requestors) - Respond Reply to requestors - -=cut - -Set($ResolveDefaultUpdateType, 'Comment'); - -=item C<$SuppressAutoOpenOnUpdate> - -When users click Comment or Reply on a new ticket in the web UI, the default -status for the ticket gets set to 'open' if the status is currently 'new'. -Setting this option to 1 will suppress that behavior and leave the default -status as 'new'. This option can be overridden by users in their preferences. - -=cut - -Set($SuppressAutoOpenOnUpdate, 0); - =item C<$OldestTransactionsFirst> By default, RT shows newest transactions at the bottom of the ticket @@ -1371,7 +1346,7 @@ customized homepage ("RT at a glance"). =cut -Set($HomepageComponents, [qw(QuickCreate Quicksearch MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards)]); +Set($HomepageComponents, [qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards)]); =item C<@MasonParameters> @@ -1395,6 +1370,7 @@ C<$DefaultSearchResultFormat> is the default format for RT search results Set ($DefaultSearchResultFormat, qq{ '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#', '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject', + Customer, Status, QueueName, OwnerName, @@ -1402,6 +1378,7 @@ Set ($DefaultSearchResultFormat, qq{ '__NEWLINE__', '', '<small>__Requestors__</small>', + '', '<small>__CreatedRelative__</small>', '<small>__ToldRelative__</small>', '<small>__LastUpdatedRelative__</small>', @@ -1504,14 +1481,12 @@ Set( =item C<$ChartsTimezonesInDB> -RT stores dates using the UTC timezone in the DB, so charts grouped +Dates are stored using UTC timezone in the DB, so charts groupped by dates and time are not representative. Set C<$ChartsTimezonesInDB> -to a true value to enable timezone conversions using your DB's -capabilities. You may need to do some work on the DB side to use this +to a true value to enable timezones conversions using DB's +capabilities. You may need to do some work on DB side to use this feature, read more in F<docs/timezones_in_charts.pod>. -At this time, this feature only applies to MySQL and PostgreSQL. - =cut Set( $ChartsTimezonesInDB, 0 ); @@ -1694,7 +1669,7 @@ Set($AmbiguousDayInFuture, 0); =head1 Approval Configuration -Configuration for the approval system +Configration for the approvl system =over 4 @@ -1773,7 +1748,7 @@ custom field values from external sources at runtime. =cut -Set(@CustomFieldValuesSources, ()); +Set(@CustomFieldValuesSources, ('RT::CustomFieldValues::Queues')); =item C<$CanonicalizeRedirectURLs> @@ -1805,7 +1780,7 @@ C<Set(@Plugins, (qw(Extension::QuickDelete RT::FM)));> =cut -Set(@Plugins, ()); +Set(@Plugins, (qw(RTx::Calendar))); #RTx::Checklist )); =back |