Changes between Version 1 and Version 2 of TracInterfaceCustomization

Mar 27, 2008, 7:31:47 AM (14 years ago)



  • TracInterfaceCustomization

    v1 v2  
    1010The 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.''
    1214Now configure the appropriate section of your [wiki:TracIni trac.ini]:
    1416=== Logo ===
    15 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.
     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).
    40 == Site Header & Footer ==
    41 In the environment folder for each Trac project there should be a directory called {{{templates}}}.  This folder contains files {{{site_header.cs}}} and {{{site_footer.cs}}}.  Users can customize their Trac site by adding the required HTML markup to these files.  The content of these two files will be placed immediately following the opening {{{<body>}}} tag and immediately preceding the closing {{{</body>}}} tag of each page in the site, respectively.
     42== Custom Navigation Entries ==
     43The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them.
    43 These files may contain static HTML, though if users desire to have dynamically generated content they can make use of the [ ClearSilver] templating language from within the pages as well. When you need to see what variables are available to the template, append the query string `?hdfdump=1` to the URL of your Trac site. This will display a structured view of the template data.
     45In 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 .
     48wiki.label = Home
     49tickets.href = /report/24
    45 == Site CSS ==
    46 The primary means to adjust the layout of a Trac site is by add [ CSS] style rules that overlay the default rules. This is best done by editing the `site_css.cs` file in the enviroment's `templates` directory. The content of that template gets inserted into a `<style type="text/css></style>` element on every HTML page generated by Trac.
    48 While you can add your custom style rules directory to the `site_css.cs` file, it is recommended that you simply reference an external style sheet, thereby enabling browsers to cache the CSS file instead of transmitting the rules with every response.
    50 The following example would import a style sheet located in the `style` root directory of your host:
    51 {{{
    52 @import url(/style/mytrac.css);
     52help = disabled
    55 You can use a !ClearSilver variable to reference a style sheet stored in the project environment's `htdocs` directory:
     56== Site Appearance ==
     58Trac is using [ Genshi] as the templating engine. Documentation is yet to be written, in the meantime the following tip should work.
     60Say you want to add a link to a custom stylesheet, and then your own
     61header and footer.  Create a file {{{/path/to/env/templates/site.html}}} or {{{/path/to/inherit/option/templates_dir/site.html}}}, with contents like this:
    57 @import url(<?cs var:chrome.href ?>/site/style.css);
     65<html xmlns=""
     66      xmlns:py=""
     67      py:strip="">
     69  <!--! Add site-specific style sheet -->
     70  <head py:match="head" py:attrs="select('@*')">
     71    ${select('*')}
     72    <link rel="stylesheet" type="text/css"
     73          href="${'site/style.css')}" />
     74  </head>
     76  <body py:match="body" py:attrs="select('@*')">
     77    <!--! Add site-specific header -->
     78    <div id="siteheader">
     79      <!--! Place your header content here... -->
     80    </div>
     82    ${select('*|text()')}
     84    <!--! Add site-specific footer -->
     85    <div id="sitefooter">
     86      <!--! Place your footer content here... -->
     87    </div>
     88  </body>
     91Note that this references your environment's `htdocs/style.css`.
     93Example snippet of adding introduction text to the new ticket form (hide when preview):
     97<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')">
     98  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
     99    <p>Please make sure to search for existing tickets before reporting a new one!</p>
     100  </py:if>
     101  ${select('*')}
    60 == Main Templates ==
     105If the environment is upgraded from 0.10 and a `site_newticket.cs` file already exists, it can actually be loaded by using a workaroud - 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:
     108<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')"
     109        xmlns:xi="">
     110  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
     111    <xi:include href="site_newticket.cs"><xi:fallback /></xi:include>
     112  </py:if>
     113  ${select('*')}
    62 It is also possible to use your own modified versions of the Trac [ ClearSilver] templates. Note though that this technique is not recommended because it makes upgrading Trac rather problematic: there are unfortunately several dependencies between the templates and the application code, such as the name of form fields and the structure of the template data, and these are likely to change between different versions of Trac.
     117Also 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.
    64 If you absolutely need to use modified templates, copy the template files from the default templates directory (usually in found in `$prefix/share/trac/templates`) into the `templates` directory of the project environment. Then modify those copies to get the desired results.
     119== Project List ==
     120You can use a custom ClearSilver template to display the list of projects if you are using Trac with multiple projects. 
     122The 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.
     126<!DOCTYPE html
     127    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     128    "">
     129<html xmlns=""
     130      xmlns:py=""
     131      xmlns:xi="">
     132  <head>
     133    <title>Available Projects</title>
     134  </head>
     135  <body>
     136    <h1>Available Projects</h1>
     137    <ul>
     138      <li py:for="project in projects" py:choose="">
     139        <a py:when="project.href" href="$project.href"
     140           title="$project.description">$</a>
     141        <py:otherwise>
     142          <small>$ <em>Error</em> <br /> ($project.description)</small>
     143        </py:otherwise>
     144      </li>
     145    </ul>
     146  </body>
     150Once 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):
     152For [wiki:TracFastCgi FastCGI]:
     154FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects
     155              -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     158For [wiki:TracModPython mod_python]:
     160PythonOption TracEnvIndexTemplate /path/to/template
     163For [wiki:TracCgi CGI]:
     165SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template
     168For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd:
     169 - Unix
     170   {{{
     172$ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     173   }}}
     174 - Windows
     175   {{{
     177$ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     178   }}}