<!DOCTYPE html><html><head>
<style type="text/css">body { font-family:'Times New Roman'; font-size:13px}</style>
</head>
<body><div>Hello there. thanks in advance for helping me. <br>After a couple of failures of dependency problems while compiling or installing newer versions , I have finalling managed to get to install an RPM of RT 3.6 on my Mandriva 2011 X86. <br><br>The RT is configurated to show up at http://localhost/rt3/. If I do I get the following errors: <br><br>RT couldn't store your session. <br>This may mean that that the directory '/var/lib/lib/rt/session_data' isn't writable or a database table is missing or corrupt. <br><br><br><br>Trace begun at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Exceptions.pm line 129 <br>HTML::Mason::Exceptions::rethrow_exception('RT couldn\'t store your session.^JThis may mean that that the directory \'/var/lib/lib/rt/session_data\' isn\'t writable or a database table is missing or corrupt.^J^J') called at /opt/otrs/Kernel/cpan-lib/CGI/Carp.pm line 379 <br>CGI::Carp::realdie('RT couldn\'t store your session.^JThis may mean that that the directory \'/var/lib/lib/rt/session_data\' isn\'t writable or a database table is missing or corrupt.^J^J') called at /opt/otrs/Kernel/cpan-lib/CGI/Carp.pm line 468 <br>CGI::Carp::die('RT couldn\'t store your session.^JThis may mean that that the directory \'/var/lib/lib/rt/session_data\' isn\'t writable or a database table is missing or corrupt.^J^J') called at /var/lib/rt/html/Elements/SetupSessionCookie line 102 <br>HTML::Mason::Commands::__ANON__ at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Component.pm line 138 <br>HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0xcb26d30)') called at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 1305 <br>eval {...} at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 1295 <br>HTML::Mason::Request::comp(undef, undef) called at /var/lib/rt/html/autohandler line 120 <br>HTML::Mason::Commands::__ANON__ at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Component.pm line 138 <br>HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0xcb1f230)') called at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 1300 <br>eval {...} at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 1295 <br>HTML::Mason::Request::comp(undef, undef, undef) called at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 484 <br>eval {...} at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 484 <br>eval {...} at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/Request.pm line 436 <br>HTML::Mason::Request::exec('HTML::Mason::Request::ApacheHandler=HASH(0xcaac870)') called at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/ApacheHandler.pm line 168 <br>HTML::Mason::Request::ApacheHandler::exec('HTML::Mason::Request::ApacheHandler=HASH(0xcaac870)') called at /usr/lib/perl5/site_perl/5.12.3/HTML/Mason/ApacheHandler.pm line 825 <br>HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0xb1d5460)', 'Apache2::RequestRec=SCALAR(0xb255368)') called at /usr/bin/webmux.pl line 125 <br>eval {...} at /usr/bin/webmux.pl line 125 <br>RT::Mason::handler('Apache2::RequestRec=SCALAR(0xb255368)') called at /usr/lib/perl5/vendor_perl/5.12.3/Apache/Session/MySQL.pm line 0 <br>eval {...} at /usr/lib/perl5/vendor_perl/5.12.3/Apache/Session/MySQL.pm line 0 <br><br>-------------- <br>/var/lib/rt/ and /var/lib/lib/rt/ have been chmod-ed with 777 and the database named "rt" has been created with "phpMyAdmin". But since I thought it might have been a reason too as the database is empty <br><br>I have also tried with the init-database script but that resulted in an empty database as well because of an error too: <br><br>-------------- <br>[root@localhost sbin]# rt-setup-database --action init --dba mysql --prompt-for-dba-password <br>In order to create or update your RT database,Use of uninitialized value $RT::DatabaseHost in concatenation (.) or string at /usr/sbin/rt-setup-database line 295. <br>this script needs to connect to your mysql instance on as mysql. <br>Please specify that user's database password below. If the user has no database <br>password, just press return. <br><br>Password: <br>Now creating a database for RT. <br>Creating mysql database rt. <br>Now populating database schema. <br>Creating database schema. <br>Problem with statement: <br> <br><br>CREATE TABLE Attachments ( <br> id INTEGER NOT NULL AUTO_INCREMENT, <br> TransactionId integer NOT NULL , <br> Parent integer NOT NULL DEFAULT 0 , <br> MessageId varchar(160) NULL , <br> Subject varchar(255) NULL , <br> Filename varchar(255) NULL , <br> ContentType varchar(80) NULL , <br> ContentEncoding varchar(80) NULL , <br> Content LONGTEXT NULL , <br> Headers LONGTEXT NULL , <br> Creator integer NOT NULL DEFAULT 0 , <br> Created DATETIME NULL , <br> PRIMARY KEY (id) <br>) TYPE=InnoDB <br>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 15 at /usr/sbin/rt-setup-database line 220, <SCHEMA> line 463. <br>[root@localhost sbin]# <br><br>-------------- <br><br>Here is the KDE_SiteConfig.PM: <br><br># <br># WARNING: NEVER EDIT RT_Config.pm. Instead, copy any sections you want to change to RT_SiteConfig.pm <br># and edit them there. <br># <br><br>package RT; <br><br>=head1 NAME <br><br>RT::Config <br><br>=for testing <br><br>use RT::Config; <br><br>=cut <br><br># {{{ Base Configuration <br><br># $rtname is the string that RT will look for in mail messages to <br># figure out what ticket a new piece of mail belongs to <br><br># Your domain name is recommended, so as not to pollute the namespace. <br># once you start using a given tag, you should probably never change it. <br># (otherwise, mail for existing tickets won't get put in the right place <br><br>Set($rtname , "example.com"); <br><br><br># This regexp controls what subject tags RT recognizes as its own. <br># If you're not dealing with historical $rtname values, you'll likely <br># never have to enable this feature. <br># <br># Be VERY CAREFUL with it. Note that it overrides $rtname for subject <br># token matching and that you should use only "non-capturing" parenthesis <br># grouping. For example: <br># <br># Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/i ); <br># <br># and NOT <br># <br># Set($EmailSubjectTagRegex, qr/(example.com|example.org)/i ); <br># <br># This setting would make RT behave exactly as it does without the <br># setting enabled. <br># <br># Set($EmailSubjectTagRegex, qr/\Q$rtname\E/i ); <br><br><br><br># You should set this to your organization's DNS domain. For example, <br># fsck.com or asylum.arkham.ma.us. It's used by the linking interface to <br># guarantee that ticket URIs are unique and easy to construct. <br><br>Set($Organization , "example.com"); <br><br># $user_passwd_min defines the minimum length for user passwords. Setting <br># it to 0 disables this check <br>Set($MinimumPasswordLength , "5"); <br><br># $Timezone is used to convert times entered by users into GMT and back again <br># It should be set to a timezone recognized by your local unix box. <br>Set($Timezone , 'US/Eastern'); <br><br># }}} <br><br># {{{ Database Configuration <br><br># Database driver beeing used. Case matters <br># Valid types are "mysql", "Oracle" and "Pg" <br><br>Set($DatabaseType , 'mysql'); <br><br># The domain name of your database server <br># If you're running mysql and it's on localhost, <br># leave it blank for enhanced performance <br>Set($DatabaseHost , ''); <br>Set($DatabaseRTHost , ''); <br><br># The port that your database server is running on. Ignored unless it's <br># a positive integer. It's usually safe to leave this blank <br>Set($DatabasePort , ''); <br><br>#The name of the database user (inside the database) <br>Set($DatabaseUser , 'mysql'); <br><br># Password the DatabaseUser should use to access the database <br>Set($DatabasePassword , 'mysql'); <br><br># The name of the RT's database on your database server <br>Set($DatabaseName , 'rt'); <br><br># If you're using Postgres and have compiled in SSL support, <br># set DatabaseRequireSSL to 1 to turn on SSL communication <br>Set($DatabaseRequireSSL , undef); <br><br># }}} <br><br># {{{ Incoming mail gateway configuration <br><br># OwnerEmail is the address of a human who manages RT. RT will send <br># errors generated by the mail gateway to this address. This address <br># should _not_ be an address that's managed by your RT instance. <br><br>Set($OwnerEmail , 'root'); <br><br># If $LoopsToRTOwner is defined, RT will send mail that it believes <br># might be a loop to $RT::OwnerEmail <br><br>Set($LoopsToRTOwner , 1); <br><br># If $StoreLoops is defined, RT will record messages that it believes <br># to be part of mail loops. <br># As it does this, it will try to be careful not to send mail to the <br># sender of these messages <br><br>Set($StoreLoops , undef); <br><br># $MaxAttachmentSize sets the maximum size (in bytes) of attachments stored <br># in the database. <br><br># For mysql and oracle, we set this size at 10 megabytes. <br># If you're running a postgres version earlier than 7.1, you will need <br># to drop this to 8192. (8k) <br><br>Set($MaxAttachmentSize , 10000000); <br><br># $TruncateLongAttachments: if this is set to a non-undef value, <br># RT will truncate attachments longer than MaxAttachmentSize. <br><br>Set($TruncateLongAttachments , undef); <br><br># $DropLongAttachments: if this is set to a non-undef value, <br># RT will silently drop attachments longer than MaxAttachmentSize. <br><br>Set($DropLongAttachments , undef); <br><br># If $ParseNewMessageForTicketCcs is true, RT will attempt to divine <br># Ticket 'Cc' watchers from the To and Cc lines of incoming messages <br># Be forewarned that if you have _any_ addresses which forward mail to <br># RT automatically and you enable this option without modifying <br># "RTAddressRegexp" below, you will get yourself into a heap of trouble. <br><br>Set($ParseNewMessageForTicketCcs , undef); <br><br># RTAddressRegexp is used to make sure RT doesn't add itself as a ticket CC if <br># the setting above is enabled. <br><br>Set($RTAddressRegexp , '^rt\@example.com$'); <br><br># RT provides functionality which allows the system to rewrite <br># incoming email addresses. In its simplest form, <br># you can substitute the value in CanonicalizeEmailAddressReplace <br># for the value in CanonicalizeEmailAddressMatch <br># (These values are passed to the CanonicalizeEmailAddress subroutine in RT/User.pm) <br># By default, that routine performs a s/$Match/$Replace/gi on any address passed to it <br><br>#Set($CanonicalizeEmailAddressMatch , '@subdomain\.example\.com$'); <br>#Set($CanonicalizeEmailAddressReplace , '@example.com'); <br><br># set this to true and the create new user page will use the values that you <br># enter in the form but use the function CanonicalizeUserInfo in User_Local.pm <br>Set($CanonicalizeOnCreate , 0); <br><br># If $SenderMustExistInExternalDatabase is true, RT will refuse to <br># create non-privileged accounts for unknown users if you are using <br># the "LookupSenderInExternalDatabase" option. <br># Instead, an error message will be mailed and RT will forward the <br># message to $RTOwner. <br># <br># If you are not using $LookupSenderInExternalDatabase, this option <br># has no effect. <br># <br># If you define an AutoRejectRequest template, RT will use this <br># template for the rejection message. <br><br>Set($SenderMustExistInExternalDatabase , undef); <br><br># }}} <br><br># {{{ Outgoing mail configuration <br><br># RT is designed such that any mail which already has a ticket-id associated <br># with it will get to the right place automatically. <br><br># $CorrespondAddress and $CommentAddress are the default addresses <br># that will be listed in From: and Reply-To: headers of correspondence <br># and comment mail tracked by RT, unless overridden by a queue-specific <br># address. <br><br>Set($CorrespondAddress , 'RT_CorrespondAddressNotSet'); <br><br>Set($CommentAddress , 'RT_CommentAddressNotSet'); <br><br>#Sendmail Configuration <br><br># $MailCommand defines which method RT will use to try to send mail <br># We know that 'sendmailpipe' works fairly well. <br># If 'sendmailpipe' doesn't work well for you, try 'sendmail' <br># <br># Note that you should remove the '-t' from $SendmailArguments <br># if you use 'sendmail' rather than 'sendmailpipe' <br><br>Set($MailCommand , 'sendmailpipe'); <br><br># $SendmailArguments defines what flags to pass to $Sendmail <br># assuming you picked 'sendmail' or 'sendmailpipe' as the $MailCommand above. <br># If you picked 'sendmailpipe', you MUST add a -t flag to $SendmailArguments <br><br># These options are good for most sendmail wrappers and workalikes <br>Set($SendmailArguments , "-oi -t"); <br><br># $SendmailBounceArguments defines what flags to pass to $Sendmail <br># assuming RT needs to send an error (ie. bounce). <br><br>Set($SendmailBounceArguments , '-f "<>"'); <br><br># These arguments are good for sendmail brand sendmail 8 and newer <br>#Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m"); <br><br># If you selected 'sendmailpipe' above, you MUST specify the path <br># to your sendmail binary in $SendmailPath. <br># !! If you did not # select 'sendmailpipe' above, this has no effect!! <br>Set($SendmailPath , "/usr/sbin/sendmail"); <br><br># By default, RT sets the outgoing mail's "From:" header to <br># "SenderName via RT". Setting this option to 0 disables it. <br><br>Set($UseFriendlyFromLine , 1); <br><br># sprintf() format of the friendly 'From:' header; its arguments <br># are SenderName and SenderEmailAddress. <br>Set($FriendlyFromLineFormat , "\"%s via RT\" <%s>"); <br><br># RT can optionally set a "Friendly" 'To:' header when sending messages to <br># Ccs or AdminCcs (rather than having a blank 'To:' header. <br><br># This feature DOES NOT WORK WITH SENDMAIL[tm] BRAND SENDMAIL <br># If you are using sendmail, rather than postfix, qmail, exim or some other MTA, <br># you _must_ disable this option. <br><br>Set($UseFriendlyToLine , 0); <br><br># sprintf() format of the friendly 'From:' header; its arguments <br># are WatcherType and TicketId. <br>Set($FriendlyToLineFormat, "\"%s of $RT::rtname Ticket #%s\":;"); <br><br># By default, RT doesn't notify the person who performs an update, as they <br># already know what they've done. If you'd like to change this behaviour, <br># Set $NotifyActor to 1 <br><br>Set($NotifyActor, 0); <br><br># By default, RT records each message it sends out to its own internal database.# To change this behaviour, set $RecordOutgoingEmail to 0 <br><br>Set($RecordOutgoingEmail, 1); <br><br># VERP support (http://cr.yp.to/proto/verp.txt) <br># uncomment the following two directives to generate envelope senders <br># of the form ${VERPPrefix}${originaladdress}@${VERPDomain} <br># (i.e. rt-jesse=fsck.com@rt.example.com ) This currently only works <br># with sendmail and sendmailppie. <br># Set($VERPPrefix, 'rt-'); <br># Set($VERPDomain, $RT::Organization); <br><br># }}} <br><br># {{{ Logging <br><br># Logging. The default is to log anything except debugging <br># information to syslog. Check the Log::Dispatch POD for <br># information about how to get things by syslog, mail or anything <br># else, get debugging info in the log, etc. <br><br># It might generally make <br># sense to send error and higher by email to some administrator. <br># If you do this, be careful that this email isn't sent to this RT instance. <br><br># the minimum level error that will be logged to the specific device. <br># levels from lowest to highest: <br># debug info notice warning error critical alert emergency <br><br># Mail loops will generate a critical log message. <br>Set($LogToSyslog , 'debug'); <br>Set($LogToScreen , 'error'); <br>Set($LogToFile , undef); <br>Set($LogDir, '/var/lib/log/rt'); <br>Set($LogToFileNamed , "rt.log"); #log to rt.log <br><br># If true generates stack traces to file log or screen <br># never generates traces to syslog <br><br>Set($LogStackTraces , 0); <br><br># On Solaris or UnixWare, set to ( socket => 'inet' ). Options here <br># override any other options RT passes to Log::Dispatch::Syslog. <br># Other interesting flags include facility and logopt. (See the <br># Log::Dispatch::Syslog documentation for more information.) (Maybe <br># ident too, if you have multiple RT installations.) <br><br>@LogToSyslogConf = () unless (@LogToSyslogConf); <br><br># RT has rudimentary SQL statement logging support if you have <br># DBIx-SearchBuilder 1.31_1 or higher; simply set $StatementLog to be <br># the level that you wish SQL statements to be logged at. <br>Set($StatementLog, undef); <br><br># }}} <br><br># {{{ Web interface configuration <br><br># This determines the default stylesheet the RT web interface will use. <br># RT ships with two valid values by default: <br># <br># 3.5-default The totally new, default layout for RT 3.5 <br># 3.4-compat A 3.4 compatibility stylesheet to make RT 3.5 look <br># (mostly) like 3.4 <br># <br># This value actually specifies a directory in share/html/NoAuth/css/ <br># from which RT will try to load the file main.css (which should <br># @import any other files the stylesheet needs). This allows you to <br># easily and cleanly create your own stylesheets to apply to RT. <br><br>Set($WebDefaultStylesheet, '3.5-default'); <br><br># Define the directory name to be used for images in rt web <br># documents. <br><br># If you're putting the web ui somewhere other than at the root of <br># your server, you should set $WebPath to the path you'll be <br># serving RT at. <br># $WebPath requires a leading / but no trailing /. <br># <br># In most cases, you should leave $WebPath set to '' (an empty value). <br><br>Set($WebPath , ""); <br><br># If we're running as a superuser, run on port 80 <br># Otherwise, pick a high port for this user. <br><br>Set($WebPort , 80);# + ($< * 7274) % 32766 + ($< && 1024)); <br><br># This is the Scheme, server and port for constructing urls to webrt <br># $WebBaseURL doesn't need a trailing / <br><br>Set($WebBaseURL , "http://localhost:$WebPort"); <br><br>Set($WebURL , $WebBaseURL . $WebPath . "/"); <br><br># $WebImagesURL points to the base URL where RT can find its images. <br><br>Set($WebImagesURL , $WebPath . "/NoAuth/images/"); <br><br># $LogoURL points to the URL of the RT logo displayed in the web UI <br><br>Set($LogoURL , $WebImagesURL . "bplogo.gif"); <br><br># WebNoAuthRegex - What portion of RT's URLspace should not require <br># authentication. <br>Set($WebNoAuthRegex, qr!^(?:/+NoAuth/| <br> /+REST/\d+\.\d+/NoAuth/)!x ); <br><br># SelfServiceRegex - What portion of RT's URLspace should <br># be accessible to Unprivileged users <br># This does not override the redirect from /Ticket/Display.html <br># to /SelfService/Display.html when Unprivileged <br># users attempt to access ticked displays <br>Set($SelfServiceRegex, qr!^(?:/+SelfService/)!x ); <br><br># For message boxes, set the entry box width and what type of wrapping <br># to use. <br># <br># Default width: 72 <br>Set($MessageBoxWidth , 72); <br><br># Default wrapping: "HARD" (choices "SOFT", "HARD") <br>Set($MessageBoxWrap, "HARD"); <br><br># Support implicit links in WikiText custom fields? A true value <br># causes InterCapped or ALLCAPS words in WikiText fields to <br># automatically become links to searches for those words. If used on <br># RTFM articles, it links to the RTFM article with that name. <br>Set($WikiImplicitLinks, 0); <br><br># if TrustHTMLAttachments is not defined, we will display them <br># as text. This prevents malicious HTML and javascript from being <br># sent in a request (although there is probably more to it than that) <br>Set($TrustHTMLAttachments , undef); <br><br># Should RT redistribute correspondence that it identifies as <br># machine generated? A true value will do so; setting this to '0' <br># will cause no such messages to be redistributed. <br># You can also use 'privileged' (the default), which will redistribute <br># only to privileged users. This helps to protect against malformed <br># bounces and loops caused by autocreated requestors with bogus addresses. <br>Set($RedistributeAutoGeneratedMessages, 'privileged'); <br><br># If PreferRichText is set to a true value, RT will show HTML/Rich text <br># messages in preference to their plaintext alternatives. RT "scrubs" the <br># html to show only a minimal subset of HTML to avoid possible contamination <br># by cross-site-scripting attacks. <br>Set($PreferRichText, undef); <br><br># If $WebExternalAuth is defined, RT will defer to the environment's <br># REMOTE_USER variable. <br><br>Set($WebExternalAuth , undef); <br><br># If $WebFallbackToInternalAuth is undefined, the user is allowed a chance <br># of fallback to the login screen, even if REMOTE_USER failed. <br><br>Set($WebFallbackToInternalAuth , undef); <br><br># $WebExternalGecos means to match 'gecos' field as the user identity); <br># useful with mod_auth_pwcheck and IIS Integrated Windows logon. <br><br>Set($WebExternalGecos , undef); <br><br># $WebExternalAuto will create users under the same name as REMOTE_USER <br># upon login, if it's missing in the Users table. <br><br>Set($WebExternalAuto , undef); <br><br># If $WebExternalAuto is true, this will be passed to User's <br># Create method. Use it to set defaults, such as creating <br># Unprivileged users with { Privileged => 0 } <br># Must be a hashref of arguments <br><br>Set($AutoCreate, undef); <br><br># $WebSessionClass is the class you wish to use for managing Sessions. <br># It defaults to use your SQL database, but if you are using MySQL 3.x and <br># plans to use non-ascii Queue names, uncomment and add this line to <br># RT_SiteConfig.pm will prevent session corruption. <br><br># Set($WebSessionClass , 'Apache::Session::File'); <br><br><br># By default, RT's session cookie isn't marked as "secure" Some web browsers <br># will treat secure cookies more carefully than non-secure ones, being careful <br># not to write them to disk, only send them over an SSL secured connection <br># and so on. To enable this behaviour, set # $WebSecureCookies to a true value. <br># NOTE: You probably don't want to turn this on _unless_ users are only connecting <br># via SSL encrypted HTTP connections. <br><br>Set($WebSecureCookies, 1); <br><br><br># By default, RT clears its database cache after every page view. <br># This ensures that you've always got the most current information <br># when working in a multi-process (mod_perl or FastCGI) Environment <br># Setting $WebFlushDbCacheEveryRequest to '0' will turn this off, <br># which will speed RT up a bit, at the expense of a tiny bit of data <br># accuracy. <br><br>Set($WebFlushDbCacheEveryRequest, '1'); <br><br><br># $MaxInlineBody is the maximum attachment size that we want to see <br># inline when viewing a transaction. 13456 is a random sane-sounding <br># default. <br><br>Set($MaxInlineBody, 13456); <br><br># $DefaultSummaryRows is default number of rows displayed in for search <br># results on the frontpage. <br><br>Set($DefaultSummaryRows, 10); <br><br># By default, RT shows newest transactions at the bottom of the ticket <br># history page, if you want see them at the top set this to '0'. <br><br>Set($OldestTransactionsFirst, '1'); <br><br># By default, RT shows images attached to incoming (and outgoing) ticket updates <br># inline. Set this variable to 0 if you'd like to disable that behaviour <br><br>Set($ShowTransactionImages, 1); <br><br><br># $HomepageComponents is an arrayref of allowed components on a user's <br># customized homepage ("RT at a glance"). <br><br>Set($HomepageComponents, [qw(QuickCreate Quicksearch MyAdminQueues MySupportQueues MyReminders RefreshHomepage)]); <br><br># @MasonParameters is the list of parameters for the constructor of <br># HTML::Mason's Apache or CGI Handler. This is normally only useful <br># for debugging, eg. profiling individual components with: <br># use MasonX::Profiler; # available on CPAN <br># @MasonParameters = (preamble => 'my $p = MasonX::Profiler->new($m, $r);'); <br><br>@MasonParameters = () unless (@MasonParameters); <br><br># $DefaultSearchResultFormat is the default format for RT search results <br>Set ($DefaultSearchResultFormat, qq{ <br> '__id__/TITLE:#', <br> '__Subject__/TITLE:Subject', <br> Status, <br> QueueName, <br> OwnerName, <br> Priority, <br> '__NEWLINE__', <br> '', <br> '<small>__Requestors__</small>', <br> '<small>__CreatedRelative__</small>', <br> '<small>__ToldRelative__</small>', <br> '<small>__LastUpdatedRelative__</small>', <br> '<small>__TimeLeft__</small>'}); <br><br># If $SuppressInlineTextFiles is set to a true value, then uploaded <br># text files (text-type attachments with file names) are prevented <br># from being displayed in-line when viewing a ticket's history. <br><br>Set($SuppressInlineTextFiles, undef); <br><br># If $DontSearchFileAttachments is set to a true value, then uploaded <br># files (attachments with file names) are not searched during full-content <br># ticket searches. <br><br>Set($DontSearchFileAttachments, undef); <br><br># The GD module (which RT uses for graphs) uses a builtin font that doesn't <br># have full Unicode support. You can use a particular TrueType font by setting <br># $ChartFont to the absolute path of that font. Your GD library must have <br># support for TrueType fonts to use this option. <br><br>Set($ChartFont, undef); <br><br><br># }}} <br><br># {{{ RT UTF-8 Settings <br><br># An array that contains languages supported by RT's internationalization <br># interface. Defaults to all *.po lexicons; setting it to qw(en ja) will make <br># RT bilingual instead of multilingual, but will save some memory. <br><br>@LexiconLanguages = qw(*) unless (@LexiconLanguages); <br><br># An array that contains default encodings used to guess which charset <br># an attachment uses if not specified. Must be recognized by <br># Encode::Guess. <br><br>@EmailInputEncodings = qw(utf-8 iso-8859-1 us-ascii) unless (@EmailInputEncodings); <br><br># The charset for localized email. Must be recognized by Encode. <br><br>Set($EmailOutputEncoding , 'utf-8'); <br><br># }}} <br><br># {{{ RT Date Handling Options (for Time::ParseDate) <br><br># Set this to 1 if your local date convention looks like "dd/mm/yy" <br># instead of "mm/dd/yy". <br><br>Set($DateDayBeforeMonth , 1); <br><br># Should an unspecified day or year in a date refer to a future or a <br># past value? For example, should a date of "Tuesday" default to mean <br># the date for next Tuesday or last Tuesday? Should the date "March 1" <br># default to the date for next March or last March? <br># Set to 0 for the next date or 1 for the last date. <br><br>Set($AmbiguousDayInPast , 1); <br><br># }}} <br><br># {{{ Miscellaneous RT Settings <br><br># You can define new statuses and even reorder existing statuses here. <br># WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT <br># will break horribly. The statuses you add must be no longer than <br># 10 characters. <br><br>@ActiveStatus = qw(new open stalled) unless @ActiveStatus; <br>@InactiveStatus = qw(resolved rejected deleted) unless @InactiveStatus; <br><br># Backward compatability setting. Add/Delete Link used to record one <br># transaction and run one scrip. Set this value to 1 if you want <br># only one of the link transactions to have scrips run. <br>Set($LinkTransactionsRun1Scrip , 0); <br><br># When this feature is enabled an user need ModifyTicket right on both <br># tickets to link them together, otherwise he can have right on any of <br># two. <br>Set($StrictLinkACL, 1); <br><br># }}} <br><br><br># {{{ Development Mode <br># <br># RT comes with a "Development mode" setting. <br># This setting, as a convenience for developers, turns on <br># all sorts of development options that you most likely don't want in <br># production: <br># <br># * Turns off Mason's 'static_source' directive. By default, you can't <br># edit RT's web ui components on the fly and have RT magically pick up <br># your changes. (It's a big performance hit) <br># <br># * More to come <br># <br><br>Set($DevelMode, '0'); <br><br># }}} <br><br><br>1; <br><br>------------- <br><br>Thanks in advance! <br>Joerg<br></div><div id="M2Signature"></div></body></html>