Changes between Initial Version and Version 1 of TracInterfaceCustomization

01/14/11 15:54:51 (12 years ago)



  • TracInterfaceCustomization

    v1 v1  
     1= Customizing the Trac Interface = 
     4== Introduction == 
     5This 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. 
     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]. 
     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'') 
     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.'' 
     14Now configure the appropriate section of your [wiki:TracIni trac.ini]: 
     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 ones). 
     21src = site/my_logo.gif 
     22alt = My Project 
     23width = 300 
     24height = 100 
     27=== Icon === 
     28Icons should be a 16x16 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. 
     32icon = site/my_icon.ico 
     35Note 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: 
     39icon = /favicon.ico 
     42Should 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.  
     46icon = /favicon.ico? 
     49== Custom Navigation Entries == 
     50The 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). 
     52In 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 . 
     55wiki.label = Home 
     56tickets.href = /report/24 
     59help = disabled 
     62See also TracNavigation for a more detailed explanation of the mainnav and metanav terms. 
     64== Site Appearance == #SiteAppearance 
     66Trac is using [ Genshi] as the templating engine. Documentation is yet to be written, in the meantime the following tip should work. 
     68Say you want to add a link to a custom stylesheet, and then your own 
     69header 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}}}: 
     73<html xmlns="" 
     74      xmlns:py="" 
     75      py:strip=""> 
     77  <!--! Add site-specific style sheet --> 
     78  <head py:match="head" py:attrs="select('@*')"> 
     79    ${select('*|comment()|text()')} 
     80    <link rel="stylesheet" type="text/css" 
     81          href="${'site/style.css')}" /> 
     82  </head> 
     84  <body py:match="body" py:attrs="select('@*')"> 
     85    <!--! Add site-specific header --> 
     86    <div id="siteheader"> 
     87      <!--! Place your header content here... --> 
     88    </div> 
     90    ${select('*|text()')} 
     92    <!--! Add site-specific footer --> 
     93    <div id="sitefooter"> 
     94      <!--! Place your footer content here... --> 
     95    </div> 
     96  </body> 
     100Those who are familiar with XSLT may notice that Genshi templates bear some similarities. However, there are some Trac specific features - for example '''${'site/style.css')}''' attribute references template placed into environment's ''htdocs/''  In a similar fashion '''${chrome.htdocs_location}''' is used to specify common ''htdocs/'' directory from Trac installation. 
     102`site.html` is one file to contain all your modifications. It usually works by the py:match (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 
     103and modify them. 
     104See [ this thread] for a detailed explanation of the above example `site.html`. 
     105A site.html can contain any number of such py:match sections for whatever you need to modify. This is all [ Genshi], so the docs on the exact syntax can be found there. 
     108Example snippet of adding introduction text to the new ticket form (hide when preview): 
     112<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)"> 
     114    <p>Please make sure to search for existing tickets before reporting a new one!</p> 
     115  </py:if> 
     116  ${select('*')}  
     120This 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. 
     122More examples snippets for `site.html` can be found at [trac:wiki:CookBook/SiteHtml CookBook/SiteHtml]. 
     124Example snippets for `style.css` can be found at [trac:wiki:CookBook/SiteStyleCss CookBook/SiteStyleCss]. 
     126If 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: 
     129<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')" 
     130        xmlns:xi=""> 
     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('*')}  
     138Also note that the `site.html` (despite its name) can be put in a common templates directory - see the `[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. 
     140== Project List == #ProjectList 
     142You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.   
     144The 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. 
     148<!DOCTYPE html 
     149    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
     150    ""> 
     151<html xmlns="" 
     152      xmlns:py="" 
     153      xmlns:xi=""> 
     154  <head> 
     155    <title>Available Projects</title> 
     156  </head> 
     157  <body> 
     158    <h1>Available Projects</h1> 
     159    <ul> 
     160      <li py:for="project in projects" py:choose=""> 
     161        <a py:when="project.href" href="$project.href" 
     162           title="$project.description">$</a> 
     163        <py:otherwise> 
     164          <small>$ <em>Error</em> <br /> ($project.description)</small> 
     165        </py:otherwise> 
     166      </li> 
     167    </ul> 
     168  </body> 
     172Once 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): 
     174For [wiki:TracModWSGI mod_wsgi]: 
     176os.environ['TRAC_ENV_INDEX_TEMPLATE'] = '/path/to/template' 
     179For [wiki:TracFastCgi FastCGI]: 
     181FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \ 
     182              -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
     185For [wiki:TracModPython mod_python]: 
     187PythonOption TracEnvParentDir /parent/dir/of/projects 
     188PythonOption TracEnvIndexTemplate /path/to/template 
     191For [wiki:TracCgi CGI]: 
     193SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template 
     196For [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   {{{ 
     200$ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
     201   }}} 
     202 - Windows 
     203   {{{ 
     205$ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
     206   }}} 
     208== Project Templates == 
     210The 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. 
     212With 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. 
     214However, 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: 
     215 * 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. 
     218Trac resolves requests for a template by first looking inside the project, then in any inherited templates location, and finally inside the Trac egg. 
     220Trac caches templates in memory by default to improve performance. To apply a template you need to restart the server. 
     222See also TracGuide, TracIni