Changes between Version 2 and Version 3 of TracInterfaceCustomization


Ignore:
Timestamp:
Aug 13, 2019, 3:52:01 PM (5 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracInterfaceCustomization

    v2 v3  
    1 = Customizing the Trac Interface = 
     1= Customizing the Trac Interface 
    22[[TracGuideToc]] 
    3 [[PageOutline]] 
     3[[PageOutline(2-5,Contents,pullout)]] 
    44 
    5 == Introduction == 
    6 This page is meant to give users suggestions on how they can customize the look of Trac.  Topics on this page cover editing the HTML templates and CSS files, but not the program code itself.  The topics are intended to show users how they can modify the look of Trac to meet their specific needs.  Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page. 
     5This page gives suggestions on how to customize the look of Trac. Topics include editing the HTML templates and CSS files, but not the program code itself. The topics show users how they can modify the look of Trac to meet their specific needs. Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page. 
    76 
    8 == Project Logo and Icon == 
    9 The easiest parts of the Trac interface to customize are the logo and the site icon.  Both of these can be configured with settings in [wiki:TracIni trac.ini]. 
     7== Project Logo and Icon 
     8The easiest parts of the Trac interface to customize are the logo and the site icon. Both of these can be configured with settings in [wiki:TracIni trac.ini]. 
    109 
    11 The logo or icon image should be put in a folder named "htdocs" in your project's environment folder.  (''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder'') 
     10The logo or icon image should be put in a folder named "htdocs" in your project's environment folder. ''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder''. 
    1211 
    13  ''Note: you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.'' 
     12'''Note''': you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration. 
    1413 
    1514Now configure the appropriate section of your [wiki:TracIni trac.ini]: 
    1615 
    17 === Logo === 
    18 Change the `src` setting to `site/` followed by the name of your image file.  The `width` and `height` settings should be modified to match your image's dimensions (the Trac chrome handler uses "`site/`" for files within the project directory `htdocs`, and "`common/`" for the common `htdocs` directory belonging to a Trac installation). Note that 'site/' is not a placeholder for your project name, it is the actual prefix that should be used (literally). For example, if your project is named 'sandbox', and the image file is 'red_logo.gif' then the 'src' setting would be 'site/red_logo.gif', not 'sandbox/red_logo.gif'. 
     16=== Logo 
     17Change the `src` setting to `site/` followed by the name of your image file. The `width` and `height` settings should be modified to match your image's dimensions. The Trac chrome handler uses `site/` for files within the project directory `htdocs`, and `common/` for the common `htdocs` directory belonging to a Trac installation. Note that 'site/' is not a placeholder for your project name, it is the literal prefix that should be used. For example, if your project is named 'sandbox', and the image file is 'red_logo.gif' then the 'src' setting would be 'site/red_logo.gif', not 'sandbox/red_logo.gif'. 
    1918 
    20 {{{ 
     19{{{#!ini 
    2120[header_logo] 
    2221src = site/my_logo.gif 
    … …  
    2625}}} 
    2726 
    28 === Icon === 
    29 Icons should be a 32x32 image in `.gif` or `.ico` format.  Change the `icon` setting to `site/` followed by the name of your icon file.  Icons will typically be displayed by your web browser next to the site's URL and in the `Bookmarks` menu. 
     27=== Icon 
     28Icons are small images displayed by your web browser next to the site's URL and in the `Bookmarks` menu. Icons should be a 32x32 image in `.gif` or `.ico` format. Change the `icon` setting to `site/` followed by the name of your icon file: 
    3029 
    31 {{{ 
     30{{{#!ini 
    3231[project] 
    3332icon = site/my_icon.ico 
    3433}}} 
    3534 
    36 Note though that this icon is ignored by Internet Explorer, which only accepts a file named ``favicon.ico`` at the root of the host. To make the project icon work in both IE and other browsers, you can store the icon in the document root of the host, and reference it from ``trac.ini`` as follows: 
     35== Custom Navigation Entries 
     36The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them, but not for adding new ones. 
    3737 
    38 {{{ 
    39 [project] 
    40 icon = /favicon.ico 
    41 }}} 
    42  
    43 Should your browser have issues with your favicon showing up in the address bar, you may put a "?" (less the quotation marks) after your favicon file extension.  
    44  
    45 {{{ 
    46 [project] 
    47 icon = /favicon.ico? 
    48 }}} 
    49  
    50 == Custom Navigation Entries == 
    51 The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them (but not for adding new ones). 
    52  
    53 In the following example, we rename the link to the Wiki start "Home", and hide the "!Help/Guide". We also make the "View Tickets" entry link to a specific report . 
    54 {{{ 
     38In the following example, we rename the link to the Wiki start "Home", and hide the "!Help/Guide". We also make the "View Tickets" entry link to a specific report: 
     39{{{#!ini 
    5540[mainnav] 
    5641wiki.label = Home 
    … …  
    6348See also TracNavigation for a more detailed explanation of the mainnav and metanav terms. 
    6449 
    65 == Site Appearance == #SiteAppearance 
     50== Site Appearance #SiteAppearance 
    6651 
    67 Trac is using [http://genshi.edgewall.org Genshi] as the templating engine. Documentation is yet to be written, in the meantime the following tip should work. 
     52Trac is using [http://genshi.edgewall.org Genshi] as the templating engine. Say you want to add a link to a custom stylesheet, and then your own header and footer. Save the following content as `site.html` inside your projects `templates/` directory (each Trac project can have their own `site.html`), eg `/path/to/env/templates/site.html`: 
    6853 
    69 Say you want to add a link to a custom stylesheet, and then your own 
    70 header and footer. Save the following content as `site.html` inside your projects `templates/` directory (each Trac project can have their own `site.html`), e.g. {{{/path/to/env/templates/site.html}}}: 
    71  
    72 {{{ 
    73 #!xml 
     54{{{#!xml 
    7455<html xmlns="http://www.w3.org/1999/xhtml" 
    7556      xmlns:py="http://genshi.edgewall.org/" 
    … …  
    7960  <head py:match="head" py:attrs="select('@*')"> 
    8061    ${select('*|comment()|text()')} 
    81     <link rel="stylesheet" type="text/css" 
    82           href="${href.chrome('site/style.css')}" /> 
     62    <link rel="stylesheet" href="${href.chrome('site/style.css')}" /> 
    8363  </head> 
    8464 
    … …  
    9979}}} 
    10080 
    101 Those who are familiar with XSLT may notice that Genshi templates bear some similarities. However, there are some Trac specific features - for example `${href.chrome('site/style.css')}` attribute references a CSS file placed into environment's `htdocs/` directory. In a similar fashion `${chrome.htdocs_location}` is used to specify the common `htdocs/` directory belonging to a Trac installation. That latter location can however be overriden using the [[TracIni#trac-config|[trac] htdocs_location]] configuration setting. 
     81Notice that XSLT bears some similarities with Genshi templates. However, there are some Trac specific features, for example the `${href.chrome('site/style.css')}` attribute references `style.css` in the environment's `htdocs/` directory. In a similar fashion `${chrome.htdocs_location}` is used to specify the common `htdocs/` directory belonging to a Trac installation. That latter location can however be overriden using the [[TracIni#trac-section|[trac] htdocs_location]] configuration setting. 
    10282 
    103 `site.html` is one file to contain all your modifications. It usually works using the `py:match` directive (element or attribute), and it allows you to modify the page as it renders - the matches hook onto specific sections depending on what it tries to find 
    104 and modify them. 
     83`site.html` is one file to contain all your modifications. It usually works using the `py:match` directive (element or attribute), and it allows you to modify the page as it renders. The matches hook onto specific sections depending on what it tries to find and modify them. 
    10584See [http://groups.google.com/group/trac-users/browse_thread/thread/70487fb2c406c937/ this thread] for a detailed explanation of the above example `site.html`. 
    10685A `site.html` can contain any number of such `py:match` sections for whatever you need to modify. This is all Genshi, so the [http://genshi.edgewall.org/wiki/Documentation/xml-templates.html docs on the exact syntax] can be found there. 
    107  
    10886 
    10987Example snippet of adding introduction text to the new ticket form (but not shown during preview): 
    … …  
    11189{{{#!xml 
    11290<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')"> 
    113   <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)"> 
     91  <py:if test="req.path_info == '/newticket' and (not 'preview' in req.args)"> 
    11492    <p>Please make sure to search for existing tickets before reporting a new one!</p> 
    11593  </py:if> 
    … …  
    11896}}} 
    11997 
    120 This example illustrates a technique of using `req.environ['PATH_INFO']` to limit scope of changes to one view only. For instance, to make changes in `site.html` only for timeline and avoid modifying other sections - use  `req.environ['PATH_INFO'] == '/timeline'` condition in `<py:if>` test. 
     98This example illustrates a technique of using `req.path_info` to limit scope of changes to one view only. For instance, to make changes in `site.html` only for timeline and avoid modifying other sections - use `req.path_info == '/timeline'` condition in `<py:if>` test. 
    12199 
    122100More examples snippets for `site.html` can be found at [trac:wiki:CookBook/SiteHtml CookBook/SiteHtml]. 
    … …  
    124102Example snippets for `style.css` can be found at [trac:wiki:CookBook/SiteStyleCss CookBook/SiteStyleCss]. 
    125103 
    126 If the environment is upgraded from 0.10 and a `site_newticket.cs` file already exists, it can actually be loaded by using a workaround - providing it contains no ClearSilver processing. In addition, as only one element can be imported, the content needs some sort of wrapper such as a `<div>` block or other similar parent container. The XInclude namespace must be specified to allow includes, but that can be moved to document root along with the others: 
    127 {{{ 
    128 #!xml 
    129 <form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')" 
    130         xmlns:xi="http://www.w3.org/2001/XInclude"> 
    131   <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">  
    132     <xi:include href="site_newticket.cs"><xi:fallback /></xi:include> 
    133   </py:if> 
    134   ${select('*')}  
    135 </form> 
    136 }}} 
     104Note that the `site.html`, despite its name, can be put in a shared templates directory, see the [[TracIni#inherit-section|[inherit] templates_dir]] option. This could provide easier maintainence as one new global `site.html` file can be made to include any existing header, footer and newticket snippets. 
    137105 
    138 Also note that the `site.html` (despite its name) can be put in a common templates directory - see the [[TracIni#inherit-section|[inherit] templates_dir]] option. This could provide easier maintainence (and a migration path from 0.10 for larger installations) as one new global `site.html` file can be made to include any existing header, footer and newticket snippets. 
     106== Project List #ProjectList 
    139107 
    140 == Project List == #ProjectList 
     108You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects. 
    141109 
    142 You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.   
     110The following is the basic template used by Trac to display a list of links to the projects. For projects that could not be loaded, it displays an error message. You can use this as a starting point for your own index template: 
    143111 
    144 The following is the basic template used by Trac to display a list of links to the projects.  For projects that could not be loaded it displays an error message. You can use this as a starting point for your own index template. 
    145  
    146 {{{ 
    147 #!text/html 
     112{{{#!text/html 
    148113<!DOCTYPE html 
    149114    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
    … …  
    170135}}} 
    171136 
    172 Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located (pls verify ... not yet changed to 0.11): 
     137Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located: 
    173138 
    174139For [wiki:TracModWSGI mod_wsgi]: 
    175 {{{ 
     140{{{#!python 
    176141os.environ['TRAC_ENV_INDEX_TEMPLATE'] = '/path/to/template.html' 
    177142}}} 
    178143 
    179144For [wiki:TracFastCgi FastCGI]: 
    180 {{{ 
     145{{{#!apache 
    181146FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \ 
    182147              -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
    … …  
    184149 
    185150For [wiki:TracModPython mod_python]: 
    186 {{{ 
     151{{{#!apache 
    187152PythonOption TracEnvParentDir /parent/dir/of/projects 
    188153PythonOption TracEnvIndexTemplate /path/to/template 
    … …  
    190155 
    191156For [wiki:TracCgi CGI]: 
    192 {{{ 
     157{{{#!apache 
    193158SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template 
    194159}}} 
    195160 
    196161For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd: 
    197  - Unix 
    198    {{{ 
    199 #!sh 
     162 - Unix: 
     163   {{{#!sh 
    200164$ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
    201165   }}} 
    202  - Windows 
    203    {{{ 
    204 #!sh 
     166 - Windows: 
     167   {{{#!sh 
    205168$ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
    206169   }}} 
    207170 
    208 == Project Templates == 
     171== Project Templates 
    209172 
    210 The appearance of each individual Trac environment (that is, instance of a project) can be customized independently of other projects, even those hosted by the same server. The recommended way is to use a `site.html` template (see [#SiteAppearance]) whenever possible. Using `site.html` means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of `theme.html` or any other Trac template, you need to migrate your modifiations to the newer version - if not, new Trac features or bug fixes may not work as expected. 
     173The appearance of each individual Trac environment, ie instance of a project, can be customized independently of other projects, even those hosted on the same server. The recommended way is to use a `site.html` template whenever possible, see [#SiteAppearance]. Using `site.html` means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of `theme.html` or any other Trac template, you need to migrate your modifiations to the newer version. If not, new Trac features or bug fixes may not work as expected. 
    211174 
    212 With that word of caution, any Trac template may be copied and customized. The default Trac templates are located inside the installed Trac egg (`/usr/lib/pythonVERSION/site-packages/Trac-VERSION.egg/trac/templates, .../trac/ticket/templates, .../trac/wiki/templates, ++`). The [#ProjectList] template file is called `index.html`, while the template responsible for main layout is called `theme.html`. Page assets such as images and CSS style sheets are located in the egg's `trac/htdocs` directory. 
     175With that word of caution, any Trac template may be copied and customized. The default Trac templates are located inside the installed Trac egg, such as `/usr/lib/pythonVERSION/site-packages/Trac-VERSION.egg/trac/templates, ../trac/ticket/templates, ../trac/wiki/templates`. The [#ProjectList] template file is called `index.html`, while the template responsible for main layout is called `theme.html`. Page assets such as images and CSS style sheets are located in the egg's `trac/htdocs` directory. 
    213176 
    214 However, do not edit templates or site resources inside the Trac egg - installing Trac again can completely delete your modifications. Instead use one of two alternatives: 
     177However, do not edit templates or site resources inside the Trac egg. Reinstalling Trac overwrites your modifications. Instead use one of these alternatives: 
    215178 * For a modification to one project only, copy the template to project `templates` directory. 
    216  * For a modification shared by several projects, copy the template to a shared location and have each project point to this location using the `[inherit] templates_dir =` trac.ini option. 
     179 * For a modification shared by several projects, copy the template to a shared location and have each project point to this location using the `[inherit] templates_dir` trac.ini option. 
    217180 
    218181Trac resolves requests for a template by first looking inside the project, then in any inherited templates location, and finally inside the Trac egg. 
    219182 
    220 Trac caches templates in memory by default to improve performance. To apply a template you need to restart the server. 
     183Trac caches templates in memory by default to improve performance. To apply a template you need to restart the web server. 
    221184 
    222185----