Ț•œì í Ÿ ŸÁ ڀ%[CyĆ>?ț~7}#”âÙ!ŒčȚ֘Ûo\KŰš\mȚ|L gÉ ‚1!yŽ!Ș."7Ù"q#ƒ%\œ%+ù%,%&.R&A&+Ă&,ï&K'(h'+‘'éœ'D§(+ì(2)7K)Mƒ)*Ń)9ü)46*?k*B«*.î*a+l+—ì+„,)Ÿ,_É,k)-M•-Mă-R1.„.Æ—/*^1‰1 2l»2%(3\N44«4Žà5”o6Ê7âÏ7’Č8vE:˜Œ;4U=Š>š@,ŻB0ÜB1 Cu?C]”D©FZœGJH‰cHEíIš3J;ÎJ3 KW>Kv–KŹ L@șLûLmNœ†Nš#OîŸO­P©ÂPžlQI RSURS©RčęRÉ·TfVfèVBOWP’W!ăW)X–/X(ÆX"ïXÆZĆÙZ Ÿ[+À[%ì[\]o6]bŠ]± ^”»^śP_/H`šx`ê!a4 b/Ab7qb-©b*Śb!cD$ccicHÍcdőeA gŐOgk%hÀ‘nÇRo—päČpè—q:€r»rMŚr%sk:tqŠtțuTvlv6~wƒ”|ę9f7„ž„ČŸ„|q†%î†=‡QR‡b€‡Kˆ)Sˆ }ˆç‡‰qoŠÇá‹F©ŒiđŒXZŽ˜łŽśLËDÇ‘1ۑ) “+4“§`“•Đ–Ńë–Öœ—"”˜D·˜“ü˜@™óљ9ĆąLÿąL„6NŠŸ…ŠŐD§ÛšWöšäN©f3Ș_šȘwúȘir«|Ü«tYŹœÎŹ;Œ­~È­G°bg°+Ê°+ö°-"±JP±,›±+ȱ>ô±(3Č+\ČˆČGŽł3Öł8 Ž5CŽIyŽ)ĂŽ8íŽA&”Eh”Eź”,ô”V!¶]x¶·Ö¶Ž·0Ș·tÛ·|PžWÍžY%čPč)Đčœúș*žŒ†ăŒ€jœrŸZ‚Ÿ\Ęż3:ÀŒnÁ ûÁӜÂòpĂ cēÆŠ˜Ç[?Éè›Ê,„Ì<±Î6îÎ9%ϝ_φęĐȚ„Ò_cÔYĂԟŐSœÖąŚ:ŽŚLïŚW<Űt”۶ Ù9ÀÙ*úÙ|%۟ąÛ BÜăÜèĘÁùĘž»ȚGtßPŒßO à–]àćôálÚămGäQ”äeć mć,Žć”»ć1Pæ=‚æÍÀ瀎è*3é6^é)•é#żé%ăê{ ë_…ëŃć랷ìŚVí-.î™\îțöî?őï>5đ/tđ1€đ/ÖđńG%ńomńCĘń !ò5+ó6aőÁ˜őuZöÛĐü±ŹęŠ^ț éțśÿB 'NLvĂxÓnL»QÁŸ2” Vèn?źÓÈ|œ*HDXˆæSo0ĂôđŹöÇŁFk¶ČSi|œ*: Ïe!È5"Bț"*A$.l$(r,g,b) color triple to use for the color corresponding to the intermediate color, if two linear interpolations are used for the color scale (see `intermediate_point`). If not set, the intermediate color between `oldest_color` and `newest_color` will be used. (''since 0.11'')(r,g,b) color triple to use for the color corresponding to the newest color, for the color scale used in ''blame'' or the browser ''age'' column if `color_scale` is enabled. (''since 0.11'')(r,g,b) color triple to use for the color corresponding to the oldest color, for the color scale used in ''blame'' or the browser ''age'' column if `color_scale` is enabled. (''since 0.11'')A Genshi text template snippet used to get the notification subject. By default, the subject template is `$prefix #$ticket.id: $summary`. `$prefix` being the value of the `smtp_subject_prefix` option. ''(since 0.11)''Alternative text for the header logo.Always send notifications to any address in the ''reporter'' field.Always send notifications to the person who causes the ticket property change and to any previous updater of that ticket.Always send notifications to the ticket owner (''since 0.9'').As the workflow for tickets is now configurable, there can be many ticket states, and simply displaying closed tickets vs. all the others is maybe not appropriate in all cases. This section enables one to easily create ''groups'' of states that will be shown in different colors in the milestone progress bar. Note that the groups can only be based on the ticket //status//, nothing else. In particular, it's not possible to distinguish between different closed tickets based on the //resolution//. Example configuration with three groups, //closed//, //new// and //active// (the default only has closed and active): {{{ # the 'closed' group correspond to the 'closed' tickets closed = closed # .order: sequence number in the progress bar closed.order = 0 # .query_args: optional parameters for the corresponding # query. In this example, the changes from the # default are two additional columns ('created' and # 'modified'), and sorting is done on 'created'. closed.query_args = group=resolution,order=time,col=id,col=summary,col=owner,col=type,col=priority,col=component,col=severity,col=time,col=changetime # .overall_completion: indicates groups that count for overall # completion percentage closed.overall_completion = true new = new new.order = 1 new.css_class = new new.label = new # Note: one catch-all group for other statuses is allowed active = * active.order = 2 # .css_class: CSS class for this interval active.css_class = open # .label: displayed label for this group active.label = in progress }}} The definition consists in a comma-separated list of accepted status. Also, '*' means any status and could be used to associate all remaining states to one catch-all group. The CSS class can be one of: new (yellow), open (no color) or closed (green). Other styles can easily be added using custom CSS rule: `table.progress td. { background: }` to a [TracInterfaceCustomization#SiteAppearance site/style.css] file for example. (''since 0.11'')Automatically reload template files after modification.Base URL for serving the core static resources below `/chrome/common/`. It can be left empty, and Trac will simply serve those resources itself. Advanced users can use this together with [TracAdmin trac-admin ... deploy ] to allow serving the static resources for Trac directly from the web server. Note however that this only applies to the `/htdocs/common` directory, the other deployed resources (i.e. those from plugins) will not be made available this way and additional rewrite rules will be needed in the web server.Base URL of a Trac instance where errors in this Trac should be reported. This can be an absolute or relative URL, or '.' to reference this Trac instance. An empty value will disable the reporting buttons. (''since 0.11.3'')Charset to be used when in doubt.Check that the committer has permission to perform the requested operations on the referenced tickets. This requires that the user names be the same for Trac and repository operations.Comma separated list of paths categorized as branches. If a path ends with '*', then all the directory entries found below that path will be included. Example: `/trunk, /branches/*, /projectAlpha/trunk, /sandbox/*`Comma separated list of paths categorized as tags. If a path ends with '*', then all the directory entries found below that path will be included. Example: `/tags/*, /projectAlpha/tags/A-1.0, /projectAlpha/tags/A-v1.1`Comma-separated list of MIME types that should be treated as binary data. (''since 0.11.5'')Comma-separated list of allowed prefixes for repository directories when adding and editing repositories in the repository admin panel. If the list is empty, all repository directories are allowed. (''since 0.12.1'')Comma-separated list of colors to use for the TracRevisionLog graph display. (''since 1.0'')Comma-separated list of domains that should be considered as valid for email addresses (such as localdomain).Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains).Comma-separated list of version control properties to hide from the repository browser. (''since 0.9'')Comma-separated list of version control properties to render as oneliner wiki content in the repository browser. (''since 0.11'')Comma-separated list of version control properties to render as wiki content in the repository browser. (''since 0.11'')Commands that add a reference, as a space-separated list. If set to the special value , all tickets referenced by the message will get a reference to the changeset.Commands that close tickets, as a space-separated list.Custom logging format. If nothing is set, the following will be used: Trac[$(module)s] $(levelname)s: $(message)s In addition to regular key names supported by the Python logger library (see http://docs.python.org/library/logging.html), one could use: - $(path)s the path for the current environment - $(basename)s the last path component of the current environment - $(project)s the project name Note the usage of `$(...)s` instead of `%(...)s` as the latter form would be interpreted by the ConfigParser itself. Example: `($(thread)d) Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s` ''(since 0.10.5)''Database backup locationDatabase connection [wiki:TracEnvironment#DatabaseConnectionStrings string] for this projectDefault cc: list for newly created tickets.Default component for newly created tickets.Default description for newly created tickets.Default host/domain to append to address that do not specify one.Default keywords for newly created tickets.Default milestone for newly created tickets.Default number of days displayed in the Timeline, in days. (''since 0.9.'')Default owner for newly created tickets.Default priority for newly created tickets.Default repository connector type. (''since 0.10'') This is also used as the default repository type for repositories defined in [[TracIni#repositories-section repositories]] or using the "Repositories" admin panel. (''since 0.12'')Default resolution for resolving (closing) tickets (''since 0.11'').Default severity for newly created tickets.Default summary (title) for newly created tickets.Default type for newly created tickets (''since 0.9'').Default value for the limit argument in the TracRevisionLog. (''since 0.11'')Default version for newly created tickets.Define charset encoding of paths within git repositories.Displayed tab width in file preview. (''since 0.9'')Don't accept tickets with a too big comment. (''since 0.11.2'')Don't accept tickets with a too big description. (''since 0.11'').E-Mail address of the project's administrator.Email address(es) to always send notifications to, addresses can be seen by all recipients (Cc:).Email address(es) to always send notifications to, addresses do not appear publicly (Bcc:). (''since 0.10'')Enable colorization of the ''age'' column. This uses the same color scale as the source code annotation: blue is older, red is newer. (''since 0.11'')Enable email notification.Enable persistent caching of commit tree.Enable reverse mapping of git email addresses to trac user ids (costly if you have many users).Enable the display of all ticket changes in the timeline, not only open / close operations (''since 0.9'').Enable the display of component of tickets in the timeline (''since 1.1.1'').Enable/disable highlighting CamelCase links to missing pages (''since 0.9'').Enable/disable splitting the WikiPageNames with space characters (''since 0.10'').Enable/disable the use of unsafe HTML tags such as `