Changeset 40542 for wiki

wiki/pages/TracInterfaceCustomization

-                      r40534
+                      r40542
+= Customizing the Trac Interface
+[[TracGuideToc]]
+[[PageOutline]]
+== Introduction
+This 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.
+== Project Logo and Icon
+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].
+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''.
+ '''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.
+Now configure the appropriate section of your [wiki:TracIni trac.ini]:
+=== Logo
+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 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'.
+{{{#!ini
+[header_logo]
+src = site/my_logo.gif
+alt = My Project
+width = 300
+height = 100
+}}}
+=== Icon
+Icons 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:
+{{{#!ini
+[project]
+icon = site/my_icon.ico
+}}}
+== Custom Navigation Entries
+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.
+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:
+{{{#!ini
+[mainnav]
+wiki.label = Home
+tickets.href = /report/24
+[metanav]
+help = disabled
+}}}
+See also TracNavigation for a more detailed explanation of the mainnav and metanav terms.
+== Site Appearance == #SiteAppearance
+Trac 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`:
+{{{#!xml
+<html xmlns="http://www.w3.org/1999/xhtml"
+      xmlns:py="http://genshi.edgewall.org/"
+      py:strip="">
+  <!--! Add site-specific style sheet -->
+  <head py:match="head" py:attrs="select('@*')">
+    ${select('*|comment()|text()')}
+    <link rel="stylesheet" href="${href.chrome('site/style.css')}" />
+  </head>
+  <body py:match="body" py:attrs="select('@*')">
+    <!--! Add site-specific header -->
+    <div id="siteheader">
+      <!--! Place your header content here... -->
+    </div>
+    ${select('*|text()')}
+    <!--! Add site-specific footer -->
+    <div id="sitefooter">
+      <!--! Place your footer content here... -->
+    </div>
+  </body>
+</html>
+}}}
+Notice 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.
+`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.
+See [http://groups.google.com/group/trac-users/browse_thread/thread/70487fb2c406c937/ this thread] for a detailed explanation of the above example `site.html`.
+A `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.
+Example snippet of adding introduction text to the new ticket form (but not shown during preview):
+{{{#!xml
+<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')">
+  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
+    <p>Please make sure to search for existing tickets before reporting a new one!</p>
+  </py:if>
+  ${select('*')}
+</form>
+}}}
+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.
+More examples snippets for `site.html` can be found at [trac:wiki:CookBook/SiteHtml CookBook/SiteHtml].
+Example snippets for `style.css` can be found at [trac:wiki:CookBook/SiteStyleCss CookBook/SiteStyleCss].
+Note 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 (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.
+== Project List == #ProjectList
+You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.
+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:
+{{{#!text/html
+<!DOCTYPE html
+    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+      xmlns:py="http://genshi.edgewall.org/"
+      xmlns:xi="http://www.w3.org/2001/XInclude">
+  <head>
+    <title>Available Projects</title>
+  </head>
+  <body>
+    <h1>Available Projects</h1>
+    <ul>
+      <li py:for="project in projects" py:choose="">
+        <a py:when="project.href" href="$project.href"
+           title="$project.description">$project.name</a>
+        <py:otherwise>
+          <small>$project.name: <em>Error</em> <br /> ($project.description)</small>
+        </py:otherwise>
+      </li>
+    </ul>
+  </body>
+</html>
+}}}
+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):
+For [wiki:TracModWSGI mod_wsgi]:
+{{{#!python
+os.environ['TRAC_ENV_INDEX_TEMPLATE'] = '/path/to/template.html'
+}}}
+For [wiki:TracFastCgi FastCGI]:
+{{{#!apache
+FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \
+              -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template
+}}}
+For [wiki:TracModPython mod_python]:
+{{{#!apache
+PythonOption TracEnvParentDir /parent/dir/of/projects
+PythonOption TracEnvIndexTemplate /path/to/template
+}}}
+For [wiki:TracCgi CGI]:
+{{{#!apache
+SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template
+}}}
+For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd:
+ - Unix
+   {{{#!sh
+$ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template
+   }}}
+ - Windows
+   {{{#!sh
+$ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template
+   }}}
+== Project Templates
+The 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 (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.
+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.
+However, do not edit templates or site resources inside the Trac egg. Reinstalling Trac overwrites your modifications. Instead use one of these alternatives:
+ * For a modification to one project only, copy the template to project `templates` directory.
+ * 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.
+Trac resolves requests for a template by first looking inside the project, then in any inherited templates location, and finally inside the Trac egg.
+Trac caches templates in memory by default to improve performance. To apply a template you need to restart the web server.
+----
+See also TracGuide, TracIni

wiki/pages/TracLanguages

-                      r40534
+                      r40542
+||=Code=||=Name=||=English name=||=Language title=||
+||Ar||العربية||Arabic||لغات أخرى||
+||Ast||asturianu||Asturian||Otres llingües||
+||Az||azərbaycanca||Azeri||Başqa dillərdə||
+||Be||беларуская||Belarusian||Іншыя мовы||
+||Bg||български||Bulgarian||Други езици||
+||Bn||বাংলা||Bengali||অন্যান্য ভাষাসমূহ||
+||Bs||bosanski||Bosnian||Drugim jezicima||
+||Ca||català||Catalan||Altres llengües||
+||Ca-Valencia||valencià||Valencian||Altres llengües||
+||Cs||čeština||Czech||Další jazyky||
+||Da||dansk||Danish||Andre sprog||
+||de||Deutsch||German||Andere Sprachen||
+||gr||Ελληνικά||Greek||Άλλες γλώσσες||
+||en||English||(American) English||Languages||
+||En_AU||Australian||Australian English||Languages||
+||En_GB||British||British||Languages||
+||Es||español||Spanish||Altres idiomas||
+||Et||eesti||Estonian||Teistes keeltes||
+||Eu||euskara||Basque||Beste hizkuntzak||
+||Fa||فارسی||Persian||زبانهای دیگر||
+||Fi||suomi||Finnish||Muilla kielillä||
+||fr||français||French||Autres langues||
+||Gl||galego||Galician||Outras linguas||
+||He||עברית||Hebrew||שפות אחרות||
+||Hi||हिन्दी||Hindi||अन्य भाषाओं||
+||Hr||hrvatski||Croatian||Drugi jezici||
+||Hu||magyar||Hungarian||Más nyelveken||
+||Hy||Հայերեն||Armenian||այլ լեզուներ||
+||Id||Bahasa Indonesia||Indonesian||Bahasa lain||
+||Is||Íslenska||Icelandic||Á öðrum tungumálum||
+||it||italiano||Italian||Altre lingue||
+||Ja||日本語||Japanese||他の言語||
+||Ka||ქართული||Georgian||სხვა ენებზე||
+||Ko||한국어||Korean||다른 언어||
+||Km||ភាសាខ្មែរ||Khmer||ភាសាផ្សេងទៀត||
+||Lt||lietuvių||Lithuanian||Kitomis kalbomis||
+||Lv||latviešu||Latvian||Pārējās valodas||
+||Mk||македонски||Macedonian||Други јазици||
+||Nb||norsk bokmål||Norwegian (Bokmal)||Andre språk||
+||nl||Nederlands||Dutch||Andere talen||
+||pl||polski||Polish||Inne języki||
+||Pt||português||Portuguese||Outras línguas||
+||Pt_BR||português brasileiro||Brazilian Portuguese||Outras línguas||
+||Ro||Română||Romanian||Alte limbi||
+||ru||русский||Russian||Другие языки||
+||Sq||shqip||Albanian||Gjuhët e tjera||
+||Sk||slovenčina||Slovak||Ďalšie jazyky||
+||Sl||slovenščina||Slovenian||Drugi jeziki||
+||Sr||српски||Serbian||Остали језици||
+||Sv||svenska||Swedish||Andra språk||
+||Th||ไทย||Thai||ภาษาอื่น ๆ||
+||Tr||Türkçe||Turkish||Diğer diller||
+||Uk||українська||Ukrainian||Інші мови||
+||Uz||ўзбек тили||Uzbek||Boshqa tillarda||
+||vn||Tiếng Việt||Vietnamese||Ngôn ngữ khác||
+||Zh_CN||简体中文||Chinese (Simplified)||其他语言||
+||Zh_TW||正體中文||Chinese (Traditional)||其他語言||

wiki/pages/TracLinks

-                      r40534
+                      r40542
+= Trac Links =
+[[TracGuideToc]]
+TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.
+TracLinks are generally of the form '''type:id''' (where ''id'' represents the
+number, name or path of the item) though some frequently used kinds of items
+also have short-hand notations.
+== Where to use TracLinks ==
+You can use TracLinks in:
+ * Source code (Subversion) commit messages
+ * Wiki pages
+ * Full descriptions for tickets, reports and milestones
+and any other text fields explicitly marked as supporting WikiFormatting.
+== Overview ==
+||= Wiki Markup =||= Display =||
+{{{#!td
+ Wiki pages :: `CamelCase` or `wiki:CamelCase`
+ Parent page :: `[..]`
+ Tickets :: `#1` or `ticket:1`
+ Ticket comments :: `comment:1:ticket:2`
+ Reports :: `{1}` or `report:1`
+ Milestones :: `milestone:1.0`
+ Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
+ Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`, `[1/repository]`
+ Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
+ Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
+          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
+          or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
+ Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
+}}}
+{{{#!td
+ Wiki pages :: CamelCase or wiki:CamelCase
+ Parent page :: [..]
+ Tickets :: #1 or ticket:1
+ Ticket comments :: comment:1:ticket:2
+ Reports :: {1} or report:1
+ Milestones :: milestone:1.0
+ Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
+ Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository]
+ Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
+ Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
+          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
+          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
+ Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
+}}}
+'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
+pages whose names do not follow WikiPageNames rules, i.e., single words,
+non-alphabetic characters, etc. See WikiPageNames for more about features specific
+to links to Wiki page names.
+{{{#!table class=""
+|||| Trac links using the full (non-shorthand) notation can also be given a custom link title like this: ||
+{{{#!td
+{{{
+[ticket:1 This is a link to ticket number one] or
+[[ticket:1|This is another link to ticket number one]].
+}}}
+}}}
+{{{#!td
+[ticket:1 This is a link to ticket number one] or
+[[ticket:1|This is another link to ticket number one]].
+}}}
+|--------------------------------------------------------------------------------------
+|||| If the title is omitted, only the id (the part after the colon) is displayed:  ||
+{{{#!td
+{{{
+[ticket:1] or [[ticket:2]]
+}}}
+}}}
+{{{#!td
+[ticket:1] or [[ticket:2]]
+}}}
+|--------------------------------------------------------------------------------------
+|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
+{{{#!td
+{{{
+[SandBox the sandbox] or
+[[SandBox|the sandbox]]
+}}}
+}}}
+{{{#!td
+[SandBox the sandbox] or
+[[SandBox|the sandbox]]
+}}}
+|--------------------------------------------------------------------------------------
+|||| The short form ''realm:target'' can also be wrapped within a <...> pair, [[br]] which allow for arbitrary characters (i.e. anything but >)  ||
+{{{#!td
+{{{
+<wiki:Strange(page@!)>
+}}}
+}}}
+{{{#!td
+<wiki:Strange(page@!)>
+}}}
+}}}
+TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
+== Advanced use of TracLinks ==
+=== Relative links ===
+To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
+{{{
+ WikiPage/SubWikiPage or ./SubWikiPage
+}}}
+To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
+{{{
+  [..] or [[..]]
+}}}
+  [..] or [[..]]
+To link from a [trac:SubWiki SubWiki] page to a [=#sibling sibling] page, use a '../':
+{{{
+  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
+}}}
+  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
+But in practice you often won't need to add the `../` prefix to link to a sibling page.
+For resolving the location of a wiki link, it's the target page closest in the hierarchy
+to the page where the link is written which will be selected. So for example, within
+a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
+This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
+In order to link explicitly to a [=#toplevel toplevel] Wiki page,
+use the `wiki:/` prefix. Be careful **not** to use the `/` prefix alone, as this corresponds to the [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` part in the resulting URL. A link such as `[../newticket]` will stay in the wiki namespace and therefore link to a sibling page.
+=== Link anchors ===
+To create a link to a specific anchor in a page, use '#':
+{{{
+ [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
+}}}
+  [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
+Hint: when you move your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the `#...` part inside a relative link to an anchor.
+To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':
+{{{
+ [#/Milestone first occurrence of Milestone] or
+ [#?Milestone last occurrence of Milestone]
+}}}
+ [#/Milestone first occurrence of Milestone] or
+ [#?Milestone last occurrence of Milestone]
+This will also highlight all other matches on the linked page. By default only case sensitive matches are considered. To include case insensitive matches append '/i':
+{{{
+ [#/Milestone/i first occurrence of Milestone or milestone] or
+ [#?Milestone/i last occurrence of Milestone or milestone]
+}}}
+ [#/Milestone/i first occurrence of Milestone or milestone] or
+ [#?Milestone/i last occurrence of Milestone or milestone]
+''(since Trac 1.0)''
+Such anchors can be very useful for linking to specific lines in a file in the source browser:
+{{{
+ [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
+ [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
+}}}
+ [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
+ [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
+(Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.)
+Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead:
+{{{
+ [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
+ [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
+}}}
+ [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
+ [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
+=== InterWiki links ===
+Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there's a more specialized way to register other Trac environments which offers greater flexibility.
+=== InterTrac links ===
+This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
+Any type of Trac link can be written in one Trac environment and actually refer to resources in another Trac environment. All that is required is to prefix the Trac link with the name of the other Trac environment followed by a colon. The other Trac environment must be registered on the InterTrac page.
+A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links (e.g. `{}`, `r`, `#`) can also be used. For example if T was set as an alias for Trac, links to Trac tickets can be written #T234, links to Trac changesets can be written [trac 1508].
+See InterTrac for the complete details.
+=== Server-relative links ===
+It is often useful to be able to link to objects in your project that
+have no built-in Trac linking mechanism, such as static resources, `newticket`,
+a shared `/register` page on the server, etc.
+To link to resources inside the project, use either an absolute path from the project root,
+or a relative link from the URL of the current page (''Changed in 0.11''):
+{{{
+[/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
+[/ home] or [[/|home]]
+}}}
+Display: [/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
+[/ home] or [[/|home]]
+To link to another location on the server (possibly outside the project but on the same host), use the `//` prefix (''Changed in 0.11''):
+{{{
+[//register Register Here] or [[//register|Register Here]]
+}}}
+Display: [//register Register Here] or [[//register|Register Here]]
+=== Quoting space in TracLinks ===
+Immediately after a TracLinks prefix, targets containing space characters should
+be enclosed in a pair of quotes or double quotes.
+Examples:
+ * !wiki:"The whitespace convention"
+ * !attachment:'the file.txt' or
+ * !attachment:"the file.txt"
+ * !attachment:"the file.txt:ticket:123"
+Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
+ * ![[The whitespace convention]]
+ * ![[attachment:the file.txt]]
+=== Escaping Links ===
+To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
+{{{
+ !NoLinkHere.
+ ![42] is not a link either.
+}}}
+Display:
+ !NoLinkHere.
+ ![42] is not a link either.
+=== Parameterized Trac links ===
+Many Trac resources have more than one way to be rendered, depending on some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.
+Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
+ - `wiki:WikiStart?format=txt`
+ - `ticket:1?version=1`
+ - `[/newticket?component=module1 create a ticket for module1]`
+ - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`
+== TracLinks Reference ==
+The following sections describe the individual link types in detail, as well as notes on advanced usage of links.
+=== attachment: links ===
+The link syntax for attachments is as follows:
+ * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
+ * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
+ * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753
+Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.
+If you'd like to create a direct link to the content of the attached file instead of a link to the attachment page, simply use `raw-attachment:` instead of `attachment:`.
+This can be useful for pointing directly to an HTML document, for example. Note that for this use case, you'd have to allow the web browser to render the content by setting `[attachment] render_unsafe_content = yes` (see TracIni#attachment-section). Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as otherwise this would open up your site to [wikipedia:Cross-site_scripting cross-site scripting] attacks.
+See also [#export:links].
+=== comment: links ===
+When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
+It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
+ - `comment:3:ticket:123`
+ - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
+It is also possible to link to the ticket's description using one of the following syntax:
+ - `comment:description` (within the ticket)
+ - `comment:description:ticket:123`
+ - `ticket:123#comment:description`
+=== htdocs: links ===
+Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
+=== query: links ===
+See TracQuery#UsingTracLinks and [#ticket:links].
+=== search: links ===
+See TracSearch#SearchLinks
+=== ticket: links ===
+ ''alias:'' `bug:`
+Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets.
+Example:
+ - `ticket:5000-6000`
+ - `ticket:1,150`
+=== timeline: links ===
+Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but if you don't want to compute the UTC time, you can specify a local time followed by your timezone offset relative to UTC.
+Examples:
+ - `timeline:2008-01-29`
+ - `timeline:2008-01-29T15:48`
+ - `timeline:2008-01-29T15:48Z`
+ - `timeline:2008-01-29T16:48+01`
+ - `timeline:2008-01-29T16:48+0100`
+ - `timeline:2008-01-29T16:48+01:00`
+=== wiki: links ===
+See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.
+=== Version Control related links ===
+It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it (the default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator).
+For example, `source:/trunk/COPYING` targets the path `/trunk/COPYING` in the default repository, whereas `source:/projectA/trunk/COPYING` targets the path `/trunk/COPYING` in the repository named `projectA`. This can be the same file if `'projectA'` is an alias to the default repository or if `''` (the default repository) is an alias to `'projectA'`.
+==== source: links ====
+ ''aliases:'' `browser:`, `repos:`
+The default behavior for a `source:/some/path link` is to open the browser in that directory directory
+if the path points to a directory or to show the latest content of the file.
+It's also possible to link directly to a specific revision of a file like this:
+ - `source:/some/file@123` - link to the file's revision 123
+ - `source:/some/file@head` - link explicitly to the latest revision of the file
+If the revision is specified, one can even link to a specific line number:
+ - `source:/some/file@123#L10`
+ - `source:/tag/0.10@head#L10`
+Finally, one can also highlight an arbitrary set of lines:
+ - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
+ - or without version number (the `@` is still needed): `source:/some/file@:10-20,100,103#L99`. Version can be omitted when the path is pointing to a source file that will no longer change (like `source:/tags/...`), otherwise it's better to specify which lines of //which version// of the file you're talking about
+Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` (e.g. `source:reponame/trunk/README`). ''(since 0.12)''
+==== export: links ====
+To force the download of a file in the repository, as opposed to displaying it in the browser, use the `export` link.  Several forms are available:
+ * `export:/some/file` - get the HEAD revision of the specified file
+ * `export:123:/some/file` - get revision 123 of the specified file
+ * `export:/some/file@123` - get revision 123 of the specified file
+This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns.
+If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of `source:/some/dir`).
+==== log: links ====
+The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions of the specified path, but it can also support displaying an arbitrary set of revisions.
+ - `log:/` - the latest revisions starting at the root of the repository
+ - `log:/trunk/tools` - the latest revisions in `trunk/tools`
+ - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
+ - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
+ - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
+There are short forms for revision ranges as well:
+ - `[20788,20791:20795]`
+ - `[20788,20791:20795/trunk/tools]`
+ - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
+Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`.
+In the presence of multiple repositories, the name of the repository should be specified as the first part of the path, e.g. `log:repos/branches` or `[20-40/repos]`.
+----
+See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki

wiki/pages/TracLogging

-                      r40534
+                      r40542
+= Trac Logging
+[[TracGuideToc]]
+Trac supports logging of system messages using the standard [http://docs.python.org/library/logging.html logging module] that comes with Python.
+Logging is configured in the `[logging]` section in [wiki:TracIni#logging-section trac.ini].
+== Supported Logging Methods
+The log method is set using the `log_type` option in [wiki:TracIni#logging-section trac.ini], which takes any of the following values:
+ '''none'':: Suppress all log messages.
+ '''file''':: Log messages to a file, specified with the `log_file` option in [wiki:TracIni#logging-section trac.ini]. Relative paths in `log_file` are resolved relative to the `log` directory of the environment.
+ '''stderr''':: Output all log entries to console ([wiki:TracStandalone tracd] only).
+ '''syslog''':: (UNIX) Send all log messages to the local syslogd via named pipe `/dev/log`. By default, syslog will write them to the file /var/log/messages.
+ '''eventlog''':: (Windows) Use the system's NT Event Log for Trac logging.
+== Log Levels
+The verbosity level of logged messages can be set using the `log_level` option in [wiki:TracIni#logging-section trac.ini]. The log level defines the minimum level of urgency required for a message to be logged, and those levels are:
+ '''CRITICAL''':: Log only the most critical (typically fatal) errors.
+ '''ERROR''':: Log failures, bugs and errors.
+ '''WARN''':: Log warnings, non-interrupting events.
+ '''INFO''':: Diagnostic information, log information about all processing.
+ '''DEBUG''':: Trace messages, profiling, etc.
+Additionally, you can  enable logging of SQL statements at debug level. This is turned off by default, as it's very verbose. Set `[trac] debug_sql = yes` in TracIni to activate.
+== Log Format
+The output format for log entries can be specified through the `log_format` option in [wiki:TracIni#logging-section trac.ini]. The format is a string which can contain any of the [http://docs.python.org/library/logging.html#logrecord-attributes Python logging Formatter variables]. Additonally, the following Trac-specific variables can be used:
+ '''$(basename)s''':: The last path component of the current environment.
+ '''$(path)s''':: The absolute path for the current environment.
+ '''$(project)s''':: The originating project's name.
+Note that variables are identified using a dollar sign (`$(...)s`) instead of percent sign (`%(...)s`).
+The default format is:
+{{{#!ini
+log_format = Trac[$(module)s] $(levelname)s: $(message)s
+}}}
+In a multi-project environment where all logs are sent to the same place (e.g. `syslog`), it makes sense to add the project name. In this example we use `basename` since that can generally be used to identify a project:
+{{{#!ini
+log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s
+}}}
+----
+See also: TracIni, TracGuide, TracEnvironment

wiki/pages/TracModPython

-                      r40534
+                      r40542
+[[TracGuideToc]]
+= Trac and mod_python
+Mod_python is an [https://httpd.apache.org/ Apache] module that embeds the Python interpreter within the server, so that web-based applications in Python will run many times faster than traditional CGI and will have the ability to retain database connections.
+Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably, especially compared to [TracCgi CGI], and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy.
+These instructions are for Apache 2. If you are using Apache 1.3, you may have some luck with [trac:wiki:TracModPython2.7 TracModPython2.7], but that is a deprecated setup.
+[[PageOutline(2-3,Overview,inline)]]
+== Simple configuration: single project == #Simpleconfiguration
+If you just installed mod_python, you may have to add a line to load the module in the Apache configuration:
+{{{#!apache
+LoadModule python_module modules/mod_python.so
+}}}
+'''Note''': The exact path to the module depends on how the HTTPD installation is laid out.
+On Debian using apt-get:
+{{{#!sh
+apt-get install libapache2-mod-python libapache2-mod-python-doc
+}}}
+Still on Debian, after you have installed mod_python, you must enable the modules in apache2, equivalent to the above Load Module directive:
+{{{#!sh
+a2enmod python
+}}}
+On Fedora use, using yum:
+{{{#!sh
+yum install mod_python
+}}}
+You can test your mod_python installation by adding the following to your httpd.conf. You should remove this when you are done testing for security reasons. Note: mod_python.testhandler is only available in mod_python 3.2+.
+{{{#!apache
+<Location /mpinfo>
+   SetHandler mod_python
+   PythonInterpreter main_interpreter
+   PythonHandler mod_python.testhandler
+   Order allow,deny
+   Allow from all
+</Location>
+}}}
+A simple setup of Trac on mod_python looks like this:
+{{{#!apache
+<Location /projects/myproject>
+   SetHandler mod_python
+   PythonInterpreter main_interpreter
+   PythonHandler trac.web.modpython_frontend
+   PythonOption TracEnv /var/trac/myproject
+   PythonOption TracUriRoot /projects/myproject
+   Order allow,deny
+   Allow from all
+</Location>
+}}}
+The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration without it; if the URLs produced by Trac look wrong, if Trac does not seem to recognize URLs correctly, or you get an odd "No handler matched request to..." error, add the '''`TracUriRoot`''' option. You will notice that the `Location` and '''`TracUriRoot`''' have the same path.
+The options available are:
+{{{#!apache
+# For a single project
+PythonOption TracEnv /var/trac/myproject
+# For multiple projects
+PythonOption TracEnvParentDir /var/trac/myprojects
+# For the index of multiple projects
+PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html
+# A space delimitted list, with a "," between key and value pairs.
+PythonOption TracTemplateVars key1,val1 key2,val2
+# Useful to get the date in the wanted order
+PythonOption TracLocale en_GB.UTF8
+# See description above
+PythonOption TracUriRoot /projects/myproject
+}}}
+=== Python Egg Cache
+Compressed Python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since Apache's home usually is not writeable, an alternate egg cache directory can be specified like this:
+{{{#!apache
+PythonOption PYTHON_EGG_CACHE /var/trac/myprojects/egg-cache
+}}}
+Or you can uncompress the Genshi egg to resolve problems extracting from it.
+=== Configuring Authentication
+See corresponding section in the [wiki:TracModWSGI#ConfiguringAuthentication] page.
+== Advanced Configuration
+=== Setting the Python Egg Cache
+If the Egg Cache isn't writeable by your Web server, you'll either have to change the permissions, or point Python to a location where Apache can write. This can manifest itself as a `500 internal server error` and/or a complaint in the syslog.
+{{{#!apache
+<Location /projects/myproject>
+  ...
+  PythonOption PYTHON_EGG_CACHE /tmp
+  ...
+</Location>
+}}}
+=== Setting the !PythonPath
+If the Trac installation isn't installed in your Python path, you will have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive:
+{{{#!apache
+<Location /projects/myproject>
+  ...
+  PythonPath "sys.path + ['/path/to/trac']"
+  ...
+</Location>
+}}}
+Be careful about using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work.
+=== Setting up multiple projects
+The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`:
+{{{#!apache
+<Location /projects>
+  SetHandler mod_python
+  PythonInterpreter main_interpreter
+  PythonHandler trac.web.modpython_frontend
+  PythonOption TracEnvParentDir /var/trac
+  PythonOption TracUriRoot /projects
+</Location>
+}}}
+When you request the `/projects` URL, you will get a listing of all subdirectories of the directory you set as `TracEnvParentDir` that look like Trac environment directories. Selecting any project in the list will bring you to the corresponding Trac environment.
+If you don't want to have the subdirectory listing as your projects home page you can use a
+{{{#!apache
+<LocationMatch "/.+/">
+}}}
+This will instruct Apache to use mod_python for all locations different from root while having the possibility of placing a custom home page for root in your !DocumentRoot folder.
+You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive:
+{{{#!apache
+<LocationMatch "/projects/[^/]+/login">
+  AuthType Basic
+  AuthName "Trac"
+  AuthUserFile /var/trac/.htpasswd
+  Require valid-user
+</LocationMatch>
+}}}
+=== Virtual Host Configuration
+Below is the sample configuration required to set up your Trac as a virtual server, ie when you access it at the URLs like
+`http://trac.mycompany.com`:
+{{{#!apache
+<VirtualHost *>
+    DocumentRoot /var/www/myproject
+    ServerName trac.mycompany.com
+    <Location />
+        SetHandler mod_python
+        PythonInterpreter main_interpreter
+        PythonHandler trac.web.modpython_frontend
+        PythonOption TracEnv /var/trac/myproject
+        PythonOption TracUriRoot /
+    </Location>
+    <Location /login>
+        AuthType Basic
+        AuthName "MyCompany Trac Server"
+        AuthUserFile /var/trac/myproject/.htpasswd
+        Require valid-user
+    </Location>
+</VirtualHost>
+}}}
+This does not seem to work in all cases. What you can do if it does not:
+ * Try using `<LocationMatch>` instead of `<Location>`.
+ * `<Location />` may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to Python and authentication does not work, ie you get the infamous Authentication information missing error. If this is the case, try using a sub-directory for Trac instead of the root, ie /web/ and /web/login instead of / and /login.
+ * Depending on apache's `NameVirtualHost` configuration, you may need to use `<VirtualHost *:80>` instead of `<VirtualHost *>`.
+For a virtual host that supports multiple projects replace `TracEnv /var/trac/myproject` with `TracEnvParentDir /var/trac`.
+'''Note''': !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment".
+== Troubleshooting
+If you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option:
+{{{#!apache
+<Location /projects/myproject>
+  ...
+  PythonDebug on
+</Location>
+}}}
+For multiple projects, try restarting the server as well.
+=== Login Not Working
+If you've used `<Location />` directive, it will override any other directives, as well as `<Location /login>`.
+The workaround is to use negation expression as follows (for multi project setups):
+{{{#!apache
+#this one for other pages
+<Location ~ "/*(?!login)">
+   SetHandler mod_python
+   PythonHandler trac.web.modpython_frontend
+   PythonOption TracEnvParentDir /projects
+   PythonOption TracUriRoot /
+</Location>
+#this one for login page
+<Location ~ "/[^/]+/login">
+   SetHandler mod_python
+   PythonHandler trac.web.modpython_frontend
+   PythonOption TracEnvParentDir /projects
+   PythonOption TracUriRoot /
+   #remove these if you don't want to force SSL
+   RewriteEngine On
+   RewriteCond %{HTTPS} off
+   RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
+   AuthType Basic
+   AuthName "Trac"
+   AuthUserFile /projects/.htpasswd
+   Require valid-user
+</Location>
+}}}
+=== Expat-related segmentation faults === #expat
+This problem will most certainly hit you on Unix when using Python 2.4.
+In Python 2.4, some version of [http://expat.sourceforge.net/ Expat] (an XML parser library written in C) is used and if Apache is using another version, this results in segmentation faults.
+As Trac 0.11 is using Genshi, which will indirectly use Expat, that problem can now hit you even if everything was working fine before with Trac 0.10. This problem has not been reported for Python 2.5+, so best to upgrade.
+=== Form submission problems
+If you're experiencing problems submitting some of the forms in Trac (a common problem is that you get redirected to the start page after submission), check whether your {{{DocumentRoot}}} contains a folder or file with the same path that you mapped the mod_python handler to. For some reason, mod_python gets confused when it is mapped to a location that also matches a static resource.
+=== Problem with virtual host configuration
+If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed, in a corresponding `<Directory>` block.
+Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able to download any CSS or images/icons. Use <Location /trac> `SetHandler None` </Location> to circumvent the problem, though this may not be the most elegant solution.
+=== Problem with zipped egg
+It's possible that your version of mod_python will not import modules from zipped eggs. If you encounter an `ImportError: No module named trac` in your Apache logs but you think everything is where it should be, this might be your problem. Look in your site-packages directory; if the Trac module appears as a ''file'' rather than a ''directory'', then this might be your problem. To rectify this, try installing Trac using the `--always-unzip` option:
+{{{#!sh
+easy_install --always-unzip Trac-0.12b1.zip
+}}}
+=== Using .htaccess
+Although it may seem trivial to rewrite the above configuration as a directory in your document root with a `.htaccess` file, this does not work. Apache will append a "/" to any Trac URLs, which interferes with its correct operation.
+It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth.
+This also works out-of-box, with following trivial config:
+{{{#!apache
+SetHandler mod_python
+PythonInterpreter main_interpreter
+PythonHandler trac.web.modpython_frontend
+PythonOption TracEnv /system/path/to/this/directory
+PythonOption TracUriRoot /path/on/apache
+AuthType Basic
+AuthName "ProjectName"
+AuthUserFile /path/to/.htpasswd
+Require valid-user
+}}}
+The `TracUriRoot` is obviously the path you need to enter to the browser to get to Trac, eg `domain.tld/projects/trac`.
+=== Additional .htaccess help
+If you are using the .htaccess method you may have additional problems if your Trac directory is inheriting .htaccess directives from another. This may also help to add to your .htaccess file:
+{{{#!apache
+<IfModule mod_rewrite.c>
+  RewriteEngine Off
+</IfModule>
+}}}
+=== Platform specific issues
+==== Win32 Issues
+If you run Trac with mod_python < 3.2 on Windows, uploading attachments will '''not''' work. This problem is resolved in mod_python 3.1.4 or later, so please upgrade mod_python to fix this.
+==== OS X issues
+When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, so please upgrade mod_python to fix this.
+==== SELinux issues
+If Trac reports something like: `Cannot get shared lock on db.lock`, then the security context on the repository may need to be set:
+{{{#!sh
+chcon -R -h -t httpd_sys_content_t PATH_TO_REPOSITORY
+}}}
+See also [http://subversion.apache.org/faq.html#reposperms How do I set repository permissions correctly?]
+==== FreeBSD issues
+The FreeBSD ports have both the new and old versions of mod_python and SQLite, but earlier versions of pysqlite and mod_python won't integrate:
+ * pysqlite requires threaded support in Python
+ * mod_python requires a threadless install.
+Apache2 does not automatically support threads on FreeBSD. You could force thread support when running `./configure` for Apache, using `--enable-threads`, but this isn´t recommended.
+The best option [http://modpython.org/pipermail/mod_python/2006-September/021983.html seems to be] adding to /usr/local/apache2/bin/ennvars the line:
+{{{#!sh
+export LD_PRELOAD=/usr/lib/libc_r.so
+}}}
+==== Fedora 7 Issues
+Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython, but not for tracd.
+=== Subversion issues
+If you get the following Trac error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. A better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.
+If this is not the case, it's possible that you are using Subversion libraries that are binary incompatible with the Apache ones and an incompatibility of the `apr` libraries is usually the cause. In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`).
+You also need a recent version of `mod_python` in order to avoid a runtime error ({{{argument number 2: a 'apr_pool_t *' is expected}}}) due to the default usage of multiple sub-interpreters. Version 3.2.8 ''should'' work, though it's probably better to use the workaround described in [trac:#3371 #3371], in order to force the use of the main interpreter:
+{{{#!apache
+PythonInterpreter main_interpreter
+}}}
+This is also the recommended workaround for other issues seen when using the Python bindings for Subversion within mod_python ([trac:#2611 #2611], [trac:#3455 #3455]). See in particular Graham Dumpleton's comment in [trac:comment:9:ticket:3455 #3455] explaining the issue.
+=== Page layout issues
+If the formatting of the Trac pages look weird, chances are that the style sheets governing the page layout are not handled properly by the web server. Try adding the following lines to your Apache configuration:
+{{{#!apache
+Alias /myproject/css "/usr/share/trac/htdocs/css"
+<Location /myproject/css>
+    SetHandler None
+</Location>
+}}}
+'''Note''': For the above configuration to have any effect it must be put after the configuration of your project root location, ie {{{<Location /myproject />}}}.
+Also, setting `PythonOptimize On` seems to mess up the page headers and footers, in addition to hiding the documentation for macros and plugins (see #Trac8956). Considering how little effect the option has, leave it `Off`.
+=== HTTPS issues
+If you want to run Trac fully under https you might find that it tries to redirect to plain http. In this case just add the following line to your Apache configuration:
+{{{#!apache
+<VirtualHost *>
+    DocumentRoot /var/www/myproject
+    ServerName trac.mycompany.com
+    SetEnv HTTPS 1
+    ....
+</VirtualHost>
+}}}
+=== Segmentation fault with php5-mhash or other php5 modules
+You may encounter segfaults (reported on Debian etch) if php5-mhash module is installed. Try to remove it to see if this solves the problem. See [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411487 Debian bug report].
+Some people also have troubles when using PHP5 compiled with its own third party libraries instead of system libraries. Check [http://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault Django segmentation fault].
+----
+See also: TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [trac:TracNginxRecipe]

wiki/pages/TracModWSGI

-                      r40534
+                      r40542
+= Trac and mod_wsgi
+[https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance.
+[[PageOutline(2-3,Overview,inline)]]
+== The `trac.wsgi` script
+Trac can be run on top of mod_wsgi with the help of an application script, which is just a Python file saved with a `.wsgi` extension.
+A robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin. The script should be sufficient for most installations and users not wanting more information can proceed to [#Mappingrequeststothescript configuring Apache].
+If you are using Trac with multiple projects, you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` in trac.wsgi:
+{{{#!python
+def application(environ, start_request):
+    # Add this to config when you have multiple projects
+    environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects')
+    ..
+}}}
+=== A very basic script
+In its simplest form, the script could be:
+{{{#!python
+import os
+os.environ['TRAC_ENV'] = '/usr/local/trac/mysite'
+os.environ['PYTHON_EGG_CACHE'] = '/usr/local/trac/mysite/eggs'
+import trac.web.main
+application = trac.web.main.dispatch_request
+}}}
+The `TRAC_ENV` variable should naturally be the directory for your Trac environment, and the `PYTHON_EGG_CACHE` should be a directory where Python can temporarily extract Python eggs. If you have several Trac environments in a directory, you can also use `TRAC_ENV_PARENT_DIR` instead of `TRAC_ENV`.
+On Windows:
+ - If run under the user's session, the Python Egg cache can be found in `%AppData%\Roaming`, for example:
+{{{#!python
+os.environ['PYTHON_EGG_CACHE'] = r'C:\Users\Administrator\AppData\Roaming\Python-Eggs'
+}}}
+ - If run under a Window service, you should create a directory for Python Egg cache:
+{{{#!python
+os.environ['PYTHON_EGG_CACHE'] = r'C:\Trac-Python-Eggs'
+}}}
+=== A more elaborate script
+If you are using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment.
+To solve this problem, use the following `.wsgi` file instead:
+{{{#!python
+import os
+os.environ['PYTHON_EGG_CACHE'] = '/usr/local/trac/mysite/eggs'
+import trac.web.main
+def application(environ, start_response):
+  environ['trac.env_path'] = '/usr/local/trac/mysite'
+  return trac.web.main.dispatch_request(environ, start_response)
+}}}
+For clarity, you should give this file a `.wsgi` extension. You should probably put the file in its own directory, since you will expose it to Apache.
+If you have installed Trac and Python eggs in a path different from the standard one, you should add that path by adding the following code at the top of the wsgi script:
+{{{#!python
+import site
+site.addsitedir('/usr/local/trac/lib/python2.4/site-packages')
+}}}
+Change it according to the path you installed the Trac libs at.
+== Mapping requests to the script
+After preparing your .wsgi script, add the following to your Apache configuration file, typically `httpd.conf`:
+{{{#!apache
+WSGIScriptAlias /trac /usr/local/trac/mysite/apache/mysite.wsgi
+<Directory /usr/local/trac/mysite/apache>
+    WSGIApplicationGroup %{GLOBAL}
+    Order deny,allow
+    Allow from all
+</Directory>
+}}}
+Here, the script is in a subdirectory of the Trac environment.
+If you followed the directions [TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
+{{{#!apache
+WSGIScriptAlias /trac /usr/share/trac/cgi-bin/trac.wsgi
+<Directory /usr/share/trac/cgi-bin>
+    WSGIApplicationGroup %{GLOBAL}
+    Order deny,allow
+    Allow from all
+</Directory>
+}}}
+In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi. This is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash. After adding this configuration, restart Apache, and then it should work.
+To test the setup of Apache, mod_wsgi and Python itself (ie. without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
+{{{#!python
+def application(environ, start_response):
+        start_response('200 OK',[('Content-type','text/html')])
+        return ['<html><body>Hello World!</body></html>']
+}}}
+For more information about using the mod_wsgi specific directives, see the [http://code.google.com/p/modwsgi/wiki/ mod_wsgi's wiki] and more specifically the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac IntegrationWithTrac] page.
+== Configuring Authentication
+The following sections describe different methods for setting up authentication. See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
+=== Using Basic Authentication
+The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program as follows:
+{{{#!sh
+$ htpasswd -c /somewhere/trac.htpasswd admin
+New password: <type password>
+Re-type new password: <type password again>
+Adding password for user admin
+}}}
+After the first user, you don't need the "-c" option anymore:
+{{{#!sh
+$ htpasswd /somewhere/trac.htpasswd john
+New password: <type password>
+Re-type new password: <type password again>
+Adding password for user john
+}}}
+  ''See the man page for `htpasswd` for full documentation.''
+After you've created the users, you can set their permissions using TracPermissions.
+Now, you need to enable authentication against the password file in the Apache configuration:
+{{{#!apache
+<Location "/trac/login">
+  AuthType Basic
+  AuthName "Trac"
+  AuthUserFile /somewhere/trac.htpasswd
+  Require valid-user
+</Location>
+}}}
+If you are hosting multiple projects, you can use the same password file for all of them:
+{{{#!apache
+<LocationMatch "/trac/[^/]+/login">
+  AuthType Basic
+  AuthName "Trac"
+  AuthUserFile /somewhere/trac.htpasswd
+  Require valid-user
+</LocationMatch>
+}}}
+Note that neither a file nor a directory named 'login' needs to exist.[[BR]]
+See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html mod_auth_basic] documentation.
+=== Using Digest Authentication
+For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”.
+You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
+{{{#!sh
+$ htdigest -c /somewhere/trac.htpasswd trac admin
+}}}
+The "trac" parameter above is the "realm", and will have to be reused in the Apache configuration in the !AuthName directive:
+{{{#!apache
+<Location "/trac/login">
+  AuthType Digest
+  AuthName "trac"
+  AuthDigestDomain /trac
+  AuthUserFile /somewhere/trac.htpasswd
+  Require valid-user
+</Location>
+}}}
+For multiple environments, you can use the same `LocationMatch` as described with the previous method.
+'''Note: `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity. '''
+Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system:
+{{{#!apache
+  LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
+}}}
+See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation.
+=== Using LDAP Authentication
+Configuration for [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2.x and OpenLDAP: slapd 2.3.19).
+. You need to load the following modules in Apache httpd.conf:
+{{{#!apache
+  LoadModule ldap_module modules/mod_ldap.so
+  LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
+}}}
+. Your httpd.conf also needs to look something like:
+{{{#!apache
+<Location /trac/>
+  # (if you're using it, mod_python specific settings go here)
+  Order deny,allow
+  Deny from all
+  Allow from 192.168.11.0/24
+  AuthType Basic
+  AuthName "Trac"
+  AuthBasicProvider "ldap"
+  AuthLDAPURL "ldap://127.0.0.1/dc=example,dc=co,dc=ke?uid?sub?(objectClass=inetOrgPerson)"
+  authzldapauthoritative Off
+  Require valid-user
+</Location>
+}}}
+. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory. Use the following as your LDAP URL:
+{{{#!apache
+  AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
+}}}
+ You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plaintext in the config, you need to use an account specifically for this task:
+{{{#!apache
+  AuthLDAPBindDN ldap-auth-user@example.com
+  AuthLDAPBindPassword "password"
+}}}
+ The whole section looks like:
+{{{#!apache
+<Location /trac/>
+  # (if you're using it, mod_python specific settings go here)
+  Order deny,allow
+  Deny from all
+  Allow from 192.168.11.0/24
+  AuthType Basic
+  AuthName "Trac"
+  AuthBasicProvider "ldap"
+  AuthLDAPURL "ldap://adserver.company.com:3268/DC=company,DC=com?sAMAccountName?sub?(objectClass=user)"
+  AuthLDAPBindDN       ldap-auth-user@company.com
+  AuthLDAPBindPassword "the_password"
+  authzldapauthoritative Off
+  # require valid-user
+  Require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
+</Location>
+}}}
+Note 1: This is the case where the LDAP search will get around the multiple OUs, conecting to the Global Catalog Server portion of AD. Note the port is 3268, not the normal LDAP 389. The GCS is basically a "flattened" tree which allows searching for a user without knowing to which OU they belong.
+Note 2: You can also require the user be a member of a certain LDAP group, instead of just having a valid login:
+{{{#!apache
+  Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
+}}}
+See also:
+ - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
+ - [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
+ - [http://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
+=== Using SSPI Authentication
+If you are using Apache on Windows, you can use mod_auth_sspi to provide single-sign-on. Download the module from the !SourceForge [http://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the following to your !VirtualHost:
+{{{#!apache
+<Location /trac/login>
+  AuthType SSPI
+  AuthName "Trac Login"
+  SSPIAuth On
+  SSPIAuthoritative On
+  SSPIDomain MyLocalDomain
+  SSPIOfferBasic On
+  SSPIOmitDomain Off
+  SSPIBasicPreferred On
+  Require valid-user
+</Location>
+}}}
+Using the above, usernames in Trac will be of the form `DOMAIN\username`, so you may have to re-add permissions and such. If you do not want the domain to be part of the username, set `SSPIOmitDomain On` instead.
+Some common problems with SSPI authentication: [trac:#1055], [trac:#1168] and [trac:#3338].
+See also [trac:TracOnWindows/Advanced].
+=== Using Apache authentication with the Account Manager plugin's Login form ===
+To begin with, see the basic instructions for using the Account Manager plugin's [http://trac-hacks.org/wiki/AccountManagerPlugin/Modules#LoginModule Login module] and its [http://trac-hacks.org/wiki/AccountManagerPlugin/AuthStores#HttpAuthStore HttpAuthStore authentication module].
+'''Note:''' If is difficult to get !HttpAuthStore to work with WSGI when using any Account Manager version prior to acct_mgr-0.4. Upgrading is recommended.
+Here is an example (from the !HttpAuthStore link) using acct_mgr-0.4 for hosting a single project:
+{{{#!ini
+[components]
+; be sure to enable the component
+acct_mgr.http.HttpAuthStore = enabled
+[account-manager]
+; configure the plugin to use a page that is secured with http authentication
+authentication_url = /authFile
+password_store = HttpAuthStore
+}}}
+This will generally be matched with an Apache config like:
+{{{#!apache
+<Location /authFile>
+   …HTTP authentication configuration…
+   Require valid-user
+</Location>
+}}}
+Note that '''authFile''' need not exist (unless you are using Account Manager older than 0.4). See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
+=== Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host
+Per the mod_wsgi documentation linked to above, here is an example Apache configuration that:
+ - serves the Trac instance from a virtualhost subdomain
+ - uses Apache basic authentication for Trac authentication.
+If you want your Trac to be served from e.g. !http://trac.my-proj.my-site.org, then from the folder e.g. `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
+Create the htpasswd file:
+{{{#!sh
+cd /home/trac-for-my-proj/the-env
+htpasswd -c htpasswd firstuser
+### and add more users to it as needed:
+htpasswd htpasswd seconduser
+}}}
+Keep the file above your document root for security reasons.
+Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following content:
+{{{#!apache
+<Directory /home/trac-for-my-proj/the-deploy/cgi-bin/trac.wsgi>
+  WSGIApplicationGroup %{GLOBAL}
+  Order deny,allow
+  Allow from all
+</Directory>
+<VirtualHost *:80>
+  ServerName trac.my-proj.my-site.org
+  DocumentRoot /home/trac-for-my-proj/the-env/htdocs/
+  WSGIScriptAlias / /home/trac-for-my-proj/the-deploy/cgi-bin/trac.wsgi
+  <Location '/'>
+    AuthType Basic
+    AuthName "Trac"
+    AuthUserFile /home/trac-for-my-proj/the-env/htpasswd
+    Require valid-user
+  </Location>
+</VirtualHost>
+}}}
+Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
+== Troubleshooting
+=== Use a recent version
+Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [http://code.google.com/p/modwsgi/issues/detail?id=100 #100] and [http://code.google.com/p/modwsgi/issues/detail?id=132 #132].
+''Note: using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks''
+If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 3.4 or greater. See [trac:#10675] for details.
+=== Getting Trac to work nicely with SSPI and 'Require Group'
+If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'.
+This WSGI script 'fixes' that:
+{{{#!python
+import os
+import trac.web.main
+os.environ['TRAC_ENV'] = '/usr/local/trac/mysite'
+os.environ['PYTHON_EGG_CACHE'] = '/usr/local/trac/mysite/eggs'
+def application(environ, start_response):
+    if "\\" in environ['REMOTE_USER']:
+        environ['REMOTE_USER'] = environ['REMOTE_USER'].split("\\", 1)[1]
+    return trac.web.main.dispatch_request(environ, start_response)
+}}}
+=== Trac with PostgreSQL
+When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as the database, the server ''may'' create a lot of open database connections and thus PostgreSQL processes.
+A somewhat brutal workaround is to disable connection pooling in Trac. This is done by setting `poolable = False` in `trac.db.postgres_backend` on the `PostgreSQLConnection` class.
+But it is not necessary to edit the source of Trac. The following lines in `trac.wsgi` will also work:
+{{{#!python
+import trac.db.postgres_backend
+trac.db.postgres_backend.PostgreSQLConnection.poolable = False
+}}}
+or
+{{{#!python
+import trac.db.mysql_backend
+trac.db.mysql_backend.MySQLConnection.poolable = False
+}}}
+Now Trac drops the connection after serving a page and the connection count on the database will be kept low.
+//This is not a recommended approach though. See also the notes at the bottom of the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac mod_wsgi's IntegrationWithTrac] wiki page.//
+=== Other resources
+For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [http://code.google.com/p/modwsgi/wiki/ApplicationIssues application issues] when using mod_wsgi. The wsgi page also has a [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac Integration With Trac] document.
+----
+See also: TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]

wiki/pages/TracNavigation

-                      r40534
+                      r40542
+= Trac Navigation
+The main and meta navigation entries can be customized in some basic ways. The `[mainnav]` and `[metanav]` configuration sections can be used to customize the navigation item text and link, change the ordering of the navigation items, or even disable them.
+=== `[mainnav]` #mainnav-bar
+`[mainnav]` corresponds to the '''main navigation bar''', the one containing entries such as ''Wiki'', ''Timeline'', ''Roadmap'', ''Browse Source'' and so on. This navigation bar is meant to access the default page of the main modules enabled in Trac that are accessible for the current user.
+** [=#Example Example] **
+In the following example we rename the link to WikiStart //Home//, and make the //View Tickets// entry link to a specific report.
+{{{#!ini
+[mainnav]
+wiki.label = Home
+tickets.href = /report/24
+}}}
+=== `[metanav]` #metanav-bar
+`[metanav]` corresponds to the '''meta navigation bar''', by default positioned above the main navigation bar and below the ''Search'' box. It contains the ''Login'', ''Logout'', ''!Help/Guide'' etc. entries. This navigation bar is meant to access some global information about the Trac project and the current user.
+There is one special entry in the  `[metanav]` section: `logout.redirect` is the page the user sees after hitting the logout button.  The ''!Help/Guide'' link is also hidden in the following example.
+[[comment(see also #Trac3808)]]
+** Example **
+{{{#!ini
+[metanav]
+help = disabled
+logout.redirect = wiki/Logout
+}}}
+=== URL Formats
+Possible URL formats for `.href` or `.redirect`:
+|| '''config''' || '''redirect to''' ||
+|| `wiki/Logout` || `/projects/env/wiki/Logout` ||
+|| `http://hostname/` || `http://hostname/` ||
+|| `/projects` || `/projects` ||
+=== Ordering #nav-order
+The `order` attribute specifies the order in which the navigation items are displayed. This can be particularly useful for plugins that add navigation items.
+Non-negative floating point values may be used for the `order` attribute. The navigation items will be arranged from left to right in increasing order. Navigation items without an `order` attribute are sorted alphabetically by name.
+The default values are:
+{{{#!ini
+[mainnav]
+browser.order = 4
+newticket.order = 6
+roadmap.order = 3
+search.order = 7
+tickets.order = 5
+timeline.order = 2
+wiki.order = 1
+[metanav]
+about.order = 5
+help.order = 4
+login.order = 1
+logout.order = 2
+prefs.order = 3
+}}}
+=== Context Navigation #ctxtnav-bar
+Note that it is still not possible to customize the '''contextual navigation bar''', ie the one usually placed below the main navigation bar.
+----
+See also: TracInterfaceCustomization, and the [http://trac-hacks.org/wiki/NavAddPlugin TracHacks:NavAddPlugin] or [http://trac-hacks.org/wiki/MenusPlugin TracHacks:MenusPlugin] (still needed for adding entries)

wiki/pages/TracNotification

-                      r40534
+                      r40542
+= Email Notification of Ticket Changes
+[[TracGuideToc]]
+Trac supports notification of ticket changes via email.
+Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list. For example, this is how the [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list is set up.
+Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini].
+== Receiving Notification Mails
+When reporting a new ticket or adding a comment, enter a valid email address or your Trac username in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket, depending on how notification is configured.
+=== How to use your username to receive notification mails
+To receive notification mails, you can either enter a full email address or your Trac username. To get notified with a simple username or login, you need to specify a valid email address in the ''Preferences'' page.
+Alternatively, a default domain name ('''`smtp_default_domain`''') can be set in the TracIni file, see [#ConfigurationOptions Configuration Options] below. In this case, the default domain will be appended to the username, which can be useful for an "Intranet" kind of installation.
+When using apache and mod_kerb for authentication against Kerberos / Active Directory, usernames take the form ('''`username@EXAMPLE.LOCAL`'''). To avoid this being interpreted as an email address, add the Kerberos domain to  ('''`ignore_domains`''').
+=== Ticket attachment notifications
+Since 1.0.3 Trac will send notifications when a ticket attachment is added or deleted. Usually attachment notifications will be enabled in an environment by default. To disable the attachment notifications for an environment the `TicketAttachmentNotifier` component must be disabled:
+{{{#!ini
+[components]
+trac.ticket.notification.TicketAttachmentNotifier = disabled
+}}}
+== Configuring SMTP Notification
+'''Important:''' For TracNotification to work correctly, the `[trac] base_url` option must be set in [wiki:TracIni trac.ini].
+=== Configuration Options
+These are the available options for the `[notification]` section in trac.ini:
+[[TracIni(notification)]]
+=== Example Configuration (SMTP)
+{{{#!ini
+[notification]
+smtp_enabled = true
+smtp_server = mail.example.com
+smtp_from = notifier@example.com
+smtp_replyto = myproj@projects.example.com
+smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
+}}}
+=== Example Configuration (`sendmail`)
+{{{#!ini
+[notification]
+smtp_enabled = true
+email_sender = SendmailEmailSender
+sendmail_path = /usr/sbin/sendmail
+smtp_from = notifier@example.com
+smtp_replyto = myproj@projects.example.com
+smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
+}}}
+=== Subscriber Configuration
+The default subscriptions are configured in the `[notification-subscriber]` section in trac.ini:
+[[TracIni(notification-subscriber)]]
+Each user can override these defaults in his ''Notifications'' preferences.
+For example to unsubscribe from notifications for one's own changes and comments, the rule "Never notify: I update a ticket" should be added above other subscription rules.
+=== Customizing the e-mail subject
+The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet. The default value is:
+{{{#!genshi
+$prefix #$ticket.id: $summary
+}}}
+The following variables are available in the template:
+ * `env`: The project environment (see [trac:source:/trunk/trac/env.py env.py]).
+ * `prefix`: The prefix defined in `smtp_subject_prefix`.
+ * `summary`: The ticket summary, with the old value if the summary was edited.
+ * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, eg `$ticket.milestone`.
+=== Customizing the e-mail content
+The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/ticket/templates`. You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this:
+{{{#!genshi
+$ticket_body_hdr
+$ticket_props
+{% choose ticket.new %}\
+{%   when True %}\
+$ticket.description
+{%   end %}\
+{%   otherwise %}\
+{%     if changes_body %}\
+${_('Changes (by %(author)s):', author=change.author)}
+$changes_body
+{%     end %}\
+{%     if changes_descr %}\
+{%       if not changes_body and not change.comment and change.author %}\
+${_('Description changed by %(author)s:', author=change.author)}
+{%       end %}\
+$changes_descr
+--
+{%     end %}\
+{%     if change.comment %}\
+${changes_body and _('Comment:') or _('Comment (by %(author)s):', author=change.author)}
+$change.comment
+{%     end %}\
+{%   end %}\
+{% end %}\
+--
+${_('Ticket URL: <%(link)s>', link=ticket.link)}
+$project.name <${project.url or abs_href()}>
+$project.descr
+}}}
+== Sample Email
+{{{
+#42: testing
+---------------------------+------------------------------------------------
+       Id:  42             |      Status:  assigned
+Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
+ Severity:  major          |   Milestone:  0.9
+ Priority:  lowest         |     Version:  0.6
+    Owner:  anonymous      |    Reporter:  jonas@example.com
+---------------------------+------------------------------------------------
+Changes:
+  * component:  changeset view => search system
+  * priority:  low => highest
+  * owner:  jonas => anonymous
+  * cc:  daniel@example.com =>
+         daniel@example.com, jonas@example.com
+  * status:  new => assigned
+Comment:
+I'm interested too!
+--
+Ticket URL: <http://example.com/trac/ticket/42>
+My Project <http://myproj.example.com/>
+}}}
+== Customizing e-mail content for MS Outlook
+MS Outlook normally presents plain text e-mails with a variable-width font, and as a result the ticket properties table will most certainly look like a mess in MS Outlook. This can be fixed with some customization of the [#Customizingthee-mailcontent e-mail template].
+Replace the following second row in the template:
+{{{
+$ticket_props
+}}}
+with this (requires Python 2.6 or later):
+{{{
+--------------------------------------------------------------------------
+{% with
+   pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in
+         [c.strip() for c in
+          ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]];
+   sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone',
+          'Component', 'Severity', 'Resolution', 'Keywords'] %}\
+${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)}
+{% end %}\
+--------------------------------------------------------------------------
+}}}
+The table of ticket properties is replaced with a list of a selection of the properties. A tab character separates the name and value in such a way that most people should find this more pleasing than the default table when using MS Outlook.
+{{{#!div style="margin: 1em 1.75em; border:1px dotted"
+{{{#!html
+#42: testing<br />
+--------------------------------------------------------------------------<br />
+<table cellpadding=0>
+<tr><td>Reporter:</td><td>jonas@example.com</td></tr>
+<tr><td>Owner:</td><td>anonymous</td></tr>
+<tr><td>Type:</td><td>defect</td></tr>
+<tr><td>Status:</td><td>assigned</td></tr>
+<tr><td>Priority:</td><td>lowest</td></tr>
+<tr><td>Milestone:</td><td>0.9</td></tr>
+<tr><td>Component:</td><td>report system</td></tr>
+<tr><td>Severity:</td><td>major</td></tr>
+<tr><td>Resolution:</td><td> </td></tr>
+<tr><td>Keywords:</td><td> </td></tr>
+</table>
+--------------------------------------------------------------------------<br />
+Changes:<br />
+<br />
+&nbsp;&nbsp;* component: &nbsp;changeset view =&gt; search system<br />
+&nbsp;&nbsp;* priority: &nbsp;low =&gt; highest<br />
+&nbsp;&nbsp;* owner: &nbsp;jonas =&gt; anonymous<br />
+&nbsp;&nbsp;* cc: &nbsp;daniel@example.com =&gt;<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;daniel@example.com, jonas@example.com<br />
+&nbsp;&nbsp;* status: &nbsp;new =&gt; assigned<br />
+<br />
+Comment:<br />
+I'm interested too!<br />
+<br />
+--<br />
+Ticket URL: &lt;http://example.com/trac/ticket/42&gt;<br />
+My Project &lt;http://myproj.example.com/&gt;<br />
+}}}
+}}}
+**Important**: Only those ticket fields that are listed in `sel` are part of the HTML mail. If you have defined custom ticket fields which are to be part of the mail, then they have to be added to `sel`. Example:
+{{{
+   sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2']
+}}}
+However, the solution is still a workaround to an automatically HTML-formatted e-mail.
+== Using GMail as the SMTP relay host
+Use the following configuration snippet:
+{{{#!ini
+[notification]
+smtp_enabled = true
+use_tls = true
+mime_encoding = base64
+smtp_server = smtp.gmail.com
+smtp_port = 587
+smtp_user = user
+smtp_password = password
+}}}
+where ''user'' and ''password'' match an existing GMail account, ie the ones you use to log in on [http://gmail.com].
+Alternatively, you can use `smtp_port = 25`.[[br]]
+You should not use `smtp_port = 465`. Doing so may deadlock your ticket submission. Port 465 is reserved for the SMTPS protocol, which is not supported by Trac. See [trac:comment:2:ticket:7107 #7107] for details.
+== Troubleshooting
+If you cannot get the notification working, first make sure the log is activated and have a look at the log to find if an error message has been logged. See TracLogging for help about the log feature.
+Notification errors are not reported through the web interface, so the user who submits a change or a new ticket never gets notified about a notification failure. The Trac administrator needs to look at the log to find the error trace.
+=== ''Permission denied'' error
+Typical error message:
+{{{#!sh
+  ...
+  File ".../smtplib.py", line 303, in connect
+    raise socket.error, msg
+  error: (13, 'Permission denied')
+}}}
+This error usually comes from a security settings on the server: many Linux distributions do not allow the web server (Apache, ...) to post email messages to the local SMTP server.
+Many users get confused when their manual attempts to contact the SMTP server succeed:
+{{{#!sh
+telnet localhost 25
+}}}
+This is because a regular user may connect to the SMTP server, but the web server cannot:
+{{{#!sh
+sudo -u www-data telnet localhost 25
+}}}
+In such a case, you need to configure your server so that the web server is authorized to post to the SMTP server. The actual settings depend on your Linux distribution and current security policy. You may find help in the Trac [trac:MailingList MailingList] archive.
+Relevant ML threads:
+ * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518
+For SELinux in Fedora 10:
+{{{#!sh
+$ setsebool -P httpd_can_sendmail 1
+}}}
+=== ''Suspected spam'' error
+Some SMTP servers may reject the notification email sent by Trac.
+The default Trac configuration uses Base64 encoding to send emails to the recipients. The whole body of the email is encoded, which sometimes trigger ''false positive'' spam detection on sensitive email servers. In such an event, change the default encoding to "quoted-printable" using the `mime_encoding` option.
+Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, stick with the Base64 encoding.
+----
+See also: TracTickets, TracIni, TracGuide, [trac:TracDev/NotificationApi]

wiki/pages/TracPermissions

-                      r40534
+                      r40542
+= Trac Permissions
+[[TracGuideToc]]
+Trac uses a simple, case sensitive, permission system to control what users can and can't access.
+Permission privileges are managed using the [TracAdmin trac-admin] tool or the ''General / Permissions'' panel in the ''Admin'' tab of the web interface.
+In addition to the default permission policy described in this page, it is possible to activate additional permission policies by enabling plugins and listing them in the `[trac] permission_policies` configuration entry in the TracIni. See TracFineGrainedPermissions for more details.
+Non-authenticated users accessing the system are assigned the name "anonymous". Assign permissions to the "anonymous" user to set privileges for anonymous/guest users. The parts of Trac that a user does not have the privileges for will not be displayed in the navigation.
+In addition to these privileges, users can be granted additional individual rights in effect when authenticated and logged into the system. All logged in users belong to the virtual group "authenticated", which inherits permissions from "anonymous".
+== Graphical Admin Tab
+To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_GRANT`, `PERMISSION_REVOKE`. The permissions can be granted using the `trac-admin` command (more on `trac-admin` below):
+{{{
+  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
+}}}
+Then, the user `bob` will be able to see the Admin tab, and can then access the permissions menu. This menu will allow you to perform all the following actions, but from the browser without requiring root access to the server (just the correct permissions for your user account). '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.'''
+. [[Image(htdocs:../common/guide/admin.png)]]
+. [[Image(htdocs:../common/guide/admin-permissions.png)]]
+. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]]
+An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [http://trac-hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user.
+From the graphical admin tab, users with `PERMISSION_GRANT` will only be allowed to grant permissions that they possess, and users with `PERMISSION_REVOKE` will only be allowed to revoke permissions that they possess. For example, a user cannot grant `MILESTONE_ADMIN` unless they have `PERMISSION_GRANT` and `MILESTONE_ADMIN`, and they cannot revoke `MILESTONE_ADMIN` unless they have `PERMISSION_REVOKE` and `MILESTONE_ADMIN`. `PERMISSION_ADMIN` just grants the user both `PERMISSION_GRANT` and `PERMISSION_REVOKE`, and users with `TRAC_ADMIN` can grant or revoke any permission.
+== Available Privileges
+To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system: it will allow you to perform any operation.
+Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''):
+=== Repository Browser
+|| `BROWSER_VIEW` || View directory listings in the [wiki:TracBrowser repository browser] ||
+|| `LOG_VIEW` || View revision logs of files and directories in the [wiki:TracBrowser repository browser] ||
+|| `FILE_VIEW` || View files in the [wiki:TracBrowser repository browser] ||
+|| `CHANGESET_VIEW` || View [wiki:TracChangeset repository check-ins] ||
+=== Ticket System
+|| `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] ||
+|| `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
+|| `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
+|| `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description field, add/remove other users from cc field when logged in, and set email to pref ||
+|| `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets]. Tickets can be assigned to users through a [TracTickets#Assign-toasDrop-DownList drop-down list] when the list of possible owners has been restricted. ||
+|| `TICKET_EDIT_CC` || Full modify cc field ||
+|| `TICKET_EDIT_DESCRIPTION` || Modify description field ||
+|| `TICKET_EDIT_COMMENT` || Modify another user's comments. Any user can modify their own comments by default. ||
+|| `TICKET_BATCH_MODIFY` || [wiki:TracBatchModify Batch modify] tickets ||
+|| `TICKET_ADMIN` || All `TICKET_*` permissions, deletion of ticket attachments and modification of the reporter field, which grants ability to create a ticket on behalf of another user (it will appear that another user created the ticket). It also allows managing ticket properties through the web administration module. ||
+Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.
+=== Roadmap
+|| `MILESTONE_VIEW` || View milestones and assign tickets to milestones. ||
+|| `MILESTONE_CREATE` || Create a new milestone ||
+|| `MILESTONE_MODIFY` || Modify existing milestones ||
+|| `MILESTONE_DELETE` || Delete milestones ||
+|| `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
+|| `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] ||
+|| `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN ||
+=== Reports
+|| `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. ||
+|| `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] ||
+|| `REPORT_CREATE` || Create new [wiki:TracReports reports] ||
+|| `REPORT_MODIFY` || Modify existing [wiki:TracReports reports] ||
+|| `REPORT_DELETE` || Delete [wiki:TracReports reports] ||
+|| `REPORT_ADMIN` || All `REPORT_*` permissions ||
+=== Wiki System
+|| `WIKI_VIEW` || View existing [wiki:TracWiki wiki] pages ||
+|| `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages ||
+|| `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages ||
+|| `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages ||
+|| `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments ||
+|| `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||
+=== Permissions
+|| `PERMISSION_GRANT` || add/grant a permission ||
+|| `PERMISSION_REVOKE` || remove/revoke a permission ||
+|| `PERMISSION_ADMIN` || All `PERMISSION_*` permissions ||
+=== Others
+|| `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page ||
+|| `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
+|| `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||
+|| `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false ||
+== Creating New Privileges
+To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation  on the [wiki:TracIni#extra-permissions-section TracIni] page after enabling the component.
+== Granting Privileges
+You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command:
+{{{
+  $ trac-admin /path/to/projenv permission list
+}}}
+This command will allow the user ''bob'' to delete reports:
+{{{
+  $ trac-admin /path/to/projenv permission add bob REPORT_DELETE
+}}}
+The `permission add` command also accepts multiple privilege names:
+{{{
+  $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE
+}}}
+Or add all privileges:
+{{{
+  $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
+}}}
+== Permission Groups
+There are two built-in groups, "authenticated" and "anonymous".
+Any user who has not logged in is automatically in the "anonymous" group.
+Any user who has logged in is also in the "authenticated" group.
+The "authenticated" group inherits permissions from the "anonymous" group.
+For example, if the "anonymous" group has permission WIKI_MODIFY,
+it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well.
+Custom groups may be defined that inherit permissions from the two built-in groups.
+Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc.
+{{{
+  $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN
+  $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN
+  $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY
+  $ trac-admin /path/to/projenv permission add bob developer
+  $ trac-admin /path/to/projenv permission add john developer
+}}}
+Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use at least one lowercase character in group names, as all-uppercase names are reserved for permissions'''.
+== Adding a New Group and Permissions
+Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group.
+The following will add ''bob'' to the new group called ''beta_testers'' and then will assign WIKI_ADMIN permissions to that group. (Thus, ''bob'' will inherit the WIKI_ADMIN permission)
+{{{
+   $ trac-admin /path/to/projenv permission add bob beta_testers
+   $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN
+}}}
+== Removing Permissions
+Permissions can be removed using the 'remove' command. For example:
+This command will prevent the user ''bob'' from deleting reports:
+{{{
+  $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE
+}}}
+Just like `permission add`, this command accepts multiple privilege names.
+You can also remove all privileges for a specific user:
+{{{
+  $ trac-admin /path/to/projenv permission remove bob '*'
+}}}
+Or one privilege for all users:
+{{{
+  $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN
+}}}
+== Default Permissions
+By default on a new Trac installation, the `anonymous` user will have ''view'' access to everything in Trac, but will not be able to create or modify anything.
+On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.
+'''anonymous'''
+{{{
+ BROWSER_VIEW
+ CHANGESET_VIEW
+ FILE_VIEW
+ LOG_VIEW
+ MILESTONE_VIEW
+ REPORT_SQL_VIEW
+ REPORT_VIEW
+ ROADMAP_VIEW
+ SEARCH_VIEW
+ TICKET_VIEW
+ TIMELINE_VIEW
+ WIKI_VIEW
+}}}
+'''authenticated'''
+{{{
+ TICKET_CREATE
+ TICKET_MODIFY
+ WIKI_CREATE
+ WIKI_MODIFY
+}}}
+----
+See also: TracAdmin, TracGuide and TracFineGrainedPermissions

wiki/pages/TracPlugins

-                      r40534
+                      r40542
+[[PageOutline(2-5,Contents,pullout)]]
+= Trac plugins
+Trac is extensible with [trac:PluginList plugins]. Plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture], with special cases described in the [trac:TracDev/PluginDevelopment plugin development] page.
+== Plugin discovery
+From the user's point of view, a plugin is either a standalone .py file or an .egg package. Trac looks for plugins in Python's `site-packages` directory, the [TracIni#GlobalConfiguration global shared] `plugins` directory and the [TracEnvironment project environment] `plugins` directory. Components defined in globally-installed plugins must be explicitly enabled in the [[TracIni#components-section| [components] ]] section of the `trac.ini` file. Components defined in the `plugins` directory of the project environment are enabled, unless explicitly disabled in the `[components]` section of the `trac.ini` file.
+== Requirements for Trac eggs
+To use egg-based plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version >= 0.6) installed.
+To install `setuptools`, download the bootstrap module [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py] and execute it as follows:
+{{{#!sh
+$ python ez_setup.py
+}}}
+If the `ez_setup.py` script fails to install the setuptools release, you can download it from [pypi:setuptools PyPI] and install it manually.
+Plugins can also consist of a single `.py` file dropped directly into either the project's or the shared `plugins` directory.
+== Installing a Trac plugin
+=== For a single project
+Plugins are typically packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are .zip archives with the file extension `.egg`.
+If you have downloaded a source distribution of a plugin, and want to build the `.egg` file:
+ * Unpack the source. It should provide `setup.py`.
+ * Run:
+ {{{#!sh
+$ python setup.py bdist_egg
+}}}
+You should now have an *.egg file. Examine the output of running Python to find where this was created.
+Once you have the plugin archive, copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg. Then restart the web server. If you are running as a [wiki:TracStandalone "tracd" standalone server], restart tracd, ie kill the process and run again.
+To uninstall a plugin installed this way, remove the egg from the `plugins` directory and restart the web server.
+'''Note''': the Python version that the egg is built with ''must'' match the Python version with which Trac is run. For example, if you are running Trac under Python 2.6, but have upgraded your standalone Python to 2.7, the eggs won't be recognized.
+'''Note''': in a multi-project setup, a pool of Python interpreter instances will be dynamically allocated to projects based on need; since plugins occupy a place in Python's module system, the first version of any given plugin to be loaded will be used for all projects. In other words, you cannot use different versions of a single plugin in two projects of a multi-project setup. It may be safer to install plugins for all projects (see below), and then enable them selectively on a project-by-project basis.
+=== For all projects
+==== With an .egg file
+Some plugins, such as [trac:SpamFilter SpamFilter], are downloadable as an `.egg` file that can be installed with `easy_install` or `pip`:
+{{{#!sh
+$ easy_install TracSpamFilter
+$ pip install TracSpamFilter
+}}}
+If `easy_install` is not on your system, see the Requirements section above to install it. Windows users will need to add the `Scripts` directory of their Python installation (for example, `C:\Python27\Scripts`) to their `PATH` environment variable, or use the full path to `easy_install` (for example, `C:\Python27\Scripts\easy_install.py`). See [http://peak.telecommunity.com/DevCenter/EasyInstall#windows-notes easy_install Windows notes] for more information.
+`pip` is included in Python 2.7.9. In earlier versions of Python it can be installed through the package manager of your OS (e.g. `apt-get install python-pip`) or using the [https://pip.pypa.io/en/latest/installing.html#install-pip get_pip.py].
+If Trac reports permission errors after installing a zipped egg, and you would rather not bother providing an egg cache directory writable by the web server, you can get around it by simply unzipping the egg. Just pass `--always-unzip` to `easy_install`:
+{{{#!sh
+$ easy_install --always-unzip TracSpamFilter-0.4.1_r10106-py2.6.egg
+}}}
+You should end up with a directory having the same name as the zipped egg, complete with `.egg` extension, and containing its uncompressed contents.
+Trac also searches for plugins installed in the shared plugins directory, see TracIni#GlobalConfiguration. This is a convenient way to share the installation of plugins across several, but not all, environments.
+==== From source
+`easy_install` makes installing from source a snap. Just give it the URL to either a Subversion repository or a tarball/zip of the source:
+{{{#!sh
+$ easy_install http://svn.edgewall.com/repos/trac/plugins/0.12/spam-filter-captcha
+}}}
+==== Enabling the plugin
+Unlike plugins installed per environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This also applies to plugins installed in the shared plugins directory, ie the path specified in the `[inherit] plugins_dir` configuration option.
+This is done in the `[components]` section of the configuration file `trac.ini`. For example:
+{{{#!ini
+[components]
+tracspamfilter.* = enabled
+}}}
+The name of the option is the Python package of the plugin. This should be specified in the documentation of the plugin, but can also be easily discovered by looking at the source: look for a top-level directory that contains a file named `__init__.py`.
+After installing the plugin, you must restart your web server.
+==== Uninstalling
+Neither `easy_install` nor `python setup.py` have an uninstall feature. However, it is usually trivial to remove a globally installed egg and reference:
+. Do `easy_install -m [plugin name]` to remove references from `$PYTHONLIB/site-packages/easy-install.pth` when the plugin installed by setuptools.
+. Delete executables from `/usr/bin`, `/usr/local/bin`, or `C:\\Python*\Scripts`. To find what executables are involved, refer to the `[console-script]` section of `setup.py`.
+. Delete the .egg file or folder from where it's installed, usually inside `$PYTHONLIB/site-packages/`.
+. Restart the web server.
+If you are uncertain about the location of the egg file, you can try to locate it by replacing `myplugin` with whatever namespace the plugin uses (as used when enabling the plugin):
+{{{#!pycon
+>>> import myplugin
+>>> print myplugin.__file__
+/opt/local/python24/lib/site-packages/myplugin-0.4.2-py2.4.egg/myplugin/__init__.pyc
+}}}
+== Setting up the plugin cache
+Some plugins will need to be extracted by the Python egg's runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory in which they are extracted defaults to `.python-eggs` in the home directory of the current user, which may or may not be a problem. You can, however, override the default location using the `PYTHON_EGG_CACHE` environment variable.
+To do this from the Apache configuration, use the `SetEnv` directive:
+{{{#!apache
+SetEnv PYTHON_EGG_CACHE /path/to/dir
+}}}
+This works whether you're using the [wiki:TracCgi CGI] or the [wiki:TracModPython mod_python] front-end. Put this directive next to where you set the path to the [wiki:TracEnvironment Trac environment], ie in the same `<Location>` block.
+For example for CGI:
+{{{#!apache
+ <Location /trac>
+   SetEnv TRAC_ENV /path/to/projenv
+   SetEnv PYTHON_EGG_CACHE /path/to/dir
+ </Location>
+}}}
+Or for mod_python:
+{{{#!apache
+ <Location /trac>
+   SetHandler mod_python
+   ...
+   SetEnv PYTHON_EGG_CACHE /path/to/dir
+ </Location>
+}}}
+'''Note''': !SetEnv requires the `mod_env` module, which needs to be activated for Apache. In this case the !SetEnv directive can also be used in the `mod_python` Location block.
+For [wiki:TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables.
+'''Note''': if you already use -initial-env to set the project directory for either a single project or parent, you will need to add an additional -initial-env directive to the !FastCgiConfig directive:
+{{{#!apache
+FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac -initial-env PYTHON_EGG_CACHE=/var/lib/trac/plugin-cache
+}}}
+=== About hook scripts
+If you have set up some Subversion hook scripts that call the Trac engine, such as the post-commit hook script provided in the `/contrib` directory, make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts as well.
+== Web-based plugin administration
+The [trac:WebAdmin] interface offers limited support for plugin configuration through the web to users with `TRAC_ADMIN` permission:
+* en/disabling installed plugins
+* installing plugins by uploading them as eggs
+If you wish to disable the second function for security reasons, add the following to your `trac.ini` file:
+{{{#!ini
+[components]
+trac.admin.web_ui.PluginAdminPanel = disabled
+}}}
+This disables the whole panel, so the first function will no longer be available either.
+== Troubleshooting
+=== Is setuptools properly installed?
+Try this from the command line:
+{{{#!sh
+$ python -c "import pkg_resources"
+}}}
+If you get '''no output''', setuptools '''is''' installed. Otherwise, you'll need to install it before plugins will work in Trac.
+=== Did you get the correct version of the Python egg?
+Python eggs have the Python version encoded in their filename. For example, `MyPlugin-1.0-py2.5.egg` is an egg for Python 2.5, and will '''not''' be loaded if you're running a different Python version (such as 2.4 or 2.6).
+Also, verify that the egg file you downloaded is indeed a .zip archive. If you downloaded it from a Trac site, chances are you downloaded the HTML preview page instead.
+=== Is the plugin enabled?
+If you install a plugin globally, ie ''not'' inside the `plugins` directory of the Trac project environment, you must explicitly enable it in [TracIni trac.ini]. Make sure that:
+ * you actually added the necessary line(s) to the `[components]` section.
+ * the package/module names are correct and do not contain typos.
+ * the value is "enabled", not "enable" or "Enable".
+ * the section name is "components", not "component".
+=== Check the permissions on the .egg file
+Trac must be able to read the .egg file.
+=== Check the log files
+Enable [wiki:TracLogging logging] and set the log level to `DEBUG`, then watch the log file for messages about loading plugins.
+=== Verify you have the proper permissions
+Some plugins require you have special permissions in order to use them. [trac:WebAdmin WebAdmin], for example, requires the user to have `TRAC_ADMIN` permissions for it to show up on the navigation bar.
+=== Is the wrong version of the plugin loading?
+If you put your plugins inside plugins directories, and certainly if you have more than one project, you need to make sure that the correct version of the plugin is loading. Here are some basic rules:
+ * Only one version of the plugin can be loaded for each running Trac server, ie each Python process. The Python namespaces and module list will be shared, and it cannot handle duplicates. Whether a plugin is `enabled` or `disabled` makes no difference.
+ * A globally installed plugin (typically `setup.py install`) will override any version in the global or project plugins directories. A plugin from the global plugins directory will be located ''before'' any project plugins directory.
+ * If your Trac server hosts more than one project (as with `TRAC_ENV_PARENT_DIR` setups), having two versions of a plugin in two different projects will give unpredicatable results. Only one of them will load, and the one loaded will be shared by both projects. Trac will load the first plugin found, usually from the project that receives the first request.
+ * Having more than one version listed inside Python site-packages is fine, ie installed with `setup.py install`, because setuptools will make sure you get the version installed most recently. However, don't store more than one version inside a global or project plugins directory: neither the version number nor the installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins.
+=== If all of the above failed
+Okay, so the logs don't mention plugins, the egg is readable, the Python version is correct, ''and'' the egg has been installed globally (and is enabled in trac.ini)... and it ''still'' doesn't work or give any error messages or any other indication as to why. Hop on the [trac:IrcChannel IrcChannel] and ask away!
+----
+See also TracGuide, [trac:PluginList plugin list], [trac:TracDev/ComponentArchitecture component architecture].

wiki/pages/TracQuery

-                      r40534
+                      r40542
+= Trac Ticket Queries
+[[TracGuideToc]]
+In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', which can be used to display tickets that meet specified criteria.
+To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.
+== Filters
+When you first go to the query page, the default filter will display tickets relevant to you:
+ * If logged in then all open tickets, it will display open tickets assigned to you.
+ * If not logged in but you have specified a name or email address in the preferences, then it will display all open tickets where your email (or name if email not defined) is in the CC list.
+ * If not logged in and no name/email is defined in the preferences, then all open issues are displayed.
+Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right.  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''Or'' on the criteria.
+You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.
+After you have edited your filters, click the ''Update'' button to refresh your results.
+== Navigating Tickets
+Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page.
+You can safely edit any of the tickets and continue to navigate through the results using the ''!Next/Previous/Back to Query'' links after saving your results. When you return to the query ''any tickets which were edited'' will be displayed with italicized text. If one of the tickets was edited such that [[html(<span style="color: grey">it no longer matches the query criteria </span>)]], the text will also be greyed. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold.
+The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
+== Saving Queries
+Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have ''Updated'' the view and then click the ''Save query'' button displayed beneath the results.
+You can also save references to queries in Wiki content, as described below.
+'''Note:''' one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click ''Save query''. This will build the query string for you. All you need to do is remove the extra line breaks.
+'''Note:''' you must have the '''REPORT_CREATE''' permission in order to save queries to the list of default reports. The ''Save query'' button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.
+=== Using TracLinks
+You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.
+{{{
+[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
+}}}
+Which is displayed as:
+  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
+This uses a very simple query language to specify the criteria, see [wiki:TracQuery#QueryLanguage Query Language].
+Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
+{{{
+[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
+}}}
+Which is displayed as:
+  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
+=== Customizing the ''table'' format
+You can also customize the columns displayed in the table format (''format=table'') by using ''col=<field>''. You can specify multiple fields and what order they are displayed in by placing pipes (`|`) between the columns:
+{{{
+[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
+}}}
+This is displayed as:
+[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
+==== Full rows
+In ''table'' format you can also have full rows by using ''rows=<field>'':
+{{{
+[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
+}}}
+This is displayed as:
+[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
+== Query Language
+`query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (`&`). Each filter consists of the ticket field name, an operator and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`).
+The available operators are:
+|| '''`=`''' || the field content exactly matches one of the values ||
+|| '''`~=`''' || the field content contains one or more of the values ||
+|| '''`^=`''' || the field content starts with one of the values ||
+|| '''`$=`''' || the field content ends with one of the values ||
+All of these operators can also be negated:
+|| '''`!=`''' || the field content matches none of the values ||
+|| '''`!~=`''' || the field content does not contain any of the values ||
+|| '''`!^=`''' || the field content does not start with any of the values ||
+|| '''`!$=`''' || the field content does not end with any of the values ||
+The date fields `created` and `modified` can be constrained by using the `=` operator and specifying a value containing two dates separated by two dots (`..`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.
+|| '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
+|| '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||
+|| '''`modified=1weekago..`''' || query tickets that have been modified in the last week ||
+|| '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days ||
+----
+See also: TracTickets, TracReports, TracGuide, TicketQuery

wiki/pages/TracReports

-                      r40534
+                      r40542
+= Trac Reports =
+[[TracGuideToc]]
+The Trac reports module provides a simple, yet powerful reporting facility
+to present information about tickets in the Trac database.
+Rather than have its own report definition format, TracReports relies on standard SQL
+`SELECT` statements for custom report definition.
+  '''Note:''' ''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''
+  ''You can already completely replace the reports module by the query module simply by disabling the former in [wiki:TracIni trac.ini]:''
+  {{{
+  [components]
+  trac.ticket.report.* = disabled
+  }}}
+  ''This will make the query module the default handler for the “View Tickets” navigation item. We encourage you to try this configuration and report back what kind of features of reports you are missing, if any.''
+A report consists of these basic parts:
+ * '''ID''' — Unique (sequential) identifier
+ * '''Title''' — Descriptive title
+ * '''Description''' — A brief description of the report, in WikiFormatting text.
+ * '''Report Body''' — List of results from report query, formatted according to the methods described below.
+ * '''Footer''' — Links to alternative download formats for this report.
+== Changing Sort Order ==
+Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.
+If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.
+== Changing Report Numbering ==
+There may be instances where you need to change the ID of the report, perhaps to organize the reports better. At present this requires changes to the trac database. The ''report'' table has the following schema:
+ * id integer PRIMARY KEY
+ * author text
+ * title text
+ * query text
+ * description text
+Changing the ID changes the shown order and number in the ''Available Reports'' list and the report's perma-link. This is done by running something like:
+{{{
+update report set id=5 where id=3;
+}}}
+Keep in mind that the integrity has to be maintained (i.e., ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace).
+You may also need to update or remove the report number stored in the report or query.
+== Navigating Tickets ==
+Clicking on one of the report results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Report'' link to return to the report page.
+You can safely edit any of the tickets and continue to navigate through the results using the ''!Next/Previous/Back to Report'' links after saving your results, but when you return to the report, there will be no hint about what has changed, as would happen if you were navigating a list of tickets obtained from a query (see TracQuery#NavigatingTickets).
+== Alternative Download Formats ==
+Aside from the default HTML view, reports can also be exported in a number of alternative formats.
+At the bottom of the report page, you will find a list of available data formats. Click the desired link to
+download the alternative report format.
+=== Comma-delimited - CSV (Comma Separated Values) ===
+Export the report as plain text, each row on its own line, columns separated by a single comma (',').
+'''Note:''' The output is fully escaped so carriage returns, line feeds, and commas will be preserved in the output.
+=== Tab-delimited ===
+Like above, but uses tabs (\t) instead of comma.
+=== RSS - XML Content Syndication ===
+All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.
+----
+== Creating Custom Reports ==
+''Creating a custom report requires a comfortable knowledge of SQL.''
+'''Note that you need to set up [TracPermissions#Reports permissions] in order to see the buttons for adding or editing reports.'''
+A report is basically a single named SQL query, executed and presented by
+Trac.  Reports can be viewed and created from a custom SQL expression directly
+in the web interface.
+Typically, a report consists of a SELECT-expression from the 'ticket' table,
+using the available columns and sorting the way you want it.
+== Ticket columns ==
+The ''ticket'' table has the following columns:
+ * id
+ * type
+ * time
+ * changetime
+ * component
+ * severity
+ * priority
+ * owner
+ * reporter
+ * cc
+ * version
+ * milestone
+ * status
+ * resolution
+ * summary
+ * description
+ * keywords
+See TracTickets for a detailed description of the column fields.
+Example: '''All active tickets, sorted by priority and time'''
+{{{
+SELECT id AS ticket, status, severity, priority, owner,
+       time AS created, summary FROM ticket
+  WHERE status IN ('new', 'assigned', 'reopened')
+  ORDER BY priority, time
+}}}
+Dynamic variables can also be used in the report title and description (since 1.1.1).
+== Advanced Reports: Dynamic Variables ==
+For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements.
+In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.
+=== Using Variables in a Query ===
+The syntax for dynamic variables is simple, any upper case word beginning with '$' is considered a variable.
+Example:
+{{{
+SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY
+}}}
+To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$'.
+Example:
+{{{
+ http://trac.edgewall.org/reports/14?PRIORITY=high
+}}}
+To use multiple variables, separate them with an '&'.
+Example:
+{{{
+ http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical
+}}}
+=== !Special/Constant Variables ===
+There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports.
+ * $USER — Username of logged in user.
+Example (''List all tickets assigned to me''):
+{{{
+SELECT id AS ticket,summary FROM ticket WHERE owner=$USER
+}}}
+== Advanced Reports: Custom Formatting ==
+Trac is also capable of more advanced reports, including custom layouts,
+result grouping and user-defined CSS styles. To create such reports, we'll use
+specialized SQL statements to control the output of the Trac report engine.
+=== Special Columns ===
+To format reports, TracReports looks for 'magic' column names in the query
+result. These 'magic' names are processed and affect the layout and style of the
+final report.
+=== Automatically formatted columns ===
+ * '''ticket''' — Ticket ID number. Becomes a hyperlink to that ticket.
+ * '''id''' — same as '''ticket''' above when '''realm''' is not set
+ * '''realm''' — together with '''id''', can be used to create links to other resources than tickets (e.g. a realm of ''wiki'' and an ''id'' to a page name will create a link to that wiki page)
+   - for some kind of resources, it may be necessary to specify their ''parent'' resources (e.g. for ''changeset'', which ''repos'') and this can be achieved using the '''parent_realm''' and '''parent_id''' columns
+ * '''created, modified, date, time''' — Format cell as a date and/or time.
+ * '''description''' — Ticket description field, parsed through the wiki engine.
+'''Example:'''
+{{{
+SELECT id AS ticket, created, status, summary FROM ticket
+}}}
+Those columns can also be defined but marked as hidden, see [#column-syntax below].
+See trac:wiki/CookBook/Configuration/Reports for some example of creating reports for realms other than ''ticket''.
+=== Custom formatting columns ===
+Columns whose names begin and end with 2 underscores (Example: '''`__color__`''') are
+assumed to be ''formatting hints'', affecting the appearance of the row.
+ * '''`__group__`''' — Group results based on values in this column. Each group will have its own header and table.
+ * '''`__grouplink__`''' — Make the header of each group a link to the specified URL. The URL is taken from the first row of each group.
+ * '''`__color__`''' — Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority.
+{{{
+#!html
+<div style="margin-left:7.5em">Defaults:
+<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fdc; border-color: #e88; color: #a22">Color 1</span>
+<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #ffb; border-color: #eea; color: #880">Color 2</span>
+<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fbfbfb; border-color: #ddd; color: #444">Color 3</span>
+<span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7ffff; border-color: #cee; color: #099">Color 4</span>
+<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #e7eeff; border-color: #cde; color: #469">Color 5</span>
+</div>
+}}}
+ * '''`__style__`''' — A custom CSS style expression to use on the `<tr>` element of the current row.
+ * '''`__class__`''' — Zero or more space-separated CSS class names to be set on the `<tr>` element of the current row. These classes are added to the class name derived from `__color__` and the odd / even indicator.
+'''Example:''' ''List active tickets, grouped by milestone, group header linked to milestone page, colored by priority''
+{{{
+SELECT p.value AS __color__,
+     t.milestone AS __group__,
+     '../milestone/' || t.milestone AS __grouplink__,
+     (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__,
+       t.id AS ticket, summary
+  FROM ticket t,enum p
+  WHERE t.status IN ('new', 'assigned', 'reopened')
+    AND p.name=t.priority AND p.type='priority'
+  ORDER BY t.milestone, p.value, t.severity, t.time
+}}}
+'''Note:''' A table join is used to match ''ticket'' priorities with their
+numeric representation from the ''enum'' table.
+=== Changing layout of report rows === #column-syntax
+By default, all columns on each row are display on a single row in the HTML
+report, possibly formatted according to the descriptions above. However, it's
+also possible to create multi-line report entries.
+ * '''`column_`''' — ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be continued on a second line.
+ * '''`_column_`''' — ''Full row''. By adding an underscore ('_') both at the beginning and the end of a column name, the data will be shown on a separate row.
+ * '''`_column`''' — ''Hide data''. Prepending an underscore ('_') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML).
+   This can be used to hide any kind of column, even important ones required for identifying the resource, e.g. `id as _id` will hide the '''Id''' column but the link to the ticket will be present.
+'''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''
+{{{
+SELECT p.value AS __color__,
+       t.milestone AS __group__,
+       (CASE owner
+          WHEN 'daniel' THEN 'font-weight: bold; background: red;'
+          ELSE '' END) AS __style__,
+       t.id AS ticket, summary AS summary_,             -- ## Break line here
+       component,version, severity, milestone, status, owner,
+       time AS created, changetime AS modified,         -- ## Dates are formatted
+       description AS _description_,                    -- ## Uses a full row
+       changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
+  FROM ticket t,enum p
+  WHERE t.status IN ('new', 'assigned', 'reopened')
+    AND p.name=t.priority AND p.type='priority'
+  ORDER BY t.milestone, p.value, t.severity, t.time
+}}}
+=== Reporting on custom fields ===
+If you have added custom fields to your tickets (see TracTicketsCustomFields), you can write a SQL query to cover them. You'll need to make a join on the ticket_custom table, but this isn't especially easy.
+If you have tickets in the database ''before'' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL's "LEFT OUTER JOIN" clauses. See [trac:TracIniReportCustomFieldSample TracIniReportCustomFieldSample] for some examples.
+=== A note about SQL rewriting #rewriting
+Beyond the relatively trivial replacement of dynamic variables, the SQL query is also altered in order to support two features of the reports:
+. [#sort-order changing the sort order]
+. pagination support (limitation of the number of result rows displayed on each page)
+In order to support the first feature, the sort column is inserted in the `ORDER BY` clause in the first position or in the second position if a `__group__` column is specified (an `ORDER BY` clause is created if needed). In order to support pagination, a `LIMIT ... OFFSET ...` clause is appended.
+The query might be too complex for the automatic rewrite to work correctly, resulting in an erroneous query. In this case you still have the possibility to control exactly how the rewrite is done by manually inserting the following tokens:
+ - `@SORT_COLUMN@`, the place where the name of the selected sort column will be inserted,
+ - `@LIMIT_OFFSET@`, the place where the pagination support clause will be added
+Note that if you write them after an SQL comment, `--`, you'll effectively disable rewriting if this is what you want!
+Let's take an example, consider the following SQL query:
+{{{
+-- ## 4: Assigned, Active Tickets by Owner ## --
+--
+-- List assigned tickets, group by ticket owner, sorted by priority.
+--
+SELECT p.value AS __color__,
+   owner AS __group__,
+   id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
+   changetime AS _changetime, description AS _description,
+   reporter AS _reporter
+  FROM ticket t,enum p
+  WHERE status = 'assigned'
+AND p.name=t.priority AND p.type='priority'
+  ORDER BY __group__, p.value, severity, time
+}}}
+The automatic rewrite will be the following (4 rows per page, page 2, sorted by `component`):
+{{{
+SELECT p.value AS __color__,
+   owner AS __group__,
+   id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
+   changetime AS _changetime, description AS _description,
+   reporter AS _reporter
+  FROM ticket t,enum p
+  WHERE status = 'assigned'
+AND p.name=t.priority AND p.type='priority'
+  ORDER BY __group__ ASC, `component` ASC,  __group__, p.value, severity, time
+ LIMIT 4 OFFSET 4
+}}}
+The equivalent SQL query with the rewrite tokens would have been:
+{{{
+SELECT p.value AS __color__,
+   owner AS __group__,
+   id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
+   changetime AS _changetime, description AS _description,
+   reporter AS _reporter
+  FROM ticket t,enum p
+  WHERE status = 'assigned'
+AND p.name=t.priority AND p.type='priority'
+  ORDER BY __group__, @SORT_COLUMN@, p.value, severity, time
+@LIMIT_OFFSET@
+}}}
+If you want to always sort first by priority and only then by the user selected sort column, simply use the following `ORDER BY` clause:
+{{{
+  ORDER BY __group__, p.value, @SORT_COLUMN@, severity, time
+}}}
+----
+See also: TracTickets, TracQuery, TracGuide, [http://www.sqlite.org/lang_expr.html Query Language Understood by SQLite]

wiki/pages/TracRepositoryAdmin

-                      r40534
+                      r40542
+= Repository Administration
+[[PageOutline(2-3)]]
+== Quick start #QuickStart
+ * Enable the repository connector(s) for the version control system(s) that you will use.
+ * Add repositories through the //Repositories// admin panel, with `trac-admin` or in the `[repositories]` section of [wiki:TracIni#repositories-section trac.ini].
+ * Set up a call to `trac-admin $ENV changeset added $REPO $REV` in the post-commit hook of each repository. Additionally, add a call to `trac-admin $ENV changeset modified $REPO $REV` in the post-revprop-change hook of repositories allowing revision property changes.
+ * Make sure the user under which your hooks are run has write access to the Trac environment, or use a tool like `sudo` to temporarily elevate privileges.
+== Enabling the components
+Support for version control systems is provided by optional components distributed with Trac, which are disabled by default //(since 1.0)//. Subversion and Git must be explicitly enabled if you wish to use them.
+The version control systems can be enabled by adding the following to the `[components]` section of your [TracIni#components-section trac.ini], or enabling the components in the //Plugins// admin panel.
+{{{#!ini
+tracopt.versioncontrol.svn.* = enabled
+}}}
+{{{#!ini
+tracopt.versioncontrol.git.* = enabled
+}}}
+== Specifying repositories #Repositories
+Trac supports multiple repositories per environment, and the repositories may be for different version control system types. Each repository must be defined in a repository configuration provider, the two supported by default are the [#ReposDatabase database store] and the [#ReposTracIni trac.ini configuration file]. A repository should not be defined in multiple configuration providers.
+It is possible to define aliases of repositories, that act as "pointers" to real repositories. This can be useful when renaming a repository, to avoid breaking links to the old name.
+A number of attributes can be associated with each repository. The attributes define the repository's location, type, name and how it is displayed in the source browser. The following attributes are supported:
+||='''Attribute''' =||='''Description''' =||
+||`alias` ||\
+||A repository having an `alias` attribute is an alias to a real repository. All TracLinks referencing the alias resolve to the aliased repository. Note that multiple indirection is not supported, so an alias must always point to a real repository. The `alias` and `dir` attributes are mutually exclusive. ||
+||`description` ||\
+||The text specified in the `description` attribute is displayed below the top-level entry for the repository in the source browser. It supports WikiFormatting. ||
+||`dir` ||\
+||The `dir` attribute specifies the location of the repository in the filesystem. It corresponds to the value previously specified in the option `[trac] repository_dir`. The `alias` and `dir` attributes are mutually exclusive. ||
+||`hidden` ||When set to `true`, the repository is hidden from the repository index page in the source browser. Browsing the repository is still possible, and links referencing the repository remain valid. ||
+||`sync_per_request`||When set to `true` the repository will be synced on every request. This is not recommended, instead a post-commit hook should be configured to provide [#ExplicitSync explicit synchronization] and `sync_per_request` should be set to `false`.||
+||`type` ||The `type` attribute sets the type of version control system used by the repository. Trac supports Subversion and Git out-of-the-box, and plugins add support for many other systems. If `type` is not specified, it defaults to the value of the `[trac] repository_type` option. ||
+||`url` ||The `url` attribute specifies the root URL to be used for checking out from the repository. When specified, a "Repository URL" link is added to the context navigation links in the source browser, that can be copied into the tool used for creating the working copy. ||
+A repository `name` and one of `alias` or `dir` attributes are mandatory. All others are optional.
+For some version control systems, it is possible to specify not only the path to the repository in the `dir` attribute, but also a ''scope'' within the repository. Trac will then only show information related to the files and changesets below that scope. The Subversion backend for Trac supports this. For other types, check the corresponding plugin's documentation.
+After adding a repository, the cache for that repository must be re-synchronized once with the `trac-admin $ENV repository resync` command.
+ `repository resync <repos>`::
+   Re-synchronize Trac with a repository.
+=== In `trac.ini` #ReposTracIni
+Repositories and repository attributes can be specified in the `[repositories]` section of [wiki:TracIni#repositories-section trac.ini]. Every attribute consists of a key structured as `{name}.{attribute}` and the corresponding value separated with an equal sign (`=`). The name of the default repository is empty.
+The main advantage of specifying repositories in `trac.ini` is that they can be inherited from a global configuration (see the [wiki:TracIni#GlobalConfiguration global configuration] section of TracIni). One drawback is that, due to limitations in the `ConfigParser` class used to parse `trac.ini`, the repository name is always all-lowercase.
+The following example defines two Subversion repositories named `project` and `lib`, and an alias to `project` as the default repository. This is a typical use case where a Trac environment previously had a single repository (the `project` repository), and was converted to multiple repositories. The alias ensures that links predating the change continue to resolve to the `project` repository.
+{{{#!ini
+[repositories]
+project.dir = /var/repos/project
+project.description = This is the ''main'' project repository.
+project.type = svn
+project.url = http://example.com/svn/project
+project.hidden = true
+lib.dir = /var/repos/lib
+lib.description = This is the secondary library code.
+lib.type = svn
+lib.url = http://example.com/svn/lib
+.alias = project
+}}}
+Note that `name.alias = target` makes `name` an alias for the `target` repo, not the other way around.
+=== In the database #ReposDatabase
+Repositories can also be specified in the database, using either the "Repositories" admin panel under "Version Control", or the `trac-admin $ENV repository` commands.
+The admin panel shows the list of all repositories defined in the Trac environment. It allows adding repositories and aliases, editing repository attributes and removing repositories. Note that repositories defined in `trac.ini` are displayed but cannot be edited.
+The following [wiki:TracAdmin trac-admin] commands can be used to perform repository operations from the command line.
+ `repository add <repos> <dir> [type]`::
+   Add a repository `<repos>` located at `<dir>`, and optionally specify its type.
+ `repository alias <name> <target>`::
+   Create an alias `<name>` for the repository `<target>`.
+ `repository remove <repos>`::
+   Remove the repository `<repos>`.
+ `repository set <repos> <key> <value>`::
+   Set the attribute `<key>` to `<value>` for the repository `<repos>`.
+Note that the default repository has an empty name, so it will likely need to be quoted when running `trac-admin` from a shell. Alternatively, the name "`(default)`" can be used instead, for example when running `trac-admin` in interactive mode.
+== Repository caching
+The Subversion and Git repository connectors support caching, which improves the performance browsing the repository, viewing logs and viewing changesets. Cached repositories must be [#Synchronization synchronized]; either explicit or implicit synchronization can be used. When searching changesets, only cached repositories are searched.
+Subversion repositories are cached unless the type is `direct-svnfs`. Git repositories are cached when `[git]` [wiki:TracIni#git-section cached_repository] is `true`.
+== Repository synchronization #Synchronization
+Prior to 0.12, Trac synchronized its cache with the repository on every HTTP request. This approach is not very efficient and not practical anymore with multiple repositories. For this reason, explicit synchronization through post-commit hooks was added.
+There is also new functionality in the form of a repository listener extension point ''(IRepositoryChangeListener)'' that is triggered by the post-commit hook when a changeset is added or modified, and can be used by plugins to perform actions on commit.
+=== Mercurial Repositories
+Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:#9485] for more information.
+=== Explicit synchronization #ExplicitSync
+This is the preferred method of repository synchronization. It requires setting the `sync_per_request` attribute to `false`, and adding a call to `trac-admin` in the `post-commit` hook of each repository. Additionally, if a repository allows changing revision metadata, a call to `trac-admin` must be added to the `post-revprop-change` hook as well.
+ `changeset added <repos> <rev> [...]`::
+   Notify Trac that one or more changesets have been added to a repository.
+ `changeset modified <repos> <rev> [...]`::
+   Notify Trac that metadata on one or more changesets in a repository has been modified.
+The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.
+Note that you may have to set the environment variable `PYTHON_EGG_CACHE` to the same value as was used for the web server configuration before calling `trac-admin`, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information.
+==== Subversion
+The following examples are complete post-commit and post-revprop-change scripts for Subversion. They should be edited for the specific environment, marked executable (where applicable) and placed in the `hooks` directory of each repository. On Unix (`post-commit`):
+{{{#!sh
+#!/bin/sh
+export PYTHON_EGG_CACHE="/path/to/dir"
+/usr/bin/trac-admin /path/to/env changeset added "$1" "$2"
+}}}
+Note: Check with `whereis trac-admin`, whether `trac-admin` is really installed under `/usr/bin/` or maybe under `/usr/local/bin/` and adapt the path.
+On Windows (`post-commit.cmd`):
+{{{#!bat
+@C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset added "%1" "%2"
+}}}
+The post-revprop-change hook for Subversion is very similar. On Unix (`post-revprop-change`):
+{{{#!sh
+#!/bin/sh
+export PYTHON_EGG_CACHE="/path/to/dir"
+/usr/bin/trac-admin /path/to/env changeset modified "$1" "$2"
+}}}
+On Windows (`post-revprop-change.cmd`):
+{{{#!bat
+@C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset modified "%1" "%2"
+}}}
+The Unix variants above assume that the user running the Subversion commit has write access to the Trac environment, which is the case in the standard configuration where both the repository and Trac are served by the web server. If you access the repository through another means, for example `svn+ssh://`, you may have to run `trac-admin` with different privileges, for example by using `sudo`.
+Note that calling `trac-admin` in your Subversion hooks can slow down the commit and log editing operations on the client side. You might want to use the [trac:source:trunk/contrib/trac-svn-hook contrib/trac-svn-hook] script which starts `trac-admin` in an asynchronous way. The script also comes with a number of safety checks and usage advices which should make it easier to set up and test your hooks. There's no equivalent `trac-svn-hook.bat` for Windows yet, but the script can be run by Cygwin's bash.
+See the [http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks section about hooks] in the Subversion book for more information. Other repository types will require different hook setups.
+==== Git
+Git hooks can be used in the same way for explicit syncing of Git repositories.  If your git repository is one that gets committed to directly on the machine that hosts trac, add the following to the `hooks/post-commit` file in your git repo (note: this will do nothing if you only update the repo by pushing to it):
+{{{#!sh
+#!/bin/sh
+REV=$(git rev-parse HEAD)
+trac-admin /path/to/env changeset added <repos> $REV
+}}}
+Alternately, if your repository is one that only gets pushed to, add the following to the `hooks/post-receive` file in the repo:
+{{{#!sh
+#!/bin/sh
+tracenv=/path/to/env     # change with your Trac environment's path
+repos=                   # change with your repository's name
+while read oldrev newrev refname; do
+    if [ "$oldrev" = 0000000000000000000000000000000000000000 ]; then
+        git rev-list --reverse "$newrev" --
+    else
+        git rev-list --reverse "$newrev" "^$oldrev" --
+    fi | xargs trac-admin "$tracenv" changeset added "$repos"
+done
+}}}
+The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.
+==== Mercurial
+For Mercurial, add the following entries to the `.hgrc` file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac `plugins` directory, download [trac:source:mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible):
+{{{#!ini
+[hooks]
+; If mercurial-plugin is installed globally
+commit = python:tracext.hg.hooks.add_changesets
+changegroup = python:tracext.hg.hooks.add_changesets
+; If mercurial-plugin is installed in a Trac plugins directory
+commit = python:/path/to/hooks.py:add_changesets
+changegroup = python:/path/to/hooks.py:add_changesets
+[trac]
+env = /path/to/env
+trac-admin = /path/to/trac-admin
+}}}
+=== Per-request synchronization #PerRequestSync
+If the post-commit hooks are not available, the environment can be set up for per-request synchronization. In that case, the `sync_per_request` attribute for each repository in the database and in [wiki:TracIni#trac-section trac.ini] must be set to `false`.
+Note that in this case, the changeset listener extension point is not called, and therefore plugins using it will not work correctly.
+== Automatic changeset references in tickets
+You can automatically add a reference to the changeset as a ticket comment whenever changes are committed to the repository. The description of the commit needs to contain one of the following formulas:
+ * '''`Refs #123`''' - to reference this changeset in `#123` ticket
+ * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed''
+This functionality requires installing a post-commit hook as described in [#ExplicitSync], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the //Plugins// admin panel.
+{{{#!ini
+tracopt.ticket.commit_updater.* = enabled
+}}}
+For more information, see the documentation of the `CommitTicketUpdater` component in the //Plugins// admin panel and the [trac:CommitTicketUpdater] page.
+== Troubleshooting
+=== My trac-post-commit-hook doesn't work anymore #trac-post-commit-hook
+You must now use the optional components from `tracopt.ticket.commit_updater.*`, which you can activate through the Plugins panel in the Administrative part of the web interface, or by directly modifying the [TracIni#components-section "[components]"] section in the trac.ini. Be sure to use [#ExplicitSync explicit synchronization] as explained above.

wiki/pages/TracRevisionLog

-                      r40534
+                      r40542
+= Viewing Revision Logs =
+[[TracGuideToc]]
+When you browse the repository, it is always possible to view the ''Revision Log'' that corresponds to the repository path. This displays a list of the most recent changesets in which the current path or any other path below it has been modified.
+== The Revision Log Form ==
+It is possible to set the revision at which the revision log should start, using the ''View log starting at'' field. An empty value or a value of ''head'' is interpreted as the newest changeset.
+It is also possible to specify the revision at which the log should stop, using the ''Back to'' field. By default it is empty,
+which means the revision log will show the latest 100 revisions.
+Also, there are three modes of operation of the revision log.
+By default, the revision log ''stops on copy'', which means that whenever an ''Add'', ''Copy'' or ''Rename'' operation is detected, no older revision will be shown. That's very convenient when working with branches, as one only sees the history corresponding to what has been done on the branch.
+It is also possible to indicate that one wants to see what happened before a ''Copy'' or ''Rename'' change, by selecting the
+''Follow copies'' mode. This will cross all copies or renames changes.
+Each time the name of the path changes, there will be an additional indentation level. That way, the changes on the different paths are easily grouped together visually.
+It is even possible to go past an ''Add'' change, in order to see if there has been a ''Delete'' change on that path, before
+that ''Add''. This mode corresponds to the mode called ''Show only adds, moves and deletes''. This operation can be quite resource intensive and therefore take some time to be shown on screen.
+Finally, there's also a checkbox ''Show full log messages'', which controls whether the full content of the commit log message
+should be displayed for each change, or only a shortened version of it.
+== The Revision Log Information ==
+For each revision log entry, the following columns are displayed:
+. The first column contains a pair of radio buttons and should be used
+    for selecting the ''old'' and the ''new'' revisions that will be
+    used for [wiki:TracRevisionLog#viewingtheactualchanges viewing the actual changes].
+. A color code (similar to the one used for the
+    [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change.
+    Clicking on this column refreshes the revision log so that it restarts
+    with this change.
+. The '''Revision''' number, displayed as `@xyz`.
+    This is a link to the TracBrowser, using the displayed revision as the base line.
+ Next to it, you can see a little "wheel" icon [[Image(htdocs:../common/changeset.png)]],  which is clickable and leads to the TracChangeset view for that revision.
+. The '''Date''' at which the change was made.
+    The date is displayed as the time elapsed from the date of the revision. The time
+    elapsed is displayed as the number of hours, days, weeks, months, or years.
+. The '''Author''' of the change.
+. The '''Log Message''', which contains either the truncated or full commit
+    log message, depending on the value of the ''Show full log messages''
+    checkbox in the form above.
+== Inspecting Changes Between Revisions ==
+The ''View changes...'' buttons (placed above and below the list of changes, on the left side) will show the set of differences
+corresponding to the aggregated changes starting from the ''old'' revision (first radio-button) to the ''new'' revision (second
+radio-button), in the TracChangeset view.
+Note that the ''old'' revision doesn't need to be actually ''older'' than the ''new'' revision: it simply gives a base
+for the diff. It's therefore entirely possible to easily generate a ''reverse diff'', for reverting what has been done
+in the given range of revisions.
+Finally, if the two revisions are identical, the corresponding changeset will be shown. This has the same effect as clicking on the !ChangeSet number.
+== Alternative Formats ==
+=== The !ChangeLog Text ===
+At the bottom of the page, there's a ''!ChangeLog'' link that will show the range of revisions as currently shown, but as a simple text, matching the usual conventions for !ChangeLog files.
+=== RSS Support ===
+The revision log also provides a RSS feed to monitor the changes. To subscribe to a RSS feed for a file or directory, open its
+revision log in the browser and click the orange 'XML' icon at the bottom of the page. For more information on RSS support in Trac, see TracRss.
+----
+See also: TracBrowser, TracChangeset, TracGuide

wiki/pages/TracRoadmap

-                      r40534
+                      r40542
+= The Trac Roadmap
+[[TracGuideToc]]
+The roadmap provides a view on the [wiki:TracTickets ticket system] that helps planning and managing the future development of a project.
+== The Roadmap View
+A roadmap is a list of future milestones. The roadmap can be filtered to show or hide ''completed milestones'' and ''milestones with no due date''. In the case that both ''show completed milestones'' and ''hide milestones with no due date'' are selected, ''completed'' milestones with no due date will be shown.
+== The Milestone View
+A milestone is a future timeframe in which tickets are expected to be solved. You can add a description to milestones (using WikiFormatting) describing main objectives, for example. In addition, tickets targeted for a milestone are aggregated, and the ratio between active and resolved tickets is displayed as a milestone progress bar. It is possible to further [trac:TracRoadmapCustomGroups customise the ticket grouping] and have multiple ticket statuses shown on the progress bar.
+It is possible to drill down into this simple statistic by viewing the individual milestone pages. By default, the active/resolved ratio will be grouped and displayed by component. You can also regroup the status by other criteria, such as ticket owner or severity. Ticket numbers are linked to [wiki:TracQuery custom queries] listing corresponding tickets.
+== Roadmap Administration
+With appropriate permissions it is possible to add, modify and remove milestones using either the web interface (roadmap and milestone pages), web administration interface or by using `trac-admin`.
+'''Note:''' Milestone descriptions can not currently be edited using 'trac-admin'.
+== iCalendar Support
+The Roadmap supports the [http://www.ietf.org/rfc/rfc2445.txt iCalendar] format to keep track of planned milestones and related tickets from your favorite calendar software. Many calendar applications support the iCalendar specification including
+ * [http://www.apple.com/ical/ Apple iCal] for Mac OS X
+ * the cross-platform [http://www.mozilla.org/projects/calendar/ Mozilla Calendar]
+ * [http://chandlerproject.org Chandler]
+ * [http://kontact.kde.org/korganizer/ Korganizer], the calendar application of the [http://www.kde.org/ KDE] project
+ * [https://wiki.gnome.org/Apps/Evolution Evolution]
+ * [http://office.microsoft.com/en-us/outlook/ Microsoft Outlook] can also read iCalendar files and appears as a new static calendar in Outlook
+ * [https://www.google.com/calendar/ Google Calendar]
+To subscribe to the roadmap, copy the iCalendar link from the roadmap (found at the bottom of the page) and choose the "Subscribe to remote calendar" action (or similar) of your calendar application, and insert the URL just copied.
+'''Note:''' For tickets to be included in the calendar as tasks, you need to be logged in when copying the link. You will only see tickets assigned to yourself and associated with a milestone.
+'''Note:''' To include the milestones in Google Calendar you might need to rewrite the URL.
+{{{
+RewriteEngine on
+RewriteRule ([^/.]+)/roadmap/([^/.]+)/ics /$1/roadmap?user=$2&format=ics
+}}}
+More information about iCalendar can be found at [http://en.wikipedia.org/wiki/ICalendar Wikipedia].
+----
+See also: TracTickets, TracReports, TracQuery, [trac:TracRoadmapCustomGroups]

wiki/pages/TracRss

-                      r40534
+                      r40542
+= Using RSS with Trac
+[[TracGuideToc]]
+Several of the Trac modules support content syndication using the RSS ([http://en.wikipedia.org/wiki/RSS Really Simple Syndication]) XML format. RSS pushes out updates to Trac whenever they occur and to whoever has subscribed to it. Using the RSS subscription feature in Trac, you can easily monitor progress of the project, a set of issues or even changes to a single file.
+Trac supports RSS feeds in:
+ * TracTimeline — Use the RSS feed to '''subscribe to project events'''. Monitor overall project progress in your favorite RSS reader.
+ * TracTickets, TracReports, and TracQuery — Allows syndication of report and ticket query results. Be notified about important and relevant issue tickets.
+ * TracBrowser and TracRevisionLog — Syndication of file changes. Stay up to date with changes to a specific file or directory.
+== How to access RSS data
+Anywhere in Trac where RSS is available, you should find a small orange '''RSS''' icon, typically at the bottom of the page:
+{{{#!html
+<a rel="nofollow" style="padding-left: 20px; background: url(../../chrome/common/feed.png) left center no-repeat;  border: none;"><span style="color: #666;padding: 0 0 2px; font-size: 11px;">RSS feed</span></a>
+}}}
+Clicking the icon will access the RSS feed for that specific resource.
+'''Note:''' Different modules provide different data in their RSS feeds. Usually the syndicated information corresponds to the current view. For example, if you click the RSS link on a report page, the feed will be based on that report. It might be explained by thinking of the RSS feeds as an ''alternate view of the data currently displayed''.
+Since Trac 1.0 an RSS feed can be retrieved from a Trac site that requires authentication. Hover over the RSS icon, right click and //copy link address//.
+== Links
+ * ''Specifications:''
+   * http://blogs.law.harvard.edu/tech/rss — RSS 2.0 Specification.
+ * ''Multi-platform RSS readers:''
+   * http://www.rssowl.org/ — Open source, Eclipse-based, RSS reader for Linux, Mac and Windows systems that supports https and authenticated feeds.
+ * ''Linux/BSD/*n*x systems:''
+   * http://liferea.sourceforge.net/ — Open source GTK2 RSS Reader for Linux.
+   * [http://akregator.sourceforge.net/ Akregator] — Open source KDE RSS Reader, part of KDE-PIM.
+ * ''Mac OS X systems:''
+   * http://ranchero.com/netnewswire/ — An excellent RSS reader for Mac OS X, has both free and paid versions.
+   * http://www.utsire.com/shrook/ — An RSS reader for Max OS X that supports https, even with self signed certificates, and authenticated feeds.
+   * http://vienna-rss.sourceforge.net/ — Open source Feed Reader for Mac OS X with smart folders support.
+ * ''Windows systems:''
+   * http://www.rssreader.com/ — Free and powerful RSS Reader for MS Windows.
+   * http://www.sharpreader.net/ — A free RSS Reader written in .NET for MS Windows.
+ * ''Firefox:''
+   * http://www.mozilla.org/products/firefox/ — Mozilla Firefox features plenty [https://addons.mozilla.org/en-US/firefox/search/?q=rss&appver=&platform= add-ons] for supporting RSS.
+----
+See also: TracGuide, TracTimeline, TracReports, TracBrowser

wiki/pages/TracSearch

-                      r40534
+                      r40542
+= Using Search
+Trac has built-in search functionality to search for occurrences of keywords and substrings in wiki pages, tickets and changeset properties, such as author, revision and log messages.
+Apart from the [search: Search module], you will also find a small search field above the navigation bar at all time. It provides convenient access to the search module from all pages.
+The search results show the most recent modifications ranked first rather than the most relevant result.
+== Quick searches
+For quick access to project resources, the quick-search field at the top of every page can be used to enter a [TracLinks wiki link], which will take you directly to the resource identified by that link:
+ * ![42] -- Opens change set 42
+ * !#42 -- Opens ticket number 42
+ * !{1} -- Opens report 1
+ * /trunk -- Opens the browser for the `trunk` directory in the default repository
+ * /repos1/trunk -- Opens the browser for the `trunk` directory in the `repos1` repository
+== Advanced
+=== Disabling Quickjump
+To disable the Quickjump feature for a keyword start the query with an exclamation mark (`!`): use `!TracGuide` to search for occurrences of the literal word !TracGuide.
+=== Search Links
+From the Wiki, it is possible to link to a specific search, using `search:` links:
+ * `search:?q=crash` will search for the string "crash"
+ * `search:?q=trac+link&wiki=on` will search for "trac" and "link" in wiki pages only
+----
+See also: TracGuide, TracLinks, TracQuery

wiki/pages/TracStandalone

-                      r40534
+                      r40542
+= Tracd
+Tracd is a lightweight standalone Trac web server.
+It can be used in a variety of situations, from a test or development server to a multiprocess setup behind another web server used as a load balancer.
+== Pros
+ * Fewer dependencies: You don't need to install apache or any other web-server.
+ * Fast: Should be almost as fast as the [wiki:TracModPython mod_python] version (and much faster than the [wiki:TracCgi CGI]), even more so since version 0.12 where the HTTP/1.1 version of the protocol is enabled by default
+ * Automatic reloading: For development, Tracd can be used in ''auto_reload'' mode, which will automatically restart the server whenever you make a change to the code (in Trac itself or in a plugin).
+== Cons
+ * Fewer features: Tracd implements a very simple web-server and is not as configurable or as scalable as Apache httpd.
+ * No native HTTPS support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead,
+   or [trac:wiki:STunnelTracd stunnel -- a tutorial on how to use stunnel with tracd] or Apache with mod_proxy.
+== Usage examples
+A single project on port 8080. (http://localhost:8080/)
+{{{#!sh
+ $ tracd -p 8080 /path/to/project
+}}}
+Strictly speaking this will make your Trac accessible to everybody from your network rather than ''localhost only''. To truly limit it use the `--hostname` option.
+{{{#!sh
+ $ tracd --hostname=localhost -p 8080 /path/to/project
+}}}
+With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/)
+{{{#!sh
+ $ tracd -p 8080 /path/to/project1 /path/to/project2
+}}}
+You can't have the last portion of the path identical between the projects since Trac uses that name to keep the URLs of the
+different projects unique. So if you use `/project1/path/to` and `/project2/path/to`, you will only see the second project.
+An alternative way to serve multiple projects is to specify a parent directory in which each subdirectory is a Trac project, using the `-e` option. The example above could be rewritten:
+{{{#!sh
+ $ tracd -p 8080 -e /path/to
+}}}
+To exit the server on Windows, be sure to use `CTRL-BREAK` -- using `CTRL-C` will leave a Python process running in the background.
+== Installing as a Windows Service
+=== Option 1
+To install as a Windows service, get the [http://www.google.com/search?q=srvany.exe SRVANY] utility and run:
+{{{#!cmd
+ C:\path\to\instsrv.exe tracd C:\path\to\srvany.exe
+ reg add HKLM\SYSTEM\CurrentControlSet\Services\tracd\Parameters /v Application /d "\"C:\path\to\python.exe\" \"C:\path\to\python\scripts\tracd-script.py\" <your tracd parameters>"
+ net start tracd
+}}}
+'''DO NOT''' use {{{tracd.exe}}}.  Instead register {{{python.exe}}} directly with {{{tracd-script.py}}} as a parameter.  If you use {{{tracd.exe}}}, it will spawn the python process without SRVANY's knowledge.  This python process will survive a {{{net stop tracd}}}.
+If you want tracd to start automatically when you boot Windows, do:
+{{{#!cmd
+ sc config tracd start= auto
+}}}
+The spacing here is important.
+{{{#!div
+Once the service is installed, it might be simpler to run the Registry Editor rather than use the `reg add` command documented above.  Navigate to:[[BR]]
+`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tracd\Parameters`
+Three (string) parameters are provided:
+||!AppDirectory ||C:\Python26\ ||
+||Application ||python.exe ||
+||!AppParameters ||scripts\tracd-script.py -p 8080 ... ||
+Note that, if the !AppDirectory is set as above, the paths of the executable ''and'' of the script name and parameter values are relative to the directory.  This makes updating Python a little simpler because the change can be limited, here, to a single point.
+(This is true for the path to the .htpasswd file, as well, despite the documentation calling out the /full/path/to/htpasswd; however, you may not wish to store that file under the Python directory.)
+}}}
+For Windows 7 User, srvany.exe may not be an option, so you can use [http://www.google.com/search?q=winserv.exe WINSERV] utility and run:
+{{{#!cmd
+"C:\path\to\winserv.exe" install tracd -displayname "tracd" -start auto "C:\path\to\python.exe" c:\path\to\python\scripts\tracd-script.py <your tracd parameters>"
+net start tracd
+}}}
+=== Option 2
+Use [http://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [http://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service.
+=== Option 3
+also cygwin's cygrunsrv.exe can be used:
+{{{#!sh
+$ cygrunsrv --install tracd --path /cygdrive/c/Python27/Scripts/tracd.exe --args '--port 8000 --env-parent-dir E:\IssueTrackers\Trac\Projects'
+$ net start tracd
+}}}
+== Using Authentication
+Tracd allows you to run Trac without the need for Apache, but you can take advantage of Apache's password tools (`htpasswd` and `htdigest`) to easily create a password file in the proper format for tracd to use in authentication. (It is also possible to create the password file without `htpasswd` or `htdigest`; see below for alternatives)
+Make sure you place the generated password files on a filesystem which supports sub-second timestamps, as Trac will monitor their modified time and changes happening on a filesystem with too coarse-grained timestamp resolution (like `ext2` or `ext3` on Linux, or HFS+ on OSX).
+Tracd provides support for both Basic and Digest authentication. Digest is considered more secure. The examples below use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the command line.
+The general format for using authentication is:
+{{{#!sh
+ $ tracd -p port --auth="base_project_dir,password_file_path,realm" project_path
+}}}
+where:
+ * '''base_project_dir''': the base directory of the project specified as follows:
+   * when serving multiple projects: ''relative'' to the `project_path`
+   * when serving only a single project (`-s`): the name of the project directory
+ Don't use an absolute path here as this won't work. ''Note:'' This parameter is case-sensitive even for environments on Windows.
+ * '''password_file_path''': path to the password file
+ * '''realm''': the realm name (can be anything)
+ * '''project_path''': path of the project
+ * **`--auth`** in the above means use Digest authentication, replace `--auth` with `--basic-auth` if you want to use Basic auth.  Although Basic authentication does not require a "realm", the command parser does, so the second comma is required, followed directly by the closing quote for an empty realm name.
+Examples:
+{{{#!sh
+ $ tracd -p 8080 \
+   --auth="project1,/path/to/passwordfile,mycompany.com" /path/to/project1
+}}}
+Of course, the password file can be be shared so that it is used for more than one project:
+{{{#!sh
+ $ tracd -p 8080 \
+   --auth="project1,/path/to/passwordfile,mycompany.com" \
+   --auth="project2,/path/to/passwordfile,mycompany.com" \
+   /path/to/project1 /path/to/project2
+}}}
+Another way to share the password file is to specify "*" for the project name:
+{{{#!sh
+ $ tracd -p 8080 \
+   --auth="*,/path/to/users.htdigest,mycompany.com" \
+   /path/to/project1 /path/to/project2
+}}}
+=== Basic Authorization: Using a htpasswd password file
+This section describes how to use `tracd` with Apache .htpasswd files.
+  Note: It is necessary (at least with Python 2.6) to install the fcrypt package in order to
+  decode some htpasswd formats.  Trac source code attempt an `import crypt` first, but there
+  is no such package for Python 2.6. Only `SHA-1` passwords (since Trac 1.0) work without this module.
+To create a .htpasswd file use Apache's `htpasswd` command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache):
+{{{#!sh
+ $ sudo htpasswd -c /path/to/env/.htpasswd username
+}}}
+then for additional users:
+{{{#!sh
+ $ sudo htpasswd /path/to/env/.htpasswd username2
+}}}
+Then to start `tracd` run something like this:
+{{{#!sh
+ $ tracd -p 8080 --basic-auth="project,/fullpath/environmentname/.htpasswd,realmname" /path/to/project
+}}}
+For example:
+{{{#!sh
+ $ tracd -p 8080 --basic-auth="project,/srv/tracenv/testenv/.htpasswd,My Test Env" /path/to/project
+}}}
+''Note:'' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD).
+=== Digest authentication: Using a htdigest password file
+If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read [http://httpd.apache.org/docs/2.0/programs/htdigest.html this page] from the Apache manual to get precise instructions.  You'll be prompted for a password to enter for each user that you create.  For the name of the password file, you can use whatever you like, but if you use something like `users.htdigest` it will remind you what the file contains. As a suggestion, put it in your <projectname>/conf folder along with the [TracIni trac.ini] file.
+Note that you can start tracd without the `--auth` argument, but if you click on the ''Login'' link you will get an error.
+=== Generating Passwords Without Apache
+Basic Authorization can be accomplished via this [http://aspirine.org/htpasswd_en.html online HTTP Password generator] which also supports `SHA-1`.  Copy the generated password-hash line to the .htpasswd file on your system. Note that Windows Python lacks the "crypt" module that is the default hash type for htpasswd. Windows Python can grok MD5 password hashes just fine and you should use MD5.
+Trac also provides `htpasswd` and `htdigest` scripts in `contrib`:
+{{{#!sh
+$ ./contrib/htpasswd.py -cb htpasswd user1 user1
+$ ./contrib/htpasswd.py -b htpasswd user2 user2
+}}}
+{{{#!sh
+$ ./contrib/htdigest.py -cb htdigest trac user1 user1
+$ ./contrib/htdigest.py -b htdigest trac user2 user2
+}}}
+==== Using `md5sum`
+It is possible to use `md5sum` utility to generate digest-password file:
+{{{#!sh
+user=
+realm=
+password=
+path_to_file=
+echo ${user}:${realm}:$(printf "${user}:${realm}:${password}" | md5sum - | sed -e 's/\s\+-//') > ${path_to_file}
+}}}
+== Reference
+Here's the online help, as a reminder (`tracd --help`):
+{{{
+Usage: tracd [options] [projenv] ...
+Options:
+  --version             show program's version number and exit
+  -h, --help            show this help message and exit
+  -a DIGESTAUTH, --auth=DIGESTAUTH
+                        [projectdir],[htdigest_file],[realm]
+  --basic-auth=BASICAUTH
+                        [projectdir],[htpasswd_file],[realm]
+  -p PORT, --port=PORT  the port number to bind to
+  -b HOSTNAME, --hostname=HOSTNAME
+                        the host name or IP address to bind to
+  --protocol=PROTOCOL   http|scgi|ajp|fcgi
+  -q, --unquote         unquote PATH_INFO (may be needed when using ajp)
+  --http10              use HTTP/1.0 protocol version instead of HTTP/1.1
+  --http11              use HTTP/1.1 protocol version (default)
+  -e PARENTDIR, --env-parent-dir=PARENTDIR
+                        parent directory of the project environments
+  --base-path=BASE_PATH
+                        the initial portion of the request URL's "path"
+  -r, --auto-reload     restart automatically when sources are modified
+  -s, --single-env      only serve a single project without the project list
+  -d, --daemonize       run in the background as a daemon
+  --pidfile=PIDFILE     when daemonizing, file to which to write pid
+  --umask=MASK          when daemonizing, file mode creation mask to use, in
+                        octal notation (default 022)
+  --group=GROUP         the group to run as
+  --user=USER           the user to run as
+}}}
+Use the -d option so that tracd doesn't hang if you close the terminal window where tracd was started.
+== Tips
+=== Serving static content
+If `tracd` is the only web server used for the project,
+it can also be used to distribute static content
+(tarballs, Doxygen documentation, etc.)
+This static content should be put in the `$TRAC_ENV/htdocs` folder,
+and is accessed by URLs like `<project_URL>/chrome/site/...`.
+Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file,
+the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`,
+which in turn can be written as `htdocs:software-0.1.tar.gz` (TracLinks syntax) or `[/<project_name>/chrome/site/software-0.1.tar.gz]` (relative link syntax).
+=== Using tracd behind a proxy
+In some situations when you choose to use tracd behind Apache or another web server.
+In this situation, you might experience issues with redirects, like being redirected to URLs with the wrong host or protocol. In this case (and only in this case), setting the `[trac] use_base_url_for_redirect` to `true` can help, as this will force Trac to use the value of `[trac] base_url` for doing the redirects.
+If you're using the AJP protocol to connect with `tracd` (which is possible if you have flup installed), then you might experience problems with double quoting. Consider adding the `--unquote` parameter.
+See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe].
+=== Authentication for tracd behind a proxy
+It is convenient to provide central external authentication to your tracd instances, instead of using `--basic-auth`. There is some discussion about this in [trac:#9206].
+Below is example configuration based on Apache 2.2, mod_proxy, mod_authnz_ldap.
+First we bring tracd into Apache's location namespace.
+{{{#!apache
+<Location /project/proxified>
+        Require ldap-group cn=somegroup, ou=Groups,dc=domain.com
+        Require ldap-user somespecificusertoo
+        ProxyPass http://localhost:8101/project/proxified/
+        # Turns out we don't really need complicated RewriteRules here at all
+        RequestHeader set REMOTE_USER %{REMOTE_USER}s
+</Location>
+}}}
+Then we need a single file plugin to recognize HTTP_REMOTE_USER header as valid authentication source. HTTP headers like '''HTTP_FOO_BAR''' will get converted to '''Foo-Bar''' during processing. Name it something like '''remote-user-auth.py''' and drop it into '''proxified/plugins''' directory:
+{{{#!python
+from trac.core import *
+from trac.config import BoolOption
+from trac.web.api import IAuthenticator
+class MyRemoteUserAuthenticator(Component):
+    implements(IAuthenticator)
+    obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false',
+               """Whether the 'Remote-User:' HTTP header is to be trusted for user logins
+                (''since ??.??').""")
+    def authenticate(self, req):
+        if self.obey_remote_user_header and req.get_header('Remote-User'):
+            return req.get_header('Remote-User')
+        return None
+}}}
+Add this new parameter to your TracIni:
+{{{#!ini
+[trac]
+...
+obey_remote_user_header = true
+...
+}}}
+Run tracd:
+{{{#!sh
+tracd -p 8101 -r -s proxified --base-path=/project/proxified
+}}}
+Note that if you want to install this plugin for all projects, you have to put it in your [TracPlugins#Plugindiscovery global plugins_dir] and enable it in your global trac.ini.
+Global config (e.g. `/srv/trac/conf/trac.ini`):
+{{{#!ini
+[components]
+remote-user-auth.* = enabled
+[inherit]
+plugins_dir = /srv/trac/plugins
+[trac]
+obey_remote_user_header = true
+}}}
+Environment config (e.g. `/srv/trac/envs/myenv`):
+{{{#!ini
+[inherit]
+file = /srv/trac/conf/trac.ini
+}}}
+=== Serving a different base path than /
+Tracd supports serving projects with different base urls than /<project>. The parameter name to change this is
+{{{#!sh
+ $ tracd --base-path=/some/path
+}}}
+----
+See also: TracInstall, TracCgi, TracModPython, TracGuide, [trac:TracOnWindowsStandalone#RunningTracdasservice Running tracd.exe as a Windows service]

wiki/pages/TracSupport

-                      r40534
+                      r40542
+= Trac Support =
+Like in most [http://www.opensource.org/ open source projects], Trac support is available primarily through the [trac:MailingList mailing list] and the [trac: project wiki]. Both are maintained by the trac community. The [trac: project wiki] is the authoritative source for the TracGuide, consisting of the administrator and user guides for Trac.
+There is also an [trac:IrcChannel IRC channel] where online users can help out. Much of the 'live' development discussions also happen there.
+Before you start a new support query, make sure you have done the appropriate searching:
+ * in the project's [trac:TracFaq FAQ]
+ * in past messages to the [http://groups.google.com/group/trac-users Trac Users Mailing List]
+ * in the Trac ticket system, using either a [trac:search:?q=&ticket=on&wiki=on full search] or a [trac:query: ticket query].
+Please '''don't''' create a ticket in trac.egdewall.org to ask a Trac support question. Only use it when you face a ''real'' and ''new'' bug in Trac, and do so only after having read the [trac:NewTicketGuidelines NewTicketGuidelines]. The more a bug report or enhancement request complies with those guidelines, the higher the chances are that it will be fixed or implemented promptly!
+----
+See also: [trac:MailingList], [trac:TracTroubleshooting], [trac:CommercialServices]

wiki/pages/nl/EPG-Search

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.1.4 EPG Search''' [=#point3.1.4] ([wiki:Interface-Operation#point3.1 Records and EPG(Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/Epg_Search.jpg)]][[BR]]
+>
+EPG Search is where you can search the EPG title, discription genra for specific keywords to search for programs to set up Recordings.
+[[br]]
+ '''Coloured and Extra Button's Functions"
+ The __"Coloured and Extra Buttons"__ along the bottom of the display bring up additional menus and options with in the Search EPG menu.
+ please see below for more info on the functions of these buttons:.
+ ||'''Red Button: (Timer)''' ||This will bring up the recording timer menu to set up a timer.||
+ ||'''Green Button: (Title)''' ||This will search the EPG title string for text you specify and bring up a list of matches where you may press the red button to set up a timer.||
+ ||'''Yellow Button: (Discription)''' ||This will search the EPG Discription string for text you specify and bring up a list of matches where you may press the red button to set up a timer.||
+ ||'''Blue Button: (All)''' ||This will search all EPG string for text you specify and bring up a list of matches where you may press the red button to set up a timer.||
+ ||'''Menu (Genre):''' ||This will search the EPG Genre string for text you specify and bring up a list of matches where you may press the red button to set up a timer.||
+For information on setting up a timer Recording using the red button see ([WikiStart#point103.10.6 Records]) for more info.

wiki/pages/nl/EPG-Settings

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.6.11 EPG Settings''' [=#point3.6.11] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>Menu Picture place holder:
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/EPG_Settings.jpg)]][[BR]]
+>
+>Here you can change your epg settings.
+[[br]]
+ ||'''EPG Path''' ||Set to any Path you want where the EPG File should be stored (on Receivers with little Memory it is strongly recommended to extend it by using a USB Pen-Drive or Harddisk)||
+ ||'''How Many Days:''' ||The Number of Days in Advance of the EPG to store (I recommend no higher than 8 Days)||
+ ||'''Delete EPG after read:''' ||Do you want the EPG file to be deleted after being read.||
+ ||'''EPG Save Mode:''' ||When should the EPG Data be stored to the storage medium. Caution: Should you not use a Pen Drive or Harddisk for EPG Storage set to Never, as Receivers with little Memory on Board tend to crash due to Insufficient free space.||
+ ||'''Show EPG Screen (EPG Button):''' ||Which EPG format should be shown on EPG Key-press on the Remote.||
+ ||'''EPG Free Space (kb):''' ||Total of minimal Free Memory that should be kept on the medium where the epg is stored to aviod free space errors.||
+ ||'''EPG List Mode:''' ||What Channels should be scanned in the background (Only for twin Receivers) for EPG (scan)(whitelist) (scanlist and whitelist) (deactivate (disable scan)).||
+ ||'''EPG Scan Time:''' ||Here you can set the time of the automatic EPG scan. The Scan will be performed every Day at that set time. Should the Receiver be in Deep Stand-by it will "wake up" aprox. 5 Minutes before the scan is due to start.||
+ ||'''EPG Button in EPG:''' ||Behavior of the EPG Button during EPG display.||
+ ||'''Grafic EPG Zoom:''' ||Sets the zoom level of the EPG to show more or less of a time span of the shown programs.||
+ ||'''Grafic EPG Picons:''' ||Set to yes to use picons or the alternative Picon sets in the infobar and EPG stored in /var/media/autofs/sda1/swapextensions/usr/local/share/titan/picons/ directory.||
+ ||'''Delete EPG Before Scan:''' ||Should the EPG be deleted before a the timed scan.||
+ ||'''After EPG Scan:''' ||Behavior after the EPG scan is completed EPG scan: Nothing (Stand-By) or Switch Off (Deep Stand-By).||
+ ||'''MHW EPG:''' ||Scan for a Media Highway EPG stream during EPG scan.||
+ ||'''MHW2 EPG:''' ||Scan for a Media Highway version 2 EPG stream during  EPG scan.||
+ ||'''OpenTV EPG:''' ||Scan for an OpenTV EPG stream during EPG scan.||
+ To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
+[[br]]
+----
+ '''Coloured Button's Functions"
+ The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
+ please see below for more info on the functions of these buttons:.
+ ||'''Red Button: (EPG Reset)''' ||This will reset the saved epg removing all program data.||
+ ||'''Green Button: (Edit)''' ||On a customisable item this will bring up editor to edit a value or text string.||
+ ||'''Yellow Button: (Scanlist)''' ||Brings up the epg scan list and you may from there add aditional boquets to be scaned during an epg scan.||
+ ||'''Blue Button: (log)''' ||This will show you the past scan log history for the epg.||

wiki/pages/nl/EPG-Short-View

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.1.1 EPG Short View''' [=#point3.1.1] ([wiki:Interface-Operation#point3.1 Records and EPG(Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/EPG_Short_View.jpg)]][[BR]]
+>
+EPG Short View is a small easy to read horozontal epg of the current displayed channel including the infomation on the program you may scroll using the direction arrows to a future time.
+[[br]]

wiki/pages/nl/External-Software

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''9 External Software''' [=#point9] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+External Software is a collection of tools to supplement TitanNit.
+This is a list of applications that can be use with or for to manipulate or control your Receiver.
+[[br]]
+Below is a list of external applications please select a link below for more information.
+{{{#!div style="width: 1100px; margin: auto"
+ {{{#!table style="border: none"
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TiMote.png,align=left,link=[wiki:External-Software-TiMote#point9.1 9.1 TiMote (Android)])]]
+  }}}
+  '''[wiki:External-Software-TiMote#point9.1 9.1 TiMote (Android)]'''[[br]]
+  {{{#!div style="float: left
+Timote is an andriod application for streaming and control of TitanNit
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TiView.png,align=left,link=[wiki:External-Software-TiView#point9.2 9.2 TiView (PC)])]]
+  }}}
+  '''[wiki:External-Software-TiView#point9.2 9.2 TiView (PC)]'''[[br]]
+  {{{#!div style="float: left
+TiView is an PC application for streaming and control of TitanNit
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/SatChannelListEditor.png,align=left,link=[wiki:External-Software-SatChannelListEditor#point9.3 9.3 SatChannelListEditor])]]
+  }}}
+  '''[wiki:External-Software-SatChannelListEditor#point9.3 9.3 SatChannelListEditor]'''[[br]]
+  {{{#!div style="float: left
+SatChannelListEditor is an PC application for manipulation of your TitanNit channel data.
+  }}}
+  }}}
+  |----
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/E2WebIFAPI.png,align=left,link=[wiki:External-Software-E2WebIfAPI#point9.4 9.4 E2WebIfAPI])]]
+  }}}
+  '''[wiki:External-Software-E2WebIfAPI#point9.4 9.4 E2WebIfAPI]'''[[br]]
+  {{{#!div style="float: left
+E2WebIfAPI is an console application to support the dreambox xml web interface commands.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TitanEditor.png,align=left,link=[wiki:External-Software-TitanEditor#point9.5 9.5 TitanEditor])]]
+  }}}
+  '''[wiki:External-Software-TitanEditor#point9.5 9.5 TitanEditor]'''[[br]]
+  {{{#!div style="float: left
+TitanEditor is an PC application for manipulation of dreambox channel data to work on of your TitanNit Receiver.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/External-Software/TitanNitLanguageEditor.png,align=left,link=[wiki:External-Software-TitanNitLanguageEditor#point9.6 9.6 TitanNitLanguageEditor])]]
+  }}}
+  '''[wiki:External-Software-TitanNitLanguageEditor#point9.6 9.6 TitanNitLanguageEditor]'''[[br]]
+  {{{#!div style="float: left
+TitanLanguageEditor is an PC application for editing GUI language translations.
+  }}}
+  }}}
+}}}
+}}}

wiki/pages/nl/External-Software-E2WebIfAPI

-                      r40540
+                      r40542
+[[TranslatedPages]]
+'''9.4 E2WebIfAPI''' [=#point9.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+== Introduction ==
+Enigma2 Web Interface ( WebIf ) API was defined for Dreambox .
+It is a protocol that allows you to control a Dreambox via HTTP requests.
+Typical control tasks are :
+* Programming (timer) and playing back recordings
+* Live streaming (TV and radio)
+* EPG functions (display, search)
+* Remote control (Remote Control)
+You can find a good overview of the E2WebIFAPI in the [http://dream.reichholf.net/wiki/Enigma2:WebInterface DreamboxWIKI].
+== Motivation ==
+For TitanNit the Android App [wiki:External-Software-TiMote#point109.1 9.1 TiMote] was developed. Anybody with an Android Smart-Phone or Tablet with this software installed can control their receiver or watch TV on the Android device. Isn't that cool?
+But owners of an iOS-device (i-Phone or i-Pad) are unlucky as there is no iOS TitanNit compatable web client such as TiMote. You can control your receiver via http protocol (same as Web Interface) but you wont be able to use all advantages like tiMote on an Android Platform.
+On the other hand iOS and Android Apps already exist for Dreambox receivers. These Apps are based on the Enigma2 protocol. Couldn't one just use that App on iOS instead of developing a new App?
+== The solution ==
+TitanNit has its own protocol but is not compatible to the Enigma2 WebIf. Following a short analysis it was discovered that converting E2 requests to Titan didn't seem so difficult. Therefore, an E2 web server (e2webserv) was developed, which implements the Enigma2 WebIf. This server receives the E2 requests, delegates the calls to TitanNit web server and the responses is converted back into the XML format, which is expected from the E2 client.
+This way the TitanNit receiver is able to correspond to existing E2 - client software.
+== Requirements ==
+* The Web server must be enabled on the receiver
+* The E2webserv must be installed on the receiver
+== IOS Apps ==
+The following apps are installed on my iPad2:
+* dreaMote
+* DreaMote Lite
+* e2RemoteHD
+* Dreambox Live
+Should you not want to purchase any apps from the Apps-Store I can recommend dreaMote Lite .
+In addition to the app you need a player.
+I have tried the following players, which work well for me:
+* Good Player
+* BUZZ Player
+* OPlayerHD Lite
+* VLC Player
+VLC and OPlayerHD Lite are free.
+== XBMC ==
+If you are running the Media Center software [http://xbmc.org/ XBMC] or [http://xbmc4xbox.org.uk/ XBMC4XBOX], you can connect your Titan receiver via the Live-TV-Plugin VU+.
+XBMC runs on Windows PCs aswell as Linux and is also available for Raspberry Pi and the Xbox.
+== VLC ==
+Having installed the e2webserv you can enjoy Live-Streaming on your Windows or Linux PC using [http://www.videolan.org/vlc/ VLC] (no further software needed).
+You do not have to switch channels manually it all happens automatically. In order for this to take place you need an M3U playlist. You can easily generate the playlist by your Favourites and save to your PC. Having done so you only need to open the M3U list in VLC and select the desired channel.
+How do you export a particular favourites list into an M3U file?
+Enter the address in your Web browser.
+Example (favourite is "Polish"):
+[http://192.168.1.1:8080/web/services.m3u?bRef=Polish]
+Enter your receivers IP address and where names of Favourites have spaces within these spaces must be replaced with "%20".
+Example (favourite is "My TV" Receiver - IP: 192.168.0.10):
+[http://192.168.0.10:8080/web/services.m3u?bRef=Mein%20TV]
+Client Configuration == ==
+Please configure the E2-clientas accordingly:
+* IP address of the receiver
+* Port: 8080
+* Streaming Port: 8001
+Please note that SSL is not supported.
+Below you see an example configuration for dreaMote.
+[[Image(DreaMote.png,384px)]]
+== E2webserv.conf ==
+You must alter the server configuration manually. Using standard configured TitanNit no alterration on the e2webserv.conf should be neccessary.
+Should you have installed the plugin to Flash the configuration file '''e2webserv.conf''' lies in the directory '''/mnt/swapextensions/etc'''
+Here is the content:
+{{{
+# E2 web port
+port = 8080
+# E2 data port
+data port = 8001
+# Titan web port
+titanium- port = 80
+# Titan data port
+titan data port = 22222
+# Titan host (change it if e2webserv is not running locally on the receiver)
+titan host = 127.0.0.1
+# Automatic switching of channels
+# It is useful if you do not want manually switch a channel on receiver with a single tuner.
+# If it is set to false and you have a single tuner you can stream the only channels located
+# On the same transponder as the current channel active on the receiver .
+Autozap = true
+# Log output file
+logFile = /tmp/e2webserv.log
+# Maximum log file size in KB. Set it to 0 (default 10KB) to disable logging (maximum allowed value is 1024).
+# When the file limit is reached a backup of the current file is created .
+# It Means maximally 2 x MaxLogSize KB will be used.
+MaxLogSize = 10
+# Thread pool size (1 through 8)
+threadpool = 2
+# Directory where the transponder and bouquet files are located.
+# You do not need to Specify it, it will be Automatically Discovered .
+# But if you you start e2webserv not on the receiver (but eg on your Linux server or Windows computer) then you
+# Shoulderstand copy the settings (channel, transponder, provider and all bouquets file) and here Specify the location on the local computer .
+titanDir = /mnt/settings
+}}}
+== Links ==
+* Enigma2 Web API in [http://www.aaf-digital.info/forum/showthread.php?90948-Enigma2-Web-API-f % FCr - TitanNit AAF Forum]
+* Sources on [https://github.com/gswiatek/e2api4titan GitHub]
+[[br]]
+[[br]]

wiki/pages/nl/External-Software-SatChannelListEditor

-                      r40540
+                      r40542
+[[TranslatedPages]]
+'''9.3 SatChannelListEditor''' [=#point9.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+This manual applies to version 5.4 of SatChannelListEditor (SCLE). In future releases,[[br]]
+possibly new features will be added, making the screen shots of this program obsolete.
+== Requirements ==
+SCLE has been programmed for the runtime environment " Microsoft. NET Framework ".[[br]]
+Currently .NET Framework version 2.0 or higher is required.
+( also take a look at [http://en.wikipedia.org/wiki/.NET_Framework Wikipedia article . NET Framework] )
+== Windows ==
+* In  Windows XP .NET Framework version 2.0, 3.0 or 3.5 must be installed.[[br]]
+(3.0 and 3.5 are extended versions include version 2.0)
+* For Windows Vista and Windows 7 the .NET Framework librarys are implemented[[br]]
+in the operating system and do not need to be installed seperately.
+* In Windows 8 .NET Framework 3.5 must be installed. As Windows 8 by default,[[br]]
+only includes .NET framework 4.5, which is not compatible with SCLE
+== Linux ==
+In Linux, the Mono framework is required (see [http://en.wikipedia.org/wiki/Mono_(software)Wikipedia article about Mono project]) .
+[[BR]] You may have to install WinForms libraries manually with "apt -get install libmono- winforms * "
+[[BR]] You may then run SCLE from the command line with the command "mono SatChannelListEditor.exe ".
+== Mac OS ==
+In Mac OS , just like Linux, the Mono-Framework is required to to run SCLE.
+== The first startup ==
+After the first startup of SCLE the language is set to English and the receiver[[br]]
+model " UFS -821 " is selected. You now have to set the language and your[[br]]
+Receiver model to suite your receiver.
+Select the receiver and its System you like to manage.
+== Setting the receiver model and type of operating system ==
+Select the menu under " Options ", select " Settings" :
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/3.png)]]
+Select Titan in the window that appears as the receiver you wish to connect to:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/4.png)]]
+After selecting the reciever type under the option " Titan " set the IP address of your Receiver, before[[br]]
+you close the window confirm the settings by clicking the OK button.[[br]]
+The other settings on this page should not be changed.
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/5.png)]]
+== Download and upload the channel list ==
+After the Receiver model and the IP address have been set, you can fetch the channel[[br]]
+list from your Receiver (Download) and after processing send it back to the Receiver (upload).
+[[BR]] Use the Buttons in the Menubar of SCLE or in the Drop-down Menu:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/6.png)]]
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/7.png)]]
+When you start an upload or download the program will automatically change to[[br]]
+the message window where status messages are displayed for file transfer.
+== Edit the channel list ==
+== Favourites ==
+All TV and Radio channels are displayed in the tab "TV" and "Radio" in the main window[[br]]
+of SCLE. Normally there are several hundreds or thousands of channels in this list.
+[[BR]] To simplify navigation on your Receiver you may add the channels to more than one Favourites list.[[br]]
+The Favourites also determine the channel number for easier and direct access with your remote control.
+[[BR]] Create new favourites by clicking the right mouse button within the tree of favourites:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/8.png)]]
+After creating the new Favourites entry assign the desired Name:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/9.png)]]
+You may now add channels to your favourites by drag & drop of the channels[[br]]
+onto the Favourites entry or by clicking the right mouse button on the desired channel[[br]]
+and selecting Add to Favourites and selecting the Favourites Entry from the drop-down-menu:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/10.png)]]
+Once a channel has been added to the favourites, a channel number is assigned.[[br]]
+The first channel in the first favourites is channel number 1:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/11.png)]]
+When a channel is assigned to more than one favourites list, it additionally[[br]]
+obtains further channel numbers:
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/12.png)]]
+=== EPG favourite "EPG scan " ===
+For TV channels there is a special favourite called "EPG scan".[[br]]
+Copy all channels you want to be included for the timed EPG scan, all channels in this list[[br]]
+will have their epg automatically scaned.
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/13.png)]]
+=== Satellite ===
+Creating and Editing Satellite entrys
+Switch to the "Satellite" tab. After clicking the right mouse button the[[br]]
+drop-down-menu is displayed, where you can create a new Satellite or edit an existing one.[[br]]
+Double - clicking on an existing Satellite also opens this for editing.
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/14.png)]]
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/15.png)]]
+=== Creating and Editing Transponders ===
+Switch to the "Transponder" tab. After clicking the right mouse button the drop-down-menu[[br]]
+is displayed, where you can create a new Transponder or edit an existing one.[[br]]
+Double - clicking on an existing Transponder also opens this for editing.
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/16.png)]]
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/17.png)]]
+=== Creating and Editing Channels ===
+Switch to the tab "TV" or "Radio". After clicking the right mouse button the drop-down-menu[[br]]
+is displayed, where you can create a new channel or edit an existing one.[[br]]
+Double - clicking on an existing channel also opens this for editing.
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/18.png)]]
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/19.png)]]
+=== Using receiver profiles ===
+If you have more than one Receiver, it is advisable to work with profiles.[[br]]
+Go to the settings and enable the checkbox "Use Receiver Profiles":
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/20.png)]]
+Enter a name for the profile, and click the "Save" button.[[br]]
+The profile will be created with the current settings specified under the "Titan" tab.
+[[BR]] To create a profile for a second titan receiver, switch to the "Titan" tab,[[br]]
+enter the IP address of the second receiver, switch back to the "General" tab,[[br]]
+enter a new profile name and click on "Save" once again.
+When you close the settings window by clicking the -OK-button- You will now[[br]]
+discover the new selection menu where you may choose your Receiver profile.
+[[Image(source:/wiki/Wiki-Pictures/NL/SCLE/21.png)]]

wiki/pages/nl/External-Software-TiMote

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''9.1 TiMote''' [=#point9.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+Timote is a universal remote control for Linux-based receivers.
+Currently (Atemio) TitanNit, Enigma2 and Neutrino are supported.
+please note that screen shots were taken from TiMote version xxx future versions of TiMote could make these screenshots invalid.
+Features:
+- Bouquets / Favorites
+- Show EPG
+- EPG search (*)
+- Show the current station
+- View recordings, stream and delete (*)
+- Create, edit and delete timer
+- Satfinder (*)
+- Power Control
+- Virtual Remote
+- News
+(*) Only Titannit/E2
+To stream an appropriate player, for example, MX Player, VPlayer or BSPlayer (lite) need to be installed.
+If the app crashes, please activate the "send error report automatically" in the Settings. you can
+thereby help improve the software and make troubleshooting easier crucial to the developer.
+Comments, questions, suggestions or requests? Write me an email or post a comment on the app homepage!
+appear
+[[br]]
+[[Image(http://www.android.com/images/brand/get_it_on_play_logo_large.png)]]
+[[br]]
+[https://play.google.com/store/apps/details?id=eu.azato.timote PlayStore]
+[[br]]
+When you open up Timote You are presented with the main interface along the top of the display the radio buttons are used as the menu of Timote [[br]]
+See below for more information.
+'''Main''' [[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TiMote/Main.png)]]
+Main contains a list of the main functions of timote:
+||'''([wiki:External-Software-TiMote-TV#point0 TV]) ''' ||This will bring up a list of Boquets on the reciever).||
+||'''([wiki:External-Software-TiMote-On-air#point0 On-air]) ''' ||This will Bring up the information of the TV channel currently displaying on the Reciever||
+||'''([wiki:External-Software-TiMote-Movies#point0 Movies]) ''' ||This will bring up the Movielist's stored on the reciever).||
+||'''([wiki:External-Software-TiMote-Timer#point0 Timer]) ''' ||This will bring up a list of the current timer recordings on the reciever).||
+||'''([wiki:External-Software-TiMote-EPG-Search#point0 EPG-Search]) ''' ||This will bring up a a search page to search the EPG for a specific keyword).||
+[[br]]
+'''Misc''' [[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TiMote/Misc.png)]]
+Misc contains a list of other functions of TiMote:
+||'''([wiki:External-Software-TiMote-Signal-Finder#point0 Signal-Finder]) ''' ||This will bring up the signal info's of the current displayed channel.||
+||'''([wiki:External-Software-TiMote-Screenshot#point9.1.1 Screenshot]) ''' ||This will take a screen shot of the TV Display||
+||'''([wiki:External-Software-TiMote-Remote#point9.1.2 Remote]) ''' ||This will bring up the on screen remote).||
+||'''([wiki:External-Software-TiMote-Message#point9.1.3 Message]) ''' ||This can be used to send messages to the TV display).||
+||'''([wiki:External-Software-TiMote-Power-Menu#point9.1.4 Power Menu]) ''' ||This will bring up the power control menu
+||'''([wiki:External-Software-TiMote-RGui#point9.1.5 RGui]) ''' ||This will start the RGui engine||
+||'''([wiki:External-Software-TiMote-LCD-Mode#point9.1.6 LCD Mode]) ''' ||???||
+||'''([wiki:External-Software-TiMote-Power-About#point09.1.7 Power About]) ''' ||This will bring up information on the developers of TiMote).||
+'''Profiles''' [[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TiMote/Profile.png)]]
+Profiles is a list of receiver profiles with the ability to select and control multiple receivers.
+you may create a new profile using the add button at the top of the display.
+----
+Temp data to move to Individual pages
+[[Image(source:/wiki/Wiki-Pictures/NL/TiMote/Stream.png)]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TiMote/Boquet.png)]]

wiki/pages/nl/External-Software-TiView

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''9.2 TiView''' [=#point9.2] ([wiki:English-Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+TiView is a Windows 32bit application, that will run on a Windows 32/64bit system.[[br]]
+The Tool uses the HTTP-RAW-Api of TitanNit.[[br]]
+[[br]]
+''Highlights of TiView''
+- *Output of the TV-Screen on your PC
+- *Watch recordings on your PC
+- *PiP function for 2 simultaneous TV-Stream or recording viewing on your PC
+- *Proxy function for external access from a remote TiView and streaming a recoded stream
+- Management of timers for recordings
+- Infobar with progress bar for the actual program
+- Picon-view in the Infobar(Enabled by adding the picons into the folder /picons in TiView)
+- Channel EPG
+- Multi EPG
+- Grafical Multi EPG
+- EPG Search
+- Overview of recordings
+- Manage profiles should one have more than one Receiver
+- Signal-Monitor
+- Send Messages to your Receiver
+- OSD-Screenshot
+'''*For Playback on your PC you need a compatable media player the 32bit version 2.x of VLC Player .'''[[br]]
+(Alternativly you can copy libvlc.dll, libvlccore.dll and the Plugins folder from VLC into the TiView folder)

wiki/pages/nl/External-Software-TitanEditor

-                      r40540
+                      r40542
+[[TranslatedPages]]
+'''9.5 TitanEditor''' [=#point19.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+Titan editor is a simple channel list editor that is able to convert enigma channel data to be able to operate[[br]]
+on a titan based receiver. It is also able to convert the filename from enigma 2 picons to the titan format.
+This software is still beta status but the basic functions are working, there has been posts noted on the AAF Forum that[[br]]
+converting picons in some instances comit an unhandled exception error causing the program to exit.
+- convert E2 channel list's incl. bouquets (this will not work 100% for some channels)
+ - edit/delete and add Titan channels
+ - convert E2 picons to Titan picons
+ - manage bouquets
+The current version of TitanEditor is version 0.15 and it may be downloaded from here [http://www.aaf-digital.info/forum/showthread.php?78014-TitanEditor-V0-15&p=802005&viewfull=1#post802005 titanEditor]

wiki/pages/nl/External-Software-TitanMote

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''9.1 TitanMote''' [=#point9.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+Titanmote is a universal remote control for Linux-based receivers.
+Currently there is a little information we can provide reguarding this from the developer jagabongo.
+''Words from the developer:''
+----
+I'm currently working on an iOS app for TitanNit . For this I would need a few beta testers .
+The app will cost money later when development is finished and will be able to be purchased from the store, I will not releace it free because I have specially bought for this purpose a developer account and will take many hours of development, I also do not want the app to feature advertising.
+requirements:
+ - IPhone or iPad with iOS > = 7.0
+ - A bit of technical understanding
+ - Lust for testing
+A few recent screenshots :
+ https://www.dropbox.com/sh/armi0c3q72i350h/vm3szZDzvK
+So in Version 1 I should be able to:
+ - Browse by bouquets / channel lists + See Epg info and switch Channels.
+ - Add timers on an event with the epg data.
+ - List all timer
+ - Delete Timer
+ - easy remote copy with touch buttons
+ - 2 profiles
+ - Everywhere pull to refresh .
+ - [ EDIT] Forgot , it will be multilingual or , DE, FR, IT and rest English. But languages are all relatively retrofitted without hazzle
+Future features:
+ - User: Password WebIf Auth . ( hopefully not often used)
+ - Https support. ( Was I already am going to test with self-signed stuff but totally in the pants ... )
+ - The stream to an iOS device is just not as easy as on Android that is why they first moved to the rear.
+BETA testing runs like this:
+ * 1 You send with your UUID ( google iOS Device UUID to find out )
+ * 2 Your you created an account at https://build.phonegap.com ( Free is sufficient).
+ * 3 You share me with your UUID and email phonegap.build accounts.
+When that's done you can you log on your mobile Safari in build.phonegap.com and always install it there through the browser to the latest build. (OTA Installation).
+This is perfectly legal and possible even without jailbreak.
+if you are intreseed in becomming a better tester please leave a message in the [[http://www.aaf-digital.info/forum/showthread.php?100699-iOS-TitanNit-iOS-App-!-titanMote-!-Tester-gesucht!&p=974748#post974748 | forum]].

wiki/pages/nl/External-Software-TitanNitLanguageEditor

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''9.6 TitanNit Language Editor''' [=#point9.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+The TitanNit Language Editor tool is used to provide translations files for devs to implement translations into the TitanNit gui.
+=== Made by Karlo ===
+German and English languages have been made and have been merged into svn.
+To support future languages you can use this program to download  the language base files from the svn for conversion it supports UTF-8 so special
+chracters from various languages can be implemented.
+Please check the [[http://www.aaf-digital.info/forum/showthread.php?98565-TitanNitLanguageEditor forum Link | main thread]] for the latest version, or the [#point9.6.7 Changelog]:
+This program requires microsoft visual basic runtime files to operate.
+Once you have made a Translation you may upload the translation po files to the aaf forum for implementation into TitanNit.
+If you think you can help with a translation please do so at the end of this page there is information on ([#point9.6.5 Submission]).
+[[br]]
+----
+'''Features''' ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+* load po file from svn __"File/ Open Source (svn)"__
+* Import po file from svn or local as source __"File/ Import Titan.po"__
+* open local file as target__"File/ Open target (local)"__
+* save target file __"File/ Save Target"__
+* save target file as titan.po __"File/ Save titan.po"__
+* export msg string for external use __"File/ Export msgstr as Titan.po"__
+* Build reciever translation file __"File/ Build Titan.mo"__
+* export sourcefile to target __"Edit/ target.po -> target"__
+* view source target differences __"Edit/ diff target - titan.po"__
+[[br]]
+----
+'''Functions'''  ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+''Select an item to view more info:''
+* ([#point9.6.1 Loading a translation from svn])
+* ([#point9.6.2 Loading a Translation from a local directory])
+* ([#point9.6.3 Import Translation from svn or local (Source/ Target Mode)])
+* ([#point9.6.4 Edit Translation])
+* ([#point9.6.5 Submission])
+* ([#point9.6.6 Local Testing])
+----
+'''Loading a translation from svn''' [=#point9.6.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+To load a translation from the server SVN repo select the translation file from the menu: [[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/open_server.jpg)]] [[br]]
+it will then start downloading from the internet.[[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/loading_server.jpg)]] [[br]]
+[[br]]
+([#point9.6 Top of Page])
+[[br]]
+----
+'''Loading a Translation from a local directory''' [=#point9.6.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+To load a translation from the local directory select the translation file from the menu: [[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/open_local.jpg)]] [[br]]
+[[br]]
+([#point9.6 Top of Page])
+[[br]]
+----
+'''Import Translation from svn or local (Source/ Target Mode)'''[=#point9.6.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+To import a translation from svn or the local directory select the translation file from the menu: [[br]]
+Note: for this to work a source file must be loaded first [[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/import_file.jpg)]] [[br]]
+[[br]]
+you will then be dispalyed with this view to view the two po files along side each other:
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/import_list_view.jpg)]] [[br]]
+[[br]]
+you can then select __"Edit/ diff target - titan.po"__ to view the source and target differences.
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/diff_target.jpg)]] [[br]]
+[[br]]
+you can also automatically merge the source files to the target file  by selecting __"Edit/ target.po -> target"__
+[[br]]
+([#point9.6 Top of Page])
+[[br]]
+----
+'''Edit Translation''' [=#point9.6.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+Now that it is loaded you may edit the msgid strings to suit your language and upload to the aaf forum.
+you may use the buttons on the lower taskbar to search for strings you wish to edit.[[br]]
+[[Image(source:/wiki/Wiki-Pictures/NL/TLE/edit.jpg)]]
+[[br]]
+([#point9.6 Top of Page])
+[[br]]
+----
+'''Submission'''[=#point9.6.5]  ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+If you could submit your completed translation file into the thread below for comitting by the devs into svn.
+please note that some translations may no be able to be imported into some receivers due to memory constarints.
+[http://www.aaf-digital.info/forum/showthread.php?98565-TitanNitLanguageEditor forum Link]
+[[br]]
+([#point9.6 Top of Page])
+[[br]]
+----
+'''Local Testing''' [=#point9.6.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+If you wish to install your modified language files into your reciever for testing you can so by exporting you file an a titan.mo file you can do this by selecting __"File/ Build Titan.mo"__ for this to work you need to install some aditional components  in to the program directory.
+To do this create a folder in the program directory called __"gettext"__ and extract the below files into that directory:
+[http://ftp.informatik.rwth-aachen.de/ftp/pub/gnu/gettext/gettext-runtime-0.13.1.bin.woe32.zip gettext-runtime] [[br]]
+[http://ftp.informatik.rwth-aachen.de/ftp/pub/gnu/libiconv/libiconv-1.9.1.bin.woe32.zip libiconv] [[br]]
+[http://ftp.informatik.rwth-aachen.de/ftp/pub/gnu/gettext/gettext-tools-0.13.1.bin.woe32.zip gettext-tools] [[br]]
+Once you have exported your titan.mo file you may ftp or manually copy it onto your Receiver to test it.
+The file needs to go into the directory and a reboot neede to be proformed afterwards:  '''/var/usr/local/share/titan/po/__??__/LC_MESSAGES/titan.mo)''' where __??__ is the language file you are editing.
+''Note: if you have trouble exporting the translation to a mo file place the program directory on the root of your harddisk it can some times fail if the program it too deep in the file system''
+[[br]]
+([#point9.6 Top of Page])
+[[br]]
+----
+'''Change log''' [=#point9.6.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+Version 0.7 :
+ * Loading and saving is now Uniformly in UTF- 8! Now special characters can be used from other languages.
+Version 0.8 :
+ * minor changes
+ * 'Build titan.mo ' for more infomation see ([#point9.6.6 Local Testing])
+Version 0.8.1 :
+ * 1 Column now displays the line number of the msgid
+ * 'Build titan.mo ' - in case of error in a makeMo.cmd Prog -Dir is created at the (click ) is probably better to see what 's going on
+ * 'Edit / show only diff ' - same entries appear at msgid <> titan.po from
+Version 0.8.2 :
+ * Fixed tooltip error
+Version 0.9.0 :
+ * Fixed Error 13 - Thanks to Channel beta-testing
+ * 'Import 2 po file ' to load an alternate po -files
+ * ' titan.po -> Target' copied now empty fields Double entry copied by msgid
+version 0.9.1 :
+ * svn version is displayed and saved as ' .... po.55555.svn '
+ * thus can also be compared with an old ( stored ) version
+[[br]]
+([#point9.6 Top of Page])
+[[br]]

wiki/pages/nl/File-Browser

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.2.5 File Browser''' [=#point3.2.5] ([wiki:Interface-Operation#point3.2 Media Center (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>Menu Picture place holder:
+>
+>[[Image(http://sbnc.dyndns.tv/trac/export/26462/wiki/Wiki-Pictures/NL/file_manager.jpg)]][[br]]
+>
+>Here you can browse files from any source available from your decoder (local or network)
+> you may do such things as copy delete and move.
+[[br]]

wiki/pages/nl/Filesystem-Check

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.5.5.1 File system Check''' [=#point3.5.5.1] ([WikiStart#point3.5 System (Back])
+>
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/Filesystem-Check.jpg)]][[br]]
+>
+Here you can format your harddisk select an item and follow the onscreen prompts.
+[[br]]
+[[BR]]

wiki/pages/nl/Format-Hdd

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.5.5 Hard Disk''' [=#point3.5.5] ([wiki:Interface-Operation#point3.5 system (Back)])
+>
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/Format-Hdd.jpg)]][[br]]
+>
+Here you can format your harddisk select an item and follow the onscreen prompts.
+Note that you must enable ([wiki:Adjust#point3.6.7 Expertmode]) to show all available format options in this display.
+[[br]]
+[[BR]]

wiki/pages/nl/Free-Space

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.7.8.2 Free Space''' [=#point3.7.8.2] ([wiki:System-Info#point3.7.8 System Info (Back])
+>
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/Free-Space.jpg)]][[br]]
+>
+Here you can view the free space of all the file systems acessable from the decoder.
+[[br]]
+[[br]]

wiki/pages/nl/Functions

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''2 Interface Elements''' [=#point2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+This section will show the functions and controls of the various elements in the gui within TitanNit and discriptions to the various
+items and their functions aswell as helpfull information and tricks to get the most possible experience with your Receiver.
+Note: pictures in this area only apply to the default skin used in Titan.
+If you do not see a specific menu item on the display please select the default skin from the menu as follows all the functions displayed below are implemented in all skins but some elements may be omitted from the display in some skins:
+ Press the __"Menu"__ button and select __"Settings"__ scroll down to __"Skin"__ and select the __"Default"__ Skin from the menu.
+ The decoder will then reboot with the new selected __Default__ skin.
+----
+{{{#!div style="width: 1100px; margin: auto"
+ {{{#!table style="border: none"
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Infobar.png,align=left,link=[#point2.1])]]
+  }}}
+  '''[#point2.1 infobar]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Info__ button while watching TV.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/playback_infobar.png,align=left,link=[wiki:History#point2.2 TitanNit Info])]]
+  }}}
+  '''[#point2.2 Playback infobar]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Info__ button while watching A recording or Media using the default player.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/AudioTracks_infobar.png,align=left,link=[#point2.3])]]
+  }}}
+  '''[#point2.3 Audiotracks infobar]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Audio__ button while watching TV, A recording or Media using the default player.
+  }}}
+  }}}
+  |----
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Channel History.png,align=left,link=[#point2.4])]]
+  }}}
+  '''[#point2.4 Channel History]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Recall__ button while watching A recording or Media using the default player.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Sleep_Timer.png,align=left,link=[#point2.5])]]
+  }}}
+  '''[#point2.5 Sleep Timer]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Sleep_ button while the decoder is in operation.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/Subtitle.png,align=left,link=[#point2.6])]]
+  }}}
+  '''[#point2.6  Subtitle]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Subtitle__ button while watching TV, A recording or Media using the default player.
+  }}}
+  }}}
+  |----
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/EPG.png,align=left,link=[#point2.7])]]
+  }}}
+  '''[#point2.7 EPG]'''[[br]]
+ {{{#!div style="float: left
+Default display when pressing the __EPG__ button while watching TV.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/program_info.png,align=left,link=[#point2.8])]]
+  }}}
+  '''[#point2.8 Program Info]'''[[br]]
+   {{{#!div style="float: left
+Default display when pressing the __Info__ button while viewing the EPG.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/player.png,align=left,link=[#point2.9])]]
+  }}}
+  '''[#point2.9 Player]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __Play_ button.
+  }}}
+  }}}
+  |----
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/favourite.png,align=left,link=[#point2.10])]]
+  }}}
+  '''[#point2.10 Favourite]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __FAV__ button.
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Functions/record.png,align=left,link=[#point2.11])]]
+  }}}
+  '''[#point2.11 Record]'''[[br]]
+  {{{#!div style="float: left
+Default display when pressing the __REC__ button while watching TV.
+  }}}
+  }}}
+ }}}
+}}}
+----
+[[BR]]
+'''Infobar''' [=#point2.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Info-OSD.jpg)]] [[br]]
+This overlay display shows when you press the __"INFO"__ button when viewing a tv channel. [[br]]
+It shows actual and next program information
+[[br]]
+'''Playback Infobar''' [=#point2.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Playback-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"INFO"__ button when playing back a program or time shift is in operation. [[br]]
+It shows a list of the available buttons to use when in playbac/timeshift to do various things.
+[[br]]
+'''Audio Track''' [=#point2.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Audio-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"AUDIO""__ button when viewing a tv channel. [[br]]
+It allows you to adjust the audio track on the current stream if an alternative audio source exists.
+[[br]]
+'''History''' [=#point2.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/History-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"RECALL"__ button when viewing a tv channel. [[br]]
+It allows you to recall the past viewed channels for fast zapping between them.
+[[br]]
+'''Sleep Timer''' [=#point2.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Sleep-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"SLEEP"__ button. [[br]]
+It allows you to set the shutdown timer to automatically shutdown the receiver.
+[[br]]
+'''Subtitle''' [=#point2.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Subtitle-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"SUBTITLE"__ button. [[br]]
+It allows you to select/enable a subtitle during playback.
+[[br]]
+'''EPG''' [=#point2.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/EPG-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"EPG"__ button. [[br]]
+It shows a list of the program information from here you can setup a timer or search the EPG.
+[[br]]
+'''Program Info''' [=#point2.8] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Program-Info-OSD.jpg)]] [[br]]
+This Overlay shows when you press the __"INFO"__ button when in the EPG display. [[br]]
+This shows the current selected program information.
+[[br]]
+'''Player''' [=#point2.9] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Internal-Player-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"PLAY"__ button. [[br]]
+It allows you to select a movie or recording to play it also has a basic file manager.
+[[br]]
+'''Favourite''' [=#point2.10] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Favourite-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"FAV"__ button. [[br]]
+It allows you to brouse through your favourits lists.
+[[br]]
+'''Record''' [=#point2.11] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+[[Image(source:/wiki/Wiki-Pictures/NL/Record-OSD.jpg)]] [[br]]
+This overlay shows when you press the __"RECORD"__ button. [[br]]
+It allows you to set the record function on the current tv channel.
+[[br]]

wiki/pages/nl/Git-Changelog

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.7.7 GIT Changelog''' [=#point3.7.7] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>Menu Picture place holder:
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/Git_Changelog.jpg)]][[BR]]
+>
+> here you can git information.
+[[br]]

wiki/pages/nl/Graphic-EPG

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.1.3 Graphic EPG''' [=#point3.1.3] ([wiki:Interface-Operation#point3.1 Records and EPG(Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>Menu Picture place holder:
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/Graphical_EPG.jpg)]][[BR]]
+>
+Graphic EPG is a multi channel graphical EPG.
+[[br]]
+ '''Coloured and Extra Button's Functions"
+ The __"Coloured and Extra Buttons"__ along the bottom of the display bring up additional menus and options with in the Single EPG menu.
+ please see below for more info on the functions of these buttons:.
+ ||'''Red Button: (Timer)''' ||This will bring up the recording timer menu to set up a timer.||
+ ||'''0 key (EPG Search):''' ||This will search the EPG for text you specify and bring up a list of matches where you may press the red button to set up a timer.||
+ ||'''FAV Button: (Favourite)''' ||This will bring up Favourite Boquet menu to select the EPG you would like to display.||
+ ||'''Info Button: (Info)''' ||This will bring up the selected program's EPG info string.||
+For information on setting up a timer Recording using the red button see ([WikiStart#point103.10.6 Records]) for more info.
+For information on setting proforming an EPG search using the 0 Key see ([WikiStart#point103.10.5 EPG Search]) for more info.

wiki/pages/nl/HTTP-Settings

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.5.4.6 HTTP Settings''' [=#point3.5.4.6] ([wiki:Interface-Operation#point3.5.1 network (Back])
+>
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/HTTP-Settings.jpg)]][[br]]
+>
+Here you can setup your HTTP interface.
+[[br]]
+||'''Start HTTPD:''' ||Start the webserver.||
+ ||'''User:''' ||Sets the zoom level of the EPG to show more or less of a time span of the shown programs.||
+ ||'''Password:''' ||Set to yes to use picons or the alternative Picon sets in the infobar and EPG stored in /var/media/autofs/sda1/swapextensions/usr/local/share/titan/picons/ directory.||
+ ||'''HTTPD Port:''' ||Should the EPG be deleted before a the timed scan.||
+ ||'''IP for Stream:''' ||Behavior after the EPG scan is completed EPG scan: Nothing (Stand-By) or Switch Off (Deep Stand-By).||
+ ||'''Stream Port:''' ||Scan for a Media Highway EPG stream during EPG scan.||
+ ||'''Start RGUID:''' ||Scan for a Media Highway version 2 EPG stream during  EPG scan.||
+ ||'''RGUID Port''' ||Scan for an OpenTV EPG stream during EPG scan.||
+ To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
+[[br]]
+----
+ '''Coloured Button's Functions"
+ The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
+ please see below for more info on the functions of these buttons:.
+ ||'''Text Button: (Keyboard)''' ||This will bring up the onscreen keyboard to edit the currently selected test string.||

wiki/pages/nl/Hard-Disk

-                      r40540
+                      r40542
+[[TranslatedPages]]
+>----
+>'''3.5.5 Hard Disk''' [=#point3.5.5] ([wiki:Interface-Operation#point3.5 System (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>Menu Picture place holder:
+>
+>[[Image(source:/wiki/Wiki-Pictures/NL/system-Hard_Disk.jpg)]][[BR]]
+>
+Here you can configure your harddisk.[[BR]]
+please select a menu item for more information.
+[[br]]
+ * ([wiki:Format-Hdd#point3.5.5.1 Format HDD])
+ * ([wiki:Filesystem-Check#point3.5.5.2 Filesystem Check])
+ * ([wiki:Configure#point3.5.5.3 Configure])
+ * ([wiki:Time-to-sleep#point3.5.5.4 Time to sleep])
+[[BR]]

wiki/pages/nl/History

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''1 TitanNit Info Contents ''' [=#point1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+This section conatins information on TitanNit and frequently asked questions about it.
+Please choose an item below to find more information.
+You may select a skip to a specific setup topic or scroll down to read the complete guide.
+{{{#!div style="width: 1100px; margin: auto"
+ {{{#!table style="border: none"
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/About.png,align=left,link=[#point1.1])]]
+  }}}
+  '''([#point1.1 About])'''[[br]]
+  {{{#!div style="float: left
+click here to find info about TitanNit
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/History.png,align=left,link=[#point1.2])]]
+  }}}
+  '''([#point1.2 History])'''[[br]]
+  {{{#!div style="float: left
+click here to find info on the beginnings of TitanNit
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/Features.png,align=left,link=[#point1.3])]]
+  }}}
+  '''([#point1.3 Features])'''[[br]]
+  {{{#!div style="float: left
+click here to find info on the various features of TitanNit
+  }}}
+  }}}
+}}}
+}}}
+{{{#!div style="width: 1100px; margin: auto"
+ {{{#!table style="border: none"
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/History/Frequnetly_Asked_Questions.png,align=left,link=[#point1.4])]]
+  }}}
+  '''([#point1.4 Frequently Asked Questions])'''[[br]]
+  {{{#!div style="float: left
+Apendixcies/ references [[br]]to other setup related topics.
+  }}}
+  }}}
+}}}
+}}}
+[[br]]
+[[br]]
+----
+'''1 About''' [=#point1.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+TitanNit is a semi closed source replacement operating system for kathrein and Atemio/Atevio digital set top receivers.
+It has come about  as the users/devs wanted something better than was currently available.
+TitanNit is spawned from other projects and is developed by users come devs so it is easy of use but yet still remains powerfull and configurable and feature packed.[[br]]
+[[br]]
+[[br]]
+----
+'''1 History''' [=#point1.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+ * Everything started in April 2011. For almost three weeks our Developer Nit secretly worked on the foundation of Titan. After the presentation by Nit Obi and the rest of the team came on board. Everybody was surprised by the rapid development of the Titan Project.
+ * From the beginning the development and source of Titan was nonpublic, as it was not to be foreseen in which direction the development would go.
+ * After a development period of 6 months our hardware manufacturer Atemio declared interest in the project. Looking back at Years of support through Atemio with the Enigma2 Software, Atemio was given main priority for Titan project.
+ * A six-months agreement with Atemio was signed in December 2011.
+ * Due to the good cooperation the agreement was extended and is still in force.
+ * The basic idea for this project originated for various reasons:
+  * due to the missing Python Chip and low CPU speed the sh4 receivers have always had problems with Enigma2.
+  * the constant improvement and expansion of Enigma2 and the TDT Git was comprehensive and time-consuming.
+  * the alternative Neutrino GIT at that time was not layed out to support twin tuner Receivers.
+  * Nit then decided to combine both, the Enigma2 and the Neutrino, to a new Gui which implemented all advantages of both systems.
+  * Neutrinos main advantage has always been its speed
+  * Enigma2s advantage was the ease of integration and expansion with skins and extensions
+  * These two systems combined into one new system was the basic idea of Titan.
+[[br]]
+[[br]]
+----
+'''2 Features''' [=#point1.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+'' Highlights of TitanNit ''
+     - Powerful Linux operating system
+     - Fast boot
+         - About 1 second from standby mode
+         - About 25 seconds from the deep standby mode
+     - Fast channel switching times (less than 1 second)
+     - Different menu interfaces (skins) including customization options
+     - Many options to customize the system to your needs
+     - Backup / Restore function
+     - Organized Favourites and Channel listings and the direct list of following Programs.
+     - Multi-Tuner
+     - Plug-in management
+     - Supports many media formats
+     - Wide range of plugins
+     - PC programs to personalize and convert the channel list
+     - Screen saver in radio mode
+     - Remote control buttons freely assignable
+     - Online update of the firmware with the ability to retain settings
+     - Low memory consumption
+     - 24 hour Forum Support
+     - Growing Community
+     - Web Interface
+     - Android app "timote"
+     - Windows App "tiView"
+     - Bouquets Editor "SatchannelListEditor"
+[[br]]
+----
+'''Frequently Asked Questions''' [=#point1.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+[[br]]
+'''What is Titan?'''[[br]]TitanNit is a semi closed source replacement operating system for kathrein and Atemio/Atevio digital set top receivers designed to completly replace the factory software.
+[[br]]
+'''What can Titan do?'''[[br]]Titan was primarally designed to play/view and record live tv services from tresterial, cable and satellite, it can also be used to play/view the most popular video, audio, and picture formats, and many more lesser-known formats, including:
+ Video - DVD-Video, VCD/SVCD, MPEG-1/2/4, DivX, XviD, Matroska
+Audio - MP3, AAC.
+Picture - JPG, GIF, PNG.
+These can all be played directly from the hard-drive or from a computer over a local network (LAN) internet IPTV services and media streams hosted by the [[wiki:Plugins-Player#point10.11 TiThek]] plugin.
+ TitanNit can play DVD-Video movies (with and without menus) from ISO/IMG images and even ZIP/RAR-archives with the use of the [[wiki:Plugins-Player#point10.11 dvd-player plugin]].
+ TitanNit has a simple user interface that's pleasant and easy to use.
+All these features enable your device to function as a full multimedia entertainment system for your tv for the whole family to enjoy.
+[[br]]
+[[br]]
+'''What features does TitanNit have?'''[[br]]See the complete list of supported features in the [[wiki:Versions#point6 software versions changelog]] for information of the offically supported features.
+[[br]]
+[[br]]
+'''Where can I suggest/request a new feature or function to be implemented into TitanNit?'''[[br]]You can log a NEW feature/function request in our tracker. Just make sure that you first remember to search for existing "Feature Requests" before logging a new request/ticket! (see [wiki:Troubleshooting#point12.1 12.1 Bug Reporting] for information on submitting a ticket).
+You may also post a copy of your suggestion in the feature-suggestion section of our [http://www.aaf-digital.info/forum/forum.php AAF Digital Forum] if you want it open for discussion,
+Please respect that your request only counts as a suggestion, there' s no guarantee that it will implemented soon or ever.
+Almost all users think their own ideas is the most important, and a very common comment is: "if you only add these features then TitanNit will be perfect for me".
+You could try bribing the devs with elaborate gifts :-) flattery will get you every where and agorant requests will most likely get your posts deleted or get you banned from the forum please follow the rules of the forum [http://www.aaf-digital.info/ here].
+[[br]]
+[[br]]
+'''When will this and that feature or function be supported by TitanNit?'''[[br]]TitanNit development is driven by the tasks that are important to the individual developers and to the hardware sponsors Atemio, if you have a funky idea or feature you wish implemented submit a request ticket (see [wiki:Troubleshooting#point12.1 12.1 Bug Reporting], but make an extensive search of the forum and tickets before requesting it as it has probally been sugested before.
+[[br]]
+[[br]]
+'''Is TitanNit, or the AAFTeam affiliated with Fortis, katherin or ..... or the hardware manufacturer of my Reciever?'''[[br]]No, TitanNit and its members are not in any way affiliated with the manufactures in any way. TitanNit is a third party operating system designed to replace the manufactures original operating system.
+[[br]]
+[[br]]
+'''Will the instalation of Titan Void my Warranty?'''[[br]]Yes probally but this software is tested to ensure it won't dammage your reciever and can be reverted at any time to a factory condition. please see [wiki:Supported-Receivers#point7 Supported Receivers] for a list of suspected supported receivers, If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated and verified.
+If the factory software was so feature packed and bugless there would be no need for software like TitanNit but sadly this is a world where software is driven by sales and purchases by the big players who request features, but TitanNit is a little different it was started just because the users/ devs wanted something better than what was handed to them by the manufacturer.
+[[br]]
+[[br]]
+'''Why is TitanNit Not available for my receiver model XXX?'''[[br]]TitanNit is funded by Atemio who supplys hardware to the devs in return for developing software for use on these devices.
+In future TitanNit may be available for your receiver as support in increaced, at this time Titan in in development for the Broadcom Mips Archeture for the upcomming release of the Atemio 5200 which will be the first non SH4 based reciever supported by TitanNit.
+[[br]]
+[[br]]
+'''How do I ...'''[[br]] I don't know I suggest you read the [wiki:Quick-Start-Guide#point0 Quick Start Guide], manual, check the rest of the wiki or proform a [http://www.aaf-digital.info/forum/search.php?search_type=1 search] on the forum, as it has most likely been asked before and you will find the answer, as a last resort post a question on the [http://www.aaf-digital.info/forum/forum.php AAF Digital Forum].
+[[br]]
+[[br]]
+'''Where should I put videos/music and pictures so that Titan can read it?''' [[br]]Anywhere you like. TitanNit can read off the local harddisk,usb sticks, or from network sources. Simply press "Add a Source" using the network Browser and browse away.
+>[[Image(source:/wiki/Wiki-Pictures/NL/Network-Browser.jpg, 25%)]][[br]]
+[[br]]
+[[br]]
+'''What is the default username and password to the built-in FTP server and telnet server?'''Both the default password and the user name is “root” (in lower case) as with many linux instalations.
+[[br]]
+[[br]]
+'''Can I watch recordings from my decoder when on holiday?'''[[br]]yes you can you will need to set up either a static ip on your home network or set up a dynadns server, from there you can log onto the web interface and use video lan to watch tv or your recordings.
+[[br]]
+[[br]]
+'''Can I thank and or Chat the TitanNit team?''[[br]]Yes sure you can jump on the [[http://www.aaf-digital.info/forum/ AAFforum]]  and leave a post and or stop by [wiki:Contact#point15 Skype] and request a invite the majority of us speak german, some of us speak english also.
+'''Do you accept donations?'''[[br]] the team is currently fully funded and no donations are nesessary but if you have some device that may be of use with titan feel free to contact us.
+'''How come the Wiki does not show how to operate feature or function.....?'''[[br]]Titan Is in development and is updated almost daily some features plugins or informations have yet to be merged in, this forum is open to editing by the community feel free to log in and add said feature's informatation to the wiki.
+[[br]]
+[[br]]
+([#point1 Top of Page])

wiki/pages/nl/Installation-Recovery

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''8 Installation and Recovery Contents''' [=#point8] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+This section contains information on installation and removal of TitanNit from your receiver
+{{{#!div style="width: 1100px; margin: auto"
+ {{{#!table style="border: none"
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Atemio.png, 60px,align=left,link=http://www.atemio.de Atemio homepage)]]
+  }}}
+  '''SH4 Atemio'''[[br]]
+  {{{#!div style="float: left
+ [http://www.atemio.de Atemio homepage]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.000 Contents]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.001 Atemio510]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.002 Atemio520]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.003 Atemio530]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.004 Atemio7600]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.005 Atemio700]
+ * [wiki:Installation-Recovery-SH4-Atemio#point8.006 Atemio7000]
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Fortis.png, 60px,align=left,link=http://www.fortis.co.kr Fortis homepage)]]
+  }}}
+  '''SH4 Fortis'''[[br]]
+   {{{#!div style="float: left
+ [http://www.fortis.co.kr Fortis homepage]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.010 Contents]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.011 Fortis Clone]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.012 Bootloader Installation]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.013 Fortis FS-9000]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.014 Fortis FS-9200]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.015 Fortis HS-9510]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.016 Fortis HX-8200]
+ * [wiki:Installation-Recovery-SH4-Fortis#point8.017 Fortis HS-7810]
+  }}}
+  }}}
+ {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/homecast.png, 60px,align=left,link=http://www.myhomecast.nl Homecast homepage)]]
+  }}}
+  '''SH4 Homecast'''[[br]]
+ {{{#!div style="float: left
+ [http://www.myhomecast.nl Homecast homepage]
+ * [wiki:Installation-Recovery-SH4-Homecast#point8.020 Contents]
+ * [wiki:Installation-Recovery-SH4-Homecast#point8.021 Homecast Pro]
+  }}}
+  }}}
+  |----
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/IPBox.png, 60px,align=left,link=http://www.abipbox.com/ AB IPBox homepage)]]
+  }}}
+  '''SH4 IPBox'''[[br]]
+  {{{#!div style="float: left
+ [http://www.abipbox.com/ AB IPBox homepage]
+ * [wiki:Installation-Recovery-SH4-IPBox#point8.030 Contents]
+ * [wiki:Installation-Recovery-SH4-IPBox#point8.031 Ipbox91]
+ * [wiki:Installation-Recovery-SH4-IPBox#point8.032 Ipbox900]
+ * [wiki:Installation-Recovery-SH4-IPBox#point8.033 Ipbox910]
+ * [wiki:Installation-Recovery-SH4-IPBox#point8.034 Ipbox9000]
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/kathrein.png, 60px,align=left,link=http://www.kathrein-gmbh.at kathrein homepage)]]
+  }}}
+  '''SH4 Katherin'''[[br]]
+  {{{#!div style="float: left
+ [http://www.kathrein-gmbh.at kathrein homepage]
+ * [wiki:Installation-Recovery-SH4-Katherin#point8.040 Contents]
+ * [wiki:Installation-Recovery-SH4-Katherin#point8.041 Ufs910]
+ * [wiki:Installation-Recovery-SH4-Katherin#point8.042 Ufs912]
+ * [wiki:Installation-Recovery-SH4-Katherin#point8.043 Ufs913]
+ * [wiki:Installation-Recovery-SH4-Katherin#point8.044 Ufs922]
+ * [wiki:Installation-Recovery-SH4-Katherin#point8.045 Ufc960]
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Spark.png, 60px,align=left,link=http://www.spark-tv.com Spark homepage)]]
+  }}}
+  '''SH4 Spark'''[[br]]
+  {{{#!div style="float: left
+ [http://www.spark-tv.com Spark homepage]
+ * [wiki:Installation-Recovery-SH4-Spark#point8.050 Contents]
+ * [wiki:Installation-Recovery-SH4-Spark#point8.051 Spark7111]
+ * [wiki:Installation-Recovery-SH4-Spark#point8.052 Spark7162]
+  }}}
+  }}}
+  |----
+ {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Atemio.png, 60px,align=left,link=http://www.atemio.de Atemio homepage)]]
+  }}}
+  '''Mips Atemio'''[[br]]
+  {{{#!div style="float: left
+ [http://www.atemio.de Atemio homepage]
+ * [wiki:Installation-Recovery-Mips-Atemio#point8.060 Contents]
+ * [wiki:Installation-Recovery-Mips-Atemio#point8.061 Atemio5000 AKA Nemesis]
+ * [wiki:Installation-Recovery-Mips-Atemio#point8.062 Atemio5200]
+ * [wiki:Installation-Recovery-Mips-Atemio#point8.063 Atemio6000]
+ * [wiki:Installation-Recovery-Mips-Atemio#point8.064 Atemio6100]
+ * [wiki:Installation-Recovery-Mips-Atemio#point8.065 Atemio6200]
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/beyonwiz.png, 60px,align=left,link=http://www.beyonwiz.com.au Beyonwiz homepage)]]
+  }}}
+  '''Mips Beyonwiz'''[[br]]
+ {{{#!div style="float: left
+ [http://www.beyonwiz.com.au Beyonwiz homepage]
+ * [wiki:Installation-Recovery-Mips-Beyonwiz#point8.070 Contents]
+ * [wiki:Installation-Recovery-Mips-Beyonwiz#point8.071 BeyonwizT4]
+  }}}
+  }}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Goldern_Interstar.png, 60px,align=left,link=http://www.golden-interstar.pl Golden Interstar homepage)]]
+  }}}
+  '''Mips Golden Interstar'''[[br]]
+  {{{#!div style="float: left
+ [http://www.golden-interstar.pl Golden Interstar homepage]
+ * [wiki:Installation-Recovery-Mips-Golden-Interstar#point8.080 Contents]
+ * [wiki:Installation-Recovery-Mips-Golden-Interstar#point8.081 Xpeedlx1/2]
+ * [wiki:Installation-Recovery-Mips-Golden-Interstar#point8.082 Xpeedlx3]
+  }}}
+  }}}
+  |----
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Miraclebox.png, 60px,align=left,link=http://www.miraclebox.se miraclebox homepage)]]
+  }}}
+  '''Mips Miraclebox[[br]]
+  {{{#!div style="float: left
+ [http://www.miraclebox.se Miraclebox homepage]
+ * [wiki:Installation-Recovery-Mips-Miraclebox#point8.090 Contents]
+ * [wiki:Installation-Recovery-Mips-Miraclebox#point8.091 MBUltra]
+ * [wiki:Installation-Recovery-Mips-Miraclebox#point8.092 MBMini]
+}}}
+}}}
+  {{{#!td align=center valign=top style="border: none; font-size: 115%"
+  {{{#!div style="float: left"
+[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Receiver_logo/Sezam.png, 60px,align=left,link=http://www.sezam-club.ru/ homepage)]]
+  }}}
+  '''Mips Sezam'''[[br]]
+ {{{#!div style="float: left
+ [http://www.sezam-club.ru/ Mips Sezam homepage]
+ * [wiki:Installation-Recovery-Mips-Sezam#point8.100 Contents]
+ * [wiki:Installation-Recovery-Mips-Sezam#point8.101 Sezam-Marvel]
+ * [wiki:Installation-Recovery-Mips-Sezam#point8.102 Sezam-1000HD]
+  }}}
+  }}}
+}}}
+}}}
+----
+'''8.113 IRD Download Locations''' [=#point8.113] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main Page])
+----
+* [wiki:Manufactures#point13 13 Manufactures] - [http://atemio.de/index.php/software-updates Stable Images][[br]]
+* [wiki:Community#point14 14 Community] - [http://www.aaf-digital.info/forum/downloads.php?do=cat&id=2 Stable Images] [http://www.aaf-digital.info/forum/pages.php?pageid=12 Nightly Images][[br]]
+  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
+* [http://sbnc.dyndns.tv/trac/wiki/en/Remote-Device-Control#point4.6  iboot sh4 loader flashing and recovery ][[br]]
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-Mips-Atemio

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''8.061 Mips Atemio''' [=#point8.061] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+manufacturer blurb.....
+----
+'''8.061 Atemio-Nemesis''' [=#point8.061] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 5000 Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.062 Atemio5200''' [=#point8.062] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 5200 Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.063 Atemio6000''' [=#point8.063] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 6000 Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.064 Atemio6100''' [=#point8.064] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 6100 Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.065 Atemio6200''' [=#point8.065] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 6200 Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-Mips-Beyonwiz

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''8.071 Beyonwiz''' [=#point8.070] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+manufacturer blurb.....
+----
+'''8.071 Beyonwiz T4''' [=#point8.071] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Beyonwiz T4 Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-Mips-Golden-Interstar

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''8.080 Goldern interstar Xpeedlx1/2''' [=#point8.080] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
+----
+manufacturer blurb
+----
+'''8.081 Goldern interstar Xpeedlx1/2''' [=#point8.081] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
+----
+''How do I install a Xpeedlx1/2 update image? ''
+ * Visit the AAF digital forum and download the latest TitanNit firmware . ([#point8.33 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped firmware folder "xpeedlx3"  to a formatted FAT32 USB stick.
+    Note: The USB stick should not be formatted with windows, but a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program). Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the update image file
+ * Switch on (mains switch) and and when prompted on the vfd press the __Volume up__ button on the unit, then the installation begins. after the update starts release the __volume up__ button.
+Note: If installation does not start, use a different USB stick.
+•After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.082 goldern interstar Xpeedlx3''' [=#point8.082] ([wiki:Wiki#point0 Inhaltsverzeichnis]) ([WikiStart#point0 Sprachauswahl])
+----
+''How do I install a Xpeedlx3 update image? ''
+ * Visit the AAF digital forum and download the latest TitanNit firmware . ([#point8.33 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped firmware folder "xpeedlx3" to a formatted FAT32 USB stick.
+    Note: The USB stick should not be formatted with windows, but a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program). Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the update image file
+ * Switch on (mains switch) and and when prompted on the vfd press the __Volume up__ button on the unit, then the installation begins. after the update starts release the __volume up__ button.
+Note: If installation does not start, use a different USB stick.
+•After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-Mips-Miraclebox

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''8.090 Miraclebox''' [=#point8.090] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+manufacturer blurb......
+----
+'''8.091 Miraclebox Ultra''' [=#point8.091] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Miraclebox Ultra Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.092 Miraclebox Mini''' [=#point8.092] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Miraclebox Mini Update UBI image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+    Note: After unpacking two subfolders atemio/5x00 will be created . The USB stick should not be formatted with windows. Use a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on ( mains plug ) and press the CH + on the unit (1 button from the right ) until the Vfd ( LCD Display) displayes " Flashing ...".
+   then the installation begins, Only then release the button.
+    Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-Mips-Sezam

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''8.100 Sezam-Marvel''' [=#point8.100] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Sprachauswahl])
+----
+manufacturer blurb....
+----
+'''8.101 Sezam-Marvel''' [=#point8.101] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Sprachauswahl])
+----
+''How do I install a Sezam-Marvel  update image? ''
+ * Visit the AAF digital forum and download the latest TitanNit firmware . ([#point8.33 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped firmware folder "enigma2" to a formatted FAT32 USB stick.
+    Note: The USB stick should not be formatted with windows, but a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program). Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the update image file
+ * Switch on (mains switch) and and when prompted on the vfd press the __Volume up__ button on the unit, then the installation begins. after the update starts release the __volume up__ button.
+Note: If installation does not start, use a different USB stick.
+•After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.102 Sezam-1000HD''' [=#point8.102] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Sprachauswahl])
+----
+''How do I install a Sezam-1000HD  update image? ''
+ * Visit the AAF digital forum and download the latest TitanNit firmware . ([#point8.33 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped firmware folder "enigma2" to a formatted FAT32 USB stick.
+    Note: The USB stick should not be formatted with windows, but a separate program, such as the " HP USB Disk Storage Format Tool" (freeware program). Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the update image file
+ * Switch on (mains switch) and and when prompted on the vfd press the __Volume up__ button on the unit, then the installation begins. after the update starts release the __volume up__ button.
+Note: If installation does not start, use a different USB stick.
+•After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-SH4-Atemio

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''SH4 Atemio (Atevio)'''[=#point8.00]
+----
+The SH4 Atemio recievers are manufactured by Fortis who are a Korean manufacturer of satellite receivers all atemio (atevio) models are compatible with TitanNit.
+as TitanNit was developed for these recievers no bootloader software ID changes are required to install TitanNit, some of these models cam factory supplied with TitanNit such as the atemio  530.
+'''SH4 Atemio Contents'''
+ * [#point8.001 8.001 Atemio510]
+ * [#point8.002 8.002 Atemio520]
+ * [#point8.003 8.003 Atemio530]
+ * [#point8.004 8.004 Atemio7600]
+ * [#point8.005 8.005 Atevio700]
+ * [#point8.006 8.006 Atevio7000]
+'''Additional Info'''
+ * [#point8.007 8.007 Uninstallation]
+ * [#point8.008 8.008 Update TitanNit]
+ * [#point8.009 8.009 IRD Download Location]
+----
+'''8.1 Atemio510 and Fortis HS-7810''' [=#point8.001] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 510 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
+* [http://sbnc.dyndns.tv/trac/wiki/en/Remote-Device-Control#point4.6  iboot sh4 loader flashing and recovery ][[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.2 Atemio520''' [=#point8.002] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 520 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
+* [http://sbnc.dyndns.tv/trac/wiki/en/Remote-Device-Control#point4.6  iboot sh4 loader flashing and recovery ][[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.3 Atemio530''' [=#point8.003] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 530 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.4 Atemio7600 and Fortis HX-8200''' [=#point8.004] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 7600 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
+* [http://sbnc.dyndns.tv/trac/wiki/en/Remote-Device-Control#point4.6  iboot sh4 loader flashing and recovery ][[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.5 Atevio700''' [=#point8.005] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 7600 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
+* [http://sbnc.dyndns.tv/trac/wiki/en/Remote-Device-Control#point4.6  iboot sh4 loader flashing and recovery ][[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.6 Atevio7000 and Fortis FS-9000/9200''' [=#point8.006] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 7000 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader sh4 Boxen]'''[[br]]
+* [http://sbnc.dyndns.tv/trac/wiki/en/Remote-Device-Control#point4.6  iboot sh4 loader flashing and recovery ][[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.007 Uninstalling Titan''' [=#point8.007] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+If you have an Atemio (Atevio) receiver all you have to do is install your original ird file as explained above and no bootloader changes are neccessary.
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.008 Update TitanNit''' [=#point8.008] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main Page])
+----
+There are two ways to update your TitanNit version and there are merits to both methods :
+IRD offline method see above [#point8.00 SH4 Atemio contents] and select your Reciever model to show information on how to update titan using an IRD titannit image.
+[[br]]
+''Note: using this method plugins and files stored to Flash will be formatted when the update is proformed.
+Plugins and files installed to MNT (except on the ufs 910/922) or a valid configured storage device will retain there settings .''
+Image Online Method see [wiki:System-Update#point3.5.7 System update] for information on how preform an online update.
+[[br]]
+''Note: using this method all plugins and settings are retained as long as they are not installed in flash.''
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.009 IRD Download Locations''' [=#point8.009] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main Page])
+----
+* [wiki:Manufactures#point13 13 Manufactures] - [http://atemio.de/index.php/software-updates Stable Images][[br]]
+* [wiki:Community#point14 14 Community] - [http://www.aaf-digital.info/forum/downloads.php?do=cat&id=2 Stable Images] [http://www.aaf-digital.info/forum/pages.php?pageid=12 Nightly Images][[br]]
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-SH4-Fortis

-                      r40540
+                      r40542
+[[TranslatedPages]]
+----
+'''SH4 Fortis (hardware profile)'''[=#point8.010]
+----
+Fortis is a Korean manufacture of satellite receivers that have a range of models that are compatible with TitanNit. These receivers were sold around the world to various resellers with customized bootloaders to lock them to a specific sales region, TitanNit installation is possible after the installation of a Atevio compatible bootloader.
+'''SH4 Fortis Contents'''
+ * [#point8.011 8.011 SH4 Fortis based clone receiver detection based on hardware profile]
+ * [#point8.012 8.012 Fortis HS-7810 (Atemio510)]
+ * [#point8.013 8.013 Fortis HX-8200 (Atemio7600)]
+ * [#point8.014 8.014 Fortis HS-9510 (Atevio700)]
+ * [#point8.015 8.015 Fortis FS-9000/9200 (Atevio7000)]
+'''Additional Info'''
+ * [#point8.012 8.016 Bootloader Installation] (required for a fortis/clone reciever to accept atemio software)
+ * [#point8.111 8.017 Uninstallation On other Fortis Receivers]
+ * [#point8.112 8.018 Update TitanNit]
+ * [#point8.113 8.019 IRD Download Location]
+----
+'''SH4 Fortis based clone receiver detection based on hardware profile''' [=#point8.011]
+----
+As it is virtually impossible to list every fortis clone box on this wiki and data would be repeated over and over again it is broken up into harware revisions to compair that to the atevio model of that box.
+This list will help you select the correct image and bootloader for your clone reciever below is a specifications list check the back of your manual included with your receiver and look at the table below to select the correct hardware model.
+See here for a full list of known Fortis ([wiki:Supported-Receivers#point7 Supported Receivers])
+{{{#!div style="width: 1000px; margin: auto"
+||'''Model System'''||'''Tuner'''||'''CPU'''||'''RAM'''||'''ROM (Flash)'''||'''USB'''||'''PVR Funktion'''||'''CardReader'''||'''Common interface'''||'''Display'''||'''Width'''||'''features'''||
+||[#point8.015 Fortis FS-9000 HD PVR]||DVB-S/S2 2||STI_7101 266 Mhz||192MB||32MB||2||Internal 2.5 or 3.5 SATA, external via USB||1 (*2)||2||12-digit 5x7matrix||43 cm|| ||
+||[#point8.015 Fortis FS-9200 HD PVR]||DVB-S/S2 2||STI_7101 266 Mhz||192MB||32MB||2||eSATA & USB||1 (*2)||2||12-digit 5x7matrix||34 cm|| ||
+||[#point8.014 Fortis HS-9510]||DVB-S/S2 1||STI_7101 266 Mhz||192MB||32MB||1||USB||1 (*2)||2||8-digit 14segment||34 cm|| ||
+||[#point8.013 Fortis HX-8200 HD PVR]||DVB-S/S2, DVB-T2, DVB-C 1/2||STI_7105 450 Mhz||256MB||64MB||3||Internal 2,5´´SATA-HDD external via eSATA + USB||2||2||12-digit 5x7matrix||34 cm||Plug&Play Tuner, Youtube, Browser, FreeTV+||
+||[#point8.012 Fortis HS-7810 HD PVR]||DVB-S/S2 1||STI_7110 450 Mhz||256MB||32MB||2||USB||1||2||4-digit 7segment||26 cm||YouTube, Browser, FreeTV+||
+}}}
+'''NOTE:'''[[BR]]
+ * The Fortis HS-7810 is a clone of the Atemio510/520 Models[[BR]]
+ * The Fortis HX-8200 is a clone of the Atemio7600 Model[[BR]]
+ * The Fortis HS-9510 is a clone of the Atemio700 clone Model[[BR]]
+ * The Fortis FS-9000/Fortis FS-9200 is a clone of the Atemio7000 Models
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.1 Fortis HS-7810 (Atemio510)''' [=#point8.012] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 510 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.4 Fortis HX-8200 (Atemio7600)''' [=#point8.013] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Atemio 7600 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.5 Fortis HS-9510 (Atevio700)''' [=#point8.014] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Fortis HS-9510 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.6 Fortis FS-9000/9200 (Atevio7000)''' [=#point8.015] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'' How do I install an Fortis FS-9000/9200 IRD image? ''
+ * Visit the Atemio homepage or the AAF digital forum and download the latest TitanNit firmware . ([#point8.15 IRD Download Locations])
+ * Extract the zip file
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * After successfully installing the receiver will reboot and the installed image should start-up
+[[br]]
+[#point8 Top of Page]
+[[br]]
+'''Aditional Info'''
+----
+'''8.012 installation on other Fortis Receivers'''  [=#point8.016] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+'''Installation Notes:'''
+''If you wish to try or install titan you need to install an Atemio/Atevio factory loader. The original Atemio Bootloader has a security code within so an installation of Titan is not possible with any other fortis loader''
+''If you wish to install Titan the loader version must be 1.54 or above. Titan versions above 1.32 require the new Iboot loader which needs to be installed first if not present.''
+''There are various ways that are explained below:''
+[[br]]
+'''AAF Recovery Tool (ART) method'''
+ * Install the AAF Recovery Tool (ART) and set up a connection to your receiver
+ * Set the IP address and subnet mask of your uboot environment.
+ * Reboot the receiver and reconnect to change the settings.
+ * Install the factory loader and reboot.
+ * The factory loader you installed is version 1.21 that you have to update to 1.54 to be compatible with Titan
+ * Visit the [http:((www-atemio.de Atemio] homepage or the [http://www.aaf-digital.info/forum AAF digital forum] and download the latest Atevio/Atemio loaader (1.54).
+ * Extract the zip file
+  * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     "HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your receiver
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: Should the installation not start, try a different USB stick.
+ * Should you have installed the loader successfully the receiver will reboot and the installed Loader should start-up.
+''You may now install Titan''
+[[br]]
+[#point8 Top of Page]
+[[br]]
+'''Cross Flash Method'''
+''This method explains how to install the HDF bootloader flash plugin to your fortis receiver and flash an Atemio/Atevio compatible bootloader from the plugin menu.''
+* Download the HDF Bootloader flash plugin from the [http://www.aaf-digital.info/forum AAF Digital forum].
+ * Extract the zip file
+ * Now copy the unzipped Plugin folder to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * go to the plugins section in your receiver and install the plugin and then start it.
+ * type in the password contained in the zip file and follow the onscreen prompts.
+ * Should you have installed the loader successfully the receiver will reboot and the installed Loader should start-up.
+''You may now install TitanNit''
+[[br]]
+[#point8 Top of Page]
+[[br]]
+'''Reseller Changer Tool Method'''
+''This method explains how to change the Reseler ID of an Atemio/Atevio compatible bootloader and flash it to any compatible Fortis receiver from the plugin menu.''
+* Visit the [http://www.atemio.de Atemio] homepage or the [http://www.aaf-digital.info/forum AAF digital forum] and download the latest Atevio/Atemio loader.
+ * Extract the zip file
+ * use the reseller ID changer tool and change the IRD to that of your reseller ID.
+ * Now copy the unzipped IRD firmware file to a formatted FAT32 USB stick.
+     Note: The USB stick should not be formatted with windows. Use a separate program, such as the
+     " HP USB Disk Storage Format Tool" (freeware program).
+     Furthermore, we recommend a cheap USB stick with a small storage capacity as well as read and write speed.
+ * Turn off the Receiver and disconnect all USB devices.
+ * Connect the USB stick with the IRD file to your Receiver.
+ * Switch on (mains switch) and at the same time hold the CH + on the unit (about 15 seconds) until "search IRD File ... " appears,
+   and the installation begins. Only then release the button
+     Note: If installation does not start , use a different USB stick.
+ * Should you have installed the loader successfully the receiver will reboot and the installed Loader should start-up.
+This method requires you to also change the reseller ID to be able to install TitanNit.
+'''Be aware should it the installation fail or a loss of Power occur during the flashing process you could brick your receiver as there is no recovery method. Compatibility with other receivers is not guaranteed but you may find a list of compatible receivers in the [wiki:Supported-Receivers#point7 Supported Receivers] section.'''
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.111 Uninstalling Titan''' [=#point8.017] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+----
+If you have an Atemio/Atevio or UFS receiver all you have to do is install your original ird file as explained above and no bootloader changes are neccessary.
+Uninstalling titan and switching back to the original reseller loader can't be done (easily) for other fortis receivers but there is one simple alternative method outlined below.
+'''Uninstalling Titan on non Atemio/Atevio receiver and restore Reseller ID with Maxi-uboot'''
+If you have iboot installed then you must install a version of TitanNit older than 1.32 before using this method.
+This will install the factory Atemio loader that is compatible with the AAF Recovery Tool (ART) to be able to install the Maxiuboot Loader.
+In order for this method to work make sure the setting Allow __"Iboot Update"__ is enabled in [wiki:Remote-Device-Control#point4.6 Iboot].
+When successfully achieved you may start up ART from your PC and install Maxiuboot.
+[[br]]
+Once installed you may set up your bootargs and change your Reseller ID back to its factory settings. For flashin original Firmware or other Software please refere to your receivers' manual or instructions.
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.112 Update TitanNit''' [=#point8.018] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main Page])
+----
+There are two ways to update your TitanNit version and there are merits to both methods :
+IRD offline method see [#point8 Installation / Recovery] and select your Reciever model to show information on how to update titan using an IRD titannit image.
+[[br]]
+''Note: using this method plugins and files stored to Flash will be formatted when the update is proformed.
+Plugins and files installed to MNT (except on the ufs 910/922) or a valid configured storage device will retain there settings .''
+Image Online Method see [wiki:System-Update#point3.5.7 System update] for information on how preform an online update.
+[[br]]
+''Note: using this method all plugins and settings are retained as long as they are not installed in flash.''
+[[br]]
+[#point8 Top of Page]
+[[br]]
+----
+'''8.113 IRD Download Locations''' [=#point8.019] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main Page])
+----
+* [wiki:Manufactures#point13 13 Manufactures] - [http://atemio.de/index.php/software-updates Stable Images][[br]]
+* [wiki:Community#point14 14 Community] - [http://www.aaf-digital.info/forum/downloads.php?do=cat&id=2 Stable Images] [http://www.aaf-digital.info/forum/pages.php?pageid=12 Nightly Images][[br]]
+[[br]]
+[#point8 Top of Page]
+[[br]]

wiki/pages/nl/Installation-Recovery-SH4-Homecast

r40540	r40542
	1	[[TranslatedPages]]
	2	----

Context Navigation

Legend: