Changeset 39712 for wiki

wiki/pages/SandBox

r38413	r39712
1		~~= The Sandbox =~~
2
3		~~This is just a page to practice and learn WikiFormatting.~~
4
5		~~Go ahead, edit it freely.~~

wiki/pages/TicketQuery

-                      r38413
+                      r39712
-= !TicketQuery Wiki Macro
-The !TicketQuery macro lets you display information on tickets within wiki pages.
-The query language used by the `[[TicketQuery]]` macro is described in [TracQuery#UsingtheTicketQueryMacro TracQuery] page.
-== Usage
-[[MacroList(TicketQuery)]]
-== Example
-||= **Example** =||= **Result** =||= **Macro** =||
-|-----------------------------------------------------------
-||=Number of [query:status=new&milestone= Triage tickets]: =||\
-|| **[[TicketQuery(status=new&milestone=,count)]]**||\
-|| `[[TicketQuery(status=new&milestone=,count)]]` ||
-|-----------------------------------------------------------
-||=Number of new tickets: =||\
-|| **[[TicketQuery(status=new,count)]]**||\
-|| `[[TicketQuery(status=new,count)]]` ||
-|-----------------------------------------------------------
-||=Number of reopened tickets: =||\
-|| **[[TicketQuery(status=reopened,count)]]**||\
-|| `[[TicketQuery(status=reopened,count)]]` ||
-|-----------------------------------------------------------
-||=Number of assigned tickets: =||\
-|| **[[TicketQuery(status=assigned,count)]]**||\
-|| `[[TicketQuery(status=assigned,count)]]` ||
-|-----------------------------------------------------------
-||=Number of invalid tickets: =||\
-|| **[[TicketQuery(status=closed,resolution=invalid,count)]]**||\
-|| `[[TicketQuery(status=closed,resolution=invalid,count)]]` ||
-|-----------------------------------------------------------
-||=Number of worksforme tickets: =||\
-|| **[[TicketQuery(status=closed,resolution=worksforme,count)]]**||\
-|| `[[TicketQuery(status=closed,resolution=worksforme,count)]]` ||
-|-----------------------------------------------------------
-||=Number of duplicate tickets: =||\
-|| **[[TicketQuery(status=closed,resolution=duplicate,count)]]**||\
-|| `[[TicketQuery(status=closed,resolution=duplicate,count)]]` ||
-|-----------------------------------------------------------
-||=Number of wontfix tickets: =||\
-|| **[[TicketQuery(status=closed,resolution=wontfix,count)]]**||\
-|| `[[TicketQuery(status=closed,resolution=wontfix,count)]]` ||
-|-----------------------------------------------------------
-||=Number of fixed tickets: =||\
-|| **[[TicketQuery(status=closed,resolution=fixed,count)]]**||\
-|| `[[TicketQuery(status=closed,resolution=fixed,count)]]` ||
-|-----------------------------------------------------------
-||=Total number of tickets: =||\
-|| **[[TicketQuery(count)]]**||\
-|| `[[TicketQuery(count)]]` ||
-|-----------------------------------------------------------
-||=Number of tickets reported **or** owned by current user: =||\
-|| **[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]**||\
-|| `[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]` ||
-|-----------------------------------------------------------
-||=Number of tickets created this month: =||\
-|| **[[TicketQuery(created=thismonth..,count)]]**||\
-|| `[[TicketQuery(created=thismonth..,count)]]` ||
-|-----------------------------------------------------------
-||=Last 3 modified tickets: =||\
-||**[[TicketQuery(max=3,order=modified,desc=1,compact)]]**||\
-|| `[[TicketQuery(max=3,order=modified,desc=1,compact)]]` ||
-|-----------------------------------------------------------
-{{{#!th rowspan=2, style="text-align: left;"
-Details of ticket #1:
-}}}
-{{{#!td style="border-bottom: 0;"
-}}}
-{{{#!td
-`[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]`
-}}}
-|-
-{{{#!td colspan=2, style="border-top: 0;"
-[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]
-}}}
-|-----------------------------------------------------------
-== Using the `[[TicketQuery]]` Macro
-The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
-Example:
-{{{
-[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
-}}}
-This is displayed as:
-  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
-Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language]. This also displays the link and description of a single ticket:
-{{{
-[[TicketQuery(id=123)]]
-}}}
-This is displayed as:
-  [[TicketQuery(id=123)]]
-A more compact representation without the ticket summaries is:
-{{{
-[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
-}}}
-This is displayed as:
-  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
-Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter:
-{{{
-[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
-}}}
-This is displayed as:
-  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
-----
-See also: TracQuery, TracTickets, TracReports, TracGuide

wiki/pages/TitleIndex

r38413	r39712
1		~~''' Index by Title ''' \| ''' [RecentChanges Index by Date] '''~~
2
3		~~[[TitleIndex(format=group,min=4)]]~~

wiki/pages/TracAccessibility

-                      r38413
+                      r39712
-= Accessibility Support in Trac =
-Not every user has a graphic environment with a mouse or other pointing device. Some users rely on keyboard, alternative keyboard or voice input to navigate links, activate form controls, etc. In a Trac session, users can use devices other than a pointing device by enabling keyboard shortcuts through the [/prefs/keybindings Keyboard Shortcuts] preferences panel.
-Trac supports accessibility keys for the most common operations. The access keys differ by browser and the following work for several browsers, but see [http://en.wikipedia.org/wiki/Access_key#Access_in_different_browsers access in different browsers] for more details.
- - on Linux platforms, press any of the keys listed below in combination with the `<Alt>` key
- - on a Mac, use the `<Ctrl>` + `<Opt>` key instead
- - on Windows, you need to hit `<Shift> + <Alt> + <Key>`. This works for the most common browsers, such as Firefox, Chrome, Safari and Internet Explorer
-== Global Access Keys ==
- * `1` - WikiStart
- * `2` - [TracTimeline Timeline]
- * `3` - [TracRoadmap Roadmap]
- * `4` - [TracSearch Search]
- * `6` - [TracGuide Trac Guide / Documentation]
- * `7` - [TracTickets New Ticket]
- * `9` - [/about About Trac]
- * `e` - Edit (wiki or report)
- * `r` - Preview (wiki or ticket)
- * `f` - Search
-----
-See also: TracGuide

wiki/pages/TracAdmin

-                      r38413
+                      r39712
-= TracAdmin
-[[PageOutline(2-5, Contents, floated)]]
-[[TracGuideToc]]
-Trac is distributed with a powerful command-line configuration tool. This tool can be used  to configure and customize your Trac-installation to better fit your needs.
-Some of those operations can also be performed via the web administration module.
-== Usage
-For nearly every `trac-admin` command, you'll need to specify the path to the TracEnvironment that you want to administer as the first argument, for example:
-{{{
-trac-admin /path/to/projenv wiki list
-}}}
-The only exception is for the `help` command, but even in this case if you omit the environment, you'll only get a very succinct list of commands (`help` and `initenv`), the same list you'd get when invoking `trac-admin` alone.
-Also, `trac-admin --version` will tell you about the Trac version (e.g. 0.12) corresponding to the program.
-If you want to get a comprehensive list of the available commands and sub-commands, you need to specify an existing environment:
-{{{
-trac-admin /path/to/projenv help
-}}}
-Some commands have a more detailed help, which you can access by specifying the command's name as a subcommand for `help`:
-{{{
-trac-admin /path/to/projenv help <command>
-}}}
-=== `trac-admin <targetdir> initenv` === #initenv
-This subcommand is very important as it's the one used to create a TracEnvironment in the specified `<targetdir>`. That directory must not exist prior to the call.
-[[TracAdminHelp(initenv)]]
-It supports an extra `--inherit` option, which can be used to specify a global configuration file which can be used to share settings between several environments. You can also inherit from a shared configuration afterwards, by setting the `[inherit] file` option in the `conf/trac.ini` file in your newly created environment, but the advantage of specifying the inherited configuration file at environment creation time is that only the options ''not'' already specified in the global configuration file will be written in the created environment's `conf/trac.ini` file.
-See TracIni#GlobalConfiguration.
-Note that in version 0.11 of Trac, `initenv` lost an extra last argument `<templatepath>`, which was used in previous versions to point to the `templates` folder. If you are using the one-liner '`trac-admin /path/to/trac/ initenv <projectname> <db> <repostype> <repospath>`' in the above and getting an error that reads ''''`Wrong number of arguments to initenv: 4`'''', then this is because you're using a `trac-admin` script from an '''older''' version of Trac.
-== Interactive Mode
-When passing the environment path as the only argument, `trac-admin` starts in interactive mode.
-Commands can then be executed on the selected environment using the prompt, which offers tab-completion
-(on non-Windows environments, and when the Python `readline` module is available) and automatic repetition of the last command issued.
-Once you're in interactive mode, you can also get help on specific commands or subsets of commands:
-For example, to get an explanation of the `resync` command, run:
-{{{
-> help resync
-}}}
-To get help on all the Wiki-related commands, run:
-{{{
-> help wiki
-}}}
-== Full Command Reference
-You'll find below the detailed help for all the commands available by default in `trac-admin`. Note that this may not match the list given by `trac-admin <yourenv> help`, as the commands  pertaining to components disabled in that environment won't be available and conversely some plugins activated in the environment can add their own commands.
-[[TracAdminHelp()]]
-----
-See also: TracGuide, TracBackup, TracPermissions, TracEnvironment, TracIni, [trac:TracMigrate TracMigrate]

wiki/pages/TracBackup

-                      r38413
+                      r39712
-= Trac Backup
-[[TracGuideToc]]
-Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command in [wiki:TracAdmin trac-admin].
-'''Note''': Trac uses the `hotcopy` nomenclature to match that of [http://subversion.tigris.org/ Subversion], to make it easier to remember when managing both Trac and Subversion servers.
-== Creating a Backup
-To create a backup of a live TracEnvironment simply run:
-{{{#!sh
-$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
-}}}
-[wiki:TracAdmin trac-admin] will lock the database while copying.
-The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
-Please note, the `hotcopy` command will not overwrite a target directory and when such exists, the operation ends with an error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].
-=== Restoring a Backup
-To restore an environment from a backup, stop the process running Trac, ie the Web server or [wiki:TracStandalone tracd], restore the contents of your backup (path/to/backupdir) to your [wiki:TracEnvironment project environment] directory and restart the service.
-To restore a PostgreSQL database backup, use the command:
-{{{#!sh
-psql -U <user> -d <database> -f postgresql.dump
-}}}
-The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//.
-----
-See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]

wiki/pages/TracBatchModify

-                      r38413
+                      r39712
-= Trac Ticket Batch Modification =
-[[TracGuideToc]]
-Trac supports modifying a batch of tickets in one request from [TracQuery custom query] results .
-To perform a batch modification, select the tickets you wish to modify and set the new field values using the section underneath the query results.
-== List fields
-The `Keywords` and `Cc` fields are treated as lists, where list items can be added and/or removed in addition of replacing the entire list value. All list field controls accept multiple items, such as multiple keywords or cc addresses.
-== Excluded fields
-Multi-line text fields are not supported, because no valid use-case has been presented for syncing them across several tickets. That restriction applies to the `Description` field as well as to any [TracTicketsCustomFields#AvailableFieldTypesandOptions custom field] of type 'textarea'. However, future versions of Trac could support in conjunction with more suitable actions like 'prepend', 'append' or 'search & replace' ([http://trac-hacks.org/ticket/2415 th:#2415]).

wiki/pages/TracBrowser

-                      r38413
+                      r39712
-= The Trac Repository Browser
-[[TracGuideToc]]
-The Trac repository browser can be used to browse specific revisions of directories and files stored in the repositories associated with the Trac environment.
-At the top-level of the repository browser is the '''Repository Index''', listing all the configured repositories.
-Each repository has a name which is used as a path prefix in a "virtual" file hierarchy encompassing all the available repositories.
-One of the repositories can be configured with an empty name; this is the default repository. When such a default repository is present, its top-level files and directories are also listed, in a '''Default Repository''' section placed before the repository index. If the default repository is the only repository associated with the Trac environment, then the '''Repository Index''' will be omitted. This means that after upgrading a single-repository Trac of version 0.11 (or earlier) to a multi-repository Trac (0.12), the repository browser will look and feel the same, that single repository becoming automatically the "default" repository.
-Directory entries are displayed in a list with sortable columns. The list entries can be sorted by ''Name'', ''Size'', ''Age'' or ''Author'' by clicking on the column headers. The sort order can be reversed by clicking on a given column header again.
-The browser can be used to navigate through the directory structure by clicking on the directory names.
-Clicking on a file name will show the contents of the file.
-Clicking on the revision number of a file or directory will take you to the TracRevisionLog for that file.
-Note that there's also a ''Revision Log'' navigation link that will do the same for the path currently being examined.
-Clicking on the ''diff'' icon after revision number will display the changes made to the files modified in that revision.
-Clicking on the ''Age'' of the file - will take you to that changeset in the timeline.
-It's also possible to browse directories or files as they were in history, at any given repository revision. The default behavior is to display the latest revision but another revision number can easily be selected using the ''View revision'' input field at the top of the page.
-The color bar next to the ''Age'' column gives a visual indication of the age of the last change to a file or directory, following the convention that '''[[span(style=color:#88f,blue)]]''' is oldest and '''[[span(style=color:#f88,red)]]''' is newest, but this can be [TracIni#browser-section configured].
-At the top of the browser page, there's a ''Visit'' drop-down menu which you can use to select some interesting places in the repository, for example branches or tags.
-This is sometimes referred to as the ''browser quickjump'' facility.
-The precise meaning and content of this menu depends on your repository backend.
-For Subversion, this list contains by default the top-level trunk directory and sub-directories of the top-level branches and tags directories (`/trunk`, `/branches/*`, and `/tags/*`). This can be [TracIni#svn-section configured] for more advanced cases.
-If you're using a Javascript enabled browser, you'll be able to expand and collapse directories in-place by clicking on the arrow head at the right side of a directory. Alternatively, the [trac:TracKeys keyboard] can also be used for this:
- - use `j` and `k` to select the next or previous entry, starting with the first
- - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected
-   directory or for visiting the selected file
- - `v` ('''v'''iew, '''v'''isit) and `<Enter>`, same as above
- - `r` can be used to force the '''r'''eload of an already expanded directory
- - `a` can be used to directly visit a file in '''a'''nnotate (blame) mode
- - `l` to view the '''l'''og for the selected entry
-If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse.
-For the Subversion backend, some advanced additional features are available:
- - The `svn:needs-lock` property will be displayed.
- - Support for the `svn:mergeinfo` property showing the merged and eligible information.
- - Support for browsing the `svn:externals` property, which can be [TracIni#svn:externals-section configured].
- - The `svn:mime-type` property is used to select the syntax highlighter for rendering the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is highlighted as HTML, regardless of the file extension. It also allows selecting the character encoding used in the file content. For example, if the file content is encoded in UTF-8, set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the default encoding defined in the `default_charset` option of the `[trac]` section of [TracIni#trac-section trac.ini].
-{{{#!comment
-MMM: I found this section a bit hard to understand. I changed the first item as I understood that well.
-but I think the other items could be changed also
- cboos: in the meantime, I've added the ''advanced'' word as a hint this can be a bit complex...
-}}}
-----
-See also: TracGuide, TracChangeset, TracFineGrainedPermissions

wiki/pages/TracCgi

-                      r38413
+                      r39712
-= Installing Trac as CGI
-[[TracGuideToc]]
-[[PageOutline]]
-{{{#!div class=important
- ''Please note that using Trac via CGI is the slowest deployment method available. It is slower than [TracModPython mod_python], [TracFastCgi FastCGI] and even [trac:TracOnWindowsIisAjp IIS/AJP] on Windows.''
-}}}
-CGI script is the entrypoint that web-server calls when a web-request to an application is made. The `trac.cgi` script can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin. Make sure the script is executable by your web server.
-== Apache web-server configuration
-In [http://httpd.apache.org/ Apache] there are two ways to run Trac as CGI:
-. Use a `ScriptAlias` directive that maps an URL to the `trac.cgi` script (recommended)
-. Copy the `trac.cgi` file into the directory for CGI executables used by your web server (commonly named `cgi-bin`). You can also create a symbolic link, but in that case make sure that the `FollowSymLinks` option is enabled for the `cgi-bin` directory.
-To make Trac available at `http://yourhost.example.org/trac` add `ScriptAlias` directive to Apache configuration file, changing `trac.cgi` path to match your installation:
-{{{#!apache
-ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.cgi
-}}}
- ''Note that this directive requires enabled `mod_alias` module.''
-If you're using Trac with a single project you need to set its location using the `TRAC_ENV` environment variable:
-{{{#!apache
-<Location "/trac">
-  SetEnv TRAC_ENV "/path/to/projectenv"
-</Location>
-}}}
-Or to use multiple projects you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` variable:
-{{{#!apache
-<Location "/trac">
-  SetEnv TRAC_ENV_PARENT_DIR "/path/to/project/parent/dir"
-</Location>
-}}}
- ''Note that the `SetEnv` directive requires enabled `mod_env` module. It is also possible to set TRAC_ENV in trac.cgi. Just add the following code between "try:" and "from trac.web ...":''
-{{{#!python
-    import os
-    os.environ['TRAC_ENV'] = "/path/to/projectenv"
-}}}
- '' Or for TRAC_ENV_PARENT_DIR: ''
-{{{#!python
-    import os
-    os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
-}}}
-If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [trac:ApacheSuexec].
-On some systems, you ''may'' need to edit the shebang line in the `trac.cgi` file to point to your real Python installation path. On a Windows system you may need to configure Windows to know how to execute a .cgi file (Explorer -> Tools -> Folder Options -> File Types -> CGI).
-=== Using WSGI
-You can run a [http://henry.precheur.org/python/how_to_serve_cgi WSGI handler] [http://pythonweb.org/projects/webmodules/doc/0.5.3/html_multipage/lib/example-webserver-web-wsgi-simple-cgi.html under CGI].  You can [wiki:TracModWSGI#Thetrac.wsgiscript write your own application function], or use the deployed trac.wsgi's application.
-== Mapping Static Resources
-See TracInstall#MappingStaticResources.
-== Adding Authentication
-See TracInstall#ConfiguringAuthentication.
-----
-See also:  TracGuide, TracInstall, [wiki:TracModWSGI], TracFastCgi, TracModPython

wiki/pages/TracChangeLog

-                      r38413
+                      r39712
-[[PageOutline(2-3)]]
-= Change Log
-This is a rough list of changes between released versions.
-To see where Trac is going in future releases, see the [trac:roadmap Roadmap].
-== 1.1.x Releases
-// 1.1.x releases are development releases leading eventually to Trac 1.2. See them as kind of snapshots of [trac:source:trunk].
-** No guarantees of feature and API compatibility is made from one 1.1.x release to the next. //
-=== 1.1.6
-//(July 17, 2015)//
-Trac 1.1.6 contains more than a half dozen minor fixes and enhancements.
-For more information see the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
-release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.6]] and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.7]]
-(as 1.1.6 contains all the fixes done for 1.0.7).
-[trac:source:/tags/trac-1.1.6 View Tag] | [trac:milestone:1.1.6 View Milestone]
-=== 1.1.5
-//(May 18, 2015)//
-Highlights of the changes:
- - Corrected highlighting of unmodified values in //Config// section of the //About Trac// page ([trac:#6551]).
- - New helper methods on `DatabaseManager` class for plugins to upgrade the database ([trac:#8172]).
- - New `[notification-subscriber]` config section for general configuration of notification subscription defaults and `SubscriberList` macro ([trac:#11875]).
- - Removed dependency on `ConfigObj` for TracFineGrainedPermissions ([trac:#11982]).
- - `Image` macro supports InterWiki prefixes ([trac:#12025]).
-See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
-release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.5]], [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.6]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.7]]
-(as 1.1.5 contains all the fixes done for 1.0.6 and 0.12.7).
-[trac:source:/tags/trac-1.1.5 View Tag] | [trac:milestone:1.1.5 View Milestone]
-=== 1.1.4
-//(March 24, 2015)//
-Highlights of the changes:
- - Performance improvements with MySQL/MariaDB ([trac:#3676]).
- - Click on //Permissions// Admin page table row toggles all
-   checkboxes in the row ([trac:#11417]).
- - Configuration sections are written to trac.ini when enabling a
-   component through TracAdmin or the web administration module
-   ([trac:#11437]).
- - Subscription rules can be reordered by drag and drop ([trac:#11941]).
-See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
-release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.4]]
-and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.4/1.0.5]]
-(as 1.1.4 contains all the fixes done for 1.0.4 and 1.0.5).
-[trac:source:/tags/trac-1.1.4 View Tag] | [trac:milestone:1.1.4 View Milestone]
-=== 1.1.3
-//(January 13, 2015)//
-The following list contains highlights of the changes:
- - The ticket creation step can be configured in the TracWorkflow and the
-   workflow controls are present on the !NewTicket page ([trac:#2045]).
- - New notification system that can be extended by plugins ([trac:#3517]).
- - New preferences panel for notification subscriptions ([trac:#4056]).
- - Wiki page version comments can be edited by users with `WIKI_ADMIN` ([trac:#6573]).
- - Improved positioning of //Add Comment// section and //author// field
-   on the ticket form ([trac:#10207]).
- - The delete confirmation pages warn if attachments will also be deleted
-   ([trac:#11542]).
- - Removed support for [trac:SilverCity], Enscript and !PhpRenderer syntax
-   highlighters ([trac:#11795]).
- - Combined //Date & Time// and //Language// preference panels as
-   //Localization// ([trac:#11813]).
- - Groups and permissions can be used in the workflow `set_owner` attribute
-   ([trac:#11839]).
-See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.3]] and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.3]] (as 1.1.3 contains all the fixes done
-for 1.0.3).
-[trac:source:/tags/trac-1.1.3 View Tag] | [trac:milestone:1.1.3 View Milestone]
-=== 1.1.2
-//(October 23, 2014)//
-The following list contains highlights of the changes:
- - Dropped support for Python 2.5. Trac can no longer be run on Python 2.5 as incompatible changes have been made in the source code ([trac:#11600]).
- - The new ticket workflow action `may_set_owner` is similar to `set_owner` but the owner defaults to the existing ticket owner rather than the current user ([trac:#10018]).
- - The new option `[ticket]` `optional_fields` specifies ticket select fields that are treated as optional (i.e. an empty value is allowed) ([trac:#10772]).
- - Line number and row highlighting annotations can be specified for !WikiProcessor code blocks ([trac:#10834]).
- - The //default handler// can be set as a session preference ([trac:#11597]), and the default value for all users can be set from the //Basic Settings// admin page ([trac:#11519]).
- - Attachments can't be added to read-only wiki pages ([trac:#11244]).
- - Tables on the admin pages have a //Select all// checkbox in the header ([trac:#10994]).
- - Submit buttons are disabled if the required items are not selected ([trac:#11056]).
- - The Admin //Permissions// page has a //Copy Permissions// form for copying permissions between users and groups ([trac:#11099]).
- - The new option `[milestone]` `default_retarget_to` determines the default milestone for retargeting tickets when a milestone is deleted or closed, and can be specified from the //Milestone// admin page ([trac:#10010]).
- - The //retarget// select is not shown when closing or deleting a milestone which has no tickets associated with it ([trac:#11366]).
- - //Clear default// buttons allow the ticket system default values (e.g. `default_milestone`, `default_version`) to be cleared through the corresponding admin pages ([trac:#10772], [trac:#11300]).
- - The `TitleIndex` macro supports relative path prefixes when used on wiki pages ([trac:#11455]).
- - [trac:CommitTicketUpdater] will recognize a ticket reference that includes a trailing `#comment:N` or `#comment:description` ([trac:#11622]).
- - The //Tickets// column of the milestone table on the //Milestone// admin page contains links to the query page showing all tickets associated with the milestone, grouped by status ([trac:#11661]).
- - Authz policy can be used to restrict access to the //Report List// page using the resource id `-1` ([trac:#11697]).
-See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.2]], [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.2]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.6]] (as 1.1.2 contains all the fixes done for 1.0.2 and 0.12.6).
-[trac:source:/tags/trac-1.1.2 View Tag] | [trac:milestone:1.1.2 View Milestone]
-=== 1.1.1
-//(February 3, 2013)//
-Trac 1.1.1 starts the 1.1.x development line leading to 1.2 with some new features and a few not-so-disruptive changes.
-The following list contains only a few highlights:
- - Added support for custom ticket fields of type time ([trac:#1942])
- - In new tickets, custom time ticket fields may default to an absolute or relative date / time ([trac:#10853])
- - In TracBatchModify, custom time ticket fields can be changed with a date(time)picker popup control ([trac:#10854])
- - Optionally display the component of tickets in their timeline entries (`[timeline]` `ticket_show_component` setting) ([trac:#10885])
- - Fixed batch modification when no fields are changed ([trac:#10924])
- - Dynamic variables can be used in the report title and description ([trac:#10979])
- - jQuery upgraded to 1.8.3, jQuery UI upgraded to 1.9.2 and jQuery UI Timepicker upgraded to 1.1.1 ([trac:#10976])
- - Dropped support for Python 2.5, either Python 2.6 or Python 2.7 is required //(well, as it happens, 2.5 //still// works, that's a bug ;-) )//
-See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.1]], [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.1]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.5]] (as 1.1.1 contains all the fixes done for 1.0.1 and 0.12.5).
-[trac:source:/tags/trac-1.1.1 View Tag] | [trac:milestone:1.1.1 View Milestone]
-== 1.0.x Releases ==
-=== 1.0.7
-//(July 17, 2015)//
-Trac 1.0.7 contains more than a dozen minor fixes and enhancements, including the following highlights:
- - Custom `svn:keywords` definitions are expanded in Subversion 1.8 and later ([trac:#11364]).
- - Fixed MySQL performance regression in query with custom fields ([trac:#12113]).
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.7]].
-[trac:source:/tags/trac-1.0.7 View Tag] | [trac:milestone:1.0.7 View Milestone]
-=== 1.0.6
-//(May 20, 2015)//
-Trac 1.0.6 provides more than 20 fixes and enhancements. The following are some highlights:
- - Hash changeset ids and branch names can be used in revision ranges ([trac:#11050])
- - Improved rendering performance using chunked response when `[trac]` `use_chunked_encoding` is `True` ([trac:#11802])
- - Improved performance of Git repositories ([trac:#11971]).
- - Header to send when `[trac]` `use_xsendfile` is `True` can be specified through the option `[trac]` `xsendfile_header`. X-Sendfile is supported in Nginx by specifying `X-Accel-Redirect` for the header ([trac:#11981]).
- - Symbolic link can be used for `conf/trac.ini` in environment directory ([trac:#12000]).
- - Hyphen character can be used in !WikiProcessor parameter name ([trac:#12023]).
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.6]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.7]] (as 1.0.6 contains all the changes in 0.12.7).
-[trac:source:/tags/trac-1.0.6 View Tag] | [trac:milestone:1.0.6 View Milestone]
-=== 1.0.5
-//(March 24, 2015)//
-Trac 1.0.5 provides several fixes. The following are some highlights:
- - Images are not rendered in the timeline ([trac:#10751]).
- - Git tags are shown in the browser view ([trac:#11964]).
- - Added support for `journal_mode` and `synchronous` pragmas in `sqlite:` database connection string ([trac:#11967]).
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.5]].
-[trac:source:/tags/trac-1.0.5 View Tag] | [trac:milestone:1.0.5 View Milestone]
-=== 1.0.4
-//(February 8, 2015)//
-Trac 1.0.4 contains a few fixes, including a fix for a regression in 1.0.3.
- - Workflow action labels were not displayed unless name attribute
-   was explicitly defined ([trac:#11930]).
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.4]].
-[trac:source:/tags/trac-1.0.4 View Tag] | [trac:milestone:1.0.4 View Milestone]
-=== 1.0.3
-//(January 13, 2015)//
-Trac 1.0.3 is a maintenance release containing numerous fixes and minor
-enhancements. The following are a few of the highlights:
-The following list contains only a few highlights:
- - Notification is sent when adding an attachment to a ticket ([trac:#2259]).
- - Stylesheets and scripts are loaded during autopreview, resulting in proper
-   syntax highlighting when code WikiProcessors are added ([trac:#10470]) and display
-   of Workflow graphs without explicit autopreview ([trac:#10674]).
- - Merge changesets are shown as differences against first parent, resulting
-   in less noisy changesets ([trac:#10740]).
- - Pygments 2.0 is supported ([trac:#11796]).
- - Fixed error when completing the `initenv` TracAdmin command ([trac:#11797]).
- - Performance improvement on systems with many thousands of authenticated
-   users due to caching of Environment.get_known_users ([trac:#11868]).
- - Distribution metadata of wheel package is supported and displayed on the
-   About page ([trac:#11877]).
- - … and more than 3 dozen total fixes!
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.3]].
-[trac:source:/tags/trac-1.0.3 View Tag] | [trac:milestone:1.0.3 View Milestone]
-=== 1.0.2
-//(October 23, 2014)//
-Trac 1.0.2 contains a number of bug fixes and minor enhancements, as well as a major update for many translations.
-The following list contains only a few highlights:
- - Subversion keywords are expanded and EOL substitutions made when viewing a file in the repository browser and when downloading a file ([trac:#717]).
- - Notification email is sent to the old owner when a ticket is reassigned ([trac:#2311]).
- - Ticket change history is updated when renaming and deleting a milestone, and when retargeting tickets to another milestone ([trac:#4582], [trac:#5658]).
- - Numerous fixes for the Authz permissions policy in the browser/repository ([trac:#10961], [trac:#11646]), wiki ([trac:#8976], [trac:#11067]), admin ([trac:#11069]) and report ([trac:#11176]) realms.
- - Multiple forms submits are disallowed ([trac:#10138]).
- - `ConfigurationError` is raised if any of the `permission_policies` can't be loaded, preventing possible information leakage due to internal and installation errors ([trac:#10285]).
- - Wiki toolbars can be disabled through a configuration setting ([trac:#10837])
- - The number of entries in a table is shown next to heading on applicable admin pages ([trac:#11027]).
- - //Cancel// buttons are consistently located on all pages ([trac:#11076]).
- - Focus is placed on a text element when an edit page is loaded ([trac:#11084]).
- - The //Edit conflict// and //Merge// warning messages are always visible in side-by-side edit mode ([trac:#11102]).
- - Improvements to the layout of the Report ([trac:#11106], [trac:#11664]) and Ticket pages ([trac:#11471]).
- - Genshi 0.7 compatibility ([trac:#11218]).
- - Numerous minor fixes for Git repository support.
- - … and more than a hundred more fixes!
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.2]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.6]] (as 1.0.2 contains all the fixes done for 0.12.6).
-[trac:source:/tags/trac-1.0.2 View Tag] | [trac:milestone:1.0.2 View Milestone]
-=== 1.0.1
-//(February 1, 2013)//
-Trac 1.0.1 contains a number of bug fixes and minor enhancements, as well as a major update for many translations.
-The following list contains only a few highlights:
- - Fix zip source download for large directories in Subversion repositories ([trac:#10840])
- - Performance improvement for the Roadmap, by caching milestone properties ([trac:#10879])
- - Added a ''select all'' checkbox to table of components for each plugin on the Plugins admin panel ([trac:#9609])
- - Restore the ''Modify'' link at the top of the ticket page, as it was in Trac 0.12 ([trac:#10856])
- - `ListOption` keeps values other than empty string and None in raw list as default ([trac:#10541])
- - Prevent possibility of multiple identical info or warning messages being presented to the user ([trac:#10987])
- - The !BatchModify select-all checkboxes are toggled with tri-state behavior when the ticket checkboxes are toggled ([trac:#10992])
- - Update the ticket changetime to the current time when deleting a ticket comment ([trac:#10486])
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.1]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.5]] (as 1.0.1 contains all the fixes done for 0.12.5).
-[trac:source:/tags/trac-1.0.1 View Tag] | [trac:milestone:1.0.1 View Milestone]
-=== '''1.0 'Cell' '''
-//(September 7, 2012)//
-Trac 1.0 is a major release adding refreshed user interface and improved DVCS repository support as the most visible changes.
-The following list contains only a few highlights:
- - The default theme looks more modern, especially on recent browsers (no effort has been made to make it look better on older browsers like IE6 or 7)
- - The [TH:GitPlugin] has been donated by Herbert Valerio Riedel to the Trac project (many thanks!) and is now maintained here as an optional component
- - As a consequence, the Subversion support has been moved below `tracopt.versioncontrol` as well
- - The Git and Mercurial log view feature a visualization of the branching structure
- - Usability improvements for the tickets, with a better support for conflict detection and resolution
- - Integration of the [TH:BatchModifyPlugin], contributed by Brian Meeker (many thanks!) and is now maintained there as a default component
- - jQuery/UI integration, featuring a date picker for date fields
- - Improved integration with Pygments syntax highlighting
- - ... and numerous smaller features added and bugs fixed since 0.12!
-See the full list in [trac:wiki:TracDev/ReleaseNotes/1.0 1.0].
-[[trac:source:/tags/trac-1.0 View Tag]] | [[trac:milestone:1.0 View Milestone]]
-== 0.12.x Releases
-=== 0.12.7
-//(May 20, 2015)//
-Trac 0.12.7 fixes a minor security issue, as well as a half dozen other minor issues:
- - InterWiki filters links through `[wiki] safe_schemes` option if `[wiki] render_unsafe_content` is disabled ([trac:#12053]).
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.7]].
-[trac:source:/tags/trac-0.12.7 View Tag] | [trac:milestone:0.12.7 View Milestone]
-=== 0.12.6
-//(October 23, 2014)//
-Trac 0.12.6 contains fixes for a few issues:
- - Subversion blame would fail for a path with URL-encoded characters ([trac:#10386]), a lower-case drive letter on Windows ([trac:#10514]), or a non-ascii filename with Subversion 1.7 ([trac:#11167]).
- - Improved performance rendering `svn:mergeinfo` properties in browser view ([trac:#8459]) and changeset view ([trac:#11219]).
- - Query with many custom fields would fail ([trac:#11140]).
- - Zip archive had a timestamp with no timezone information ([trac:#11162]).
- - Failure or incorrect ranges rendering log TracLinks ([trac:#11308], [trac:#11346]).
- - Textareas in ticket view did not wrap correctly in IE 11 ([trac:#11376]).
- - Emails were not being obfuscated in owner field on CSV export from ticket and query pages ([trac:#11594]).
- - Locale data was not being included in egg in Distribute 0.6.29 and later ([trac:#11640]).
- - Deleting a milestone would not delete its attachments ([trac:#11672]).
- - Added support for Babel 1.0 and later ([trac:#11258], [trac:#11345]).
- - Added support for `ConfigObj` 5.0 and later ([trac:#11498]).
- - … and dozens more fixes!
-See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.6]].
-[trac:source:/tags/trac-0.12.6 View Tag] | [trac:milestone:0.12.6 View Milestone]
-=== 0.12.5
-//(January 15, 2013)//
-Trac 0.12.5 contains fixes for a few issues:
- - upload of .mht files ([Wikipedia:MHTML] web page archive files) now works ([trac:#9880])
- - more robust parsing of attachment URLs ([trac:#10280]) and uploaded file names ([trac:#10850])
- - lots of improvement to the date formatting code, which is now much more robust when timezone and daylight saving time computations are involved ([trac:#10768], [trac:#10863], [trac:#10864], [trac:#10912], [trac:#10920])
- - no longer generate invalid JSON encoded data with Python 2.4 and 2.5 ([trac:#10877])
- - ... and fix a couple more minor defects ([trac:#10967], [trac:#10892], [trac:#10923], [trac:#10858], [trac:#10835])
-[trac:source:/tags/trac-0.12.5 View Tag] | [trac:milestone:0.12.5 View Milestone]
-=== 0.12.4
-//(September 7, 2012)//
-Trac 0.12.4 contains only a handful of minor fixes.
-[trac:source:/tags/trac-0.12.4 View Tag] | [trac:milestone:0.12.4 View Milestone]
-=== 0.12.3 ===
-//(February 6, 2012)//
-Trac 0.12.3 contains a few minor fixes and a few minor features.
- - compatibility with Subversion 1.7 ([trac:#10414])
- - easier troubleshooting of common startup errors ([trac:#10024])
- - jQuery upgraded to 1.4.4 ([trac:#10001])
- - improve fine-grained permission handling in the source browser ([trac:#9976], [trac:#10208], [trac:#10110])
- - added compatibility with MySQL 5.5.3 utf8mb4 databases ([trac:#9766])
- - ... and dozens more fixes!
-[trac:source:/tags/trac-0.12.3 View Tag] | [trac:milestone:0.12.3 View Milestone]
-=== 0.12.2
-//(January 31, 2011)//
-Trac 0.12.2 contains a few minor fixes and a few minor features.
-This list contains only a few highlights:
- - install: improved robustness of Trac installation if Babel is
-   installed after the fact ([trac:#9439], [trac:#9595], [trac:#9961])
- - notifications: support for Asian character width ([trac:#4717])
- - roadmap: fix display of progress bar in some corner cases ([trac:#9718])
-   and respect the overall_completion milestone group setting ([trac:#9721])
- - reports: reports and queries look much better, as the columns now
-   keep the same width across groups; the absence of word wrapping in
-   reports has been fixed ([trac:#9825])
- - web admin: improved layout ([trac:#8866], [trac:#9963])
- - web: it's now possible to log in different Trac instances sharing
-   the same URL prefix (e.g. /project and /project-test) ([trac:#9951])
-[trac:source:/tags/trac-0.12.2 View Tag] | [trac:milestone:0.12.2 View Milestone]
-=== 0.12.1
-//(October 9, 2010)//
-Trac 0.12.1 contains a few important performance improvements, some minor fixes and a few minor features.
-This list contains only a few highlights:
- - db: improve concurrency behavior ([trac:#9111])
- - fcgi: add an environment variable `TRAC_USE_FLUP` to control the usage of flup vs. bundled _fcgi.py (defaults to 0, i.e. use bundled as before)
- - svn authz: improve compatibility with svn 1.5 format ([trac:#8289])
- - milestone: allow to set the time for the due date ([trac:#6369], [trac:#9582])
- - ticket: fixes for the CC: property ([trac:#8597], [trac:#9522])
- - notification: improved the formatting of ticket fields in notification e-mails ([trac:#9484], [trac:#9494])
- - i18n: added a configuration option to set the default language ([trac:#8117])
- - several fixes for upgrade ([trac:#9400], [trac:#9416], [trac:#9483], [trac:#9556])
-[trac:source:/tags/trac-0.12.1 View Tag] | [trac:milestone:0.12.1 View Milestone]
-=== ''' 0.12 'Babel' '''
-//(June 13, 2010)//
-Trac 0.12 is a major release introducing i18n and multiple repository support as the most visible changes.
-The following list contains only a few highlights:
- - The user interface is translated in a dozen of languages, provided the [Babel:] package is installed
- - Multiple repositories can be associated to a single Trac environment; the repositories can be of heterogeneous types (svn, hg, git, darcs...)
- - Usability improvements for the Wiki, with a nice side-by-side edit mode with automatic preview
- - Richer Wiki syntax, with much improved support for tables, partial [trac:WikiCreole] compatibility and numerous smaller improvements
- - Usability improvements for the Ticket module, with automatic preview of comments while you type and possibility to edit or remove them later
- - Improved Custom Queries (time fields, multiple disjoint conditions, a.k.a. OR queries)
- - Timeline filtering by user
- - ... and numerous smaller features added and bugs fixed since 0.11!
-[trac:source:/tags/trac-0.12 View Tag] | [trac:milestone:0.12 View Milestone]
-== Older Releases
-For releases prior to 0.12, see [trac:TracChangeLog@95].

wiki/pages/TracChangeset

-                      r38413
+                      r39712
-= Trac Changeset Module =
-[[TracGuideToc]]
-Trac has a built-in functionality for visualizing “diffs”, or changes to files.
-There are different kinds of ''change sets''.  Some correspond to revisions made in the repositories, others aggregate changes made in several revisions. Ultimately, any kind of difference can be shown.
-The changeset view consists of two parts, the ''header'' and the ''diff views''.
-== Changeset Header ==
-The header shows an overview of the whole changeset.
-Here you will find information such as:
- * Timestamp — When the changeset was commited
- * Author — Who commited the changeset
- * Message — A brief description from the author (the commit log message)
- * Location — Parent directory of all files affected by this changeset
- * Files — A list of files affected by this changeset
-If more than one revision is involved in the set of changes being displayed, the ''Timestamp'', ''Author'' and ''Message'' fields will not be shown.
-A colored rectangle indicates how the file is affected by the changeset:
- [[span(style=background:#bfb;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Green: Added \\
- [[span(style=background:#f88;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Red: Removed \\
- [[span(style=background:#fd8;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Yellow: Modified \\
- [[span(style=background:#88f;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Blue: Copied \\
- [[span(style=background:#ccc;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Gray: Moved \\
-The color legend is located below the header as a reminder.
-== Diff Views ==
-Below the header is the main part of the changeset, the diff view. Each file is shown in a separate section, each of which contains only the regions of the file that are affected by the changeset. There are two different styles to display the diffs: ''inline'' or ''side-by-side''. You can switch between the styles using the preferences form:
- * The ''inline'' style shows the changed regions of a file underneath each other. A region removed from the file will be colored red, an added region will be colored green. If a region was modified, the old version is displayed above the new version. Line numbers indicate the exact position of the change in both the old and the new version of the file.
- * The ''side-by-side'' style shows the old version on the left and the new version on the right and this will typically require more screen width than the inline style. Added and removed regions will be colored in the same way as with the inline style (green and red), and modified regions will have a yellow background.
-In addition, various advanced options are available in the preferences form for adjusting the display of the diffs:
- * You can set how many lines are displayed before and after every change; if the value ''all'' is used, then the full file will be shown.
- * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly.
-== The Different Ways to Get a Diff ==
-=== Examining a Changeset ===
-When viewing a repository check-in, such as when following a changeset [wiki:TracLinks link] or a changeset event in the [wiki:TracTimeline timeline], Trac will display the exact changes made by the check-in.
-There will be also navigation links to the ''Previous Changeset'' to and ''Next Changeset''.
-=== Examining Differences Between Revisions ===
-Often you want to look at changes made on a file or on a directory spanning multiple revisions. The easiest way to get there is from the TracRevisionLog, where you can select the ''old'' and the ''new'' revisions of the file or directory, and then click the ''View changes'' button.
-=== Examining Differences Between Branches ===
-One of the core features of version control systems is the possibility to work simultaneously on different ''Lines of Developments'', commonly called “branches”. Trac enables you to examine the exact differences between such branches.
-Using the '''View changes ...''' button in the TracBrowser allows you to enter ''From:'' and ''To:'' path/revision pairs. The resulting set of differences consist of the changes that should be applied to the ''From:'' content to get to the ''To:'' content.
-For convenience, it is possible to invert the roles of the ''old'' and the ''new'' path/revision pairs by clicking the ''Reverse Diff'' link on the changeset page.
-=== Checking the Last Change ===
-Another way to examine changes is to use the ''Last Change'' link provided by the TracBrowser.
-This link will take you to the last change that was made on that path. From there, you can use the ''Previous Change'' and ''Next Change'' links to traverse the change history of the file or directory.
-----
-See also: TracGuide, TracBrowser

wiki/pages/TracEnvironment

-                      r38413
+                      r39712
-= The Trac Environment
-[[TracGuideToc]]
-[[PageOutline(2-5)]]
-Trac uses a directory structure and a database for storing project data. The directory is referred to as the environment.
-== Creating an Environment
-A new Trac environment is created using [TracAdmin#initenv trac-admin's initenv]:
-{{{#!sh
-$ trac-admin /path/to/myproject initenv
-}}}
-`trac-admin` will ask you for the name of the project and the database connection string, see below.
-=== Useful Tips
- - Place your environment's directory on a filesystem which supports sub-second timestamps, as Trac monitors the timestamp of its configuration files and changes happening on a filesystem with too coarse-grained timestamp resolution may go undetected in Trac < 1.0.2. This is also true for the location of authentication files when using TracStandalone.
- - The user under which the web server runs will require file system write permission to the environment directory and all the files inside. Please remember to set the appropriate permissions. The same applies to the source code repository, although the user under which Trac runs will only require write access to a Subversion repository created with the BDB file system; for other repository types, check the corresponding plugin's documentation.
- - `initenv`, when using an svn repository, does not imply that trac-admin will perform `svnadmin create` for the specified repository path. You need to perform the `svnadmin create` prior to `trac-admin initenv` if you're creating a new svn repository altogether with a new Trac environment; otherwise you will see a message "Warning: couldn't index the repository" when initializing the environment.
- - Non-ascii environment paths are not supported.
- - Also, it seems that project names with spaces can be problematic for authentication, see [trac:#7163].
- - TracPlugins located in a [TracIni#inherit-section shared plugins folder] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are currently not loaded during creation, and hence, if they need to create extra tables for example, you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment] before being able to use it.
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Caveat:** don't confuse the //Trac environment directory// with the //source code repository directory//.
-This is a common beginners' mistake.
-It happens that the structure for a Trac environment is loosely modeled after the Subversion repository directory structure, but those are two disjoint entities and they are not and //must not// be located at the same place.
-}}}
-== Database Connection Strings
-Trac supports [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] database backends. The default is SQLite, which is probably sufficient for most projects. The database file is then stored in the environment directory, and can easily be [wiki:TracBackup backed up] together with the rest of the environment.
-Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded.
-=== SQLite Connection String
-The connection string for an SQLite database is:
-{{{
-sqlite:db/trac.db
-}}}
-where `db/trac.db` is the path to the database file within the Trac environment.
-=== PostgreSQL Connection String
-If you want to use PostgreSQL instead, you'll have to use a different connection string. For example, to connect to a PostgreSQL database on the same machine called `trac` for user `johndoe` with the password `letmein` use:
-{{{
-postgres://johndoe:letmein@localhost/trac
-}}}
-If PostgreSQL is running on a non-standard port, for example 9342, use:
-{{{
-postgres://johndoe:letmein@localhost:9342/trac
-}}}
-On UNIX, you might want to select a UNIX socket for the transport, either the default socket as defined by the PGHOST environment variable:
-{{{
-postgres://user:password@/database
-}}}
-or a specific one:
-{{{
-postgres://user:password@/database?host=/path/to/socket/dir
-}}}
-Note that with PostgreSQL you will have to create the database before running `trac-admin initenv`.
-See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL].
-Generally, the following is sufficient to create a database user named `tracuser` and a database named `trac`:
-{{{#!sh
-$ createuser -U postgres -E -P tracuser
-$ createdb -U postgres -O tracuser -E UTF8 trac
-}}}
-When running `createuser` you will be prompted for the password for the user 'tracuser'. This new user will not be a superuser, will not be allowed to create other databases and will not be allowed to create other roles. These privileges are not needed to run a Trac instance. If no password is desired for the user, simply remove the `-P` and `-E` options from the `createuser` command. Also note that the database should be created as UTF8. LATIN1 encoding causes errors, because of Trac's use of unicode. SQL_ASCII also seems to work.
-Under some default configurations (Debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user:
-{{{#!sh
-$ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
-$ sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac'
-}}}
-Trac uses the `public` schema by default, but you can specify a different schema in the connection string:
-{{{
-postgres://user:pass@server/database?schema=yourschemaname
-}}}
-=== MySQL Connection String
-The format of the MySQL connection string is similar to those for PostgreSQL, with the `postgres` scheme being replaced by `mysql`. For example, to connect to a MySQL database on the same machine called `trac` for user `johndoe` with password `letmein`:
-{{{
-mysql://johndoe:letmein@localhost:3306/trac
-}}}
-== Source Code Repository
-A single environment can be connected to more than one repository. However, by default Trac is not connected to any source code repository, and the ''Browse Source'' toolbar item will not be displayed.
-There are many different ways to connect repositories to an environment, see TracRepositoryAdmin. A single repository can be specified when the environment is created by passing the optional arguments `repository_type` and `repository_dir` to the `initenv` command.
-== Directory Structure
-An environment directory will usually consist of the following files and directories:
- * `README` - Brief description of the environment.
- * `VERSION` - Environment version identifier.
- * `files`
-  * `attachments` - Attachments to wiki pages and tickets.
- * `conf`
-  * `trac.ini` - Main configuration file. See TracIni.
- * `db`
-  * `trac.db` - The SQLite database, if you are using SQLite.
- * `htdocs` - Directory containing web resources, which can be referenced in Genshi templates using `/chrome/site/...` URLs.
- * `log` - Default directory for log files, if `file` logging is enabled and a relative path is given.
- * `plugins` - Environment-specific [wiki:TracPlugins plugins].
- * `templates` - Custom Genshi environment-specific templates.
-  * `site.html` - Method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance.
-----
-See also: TracAdmin, TracBackup, TracIni, TracGuide

wiki/pages/TracFastCgi

-                      r38413
+                      r39712
-= Trac with FastCGI
-[[TracGuideToc]]
-[[PageOutline(2-5, Contents, floated)]]
-[http://www.fastcgi.com/ FastCGI] interface allows Trac to remain resident much like with [wiki:TracModPython mod_python] or [wiki:TracModWSGI mod_wsgi]. It is faster than external CGI interfaces which must start a new process for each request.  Additionally, it is supported by much wider variety of web servers.
-Note that unlike mod_python, FastCGI supports [http://httpd.apache.org/docs/suexec.html Apache SuEXEC], ie run with different permissions than the web server runs with. `mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect.
-'''Note for Windows:''' Trac's FastCGI does not run under Windows, as Windows does not implement `Socket.fromfd`, which is used by `_fcgi.py`. If you want to connect to IIS, you may want to try [trac:TracOnWindowsIisAjp AJP]/[trac:TracOnWindowsIisAjp ISAPI].
-== Simple Apache configuration
-There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and
-`mod_fcgid` (preferred). The latter is more up-to-date.
-The following sections focus on the FCGI specific setup, see also [wiki:TracModWSGI#ConfiguringAuthentication] for configuring the authentication in Apache.
-Regardless of which cgi module is used, be sure the web server has executable permissions on the cgi-bin folder. While FastCGI will throw specific permissions errors, mod_fcgid will throw an ambiguous error if this has not been done. Connection reset by peer: mod_fcgid: error reading data from FastCGI server.
-=== Set up with `mod_fastcgi`
-`mod_fastcgi` uses `FastCgiIpcDir` and `FastCgiConfig` directives that should be added to an appropriate Apache configuration file:
-{{{
-# Enable fastcgi for .fcgi files
-# (If you're using a distro package for mod_fcgi, something like
-# this is probably already present)
-<IfModule mod_fastcgi.c>
-   AddHandler fastcgi-script .fcgi
-   FastCgiIpcDir /var/lib/apache2/fastcgi
-</IfModule>
-LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so
-}}}
-Setting `FastCgiIpcDir` is optional if the default is suitable. Note that the `LoadModule` line must be after the `IfModule` group.
-Configure `ScriptAlias` or similar options as described in TracCgi, but
-calling `trac.fcgi` instead of `trac.cgi`.
-Add the following to the Apache configuration file (below the `FastCgiIpcDir` line) if you intend to set up the `TRAC_ENV` as an overall default:
-{{{
-FastCgiConfig -initial-env TRAC_ENV=/path/to/env/trac
-}}}
-Alternatively, you can serve multiple Trac projects in a directory by adding this:
-{{{
-FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects
-}}}
-=== Set up with `mod_fcgid`
-Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` instead of `trac.cgi`:
-{{{
-ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.fcgi/
-}}}
-Note the slash at the end.
-To set up Trac environment for `mod_fcgid` it is necessary to use `DefaultInitEnv` directive. It cannot be used in `Directory` or `Location` context, so if you need to support multiple projects, try alternative environment setup below.
-{{{
-DefaultInitEnv TRAC_ENV /path/to/env/trac/
-}}}
-=== alternative environment setup
-A better method to specify path to the Trac environment is to embed the path into `trac.fcgi` script itself. That doesn't require configuration of the server environment variables, works for both [trac:FastCgi] modules as well as for [http://www.lighttpd.net/ lighttpd] and CGI:
-{{{
-import os
-os.environ['TRAC_ENV'] = "/path/to/projectenv"
-}}}
-or:
-{{{
-import os
-os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
-}}}
-With this method different projects can be supported by using different `.fcgi` scripts with different `ScriptAliases`.
-See [https://coderanger.net/~coderanger/httpd/fcgi_example.conf this fcgid example config] which uses a !ScriptAlias directive with trac.fcgi with a trailing / like this:
-{{{
-ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/
-}}}
-== Simple Cherokee Configuration
-The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process.
-You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down.
-First set up an information source in cherokee-admin with a local interpreter:
-{{{
-Host:
-localhost:4433
-Interpreter:
-/usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/
-}}}
-If the port was not reachable, the interpreter command would be launched. Note that, in the definition of the information source, you will have to manually launch the spawner if you use a ''Remote host'' as ''Information source'' instead of a ''Local interpreter''.
-After doing this, we will just have to create a new rule managed by the SCGI handler to access Trac. It can be created in a new virtual server, trac.example.net for instance, and will only need two rules. The '''default''' one will use the SCGI handler associated to the previously created information source.
-The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''$TRAC_LOCAL/htdocs/'' (where $TRAC_LOCAL is a directory defined by the user or the system administrator to place local trac resources).
-Note:\\
-If the tracd process fails to start up, and cherokee displays a 503 error page, you might be missing the [http://trac.saddi.com/flup python-flup] package.\\
-Python-flup is a dependency which provides trac with SCGI capability. You can install it on debian based systems with:
-{{{
-sudo apt-get install python-flup
-}}}
-== Simple Lighttpd Configuration
-The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.lighttpd.net/ Lighttpd].
-Lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance environments. It has a very low memory footprint compared to other web servers and takes care of CPU load.
-For using `trac.fcgi`(prior to 0.11) / fcgi_frontend.py (0.11) with Lighttpd add the following to your lighttpd.conf:
-{{{
-#var.fcgi_binary="/usr/bin/python /path/to/fcgi_frontend.py" # 0.11 if installed with easy_setup, it is inside the egg directory
-var.fcgi_binary="/path/to/cgi-bin/trac.fcgi" # 0.10 name of prior fcgi executable
-fastcgi.server = ("/trac" =>
-                   ("trac" =>
-                     ("socket" => "/tmp/trac-fastcgi.sock",
-                      "bin-path" => fcgi_binary,
-                      "check-local" => "disable",
-                      "bin-environment" =>
-                        ("TRAC_ENV" => "/path/to/projenv")
+                     )
+                   )
+                 )
-}}}
-Note that you will need to add a new entry to `fastcgi.server` for each separate Trac instance that you wish to run. Alternatively, you may use the `TRAC_ENV_PARENT_DIR` variable instead of `TRAC_ENV` as described above, and you may set one of the two in `trac.fcgi` instead of in `lighttpd.conf` using `bin-environment`, as in the section above on Apache configuration.
-Note that Lighttpd has a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example (see [trac:#2418]). This is fixed in Lighttpd 1.5, and under Lighttpd 1.4.23 or later the workaround is to add `"fix-root-scriptname" => "enable"` as a parameter of fastcgi.server.
-For using two projects with lighttpd add the following to your `lighttpd.conf`:
-{{{
-fastcgi.server = ("/first" =>
-                   ("first" =>
-                    ("socket" => "/tmp/trac-fastcgi-first.sock",
-                     "bin-path" => fcgi_binary,
-                     "check-local" => "disable",
-                     "bin-environment" =>
-                       ("TRAC_ENV" => "/path/to/projenv-first")
+                    )
-                  ),
-                  "/second" =>
-                    ("second" =>
-                    ("socket" => "/tmp/trac-fastcgi-second.sock",
-                     "bin-path" => fcgi_binary,
-                     "check-local" => "disable",
-                     "bin-environment" =>
-                       ("TRAC_ENV" => "/path/to/projenv-second")
+                    )
+                  )
+                )
-}}}
-Note that field values are different. If you prefer setting the environment variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, eg to `first.fcgi` and `second.fcgi`, and reference them in the above settings.
-Note that the above will result in different processes in any event, even if both are running from the same `trac.fcgi` script.
-{{{
-#!div class=important
-'''Note''' It's very important the order on which server.modules are loaded, if mod_auth is not loaded '''BEFORE''' mod_fastcgi, then the server will fail to authenticate the user.
-}}}
-For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules:
-{{{
-server.modules              = (
-...
-  "mod_auth",
-...
+)
-auth.backend               = "htpasswd"
-# Separated password files for each project
-# See "Conditional Configuration" in
-# http://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/configuration.txt
-$HTTP["url"] =~ "^/first/" {
-  auth.backend.htpasswd.userfile = "/path/to/projenv-first/htpasswd.htaccess"
+}
-$HTTP["url"] =~ "^/second/" {
-  auth.backend.htpasswd.userfile = "/path/to/projenv-second/htpasswd.htaccess"
+}
-# Enable auth on trac URLs, see
-# http://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/authentication.txt
-auth.require = ("/first/login" =>
-                ("method"  => "basic",
-                 "realm"   => "First project",
-                 "require" => "valid-user"
-                ),
-                "/second/login" =>
-                ("method"  => "basic",
-                 "realm"   => "Second project",
-                 "require" => "valid-user"
+                )
+               )
-}}}
-Note that Lighttpd (v1.4.3) stops if the password file doesn't exist.
-Note that Lighttpd doesn't support 'valid-user' in versions prior to 1.3.16.
-Conditional configuration is also useful for mapping static resources, ie serving out images and CSS directly instead of through FastCGI:
-{{{
-# Aliasing functionality is needed
-server.modules += ("mod_alias")
-# Set up an alias for the static resources
-alias.url = ("/trac/chrome/common" => "/usr/share/trac/htdocs")
-# Use negative lookahead, matching all requests that ask for any resource under /trac, EXCEPT in
-# /trac/chrome/common, and use FastCGI for those
-$HTTP["url"] =~ "^/trac(?!/chrome/common)" {
-# Even if you have other fastcgi.server declarations for applications other than Trac, do NOT use += here
-fastcgi.server = ("/trac" =>
-                   ("trac" =>
-                     ("socket" => "/tmp/trac-fastcgi.sock",
-                      "bin-path" => fcgi_binary,
-                      "check-local" => "disable",
-                      "bin-environment" =>
-                        ("TRAC_ENV" => "/path/to/projenv")
+                     )
+                   )
+                 )
+}
-}}}
-The technique can be easily adapted for use with multiple projects by creating aliases for each of them, and wrapping the fastcgi.server declarations inside conditional configuration blocks.
-Also there is another way to handle multiple projects and it's to use TRAC_ENV_PARENT_DIR instead of TRAC_ENV and use global auth, let's see an example:
-{{{
-#  This is for handling multiple projects
-  alias.url       = ( "/trac/" => "/path/to/trac/htdocs/" )
-  fastcgi.server += ("/projects"  =>
-                      ("trac" =>
+                        (
-                          "socket" => "/tmp/trac.sock",
-                          "bin-path" => fcgi_binary,
-                          "check-local" => "disable",
-                          "bin-environment" =>
-                            ("TRAC_ENV_PARENT_DIR" => "/path/to/parent/dir/of/projects/" )
+                        )
+                      )
+                    )
-#And here starts the global auth configuration
-  auth.backend = "htpasswd"
-  auth.backend.htpasswd.userfile = "/path/to/unique/htpassword/file/trac.htpasswd"
-  $HTTP["url"] =~ "^/projects/.*/login$" {
-    auth.require = ("/" =>
+                     (
-                       "method"  => "basic",
-                       "realm"   => "trac",
-                       "require" => "valid-user"
+                     )
+                   )
+  }
-}}}
-Changing date/time format also supported by lighttpd over environment variable LC_TIME:
-{{{
-fastcgi.server = ("/trac" =>
-                   ("trac" =>
-                     ("socket" => "/tmp/trac-fastcgi.sock",
-                      "bin-path" => fcgi_binary,
-                      "check-local" => "disable",
-                      "bin-environment" =>
-                        ("TRAC_ENV" => "/path/to/projenv",
-                        "LC_TIME" => "ru_RU")
+                     )
+                   )
+                 )
-}}}
-For details about languages specification see [trac:TracFaq TracFaq] question 2.13.
-Other important information like the [wiki:TracInstall#MappingStaticResources mapping static resources advices] are useful for non-fastcgi specific installation aspects.
+]
-Relaunch Lighttpd and browse to `http://yourhost.example.org/trac` to access Trac.
-Note about running Lighttpd with reduced permissions: If nothing else helps and trac.fcgi doesn't start with Lighttpd settings `server.username = "www-data"`, `server.groupname = "www-data"`, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.
-== Simple !LiteSpeed Configuration
-The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed].
-!LiteSpeed web server is an event-driven asynchronous Apache replacement designed from the ground-up to be secure, scalable, and operate with minimal resources. !LiteSpeed can operate directly from an Apache config file and is targeted for business-critical environments.
-. Please make sure you have a working install of a Trac project. Test install with "tracd" first.
-. Create a Virtual Host for this setup. From now on we will refer to this vhost as !TracVhost. For this tutorial we will be assuming that your Trac project will be accessible via:
-{{{
-http://yourdomain.com/trac/
-}}}
-. Go "!TracVhost → External Apps" tab and create a new "External Application".
-{{{
-Name: MyTracFCGI
-Address: uds://tmp/lshttpd/mytracfcgi.sock
-Max Connections: 10
-Environment: TRAC_ENV=/fullpathto/mytracproject/ <--- path to root folder of trac project
-Initial Request Timeout (secs): 30
-Retry Timeout (secs): 0
-Persistent Connection   Yes
-Connection Keepalive Timeout: 30
-Response Bufferring: No
-Auto Start: Yes
-Command: /usr/share/trac/cgi-bin/trac.fcgi  <--- path to trac.fcgi
-Back Log: 50
-Instances: 10
-}}}
-. Optional: If you need to use htpasswd based authentication. Go to "!TracVhost → Security" tab and create a new security Realm.
-{{{
-DB Type: Password File
-Realm Name: MyTracUserDB               <--- any name you wish and referenced later
-User DB Location: /fullpathto/htpasswd <--- path to your htpasswd file
-}}}
-If you don’t have a htpasswd file or don’t know how to create the entries within one, go to http://sherylcanter.com/encrypt.php, to generate the user:password combos.
-. Go to "!PythonVhost → Contexts" and create a new FCGI Context.
-{{{
-URI: /trac/                              <--- URI path to bind to python fcgi app we created
-Fast CGI App: [VHost Level] MyTractFCGI  <--- select the trac fcgi extapp we just created
-Realm: TracUserDB                        <--- only if (4) is set. select realm created in (4)
-}}}
-. Modify `/fullpathto/mytracproject/conf/trac.ini`
-{{{
-#find/set base_rul, url, and link variables
-base_url = http://yourdomain.com/trac/ <--- base url to generate correct links to
-url = http://yourdomain.com/trac/      <--- link of project
-link = http://yourdomain.com/trac/     <--- link of graphic logo
-}}}
-. Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
-{{{
-http://yourdomain.com/trac/
-}}}
-== Simple Nginx Configuration
-Nginx is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately.
-. Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32
- {{{
-    server {
-        listen       10.9.8.7:443;
-        server_name  trac.example;
-        ssl                  on;
-        ssl_certificate      /etc/ssl/trac.example.crt;
-        ssl_certificate_key  /etc/ssl/trac.example.key;
-        ssl_session_timeout  5m;
-        ssl_protocols  SSLv2 SSLv3 TLSv1;
-        ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
-        ssl_prefer_server_ciphers   on;
-        # it makes sense to serve static resources through Nginx (or ``~ [/some/prefix]/chrome/(.*)``)
-        location ~ /chrome/(.*) {
-             alias /home/trac/instance/static/htdocs/$1;
+        }
-        # You can copy this whole location to ``location [/some/prefix](/login)``
-        # and remove the auth entries below if you want Trac to enforce
-        # authorization where appropriate instead of needing to authenticate
-        # for accessing the whole site.
-        # (Or ``~ location /some/prefix(/.*)``.)
-        location ~ (/.*) {
-            auth_basic            "trac realm";
-            auth_basic_user_file /home/trac/htpasswd;
-            # socket address
-            fastcgi_pass   unix:/home/trac/run/instance.sock;
-            # python - wsgi specific
-            fastcgi_param HTTPS on;
-            ## WSGI REQUIRED VARIABLES
-            # WSGI application name - trac instance prefix.
-            # (Or ``fastcgi_param  SCRIPT_NAME  /some/prefix``.)
-            fastcgi_param  SCRIPT_NAME        "";
-            fastcgi_param  PATH_INFO          $1;
-            ## WSGI NEEDED VARIABLES - trac warns about them
-            fastcgi_param  REQUEST_METHOD     $request_method;
-            fastcgi_param  SERVER_NAME        $server_name;
-            fastcgi_param  SERVER_PORT        $server_port;
-            fastcgi_param  SERVER_PROTOCOL    $server_protocol;
-            fastcgi_param  QUERY_STRING       $query_string;
-            # For Nginx authentication to work - do not forget to comment these
-            # lines if not using Nginx for authentication
-            fastcgi_param  AUTH_USER          $remote_user;
-            fastcgi_param  REMOTE_USER        $remote_user;
-            # for ip to work
-            fastcgi_param REMOTE_ADDR         $remote_addr;
-            # For attchments to work
-            fastcgi_param    CONTENT_TYPE     $content_type;
-            fastcgi_param    CONTENT_LENGTH   $content_length;
+        }
+    }
-}}}
-. Modified trac.fcgi:
- {{{
-#!/usr/bin/env python
-import os
-sockaddr = '/home/trac/run/instance.sock'
-os.environ['TRAC_ENV'] = '/home/trac/instance'
-try:
-     from trac.web.main import dispatch_request
-     import trac.web._fcgi
-     fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request,
-          bindAddress = sockaddr, umask = 7)
-     fcgiserv.run()
-except SystemExit:
-    raise
-except Exception, e:
-    print 'Content-Type: text/plain\r\n\r\n',
-    print 'Oops...'
-    print
-    print 'Trac detected an internal error:'
-    print
-    print e
-    print
-    import traceback
-    import StringIO
-    tb = StringIO.StringIO()
-    traceback.print_exc(file=tb)
-    print tb.getvalue()
-}}}
-. reload nginx and launch trac.fcgi like that:
- {{{#!sh
-trac@trac.example ~ $ ./trac-standalone-fcgi.py
-}}}
-The above assumes that:
- * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory
- * `/home/trac/instance` contains a trac environment
- * `/home/trac/htpasswd` contains authentication information
- * `/home/trac/run` is owned by the same group the nginx runs under
-  * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`)
-  * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time
-Unfortunately nginx does not support variable expansion in fastcgi_pass directive.
-Thus it is not possible to serve multiple Trac instances from one server block.
-If you worry enough about security, run Trac instances under separate users.
-Another way to run Trac as a FCGI external application is offered in ticket #T6224
-----
-See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]

wiki/pages/TracFineGrainedPermissions

-                      r38413
+                      r39712
-= Fine grained permissions =
-[[PageOutline(2-5, Contents, floated)]]
-[[TracGuideToc]]
-There is a general mechanism in place that allows custom **permission policy plugins** to grant or deny any action on any kind of Trac resource, even at the level of specific versions of such resources.
-That mechanism is `authz_policy`, which is an optional module in `tracopt.perm.authz_policy.*`, so it is installed by default. It can be activated via the //Plugins// panel in the Trac administration module.
-== Permission Policies ==
-A great diversity of permission policies can be implemented and Trac comes with a few examples.
-Which policies are currently active is determined by a configuration setting in TracIni:
-{{{#!ini
-[trac]
-permission_policies = ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
-}}}
-This lists the [#ReadonlyWikiPolicy] which controls readonly access to wiki pages, followed by the !DefaultPermissionPolicy which checks for the traditional coarse grained style permissions described in TracPermissions, and the !LegacyAttachmentPolicy which knows how to use the coarse grained permissions for checking the permissions available on attachments.
-Among the optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See
-[trac:source:branches/1.0-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.
-Another popular permission policy [#AuthzSourcePolicy], re-implements the pre-0.12 support for checking fine-grained permissions limited to Subversion repositories in terms of the new system.
-See also [trac:source:branches/1.0-stable/sample-plugins/permissions sample-plugins/permissions] for more examples.
-=== !AuthzPolicy ===
-==== Configuration ====
-* Put a [http://swapoff.org/files/authzpolicy.conf authzpolicy.conf] file somewhere, preferably on a secured location on the server, not readable for others than the webuser. If the  file contains non-ASCII characters, the UTF-8 encoding should be used.
-* Update your `trac.ini`:
-. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section:
-{{{#!ini
-[trac]
-...
-permission_policies = AuthzPolicy, ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
-}}}
-. add a new `[authz_policy]` section:
-{{{#!ini
-[authz_policy]
-authz_file = /some/trac/env/conf/authzpolicy.conf
-}}}
-. enable the plugin through [/admin/general/plugin WebAdmin] or by editing the `[components]` section:
-{{{#!ini
-[components]
-tracopt.perm.authz_policy.* = enabled
-}}}
-==== Usage Notes ====
-Note the order in which permission policies are specified: policies are implemented in the sequence provided and therefore may override earlier policy specifications.
-A policy will return either `True`, `False` or `None` for a given permission check. `True` is returned if the policy explicitly grants the permission. `False` is returned if the policy explicitly denies the permission. `None` is returned if the policy is unable to either grant or deny the permission.
-NOTE: Only if the return value is `None` will the ''next'' permission policy be consulted. If none of the policies explicitly grants the permission, the final result will be `False`, i.e. permission denied.
-The `authzpolicy.conf` file is a `.ini` style configuration file:
-{{{#!ini
-[wiki:PrivatePage@*]
-john = WIKI_VIEW, !WIKI_MODIFY
-jack = WIKI_VIEW
-* =
-}}}
-* Each section of the config is a glob pattern used to match against a Trac resource descriptor. These descriptors are in the form:
-{{{
-<realm>:<id>@<version>[/<realm>:<id>@<version> ...]
-}}}
-Resources are ordered left to right, from parent to child. If any component is inapplicable, `*` is substituted. If the version pattern is not specified explicitly, all versions (`@*`) is added implicitly. Example: Match the WikiStart page:
-{{{#!ini
-[wiki:*]
-[wiki:WikiStart*]
-[wiki:WikiStart@*]
-[wiki:WikiStart]
-}}}
-Example: Match the attachment `wiki:WikiStart@117/attachment:FOO.JPG@*` on WikiStart:
-{{{#!ini
-[wiki:*]
-[wiki:WikiStart*]
-[wiki:WikiStart@*]
-[wiki:WikiStart@*/attachment:*]
-[wiki:WikiStart@117/attachment:FOO.JPG]
-}}}
-* Sections are checked against the current Trac resource descriptor '''IN ORDER''' of appearance in the configuration file. '''ORDER IS CRITICAL'''.
-* Once a section matches, the current username is matched against the keys (usernames) of the section, '''IN ORDER'''.
-  * If a key (username) is prefixed with a `@`, it is treated as a group.
-  * If a value (permission) is prefixed with a `!`, the permission is denied rather than granted.
-The username will match any of 'anonymous', 'authenticated', <username> or '*', using normal Trac permission rules. || '''Note:''' Other groups which are created by user (e.g. by 'adding subjects to groups' on web interface page //Admin / Permissions//) cannot be used. See [trac:ticket:5648 #5648] for details about this missing feature. ||
-For example, if the `authz_file` contains:
-{{{#!ini
-[wiki:WikiStart@*]
-* = WIKI_VIEW
-[wiki:PrivatePage@*]
-john = WIKI_VIEW
-* = !WIKI_VIEW
-}}}
-and the default permissions are set like this:
-{{{
-john           WIKI_VIEW
-jack           WIKI_VIEW
-# anonymous has no WIKI_VIEW
-}}}
-Then:
-  * All versions of WikiStart will be viewable by everybody, including anonymous
-  * !PrivatePage will be viewable only by john
-  * other pages will be viewable only by john and jack
-Groups:
-{{{#!ini
-[groups]
-admins = john, jack
-devs = alice, bob
-[wiki:Dev@*]
-@admins = TRAC_ADMIN
-@devs = WIKI_VIEW
-* =
-[*]
-@admins = TRAC_ADMIN
-* =
-}}}
-Then:
-- everything is blocked (whitelist approach), but
-- admins get all TRAC_ADMIN everywhere and
-- devs can view wiki pages.
-Some repository examples (Browse Source specific):
-{{{#!ini
-# A single repository:
-[repository:test_repo@*]
-john = BROWSER_VIEW, FILE_VIEW
-# John has BROWSER_VIEW and FILE_VIEW for the entire test_repo
-# The default repository (requires Trac 1.0.2 or later):
-[repository:@*]
-john = BROWSER_VIEW, FILE_VIEW
-# John has BROWSER_VIEW and FILE_VIEW for the entire default repository
-# All repositories:
-[repository:*@*]
-jack = BROWSER_VIEW, FILE_VIEW
-# Jack has BROWSER_VIEW and FILE_VIEW for all repositories
-}}}
-Very granular repository access:
-{{{#!ini
-# John has BROWSER_VIEW and FILE_VIEW access to trunk/src/some/location/ only
-[repository:test_repo@*/source:trunk/src/some/location/*@*]
-john = BROWSER_VIEW, FILE_VIEW
-# John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of all files at trunk/src/some/location only
-[repository:test_repo@*/source:trunk/src/some/location/*@1]
-john = BROWSER_VIEW, FILE_VIEW
-# John has BROWSER_VIEW and FILE_VIEW access to all revisions of 'somefile' at trunk/src/some/location only
-[repository:test_repo@*/source:trunk/src/some/location/somefile@*]
-john = BROWSER_VIEW, FILE_VIEW
-# John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of 'somefile' at trunk/src/some/location only
-[repository:test_repo@*/source:trunk/src/some/location/somefile@1]
-john = BROWSER_VIEW, FILE_VIEW
-}}}
-Note: In order for Timeline to work/visible for John, we must add CHANGESET_VIEW to the above permission list.
-==== Missing Features ====
-Although possible with the !DefaultPermissionPolicy handling (see Admin panel), fine-grained permissions still miss those grouping features (see [trac:ticket:9573 #9573], [trac:ticket:5648 #5648]). Patches are partially available, see authz_policy.2.patch, part of [trac:ticket:6680 #6680].
-You cannot do the following:
-{{{#!ini
-[groups]
-team1 = a, b, c
-team2 = d, e, f
-team3 = g, h, i
-departmentA = team1, team2
-}}}
-Permission groups are not supported either, so you cannot do the following:
-{{{#!ini
-[groups]
-permission_level_1 = WIKI_VIEW, TICKET_VIEW
-permission_level_2  = permission_level_1, WIKI_MODIFY, TICKET_MODIFY
-[*]
-@team1 = permission_level_1
-@team2 = permission_level_2
-@team3 = permission_level_2, TICKET_CREATE
-}}}
-=== !AuthzSourcePolicy  (mod_authz_svn-like permission policy) === #AuthzSourcePolicy
-At the time of this writing, the old granular permissions system from Trac 0.11 and before used for restricting access to the repository has been converted to a permission policy component. But from the user's point of view, this makes little if any difference.
-That kind of granular permission control needs a definition file, which is the one used by Subversion's mod_authz_svn.
-More information about this file format and about its usage in Subversion is available in the [http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html Path-Based Authorization] section in the Server Configuration chapter of the svn book.
-Example:
-{{{#!ini
-[/]
-* = r
-[/branches/calc/bug-142]
-harry = rw
-sally = r
-[/branches/calc/bug-142/secret]
-harry =
-}}}
- * '''/''' = ''Everyone has read access by default''
- * '''/branches/calc/bug-142''' = ''harry has read/write access, sally read only''
- * '''/branches/calc/bug-142/secret''' = ''harry has no access, sally has read access (inherited as a sub folder permission)''
-==== Trac Configuration ====
-To activate granular permissions you __must__ specify the {{{authz_file}}} option in the `[svn]` section of trac.ini. If this option is set to null or not specified, the permissions will not be used.
-{{{#!ini
-[svn]
-authz_file = /path/to/svnaccessfile
-}}}
-If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add:
-{{{#!ini
-authz_module_name = modulename
-}}}
-where ''modulename'' refers to the same repository indicated by the `<name>.dir` entry in the `[repositories]` section. As an example, if the `somemodule.dir` entry in the `[repositories]` section is `/srv/active/svn/somemodule`, that would yield the following:
-{{{ #!ini
-[svn]
-authz_file = /path/to/svnaccessfile
-authz_module_name = somemodule
-...
-[repositories]
-somemodule.dir = /srv/active/svn/somemodule
-}}}
-where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[somemodule:/some/path]}}}.
-'''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac.
-As of version 0.12, make sure you have ''!AuthzSourcePolicy'' included in the permission_policies list in trac.ini, otherwise the authz permissions file will be ignored.
-{{{#!ini
-[trac]
-permission_policies = AuthzSourcePolicy, ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
-}}}
-==== Subversion Configuration ====
-The same access file is typically applied to the corresponding Subversion repository using an Apache directive like this:
-{{{#!apache
-<Location /repos>
-  DAV svn
-  SVNParentPath /usr/local/svn
-  # our access control policy
-  AuthzSVNAccessFile /path/to/svnaccessfile
-</Location>
-}}}
-For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess].
-=== ReadonlyWikiPolicy
-Since 1.1.2, the read-only attribute of wiki pages is enabled and enforced when `ReadonlyWikiPolicy` is in the list of active permission policies. The default for new Trac installations in 1.1.2 and later is:
-{{{
-[trac]
-permission_policies = ReadonlyWikiPolicy,
- DefaultPermissionPolicy,
- LegacyAttachmentPolicy
-}}}
-When upgrading from earlier versions of Trac, `ReadonlyWikiPolicy` will be appended to the list of `permission_policies` when upgrading the environment, provided that `permission_policies` has the default value. If any non-default `permission_polices` are active, `ReadonlyWikiPolicy` **will need to be manually added** to the list. A message will be echoed to the console when upgrading the environment, indicating if any action needs to be taken.
-**!ReadonlyWikiPolicy must be listed //before// !DefaultPermissionPolicy**. The latter returns `True` to allow modify, delete or rename actions when the user has the respective `WIKI_*` permission, without consideration for the read-only attribute.
-The `ReadonlyWikiPolicy` returns `False` to deny modify, delete and rename actions on wiki pages when the page has the read-only attribute set and the user does not have `WIKI_ADMIN`, regardless of `WIKI_MODIFY`, `WIKI_DELETE` and `WIKI_RENAME` permissions. It returns `None` for all other cases.
-When active, the [#AuthzPolicy] should therefore come before `ReadonlyWikiPolicy`, allowing it to grant or deny the actions on individual resources, which is the usual ordering for `AuthzPolicy` in the `permission_policies` list.
-{{{
-[trac]
-permission_policies = AuthzPolicy,
- ReadonlyWikiPolicy,
- DefaultPermissionPolicy,
- LegacyAttachmentPolicy
-}}}
-The placement of [#AuthzSourcePolicy] relative to `ReadonlyWikiPolicy` does not matter since they don't perform checks on the same realms.
-For all other permission policies, the user will need to decide the proper ordering. Generally, if the permission policy should be capable of overriding the check performed by `ReadonlyWikiPolicy`, it should come before `ReadonlyWikiPolicy` in the list. If the `ReadonlyWikiPolicy` should override the check performed by another permission policy, as is the case for `DefaultPermissionPolicy`, then `ReadonlyWikiPolicy` should come first.
-== Debugging permissions
-In trac.ini set:
-{{{#!ini
-[logging]
-log_file = trac.log
-log_level = DEBUG
-log_type = file
-}}}
-Display the trac.log to understand what checks are being performed:
-{{{#!sh
-tail -n 0 -f log/trac.log | egrep '\[perm\]|\[authz_policy\]'
-}}}
-See the sourced documentation of the plugin for more info.
-----
-See also: TracPermissions,
-[http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin TracHacks:FineGrainedPageAuthzEditorPlugin] for a simple editor plugin.

wiki/pages/TracGuide

-                      r38413
+                      r39712
-= The Trac User and Administration Guide =
-[[TracGuideToc]]
-{{{#!span style="font-size:90%"
-//The TracGuide is meant to serve as a starting point for all documentation regarding Trac usage and development. The guide is a free document, a collaborative effort, and a part of the [http://trac.edgewall.org Trac Project] itself.//
-}}}
-== Introduction
-Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. It strives to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.
-It provides an interface to Subversion (and other version control systems), an integrated Wiki and convenient reporting facilities.
-Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all current and past project events in order, making the acquisition of an overview of the project and tracking progress very easy. The roadmap shows the road ahead, listing the upcoming milestones.
-== User Guide
-   * Using the Wiki subsystem
-     * TracWiki — How to use the built-in Wiki.
-     * WikiFormatting — Reference to the wiki syntax used throughout.
-   * Using the Version Control subsystem
-     * TracBrowser — Browsing source code with Trac.
-     * TracChangeset — Viewing changes to source code.
-     * TracRevisionLog — Viewing change history.
-   * Using the Ticket subsystem
-     * TracTickets — Using the issue tracker.
-     * TracRoadmap — The roadmap helps tracking project progress.
-     * TracReports — Writing and using reports.
-     * TracQuery — Executing custom ticket queries.
-     * TracBatchModify - Modifying a batch of tickets in one request.
-   * Other modules and general topics
-     * TracSearch — Full text search in all content.
-     * TracTimeline — The timeline provides a historic perspective on a project.
-     * TracRss — RSS content syndication in Trac.
-     * TracAccessibility — Accessibility keys support
-== Administrator Guide
-   * Installation and upgrade
-     * TracInstall — How to install and run Trac.
-     * TracUpgrade — How to upgrade existing installations.
-     * TracImport — Importing tickets from other bug databases.
-     * TracPlugins — Installing and managing Trac extensions.
-   * Configuration and customization
-     * TracIni — Trac configuration file reference.
-     * TracPermissions — Access control and permissions.
-     * TracNavigation — Customize main navigation menus.
-     * TracInterfaceCustomization — Customizing the Trac interface.
-     * TracLogging — The Trac logging facility.
-   * Administering the Version Control subsystem
-     * TracRepositoryAdmin — Management of Source Code Repositories.
-   * Administering the Ticket subsystem
-     * TracTicketsCustomFields — Expanding tickets with customized fields.
-     * TracNotification — Email notification.
-     * TracWorkflow — Configurable Ticket Workflow.
-   * Reference
-     * TracEnvironment — All you need to know about Trac environments
-     * TracAdmin — Administering a Trac project via the command-line.
-== Support and Other Sources of Information ==
- * [trac:TracFaq Trac FAQ] — A collection of Frequently Asked Questions (on the project website).
- * [trac:TracDev] and [trac:TracDev/ApiDocs API docs] — Trac Developer documentation
- * TracSupport — How to get more information
-If you are looking for a good place to ask a question about Trac, look no further than the [trac:MailingList MailingList]. It provides a friendly environment to discuss openly among Trac users and developers.

wiki/pages/TracImport

-                      r38413
+                      r39712
-= Importing ticket data =
-[[PageOutline]]
-To migrate issue tickets from other issue-tracking systems or perform housekeeping actions on tickets or simply synchronize different databases, there are some tools, plug-ins and scripts available, which let you import or update tickets into Trac.
-== !TicketImportPlugin ==
-[http://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin]: this plug-in lets you import or update into Trac a series of tickets from a '''CSV file''' or (if the [http://pypi.python.org/pypi/xlrd xlrd library] is installed) from an '''Excel spreadsheet'''.
-== !ExportImportXlsPlugin ==
-[http://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin]: this plug-in adds an admin panel for exporting and importing tickets via '''XLS file'''. Requires the python packages xlwt/rxld.
-== Bugzilla ==
-[http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin]: integrates Bugzilla issue data into Trac keeping TracLinks. Ticket data can be imported from Bugzilla using the [trac:browser:trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution.
-{{{
-$ bugzilla2trac.py
-bugzilla2trac - Imports a bug database from Bugzilla into Trac.
-Usage: bugzilla2trac.py [options]
-Available Options:
-  --db <MySQL dbname>              - Bugzilla's database
-  --tracenv /path/to/trac/env      - full path to Trac db environment
-  -h | --host <MySQL hostname>     - Bugzilla's DNS host name
-  -u | --user <MySQL username>     - effective Bugzilla's database user
-  -p | --passwd <MySQL password>   - Bugzilla's user password
-  -c | --clean                     - remove current Trac tickets before importing
-  --help | help                    - this help info
-Additional configuration options can be defined directly in the script.
-}}}
-Currently, the following data is imported from Bugzilla:
-  * bugs
-  * bug activity (field changes)
-  * bug attachments
-  * user names and passwords (put into a htpasswd file)
-The script provides a number of features to ease the conversion, such as:
-  * PRODUCT_KEYWORDS: Trac has no concept of products, so the script provides the ability to attach a ticket keyword instead.
-  * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp.
-  * STATUS_KEYWORDS: Attach ticket keywords for the Bugzilla statuses not available in Trac. By default, the 'VERIFIED' and 'RELEASED' Bugzilla statuses are translated into Trac keywords.
-For more details on the available options, see the configuration section at the top of the script.
-=== Known Issues ===
-{{{
-#!comment
-                   Don't merge this section in the default page
-}}}
-[[TicketQuery(keywords=~bugzilla,status=!closed)]]
-The adequate milestone for valid bugzilla2trac issue is usually ''Not applicable'', which means that fixes to the contributed script are not planned for a particular Trac release, but can happen anytime.
-== Jira ==
-[http://trac-hacks.org/wiki/JiraToTracIntegration JiraToTracIntegration]: provides tools to import Atlassian Jira backup files into Trac. The plug-in consists of a Python 3.1 commandline tool that:
-  - Parses the Jira backup XML file.
-  - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin].
-  - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords.
-== Mantis ==
-[http://trac-hacks.org/wiki/MantisImportScript MantisImportScript]: script to import the following data from Mantis into Trac:
-  * bugs
-  * bug comments
-  * bug activity (field changes)
-  * attachments (as long as the files live in the mantis db, not on the filesystem) .
-== !PlanetForge ==
-[http://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin]: this plugin exports Trac data (wiki, tickets, compoments, permissions, repositories, etc.) using the open format designed by the COCLICO project. It extends the webadmin panel and the 'trac admin ...' command. Has no 'import' feature.
-== Scarab ==
-[http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: script that migrates Scarab issues to Trac tickets. Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
-== Sourceforge ==
-[http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521).
-Also, ticket data can be imported from Sourceforge using the [trac:browser:trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution.
-== Other ==
-Since Trac uses a SQL database to store the data, you can also custom-import from other systems by examining the database tables. Just go into [http://www.sqlite.org/sqlite.html sqlite] command line to look at the tables and import them from your application.
-=== Comma delimited file - CSV ===
-See [trac:attachment:csv2trac.2.py:wiki:TracSynchronize csv2trac.2.py] for details. This approach is particularly useful if you need to enter a large number of tickets by hand. Note that the ticket type type field, (task etc...) is also needed for this script to work with more recent Trac releases.
-Comments on script: The script has an error on line 168: 'Ticket' needs to be 'ticket'. Also, the listed values for severity and priority are swapped.
-----
-See also:
- * to import/export wiki pages: TracAdmin,
- * to export tickets: TracTickets, TracQuery

wiki/pages/TracIni

-                      r38413
+                      r39712
-= The Trac Configuration File
-[[TracGuideToc]]
-[[PageOutline]]
-Trac is configured by editing the **`trac.ini`** file, located in the `<projectenv>/conf` directory. The `trac.ini` configuration file and its parent directory should be writable by the web server.
-Trac monitors the timestamp of the file to trigger a complete environment reload and flush its caches when the timestamp changes. Most changes to the configuration will be reflected immediately, though changes to the `[components]` or `[logging]` sections will require restarting the web server. You may also need to restart the web server after creating a [#GlobalConfiguration global configuration] file when none was previously present.
-== Global Configuration
-Configuration can be shared among environments using one or more global configuration files. Options in the global configuration will be merged with the environment-specific options, with local options overriding global options. The global configuration file is specified as follows:
-{{{#!ini
-[inherit]
-file = /path/to/global/trac.ini
-}}}
-Multiple files can be specified using a comma-separated list.
-Note that you can also specify a global option file when creating a new project,  by adding the option `--inherit=/path/to/global/trac.ini` to [TracAdmin#initenv trac-admin]'s `initenv` command.  If you do not do this but nevertheless intend to use a global option file with your new environment, you will have to go through the newly generated `conf/trac.ini` file and delete the entries that will otherwise override those set in the global file.
-There are two more entries in the [[#inherit-section| [inherit] ]] section, `templates_dir` for sharing global templates and `plugins_dir`, for sharing plugins. Those entries can themselves be specified in the shared configuration file, and in fact, configuration files can even be chained if you specify another `[inherit] file` there.
-Note that the templates found in the `templates/` directory of the TracEnvironment have precedence over those found in `[inherit] templates_dir`. In turn, the latter have precedence over the installed templates, so be careful about what you put there. Notably, if you override a default template, refresh your modifications when you upgrade to a new version of Trac. The preferred way to perform TracInterfaceCustomization is still to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation.
-== Reference for settings
-This is a brief reference of available configuration options, and their default settings.
-Documentation improvements should be discussed on the [trac:MailingList#Trac-dev trac-dev mailing list] or described in a [trac:NewTicket ticket]. Even better, [trac:TracDev/SubmittingPatches submit a patch] against the docstrings in the code.
-{{{ #!comment
-Please don't waste your time by editing the HTML code below, changes won't be picked up. Instead, follow the above guidance for suggesting documentation improvements.
-}}}
-[[TracIni]]
-----
-See also: TracGuide, TracAdmin, TracEnvironment

wiki/pages/TracInstall

-                      r38413
+                      r39712
-= Trac Installation Guide for 1.1
-[[TracGuideToc]]
-Trac is written in the Python programming language and needs a database, [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system.
-Trac can also be localized, and there is probably a translation available in your language. If you want to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default English version.
-If you're interested in contributing new translations for other languages or enhancing the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N].
-What follows are generic instructions for installing and setting up Trac. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms], please '''first read through these general instructions''' to get a good understanding of the tasks involved.
-[[PageOutline(2-3,Installation Steps,inline)]]
-== Dependencies
-=== Mandatory Dependencies
-To install Trac, the following software packages must be installed:
- * [http://www.python.org/ Python], version >= 2.6 and < 3.0
-   (note that we dropped the support for Python 2.5 in this release)
- * [http://pypi.python.org/pypi/setuptools setuptools], version >= 0.6
- * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6
-You also need a database system and the corresponding python bindings. The database can be either SQLite, PostgreSQL or MySQL.
-==== For the SQLite database #ForSQLite
-As you must be using Python 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).
-Optionally, you may install a newer version of [pypi:pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details.
-==== For the PostgreSQL database #ForPostgreSQL
-You need to install the database and its Python bindings:
- * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later
- * [http://pypi.python.org/pypi/psycopg2 psycopg2], version 2.0 or later
-See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
-==== For the MySQL database #ForMySQL
-Trac works well with MySQL, provided you follow the guidelines:
- * [http://mysql.com/ MySQL], version 5.0 or later
- * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later
-Given the caveats and known issues surrounding MySQL, read carefully the [trac:MySqlDb] page before creating the database.
-=== Optional Dependencies
-==== Subversion
-[http://subversion.apache.org/ Subversion], 1.6.x or later and the '''''corresponding''''' Python bindings.
-There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. [trac:TracSubversion] points you to [http://alagazam.net Alagazam], which works for me under Python 2.6.)
-For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page.
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Note:**
-* Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], nor does it work yet with the newer `ctype`-style bindings.
-* If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
-}}}
-==== Git
-[http://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page.
-==== Other Version Control Systems
-Support for other version control systems is provided via third-party plugins. See [trac:PluginList#VersionControlSystems] and [trac:VersionControlSystem].
-==== Web Server
-A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below.
-Alternatively you can configure Trac to run in any of the following environments:
- * [http://httpd.apache.org/ Apache] with
-   - [https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi], see [wiki:TracModWSGI] and
-     [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac].
-   - [http://modpython.org/ mod_python 3.5.0], see TracModPython
- * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
- * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
-   server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
- * Microsoft IIS with FastCGI and a FastCGI-to-WSGI gateway (see [trac:CookBook/Installation/TracOnWindowsIisWfastcgi IIS with FastCGI])
- * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script
-   is highly discouraged''', better use one of the previous options.
-==== Other Python Packages
- * [http://babel.edgewall.org Babel], version 0.9.6 or >= 1.3,
-   needed for localization support
- * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
-   for WikiRestructuredText.
- * [http://pygments.org Pygments] for
-   [TracSyntaxColoring syntax highlighting].
- * [http://pytz.sf.net pytz] to get a complete list of time zones,
-   otherwise Trac will fall back on a shorter list from
-   an internal time zone implementation.
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Attention**: The available versions of these dependencies are not necessarily interchangeable, so please pay attention to the version numbers. If you are having trouble getting Trac to work, please double-check all the dependencies before asking for help on the [trac:MailingList] or [trac:IrcChannel].
-}}}
-Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there ''probably concern older versions of Trac than the one you're installing''.
-== Installing Trac
-The [TracAdmin trac-admin] command-line tool, used to create and maintain [TracEnvironment project environments], as well as the [TracStandalone tracd] standalone server are installed along with Trac. There are several methods for installing Trac.
-=== Using `easy_install`
-Trac can be installed from PyPI or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].
-A few examples:
- - Install Trac 1.0:
-   {{{#!sh
-   easy_install Trac==1.0
-   }}}
- - Install latest development version:
-   {{{#!sh
-   easy_install Trac==dev
-   }}}
-   Note that in this case you won't have the possibility to run a localized version of Trac;
-   either use a released version or install from source
-More information can be found on the [trac:setuptools] page.
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in the sections on [#RunningtheStandaloneServer Running The Standalone Server] and [#RunningTraconaWebServer Running Trac on a Web Server].
-}}}
-=== Using `pip`
-'pip' is an easy_install replacement that is very useful to quickly install python packages.
-To get a Trac installation up and running in less than 5 minutes:
-Assuming you want to have your entire pip installation in `/opt/user/trac`
+ -
- {{{#!sh
-pip install trac psycopg2
-}}}
-or
+ -
- {{{#!sh
-pip install trac mysql-python
-}}}
-Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings.
-pip will automatically resolve all dependencies (like Genshi, pygments, etc.), download the latest packages from pypi.python.org and create a self contained installation in `/opt/user/trac`.
-All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive)
-Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip.
-=== From source
-Using the python-typical setup at the top of the source directory also works. You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. `Trac-1.0.tar.gz`) from the [trac:TracDownload] page, or you can get the source directly from the repository. See [trac:TracRepositories#OfficialSubversionrepository TracRepositories] for details.
-{{{#!sh
-$ python ./setup.py install
-}}}
-''You will need root permissions or equivalent for this step.''
-This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory
-of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`.
-If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
-{{{#!sh
-$ python ./setup.py install
-}}}
-Alternatively, you can run `bdist_egg` and copy the .egg from `dist/` to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
-=== Using installer
-On Windows, Trac can be installed using the exe installers available on the [trac:TracDownload] page. Installers are available for the 32-bit and 64-bit versions of Python. Make sure to use the installer that matches the architecture of your Python installation.
-=== Using package manager
-Trac may be available in your platform's package repository. Note however, that the version provided by your package manager may not be the latest release.
-=== Advanced `easy_install` Options
-To install Trac to a custom location, or find out about other advanced installation options, run:
-{{{#!sh
-easy_install --help
-}}}
-Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information.
-Specifically, you might be interested in:
-{{{#!sh
-easy_install --prefix=/path/to/installdir
-}}}
-or, if installing Trac on a Mac OS X system:
-{{{#!sh
-easy_install --prefix=/usr/local --install-dir=/Library/Python/2.6/site-packages
-}}}
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Mac OS X Note:** On Mac OS X 10.6,  running `easy_install trac` will install into `/usr/local` and `/Library/Python/2.6/site-packages` by default.
-The `tracd` and `trac-admin` commands will be placed in `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.6/site-packages`, which is Apple's preferred location for third-party Python application installations.
-}}}
-== Creating a Project Environment
-A [TracEnvironment Trac environment] is the backend where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is a directory that contains a human-readable [TracIni configuration file], and other files and directories.
-A new environment is created using [TracAdmin trac-admin]:
-{{{#!sh
-$ trac-admin /path/to/myproject initenv
-}}}
-[TracAdmin trac-admin] will prompt you for the information it needs to create the environment: the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for any of these options, just press `<Enter>` to use the default value.
-Using the default database connection string will always work as long as you have SQLite installed. For the other [trac:DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
-Also note that the values you specify here can be changed later using TracAdmin or directly editing the [TracIni conf/trac.ini] configuration file.
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Filesystem Warning:** When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux, or HFS+ on OSX), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2. The best advice is to opt for a platform with sub-second timestamp resolution, regardless of the Trac version.
-}}}
-Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
-{{{#!sh
-$ chown -R apache:apache /path/to/myproject
-}}}
-The actual username and groupname of the apache server may not be exactly `apache`, and are specified in the Apache configuration file by the directives `User` and `Group` (if Apache `httpd` is what you use).
-{{{#!div class=important
-'''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there.
-}}}
-== Deploying Trac
-=== Running the Standalone Server
-After having created a Trac environment, you can easily try the web interface by running the standalone server [TracStandalone tracd]:
-{{{#!sh
-$ tracd --port 8000 /path/to/myproject
-}}}
-Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this:
-{{{#!sh
-$ tracd -s --port 8000 /path/to/myproject
-}}}
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. The environment variable can be set system-wide, or for just the user that runs the `tracd` process. There are several ways to accomplish this in addition to what is discussed here, and depending on the distribution of your OS.
-To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`. To be effective for a user session the `export` statement may be added to `~/.profile`.
-{{{#!sh
-export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1
-}}}
-Alternatively, the variable can be set in the shell before executing `tracd`:
-{{{#!sh
-$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
-}}}
-}}}
-=== Running Trac on a Web Server
-Trac provides various options for connecting to a "real" web server:
- - [TracFastCgi FastCGI]
- - [wiki:TracModWSGI mod_wsgi]
- - [TracModPython mod_python]
- - //[TracCgi CGI] (should not be used, as the performance is far from optimal)//
-Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [http://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.
-==== Generating the Trac cgi-bin directory #cgi-bin
-In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [TracAdmin trac-admin].
-There is, however, a bit of a chicken-and-egg problem. The [TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
-{{{#!sh
-mkdir -p /usr/share/trac/projects/my-project
-trac-admin /usr/share/trac/projects/my-project initenv
-trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
-mv /tmp/deploy/* /usr/share/trac
-}}}
-Don't forget to check that the web server has the execution right on scripts in the `/usr/share/trac/cgi-bin` directory.
-==== Mapping Static Resources
-Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance).
-Web servers such as [http://httpd.apache.org/ Apache] allow you to create “Aliases” to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself.
-There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything.
-Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the TracAdmin `deploy` command:
-[[TracAdminHelp(deploy)]]
-The target `<directory>` will then contain an `htdocs` directory with:
- - `site/` - a copy of the environment's directory `htdocs/`
- - `common/` - the static resources of Trac itself
- - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
-===== Example: Apache and `ScriptAlias` #ScriptAlias-example
-Assuming the deployment has been done this way:
-{{{#!sh
-$ trac-admin /var/trac/env deploy /path/to/shared/trac
-}}}
-Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment:
-{{{#!apache
-Alias /trac/chrome/common /path/to/trac/htdocs/common
-Alias /trac/chrome/site /path/to/trac/htdocs/site
-<Directory "/path/to/www/trac/htdocs">
-  Order allow,deny
-  Allow from all
-</Directory>
-}}}
-If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
-{{{#!apache
-<Location "/trac/chrome/common/">
-  SetHandler None
-</Location>
-}}}
-Note that we mapped the `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources.
-Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):
-{{{#!apache
-Alias /trac/chrome/site /path/to/projectenv/htdocs
-<Directory "/path/to/projectenv/htdocs">
-  Order allow,deny
-  Allow from all
-</Directory>
-}}}
-Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[TracIni#trac-section| [trac] htdocs_location]] configuration setting:
-{{{#!ini
-[trac]
-htdocs_location = http://static.example.org/trac-common/
-}}}
-Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less]).
-Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
-{{{#!sh
-$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
-}}}
-==== Setting up the Plugin Cache
-Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the `PYTHON_EGG_CACHE` environment variable. Refer to your server documentation for detailed instructions on how to set environment variables.
-== Configuring Authentication
-Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the `REMOTE_USER` variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.
-The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.
-Please refer to one of the following sections:
- * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`.
- * [wiki:TracModWSGI#ConfiguringAuthentication TracModWSGI#ConfiguringAuthentication] if you use the Apache web server, with any of its front end: `mod_wsgi`, `mod_python`, `mod_fcgi` or `mod_fastcgi`.
- * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
-[trac:TracAuthenticationIntroduction] also contains some useful information for beginners.
-== Granting admin rights to the admin user
-Grant admin rights to user admin:
-{{{#!sh
-$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
-}}}
-This user will have an //Admin// navigation item that directs to pages for administering your Trac project.
-== Configuring Trac
-TracRepositoryAdmin provides information on configuring version control repositories for your project.
-== Using Trac
-Once you have your Trac site up and running, you should be able to create tickets, view the timeline, browse your version control repository if configured, etc.
-Keep in mind that //anonymous// (not logged in) users can by default access only a few of the features, in particular they will have a read-only access to the resources. You will need to configure authentication and grant additional [TracPermissions permissions] to authenticated users to see the full set of features.
-'' Enjoy! ''
-[trac:TracTeam The Trac Team]
-----
-See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade, TracPermissions

wiki/pages/TracInterfaceCustomization

-                      r38413
+                      r39712
-= 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

-                      r38413
+                      r39712
-||=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

-                      r38413
+                      r39712
-= 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/gr/Plugins-Channel-Lists

-                      r37662
+                      r39712
-[[TranslatedPages]]
-'''10.6 Channel Lists''' [=#point10.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-Channel list's are provided by other users.[[br]]
-They contain complete satellite listings aswell as sorted favourites to make it[[br]]
-easier for you to use on your receiver.
-[[br]]
-A list of the current channel lists provided are:
-Satellite:
- * Hotbird 13.0
- * Astra 19.2
- * Astra 28.2
-Cable:
- * Cable germany
- * Cable BW
- * Cable Unitymedia
- * Primacom Cable
-If you wish to provide your own satellite configurations please post them in the [http://aaf-digital.info AAF forum].
-----
-||= '''Default Kabel''' =||= '''Default Sat''' =||= '''Matze70 Neues Design''' =||= '''Matze70 Sat''' =||
-||= [[Image(source:/ipk/source/settings_cableD_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_default_sat_1_0/preview/prev.png)]] =||= [[Image(source:ipk/source/settings_matze70neueDesign_sat19_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_matze70_sat_1_0/preview/prev.png)]] =||
-[[br]]
-||= '''Bulldog 3xsat''' =||= '''Sofa Kabel-BW''' =||= '''Uljanow Sat''' =||= '''Unitymedia Cable''' =||
-||= [[Image(source:/ipk/source/settings_bulldog_3xSat_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_sofa_cableBW_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_uljanow_1sat_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_unitymedia_cable/preview/prev.png)]] =||
-[[br]]
-||= '''Primacom Kabel''' =||= '''Settings Eutelsat 36.0''' =||= '''Kabel Deutschland UH-Kreis''' =||= '''Sat Astra ORF''' =||
-||= [[Image(source:/ipk/source/settings_primacom_cable_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_ser6_eutelsat36_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_paule_cable_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_orf_1xsat_1_0/preview/prev.png)]] =||
-[[br]]
-||= '''Kabelplus ORF''' =||= '''Astra 19.2 KabelD''' =||= '''Bulldog 2xsat''' =||= '''Bulldog 1xsat''' =||
-||= [[Image(source:/ipk/source/settings_kabelplus_cable_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_default_all_2_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_bulldog_2xSat_1_0/preview/prev.png)]] =||= [[Image(source:/ipk/source/settings_bulldog_1xsat_1_0/preview/prev.png)]] =||
-[[br]]
-||= '''SAT/Cable 19.2 13.0 KabelD''' =||
-||= [[Image(source:/ipk/source/settings_andy_2xSat_KabelD_1_0/preview/prev.png)]] =||
-[#point10.6 Top of Page]

wiki/pages/it/Plugins-Screensavers

-                      r37419
+                      r39712
 ||= [[Image(source:/ipk/source/screensaver_dreamy.fantasy_1.0/preview/prev.png,link=source:/ipk/source/screensaver_dreamy.fantasy_1.0/_path_/usr/local/share/titan/saver/dreamy.fantasy)]] =||=[[Image(source:/ipk/source/screensaver_eisriesenwelt_1_0/preview/prev.png,link=source:/ipk/source/screensaver_eisriesenwelt_1_0/_path_/usr/local/share/titan/saver/eisriesenwelt)]] =||= [[Image(source:/ipk/source/screensaver_fantasy.girls_1.0/preview/prev.png,link=source:/ipk/source/screensaver_fantasy.girls_1.0/_path_/usr/local/share/titan/saver/fantasy.girls)]] =||= [[Image(source:/ipk/source/screensaver_fcbayern_1_0/preview/prev.png,link=source:/ipk/source/screensaver_fcbayern_1_0/_path_/usr/local/share/titan/saver/fcbayern)]] =||= [[Image(source:/ipk/source/screensaver_flowers_1.0/preview/prev.png,link=source:/ipk/source/screensaver_flowers_1.0/_path_/usr/local/share/titan/saver/flowers)]] =||= [[Image(source:/ipk/source/screensaver_games_1.0/preview/prev.png,link=source:/ipk/source/screensaver_games_1.0/_path_/usr/local/share/titan/saver/games)]]
 [[br]]
+||= '''HDR Pictures''' =||= '''Hotgirls 1''' =||= '''Hotgirls 2''' =||= '''Inspirational''' =||= '''Love''' =||= '''Movies''' =||
+||= [[Image(source:/ipk/source/screensaver_HDR-Pictures_1.0/preview/prev.png,link=source:/ipk/source/screensaver_HDR-Pictures_1.0/_path_/usr/local/share/titan/saver/HDR-Pictures)]] =||=[[Image(source:/ipk/source/screensaver_hotgirls_1_0/preview/prev.png,link=source:/ipk/source/screensaver_hotgirls_1_0/_path_/usr/local/share/titan/saver/hotgirls)]] =||= [[Image(source:/ipk/source/screensaver_hotgirls_2.0/preview/prev.png,link=source:/ipk/source/screensaver_hotgirls_2.0/_path_/usr/local/share/titan/saver/hotgirls_2)]] =||= [[Image(source:/ipk/source/screensaver_inspirational_1.0/preview/prev.png,link=source:/ipk/source/screensaver_inspirational_1.0/_path_/usr/local/share/titan/saver/inspirational)]] =||= [[Image(source:/ipk/source/screensaver_love_1.0/preview/prev.png,link=source:/ipk/source/screensaver_love_1.0/_path_/usr/local/share/titan/saver/love)]] =||= [[Image(source:/ipk/source/screensaver_movies_1.0/preview/prev.png,link=source:/ipk/source/screensaver_movies_1.0/_path_/usr/local/share/titan/saver/movies)]]
+[[br]]
+||= '''Nature Landscape''' =||= '''Others''' =||= '''Photography''' =||= '''Planes''' =||= '''Radio''' =||= '''Sports''' =||
+||= [[Image(source:/ipk/source/screensaver_nature.landscape_1.0/preview/prev.png,link=source:/ipk/source/screensaver_nature.landscape_1.0/_path_/usr/local/share/titan/saver/nature.landscape)]] =||=[[Image(source:/ipk/source/screensaver_others_1.0/preview/prev.png,link=source:/ipk/source/screensaver_others_1.0/_path_/usr/local/share/titan/saver/others)]] =||= [[Image(source:/ipk/source/screensaver_photography_1.0/preview/prev.png,link=source:/ipk/source/screensaver_photography_1.0/_path_/usr/local/share/titan/saver/photography)]] =||= [[Image(source:/ipk/source/screensaver_planes_1.0/preview/prev.png,link=source:/ipk/source/screensaver_planes_1.0/_path_/usr/local/share/titan/saver/planes)]] =||= [[Image(source:/ipk/source/screensaver_radio_1.0/preview/prev.png,link=source:/ipk/source/screensaver_radio_1.0/_path_/usr/local/share/titan/saver/radio)]] =||= [[Image(source:/ipk/source/screensaver_sports_1.0/preview/prev.png,link=source:/ipk/source/screensaver_sports_1.0/_path_/usr/local/share/titan/saver/sports)]]
+[[br]]
+||= '''Travel World''' =||
+||= [[Image(source:/ipk/source/screensaver_travel.world_1.0/preview/prev.png,link=source:/ipk/source/screensaver_travel.world_1.0/_path_/usr/local/share/titan/saver/travel.world)]] =||
+[[br]]
+([#point10.1 Top of Pge])
+||= '''HDR Pictures''' =||= '''Hotgirls 1''' =||= '''Hotgirls 2''' =||= '''Inspirational''' =||= '''

wiki/pages/it/Plugins-Skins

-                      r37419
+                      r39712
-[[TranslatedPages]]
-----
-'''10.14 Skins''' [=#point10.14] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Installing one of the follwing skins will change the look of the titan interface you may select and install skins from the online extentions.[[br]]
-||= '''0Acht5Zehn''' =||= '''0Acht5Zehnblack''' =||= '''0Acht5Zehnwhite''' =||= '''Cool''' =||= '''CoolMiniTV''' =||= '''Default''' =||
-||= [[Image(source:/ipk/source/skins_0Acht5Zehn/preview/prev.png,link=source:/ipk/source/skins_0Acht5Zehn/_path_/usr/local/share/titan/skin/0Acht5Zehn)]] =||=[[Image(source:/ipk/source/skins_0Acht5Zehnblack/preview/prev.png,link=source:/ipk/source/skins_0Acht5Zehnblack/_path_/usr/local/share/titan/skin/0Acht5Zehn_black)]] =||= [[Image(source:/ipk/source/skins_0Acht5Zehnwhite/preview/prev.png,link=source:/ipk/source/skins_0Acht5Zehnwhite/_path_/usr/local/share/titan/skin/0Acht5Zehn_white)]] =||= [[Image(source:/ipk/source/skins_cool/preview/prev.png,link=source:/ipk/source/skins_cool/_path_/usr/local/share/titan/skin/cool)]] =||= [[Image(source:/ipk/source/skins_coolMiniTV/preview/prev.png,link=source:/ipk/source/skins_coolMiniTV/_path_/usr/local/share/titan/skin/coolMiniTV)]] =||= [[Image(source:/ipk/source/skinsdefault_default/preview/prev.png,link=source:/ipk/source/skinsdefault_default/_path_/usr/local/share/titan/skin/default)]]
-=||
-[[br]]
-||= '''Default no MiniTV''' =||= '''Megastyle-Blue''' =||= '''Megastyle-Blue-MiniTV''' =||= '''MegaStyle-Grey''' =||= '''MegaStyle-Grey-MiniTV''' =||= '''MetrixHD''' =||
-||= [[Image(source:/ipk/source/skinsdefault_defnominitv/preview/prev.png,link=source:/ipk/source/skinsdefault_defnominitv/_path_/usr/local/share/titan/skin/defnominitv)]]||= [[Image(source:/ipk/source/skins_MegaStyle_blue/preview/prev.png,link=source:/ipk/source/skins_MegaStyle_blue/_path_/usr/local/share/titan/skin/MegaStyle-Blue)]] =||=[[Image(source:/ipk/source/skins_MegaStyle_blue_MiniTV/preview/prev.png,link=source:/ipk/source/skins_MegaStyle_blue_MiniTV/_path_/usr/local/share/titan/skin/MegaStyle-Blue-MiniTV)]] =||= [[Image(source:/ipk/source/skins_MegaStyle_grey/preview/prev.png,link=source:/ipk/source/skins_MegaStyle_grey/_path_/usr/local/share/titan/skin/MegaStyle-Grey)]] =||= [[Image(source:/ipk/source/skins_MegaStyle_grey_MiniTV/preview/prev.png,link=source:/ipk/source/skins_MegaStyle_grey_MiniTV/_path_/usr/local/share/titan/skin/MegaStyle-Grey-MiniTV)]] =||= [[Image(source:/ipk/source/skins_MetrixHD/preview/prev.png,link=source:/ipk/source/skins_MetrixHD/_path_/usr/local/share/titan/skin/MetrixHD)]]
-=||
-[[br]]
-||= '''NoGfx''' =||= '''NoGfx Grey''' =||= '''SmartTV''' =||= '''tobayer01''' =||= '''ufs912''' =||
-||= [[Image(source:/ipk/source/skins_nogfx/preview/prev.png,link=source:/ipk/source/skins_nogfx/_path_/usr/local/share/titan/skin/nogfx)]]=||= [[Image(source:/ipk/source/skins_nogfx_grey/preview/prev.png,link=source:/ipk/source/skins_nogfx_grey/_path_/usr/local/share/titan/skin/nogfx_grey)]] =||=[[Image(source:/ipk/source/skins_smartTV/preview/prev.png,link=source:/ipk/source/skins_smartTV/_path_/usr/local/share/titan/skin/smartTV)]] =||= [[Image(source:/ipk/source/skins_tobayer01/preview/prev.png,link=source:/ipk/source/skins_tobayer01/_path_/usr/local/share/titan/skin/tobayer01)]] =||= [[Image(source:/ipk/source/skins_ufs912/preview/prev.png,link=source:/ipk/source/skins_ufs912/_path_/usr/local/share/titan/skin/ufs912)]]
-=||
-([#point10.14 Top of Page])

wiki/pages/it/Plugins-Tools

-                      r37419
+                      r39712
-[[TranslatedPages]]
-----
-'''10.16 Tools''' [=#point10.16] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_autotimer/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Auto timer'''
- Set repeat timers for timer recordings to automatically record[[br]]
- the same program in future (i.e. serials) or automatic channel switch
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_callmonitor/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Callmonitor'''
- Incoming / outgoing phone calls are displayed on the screen.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_filemanager/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Filemanager'''
- Access your files on the receiver and external drives[[br]]
- move/copy/delete them.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_IP-Kamera/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''IP Camera'''
- An in-network IP camera can be displayed on the screen.[[br]]
- Movement of the camera is possible if the camera supports it.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th style="border: none" rowspan=0 align=left
-[[Image(source:/ipk/source.sh4/tools_lcdpearl1/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''LCD-Pearl'''
- Viewing EPG info, station logos, on the small external Pearl-USB picture frame.[[br]]
- Additional Skin informationcan be found at ([wiki:Plugins-LcdPearlSkins#point110.8 10.8 LCD Pearl Skins]).
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_lcdsamsung/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
-  '''LCD-Samsung'''
- Viewing EPG info, station logos, on the small external Samsung-USB picture frame.[[br]]
- Additional Skin informationcan be found at ([wiki:Plugins-LcdSamsungSkins#point110.9 10.9 LCD Samsung Skins]).
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_optimize/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Optimize'''[[BR]][[BR]]
- A tool to optimize the channel lists in TitanNit. Redundant transmitters[[br]]
- and transponders can be removed here.[[br]]
- The speed when scrolling through the channel list increases.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_parted/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Parted'''
- Parted is neccessary to format a Harddisk with a capacity larger 2TB. After installing[[br]]
- the plugin it is active so you can setup your Haiddisk straight away.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_PermanentTime/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Permanent Time'''
- Activate it and the time is shown permanently on your screen[[br]]
- until you call up the function again to deactivate it.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_tsschnitt/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Record cut'''
- With 'Record cut' You can edit the recordings in titan by cutting the beginning and end.[[br]]
- Start the desired movie with the internal player, at the desired start-point and End-point[[br]]
- press the -0- Key on your Remote Control. To view the set markers press -5- on your Remote Control.[[br]]
- 'Record cut' is now started and by pressing the -Green- button select the movie and with the -Blue- button[[br]]
- By pressing the -Yeelow- button the cutting process can be executed in the backbround.[[br]]
- After the Process has finished an information is shown on the TV-screen.[[br]]
- The Process can be watched or abborted by pressing the -Red- button.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_rgui/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''RGUI'''
- With Rgui you can access a different Titan Receiver.[[br]]
- You may also access the TV Program of the other receiver.[[br]]
- Streaming between both receivers is also possible.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_scriptexec/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Scriptexec'''
- A small plugin to execute code on the receiver.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_stopifnotused/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''stop if not used'''
- Your receiver is automatically turned off after a set time should no further Key be pressed.[[br]]
- Autostart = yes / no - Time to Action (min) = 30/60/90/120/180/240 - Action = standby / off
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_usbreset/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''USB Reset'''
- Attached USB devices are re-read.
-}}}
-([#point10.16 Top of Page])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/ipk/source.sh4/tools_zapback/preview/prev.png)]]
-}}}
-|----------------
-{{{#!td style="border: none"
- '''Zapback'''
- Zapback will after a given time automatically switch back to a pre-set channel .
-}}}
-([#point10.16 Top of Page])

wiki/pages/it/Plugins-Wlan

-                      r37662
+                      r39712
-[[TranslatedPages]]
-----
-'''10.17 WLAN Module''' [=#point10.17] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-TitanNit is compatable with several usb Wireless lan devices below is a list of compatable wireless modules chipset's:
- * Realtek RTL8192SE (802.11N)
- * Realtek RTL8712U (802.11N)
- * Ralink RT2870STA (802.11N)
- * Ralink RT3070STA (802.11N)
- * Ralink RT5370STA (802.11N)
-Drivers can be installed from any of the above devices from the online extentions ([wiki:TPK-Install#point3.4.4 TPK Install (Online)])
-||= '''WLAN 8192 driver''' =||= '''WLAN Driver 8172u''' =||= '''WLAN Driver rt2870sta''' =||= '''WLAN Driver rt3070sta''' =||= '''WLAN Driver rt5370sta''' =||
-||= [[Image(source:/ipk/source.sh4/wlan_8192cu/preview/prev.png)]] =||= [[Image(source:/ipk/source.sh4/wlan_8712u/preview/prev.png)]] =||= [[Image(source:/ipk/source.sh4/wlan_rt2870sta/preview/prev.png)]] =||= [[Image(source:/ipk/source.sh4/wlan_rt3070sta/preview/prev.png)]] =||= [[Image(source:/ipk/source.sh4/wlan_rt5370sta/preview/prev.png)]] =||

wiki/pages/it/Plugins-station-logos

-                      r37419
+                      r39712
-[[TranslatedPages]]
-----
-'''10.13 Channel logos (Picons)''' [=#point10.13] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-'''picons_transparent'''
-[[Image(source:/ipk/source/picons_transparent_SAT13_0/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_transparent_SAT19_2/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_transparent_SAT23_5/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_transparent_SAT28_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point110.13 Top of Page])
-'''picons_black3d'''
-[[Image(source:/ipk/source/picons_black3d_SAT13_0/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_black3d_SAT19_2/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_black3d_SAT23_5/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point10.13 Top of Page])
-'''picons_gold'''
-[[Image(source:/ipk/source/picons_gold_SAT13_0/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_gold_SAT19_2/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_gold_SAT23_5/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_gold_SAT28_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point10.13 Top of Page])
-'''picons_Kabel'''
-[[Image(source:/ipk/source/picons_KabelBW/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_KabelDblack3d/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_KabelDtransparent/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_spiegel_SAT19_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point10.13 Top of Page])
-'''picons_transparent_small_black'''
-[[Image(source:/ipk/source/picons_transparent_small_black_SAT19_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point10.13 Top of Page])
-'''picons_white3d'''
-[[Image(source:/ipk/source/picons_white3d_SAT13_0/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_white3d_SAT19_2/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_white3d_SAT23_5/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_white3d_SAT28_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point110.13 Top of Page])
-'''picons_white70'''
-[[Image(source:/ipk/source/picons_white70_SAT13_0/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_white70_SAT19_2/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_white70_SAT23_5/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_white70_SAT28_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point10.13 Top of Page])
-'''picons_X_LightTransparen'''
-[[Image(source:/ipk/source/picons_X_LightTransparent_SAT13_0/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_X_LightTransparent_SAT19_2/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_X_LightTransparent_SAT23_5/preview/prev.png)]]
-[[Image(source:/ipk/source/picons_X_LightTransparent_SAT28_2/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point110.13 Top of Page])
-'''picons_X_LightTransparent_SAT19_2_small'''
-[[Image(source:/ipk/source/picons_X_LightTransparent_SAT19_2_small/preview/prev.png)]]
-[[BR]]
-[[br]]
-([#point10.13 Top of Page])

wiki/pages/it/Power-Off-Timer

-                      r37419
+                      r39712
-[[TranslatedPages]]
->----
->'''3.8.4 Power Off Timer''' [=#point3.8.4] ([wiki:Interface-Operation#point3.8 Standby-Poweroff (return)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Power-Off-Timer.jpg)]][[br]]
+>
-> here you change your shutdown settings such as fixed shutdown timer.
-[[br]]

wiki/pages/it/Quick-Start-Guide

-                      r37377
+                      r39712
-[[TranslatedPages]]
-----
-'''Quick Start Guide''' [=#point0] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-New Gui section work in progress expect dead links or missing data.
-----
-TitanNit was designed to do two things really well. It can display live tv and it play your videos and recordings, the scope of this quick start guide will explain the setup and operation of those features in a short precise way.
-This section was designed for those who do not care to ever read the manual and just want to jump in and get their hands dirty in all that is TitanNit.
-Note: It is asumed the decoder has just been freshly removed from the packing or freshly had TitanNit installed and is booted with the default settings if you wish to install TitanNit please see the section [wiki:Installation-Recovery#point8 Installation and Recovery Contents]
-be aware that as TitanNit has been developed for multiple hardware devices the precedures outlined below may not be the same as your reciever.
-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/quick-start-guide/Setting_Up_the_Language.png,align=left,link=[#point0.1])]]
-  }}}
-  '''([#point0.1 Setting Up the language])'''[[br]]
-  {{{#!div style="float: left
-click here to find info on setting up the language
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up_the_Network.png,align=left,link=[#point0.2])]]
-  }}}
-  '''([#point0.2 Setting Up the Network])'''[[br]]
-  {{{#!div style="float: left
-click here to find info on setting up the Network
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up_the_HDD.png,align=left,link=[#point0.3])]]
-  }}}
-  '''([#point0.3 Setting Up the Hdd])'''[[br]]
-  {{{#!div style="float: left
-click here to find info on setting up the HDD
-  }}}
-  }}}
-  |---
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up-the_Tuner.png,align=left,link=[#point0.4])]]
-  }}}
-  '''([#point0.4 Setting Up the Tuner])'''[[br]]
-  {{{#!div style="float: left
-click here to find info on Setting Up the Tuner
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Preforming_a_Scan.png,align=left,link=[#point0.5])]]
-  }}}
-  '''([#point0.5 Proforming a Scan])'''[[br]]
-  {{{#!div style="float: left
-click here to find info Proforming a Scan
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Orginising_Your_Channels.png,align=left,link=[#point0.6])]]
-  }}}
-  '''([#point0.6 Orginising Your Channels])'''[[br]]
-  {{{#!div style="float: left
-click here to find info on Orginising Your Channels
-  }}}
-  }}}
-  |---
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up_Media.png,align=left,link=[#point0.7])]]
-  }}}
-  '''([#point0.7 Setting Up a Media])'''[[br]]
-  {{{#!div style="float: left
-click here to find info on Setting Up a Media
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Playing_Back_Media.png,align=left,link=[#point0.8])]]
-  }}}
-  '''([#point0.8 Playing Back Media])'''[[br]]
-  {{{#!div style="float: left
-click here to find info Playing Back Media
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Conclusion.png,align=left,link=[#point0.9])]]
-  }}}
-  '''([#point0.9 Conclusion])'''[[br]]
-  {{{#!div style="float: left
-Conclusion/ what to do next after stting up Titan
-  }}}
-  }}}
-  |----
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Apendixcies.png,align=left,link=[#point0.10])]]
-  }}}
-  '''([#point0.10 Apendixcies])'''[[br]]
-  {{{#!div style="float: left
-Apendixcies/ references [[br]]to other setup related topics.
-  }}}
-  }}}
-}}}
-}}}
-[[br]]
-[[br]]
-----
-''' Welcome to TitanNit! '''
-----
-Congratulations new users to your choice in your new Atemio Receiver or on the instalation of TitanNit onto your exising receiver. The TitanNit interface is designed with the 'Home Theater' in mind. This means it is best viewed on a large-screen TV while you sit on your couch 10-feet away from the TV, If it helps, you can think of TitanNit as the ultimate media player/Set-top-box, rather than just another set top box operating system.
-----
-'''Setting Up the Language''' [=#point0.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-By default the language of the TitanNit interface is in German and must be switched on setup to your language.
-To set up the language of the interface go to menu the __"Menu"__ and select > __"Einstellungen"__ > __"Sprache"__ then select the language desired then the reciever will then reboot and restart with the new language settings.
-[[Image(source:/wiki/Wiki-Pictures/IT/Language.jpg, 50%)]][[BR]]
-[[br]]
-[[br]]
-----
-'''Setting Up the Network''' [=#point0.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-To Set Up the Network Interface of the receiver go into the __"Menu"__ and select > __"System"__ > __"Network"__
-[[Image(source:/wiki/Wiki-Pictures/IT/system-Network.jpg, 50%)]][[BR]]
-If you wish to setup a wired network select __"LAN Interface Setup"__ and press the red button.
-you will then be presented with a list of network settings, set up your reciever as required and press __"OK"__ and follow the on screen propmts.
-If you wish to setup a wireless network select __"WLAN"__
-if your sever is sending out a ssid you may press the __"Red button"__ and preform a scan of available networks, select your network and press ok to save.
-you will then need to set your security type and key using the remote and press the __"green button"__ to start the network connection.
-[[br]]
-[[br]]
-----
-'''Setting Up the Hdd''' [=#point0.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-If you have just purchased your receiver or converted from the manufactures included software the hdd will need formatting and setting up for use with TitanNit.
-To format the Hdd of the receiver to be able to be used with TitanNit go into the __"Menu"__ and select > __"System"__ > __"Storage Device"__ and select __"format Device"__ then select the hdd you wish to format. (Note: doing this will remove all content on the hdd if you have important data on there please back it up before preforming this step.)
-you will then need to select the type of file system you wish to use on the hdd if you have no idea what to pick leave it as default, select an item and press the __"OK"__ button.
-[[Image(source:/wiki/Wiki-Pictures/IT/Format-Hdd.jpg, 50%)]][[br]]
-Now that the Hdd is formatted you may set it up, go into the __"Menu"__ and select > __"System"__ > __"Storage Device"__ and select __"Configure device"__
-Select the Hdd you formatted before and and then you will be presented with a set of features to enable the hard disk to be used for.
-I suggest you enable all options.
-[[br]]
-[[br]]
-----
-'''Setting up the Tuner''' [=#point0.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Before you can watch TV you must set the tuner up in the Reciver as your system is physically connected to your Satellite cable or trestrial antenna.
-As no two systems are the same we will show you how to set up a simple single universal lnb connected to your reciever with a list of satellites in your sky you wish to receive.
-Before we can do this we need to program in a list of satellites and transponders as not all satellite lists are installed in the Reciever by default.
-''Setting up the default transponder/satellite lists''
-Programming in transponders can be quite daunting for new users so the devs have set up a simple way to program your transponders into yoru receiver, the [wiki:Create-Transponder-List#point3.5.1.7 Create Transponder List] function can download transponders for various services from the TitanNit online repo, this will save you from having to manually create these lists from your pc, receiver or from a satellite xml generator, this greatly simpifly channel and tuner setup.
-(Note that these transponder lists may not allways be 100% correct as services may change)
-[[Image(source:/wiki/Wiki-Pictures/IT/Create-Transponder-List.jpg, 50%)]][[br]]
-Go into the __"Menu"__ and select > __"System"__ > __"Channel setup"__ > __"Create Transponder List"__ and follow the onscreen propmts to download a current list of transponders from your selected tuner type.
-Alternativly you can use the[wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor] from your pc this is a little bit more flexible that you can just program in the satellites you wish to recieve as opposed to every satelite or transponder programmed into the repo, the hard core or pro users may prefer this option to customise their setup.
-Proform these steps in this sequence to import a list of satellites on to your receiver:
- * Download a satellite xml file for the satellites you wish to receive from an [[http://satellites-xml.eu/ | Online xml generator]]
- * Download and install [wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor] to your pc and set up a connection to your receiver.
- * Import the xml file.
-[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/Import-Satellite.png)]]
- * Upload the satellite.xml file to your receiver
-[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/6.png)]]
-The reciever will then reboot if it does not then reboot manually to comit the changes.
-''Setting up the tuner''
-To Set up the Tuner of the receiver go into the __"Menu"__ and select > __"System"__ > __"Channel setup"__
- * 1 Select tuner 0/0 and press the sideways key and select __"Tuner looped to 0/1"__
- * 2 Select tuner 0/1 and press the sideways key and select __"Tuner looped to 0/0"__
- * 3 Select tuner 0/0 and press the __"Red Button"__ to configuere the tuner
- * 4 Select the satellite type press sideways and select __"Single Lnb"__.
- * 5 Scroll down and select __"SAT 1"__ press the sideways key and select the satellite you wish to receive.
- * 6 Scroll down to Lnb/Unicable and press the __"Red Button"__ to configure the lnb type.
- * 7 scroll down to LOF/Unicable press the sideways key and select universal.
- * 8 Press ok button twice to store the lnb type and tuner configuration.
- * Repeat steps 4-8 on tuner 0/1
-your lnb is now set up and if all was done correctly you should now be able to scan for stations on the selected satellite.
-[[br]]
-[[br]]
-----
-'''Proforming a Scan''' [=#point0.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Before you can watch TV you must preform a scan of the transponders for available channels
-To Proforming a Scan of the receiver go into the __"Menu"__ and select > __"System"__ > __"Channel Service"__ >__"Automatic Search"__ and press the __"Red Button"__ as you have already setup your satellites and transponders the default settings will be ok.
-[[Image(source:/wiki/Wiki-Pictures/IT/Automatic-Search.jpg, 50%)]]
-Once the scan has finished you may press the __"Green"__ button to store all the channel data or alternativly you may select the individual channels and press the __"Red"__ button.
-[[br]]
-[[br]]
-----
-'''Orginising Your Scanned Channels''' [=#point0.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Now you have your receiver setup you can start to watch tv if you exit from the menu after proforming the scan you should be presented with a high definition display of your local tv stations.
-but as you may notice they are un orginised and it may be hard finding the tv stations you wish to watch for this you can orginise them in to your own persionalised favourite menu's.
-The easyest way to do this is with the [wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor].
- * Download and install [wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor] to your pc and set up a connection to your receiver.
- * Read in the channel data as follows :
-[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/6.png)]]
-[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/7.png)]]
-'' Favourites setup ''
-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/IT/SCLE/8.png)]]
-After creating the new Favourites entry assign the desired Name:
-[[Image(source:/wiki/Wiki-Pictures/IT/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/IT/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/IT/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/IT/SCLE/12.png)]]
-[[br]]
-[[br]]
-----
-'''Setting Up a Media Source''' [=#point0.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-To Set up a media source to be acessable from the reciever of the receiver go into the __"Menu"__ and select > __"System"__ > __"Network"__> __"Network Browser"__
-[[Image(source:/wiki/Wiki-Pictures/IT/Network-Browser.jpg, 50%)]][[br]]
-now press the __"Red"__ button to add a source and you will be presented with a list of share options.
-set up your share type adress and details for your media server and press __OK"__ to store it in.
-your share will now be mounted and it will now show up in the media/net/ directory
-[[br]]
-[[br]]
-----
-'''Playing Back Media''' [=#point0.8] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-To Play back a media file or recording it is very simple, to open the default media player press the __"PLAY"__ button and you will be presented with the player file select display, Navigate the file list and select the file you wish to play.
-You may play media from your network share by browsing to the media/net if you wish.
-[[Image(source:/wiki/Wiki-Pictures/IT/Internal-Player-OSD.jpg, 50%)]][[br]]
-[[br]]
-[[br]]
-----
-'''Conclusion''' [=#point0.9] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Conclusion
-Thanks for reading this Quick Start Guide. Below in the "Apendixces" section you will find additional suggested reading that may be useful for getting started with the advanced features of TitanNit.
-[[br]]
-[[br]]
-----
-'''Apendixcies''' [=#point0.10] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Please see below for more advanced topics and information
- * [wiki:Interface-Operation#point3 Interface and Operation]
- * [wiki:Remote-Device-Control#point3.9 Remote/ Device Control]
- * [wiki:Installation-Recovery#point8 Installation / Recovery]
- * [wiki:External-Software#point9 External Software]
- * [wiki:Plugins-Contents#point10 Plugins]
- * [wiki:Troubleshooting#point12 Troubleshooting]
-We have tried our best to make this quick start manual as complete and precice as we can if you have any issuies with this manual, wish for something to be added, thank or abuse us please see [wiki:Community#point14 Community] for information on how to contact us.
-Oh and by the way as a final remark thanks for choosing TitanNit!.
-[[br]]
-[[br]]

wiki/pages/it/Ram

-                      r37425
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8.6 Ram''' [=#point3.7.8.6] ([wiki:System-Info#point3.7.8 System Info (Back])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/System-Info-Ram.jpg)]][[br]]
+>
-Here you can view the memory information.
-[[br]]
-[[br]]

wiki/pages/it/Receiver-Unlock

-                      r37425
+                      r39712
-[[TranslatedPages]]
->----
->'''3.5.10 Receiver Unlock''' [=#point3.5.10] ([wiki:Interface-Operation#point3.5 System (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/system_receiver_unlock.jpg)]][[br]]
+>
->Here you can unlock the special features of the decoder after purchase.
-[[br]]

wiki/pages/it/Record-Path

-                      r37419
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.8 Record Path''' [=#point3.6.8] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Record_Path.jpg)]][[BR]]
+>
-> here you can recording directorys.
-[[br]]
- ||'''Movie  Path''' ||This is the path to the Movie Directory.||
- ||'''Timer Record Path:''' ||This is the path to the directory where the timer recordings are stored.||
- ||'''Record Patht''' ||This is the path to the directory where the manual recordings are stored.||
- ||'''Timeshift Path:''' ||This is the path to the directory where the Timeshift files are stored.||
- ||'''Stream Path''' ||This is the path to the directory where temporary Streams are stored.||
- 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: (Edit)''' ||This button allows editing of the above paths it will bring up an onscreen keyboard to edit the string selected.||

wiki/pages/it/Records

-                      r37662
+                      r39712
-[[TranslatedPages]]
->----
->'''3.1.5 Records''' [=#point3.1.5] ([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/IT/Records.jpg)]][[BR]]
+>
->Recordings is where you can set up and edit timer set recordings.
-[[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: (Del)''' ||This will delete the currently selected timer or recording.||
- ||'''Green Button: (Add)''' ||this will add a new timer recording.||
- ||'''Yellow Button: (Stop/ Start)''' ||this will stop or start the currently selected timer recording.||
- ||'''Blue Button: (log)''' ||This will show you the past log file for the past timer recordings.||

wiki/pages/it/Red-Button

-                      r37662
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.4 Red Button''' [=#point3.6.4] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0.2 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Red_Button.jpg)]][[BR]]
+>
->here you can configure what happens with the press of the red button
-[[br]]

wiki/pages/it/Remote-Device-Control

-                      r37425
+                      r39712
-[[TranslatedPages]]
-----
-'''4 Remote/ Device control''' [=#point4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-New Gui section work in progress expect dead links or missing data.
-----
-== Remote/ Device control ==
-This section contains information about how to control your decoder and how it can be controlled from local and remote sources and helpfull information and tricks to get the most possible experience with your Receiver.
- ''Please select a menu item from the GUI 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/Remote-Device-Control/Remote_Control.png,align=left,link=[#point4.1])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.1 4.1 RC Remote control]'''[[br]]
-  {{{#!div style="float: left
-click here to find info on setting up the language
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/On_Device_control.png,align=left,link=[#point4.2])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.2 4.2 On Device Control]'''[[br]]
-  {{{#!div style="float: left
-click here to find info on setting up the Network
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Web_Interface.png,align=left,link=[#point4.3])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.3 4.3 Web Interface]'''[[br]]
-  {{{#!div style="float: left
-click here to find info on setting up the HDD
-  }}}
-  }}}
-  |---
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Telnet_Control.png,align=left,link=[#point4.4])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.4 4.4 Telnet Control]'''[[br]]
-  {{{#!div style="float: left
-click here to find info on Setting Up the Tuner
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Rgui.png,align=left,link=[#point4.5])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.5 4.5 Rgui]'''[[br]]
-  {{{#!div style="float: left
-click here to find info Proforming a Scan
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Bootloader.png,align=left,link=[#point4.6])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader]'''[[br]]
-  {{{#!div style="float: left
-click here to find info on Orginising Your Channels
-  }}}
-  }}}
-  |---
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/TitanNit_WebIF.png,align=left,link=[#point4.7])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.7 4.7 TitanNit WebIF]'''[[br]]
-  {{{#!div style="float: left
-click here to find info on Setting Up a Media
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/FTP.png,align=left,link=[#point4.8])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.8 4.8 FTP (File Transfer Protocol)]'''[[br]]
-  {{{#!div style="float: left
-click here to find info Playing Back Media
-  }}}
-  }}}
-  {{{#!td align=center valign=top style="border: none; font-size: 115%"
-  {{{#!div style="float: left"
-[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Autostart_Scripting.png,align=left,link=[#point4.9])]]
-  }}}
-  '''[wiki:Remote-Device-Control#point4.9 4.9 Autostart Scripting (usercmd.sh)]'''[[br]]
-  {{{#!div style="float: left
-Conclusion/ what to do next after stting up Titan
-  }}}
-  }}}
-}}}
-}}}
-[[br]]
-[[br]]
-----
-'''4.1 RC Remote Control''' [=#point4.1] ([#point4 top of the page])
-----
- * ([#point4.1.1 RC Atevio700])
- * ([#point4.1.2 RC Atevio7000, Atevio7500, Atemio7600])
- * ([#point4.1.3 RC Atemio500, Atemio510])
- * ([#point4.1.4 RC Atemio520])
- * ([#point4.1.5 RC Atemio520-V2])
- * ([#point4.1.6 RC Atemio530])
- * ([#point4.1.7 RC UFS910])
- * ([#point4.1.8 RC UFS912])
- * ([#point4.1.9 RC UFS922])
-[[BR]]
-[[BR]]
-[[BR]]
-'''4.1.1 RC Remote Control Atevio700''' [=#point4.1.1]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.atevio700.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC Atevio 700'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.2 RC Remote Control Atevio7000, Atevio7500, Atemio7600''' [=#point4.1.2]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.atevio7000.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
- The section contains information on the functions and operation of your remote control unit.
- '''Special Function Buttons operation during channel streaming'''
- ||'''Resolution:''' ||This Key Switches the videomode.||
- ||'''V.Format:''' ||This Key Switches the Video format.||
- ||'''Recall:''' ||This key can bring up the recent channel history so you can jump easily between programs.||
- ||'''Info:''' ||This Button displays the infobar.||
- ||'''fav:''' ||This button brings up the favourite and Bouquet lists to easily select programs.||
- ||'''Menu:''' ||This key opens the menu.||
- ||'''Sleep:''' ||This Key can setup the sleep timer.||
- ||'''Help:''' ||This key can display detailed information and help text's.||
- ||'''Exit:''' ||This key exits menus and popups .||
- ||'''text:''' ||This key shows the teletext display.||
- ||'''Ok:''' ||This button confirms menu items and popups.||
-[[br]]
-'''Programming the universal remote to operate a supported TV'''
-This section explains how to automatically search and program your universal remote control to operate your tv
-NOTE: If there are no inputs for 10 seconds during setting the TV RC code the setting mode is terminated.
-'''Automatic code search '''
- * Press the TV / Atevio button on the remote (for at least 3 seconds) until the LED flashes twice.
-   Enter the code 001. The LED flashes twice to confirm the entry.
- * Press and hold the "ON / OFF" button until the TV turns off.
-   Note: The LED flashes every 1.5 seconds and sends a new TV power rc code.
- * Release the button immediately then press the "OK" button to store the TV code.
-  (This can take up to 15 minutes to cycle all the tv's pre programmed in to the remote from the factory)
-   If you dont let go of the power key in time it will step to the next RC Power button code if this happens use the D-Pad down to rewind 5 codes to attempt to store the code again.
- * To interrupt the search mode, press the Exit button for 2 seconds and return to normal operation or wait for 10 seconds with no key presses.
- * The remote control blinks 5 times at the end of the list if the tv has not turned off by the time your tv is not a supported model.
-'''Reset remote to factory programming'''
-This will reset the remote back to a factory non programmed state, this is necessary if the remote  needs to be reprogrammed to operate a new TV and was previously programmed.
- * Press the TV / Atevio button on the remote (for at least 3 seconds) until the LED flashes twice.
- * Enter the code 000.
- * The LED flashes twice to confirm the entry. The remote control will now be reset (no code programmed)
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.3 RC Remote Control Atemio 500 / Atemio 510''' [=#point4.1.3]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.atemio510.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC Atemio 500/510'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.4 RC Remote Control Atemio 520''' [=#point4.1.4]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.atemio520.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC Atemio 520'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.5 RC Remote Control Atemio 520 V2''' [=#point4.1.5]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.atemio520-V2.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC Atemio 520-V2'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.6 RC Remote Control Atemio 530''' [=#point4.1.6]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.atemio530.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC Atemio 530'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.7 RC Remote Control Kathrein UFS910''' [=#point4.1.7]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.ufs910.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC UFS 910'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.8 RC Remote Control Kathrein UFS912''' [=#point4.1.8]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.ufs912.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC UFS912'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-'''4.1.9 RC Remote Control Kathrein UFS922''' [=#point4.1.9]  ([#point4.1 back])
-[[BR]]
-{{{#!th rowspan=0 align=left style="border: none"
-[[Image(source:/titan/web/img/rc.ufs922.png)]][[br]]
-}}}
-|----------------
-{{{#!td style="border: none"
-'''TEXT RC UFS922'''
-}}}
-[[br]]
-[[br]]
-[[br]]
-[[br]]
-----
-'''4.2 On Device Control''' [=#point4.2] ([#point4 top of the page])
-----
-[[Image(source:/wiki/Wiki-Pictures/IT/On_Device_Control.jpg)]][[br]]
-The section contains information on the functions and operation of your Receiver from the onboard buttons.
-Please note: the control is very limited from the on device controls but simple menu and tv control's can be made:
-'''Device Controll keys'''
- ||'''Power''' ||This Key Switches to the power menu or shuts down depending on the "power action" see ([#point3.6.6 Adjust]) for more info. ||
- ||'''Menu:''' ||This Key brongs up the on screen display/ menu. ||
- ||'''Ok:''' ||This key accept on screen prompts. ||
- ||'''D-pad:''' ||These buttons can control the volume and TV channel when on the TV display it can also be used to navigate the menu and on screen prompts. ||
-----
-'''4.3 Web Interface''' [=#point4.3] ([#point4 top of the page])
-----
-[[Image(source:/wiki/Wiki-Pictures/IT/Web_Control.jpg)]][[br]]
-The section contains information on the functions and operation of your Receiver from the web interface over LWAN, LAN or wifi.
-[[br]]
-----
-'''4.3.1 Channel list''' [=#point4.3.1] ([#point4 top of the page])
-----
-[[br]]
- ||'''All''' ||Show All Channels from all Bouquets .||
- ||'''Sat''' ||Sort channels By Satellite.||
- ||'''provider:''' ||Sort channels By provider.||
- ||'''A-Z:''' ||Sort channels Alphabetically.||
- ||'''Bouquets:''' ||Sort channels By Boquet.||
-[[br]]
-----
-'''4.3.2 Box Control''' [=#point4.3.2] ([#point4 top of the page])
-----
-[[br]]
- ||'''Power Control:''' ||This brings up the links to control the power settings (shutdown, restart, etc....)||
- ||'''Message:''' ||Send a message to the display of the tv.||
- ||'''Remote:''' ||Bring up the remote on the web page for control of the decoder.||
- ||'''Screenshot OSD:''' ||Take a screen shot of the OSD.||
- ||'''Play Movie (URL:''' ||Play a movie from the selected url.||
-[[br]]
-----
-'''4.3.3 Movies''' [=#point4.3.3] ([#point4 top of the page])
-----
-[[br]]
-This will bring up a list of the movie directory on the receiver please see ([#point3.12.5 Web Controls]) for more information
-[[br]]
-----
-'''4.3.4 Timer''' [=#point4.3.4] ([#point4 top of the page])
-----
-[[br]]
- ||'''Timer List:''' ||Show a list of the timer Recordings.||
- ||'''Timer Archive:''' ||Show a list of all the completed timer recordings.||
- ||'''Add Timer:''' ||Add a timer recording.||
-[[br]]
-----
-'''4.3.5 System''' [=#point4.3.5] ([#point4 top of the page])
-----
-[[br]]
- ||'''Extensions:''' ||Show a list of alailable extensions and plugins to install.||
- ||'''System update:''' ||Update the system  software.||
- ||'''System Backup:''' ||backup the system to an image file.||
- ||'''Settings Backup/ restore:''' ||Take/ restore a backup of the current settings and config.||
-[[br]]
-----
-'''4.3.6 Settings''' [=#point4.3.6] ([#point4 top of the page])
-----
-[[br]]
- ||'''system settings:''' ||This brings up a list of the items in the adjust menu of the receiver See [wiki:Adjust#point3.6.6 Adjust] for more information on the items in this menu.||
- ||'''Oscam web interface:''' ||Shows config http information for the oscam plugin (if installed).||
- ||'''Xupnpd:''' ||Shows information on the Xupnpd media streaming plugin.||
-[[br]]
-----
-'''4.3.7 Information''' [=#point4.3.7] ([#point4 top of the page])
-----
-[[br]]
-This section contains detailed config and system info about your reciever and TitanNit.
-Please see the below links for more information on the items contained with in this menu.
- * ([wiki:Service#point3.7.1 Service])
- * ([wiki:News-letter#point3.7.2 News letter])
- * ([wiki:About#point3.7.3 About])
- * ([wiki:Streaming#point3.7.4 Streaming])
- * ([wiki:Atemio-Hotline#point3.7.5 Atemio (Hotline)])
- * ([wiki:Titan-Changelog#point3.7.6 Titan Changelog])
- * ([wiki:Git-Changelog#point3.7.7 Git Changelog])
- * ([wiki:System-Info#point3.7.8 System Info])
- * ([wiki:Log#point3.7.9 Log])
-[[br]]
-----
-'''4.3.8 Help''' [=#point4.3.8] ([#point4 top of the page])
-----
-[[br]]
- ||'''Offline help:''' ||Currently this has no function and is for future use.||
- ||'''Online help:''' ||Shows this wiki from the web interface for help and support.||
-[[br]]
-----
-'''4.3.9 Web Controls''' [=#point4.3.9] ([#point4 top of the page])
-----
-[[br]]
-'''Filelist Display Web Buttons'''
-This section explains the functions and discriptions of the icons displayed on the web page along side the file list display.
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Webstream.png)]] ||This button plays the selected program (web Stream) ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Stream.png)]] ||This button plays the selected program (Stream) ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Delete.png)]] ||This button deletes the selected program ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Edit.png)]] ||This button downloads the selected program ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Singleepg.png)]] ||This button displays the (EPG) ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/web_radio.png)]] ||This button shows the selected channel is audio only (radio)||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/web_tv.png)]] ||This button shows the selected channel is audio and video (TV)||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Cross.png)]] ||This button shows the selected channel is not available ||
-'''Other Web Buttons'''
-This section explains the functions and discriptions icons displayed on the web page title area.
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Rcopen.png)]] ||This button shows or hides the onscreen remote control ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Poweroff.png)]] ||This button turns off the Receiver ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Restart.png)]] ||This button restarts the Receiver ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Guirestart.png)]] ||This button restarts the GUI ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Standby.png)]] ||This button puts the receiver into standby ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Speak_On.png)]] ||This button mute's the sound ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/web_led_on.png)]] ||These buttons select the volume 10 to 100% (left to right) ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Record.png)]] ||This button starts a Recording ||
- ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Signal.png)]] ||This button shows the signal info's ||
- ||EPG Search ||This box enables you to search the EPG type your test into the box and press enter. ||
-[[br]]
-----
-To open the web interface, use an Internet browser and enter the ip address of your decoder in the adress bar as follows: you may find your ip adress from the system information/network display.
-http:// IP.of.receiver
-[[br]]
-----
-'''4.4 Telnet Control''' [=#point4.4] ([#point4 top of the page])
-----
-[[Image(source:/wiki/Wiki-Pictures/IT/Telnet_Control.jpg)]][[br]]
-The section contains information on the operation of your Receiver over a telnet session.
-'''Telnet Setup'''
- * Eithernet Interface Telnet Setup
-A Network connection must be active
-Install the client found here: ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty]).
-Find the IP address from the system info ([wiki:Network#point3.7.8.5 Network]) section
-Insert the IP address info into the telnet client
-Click connect.
-[[br]]
- * Serial Interface Telnet Setup
-Connect a null modem cable between the Receiver and PC
-Install the client found here: ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty])
-Set up the serial port connection parameters
-Click connect.
-After the above steps are completed you will now be presented with a console where you can login to your Receiver with a username and password.
-after entering your login information there are a few receiver specific functions that may be handy if you require information on basic telnet commands i suggest you have a look on [http://www.linux.org linux.org]
-'''Remote RC debugging'''
-{{{
-#!python
-killall -9 evremote2
-evremote2
-}}}
-[[br]]
-'''Start FTDI driver'''
-{{{
-#!python
-mknod / dev.static/ttyUSB0 c 188 0"
-}}}
-[[br]]
-'''Test FTDI driver commands'''
-{{{
-#!python
-ls-al / dev/ttyUSB0
-}}}
-[[br]]
-{{{
-#!python
-cat /proc/bus/usb/devices
-}}}
-[[br]]
-{{{
-#!python
-lsmod | grep usbserial
-}}}
-[[br]]
-'''Take a screen shot'''
-{{{
-#!python
-/sbin/grab -j 100 -r 960 /tmp/000.jpg
-}}}
-----
-'''4.5 Rgui''' [=#point4.5] ([#point4 top of the page])
-----
-[[br]]
-[[Image(source:/wiki/Wiki-Pictures/IT/Mainmenu.jpg)]][[br]]
-RGui is a TitanNit plugin which allows you to operate your Receiver from a different Receiver. Only the Gui is completely transmitted.
-Thus one can operate the receiver remotely, but not stream the TV signal.
-[[br]]
-----
-'''4.6 Bootloader''' [=#point4.6] ([#point4 top of the page])
-----
-[[br]]
-[[Image(source:/wiki/Wiki-Pictures/IT/On_Device_Control.jpg)]][[br]]
-== Iboot is a boot loader. ==
-"written by Solala based on based on the project uboot by wolfgang denk [http://www.denx.de]"  (Iboot is included in versions of TitanNit from 1.32 for the atemio and atevio receivers) [[br]]
-Please note that there is differences between the Iboot menu structure on the different models of decoders.
-''' Functions of the boot loader:'''
-* Identification of the Hardware
-* Starting the Image
-''' Iboot early startup menu '''
-To enter the Iboot startup menu shutdown the receiver and power up pressing the __"Menu"__ button on the remote control.
-Iboot will then startup showing __"Flash Menu"__ on the VFDisplay from here you may scroll through the list of available menu items using the D-pad -OK- and -Exit- buttons on the RC Remote.
-----
-''' Expert Mode ''' (not present in av700/7000)
-----
-[[br]]
-Expert mode is a setting allowing you to enable the advanced menu in Iboot that are hidden by default as these extra setting's enable such features as overclocking that could void your warranty.
-To switch Iboot into __"Expert Mode"__ Shutdown the receiver and power up pressing the __"Menu"__ button on the remote control .
-Iboot will then startup showing __"Flash Menu"__ on the VFDisplay
-now using D-pad left / right select __"SETTINGS"__  and with up / down button select __"set OSD color"__ and click __"OK"__
-now using the left and right D-pad buttons  left / right to change the colors
-with up / down set the colors individually to
-for the '''AM 510/AM520 ''' the code is
- * Red = 11
- * Green = 47
- * Blue = 11
-for the '''AM 7500/7600 ''' the code is
- * Red = 7
- * Green = 10
- * Blue = 5
-Then press the __"Exit"__ button twice to return to the menu __"Flash"__ the display on the TV screen should now show:
-''' ! YOU ACTIVATED EXPERT MODE ! ''' - expert mode enabled
-''' ! NO WARRANTY ----- USE AT YOUR OWN RISK ! ''' No warranty - use at your own risk
-if you dont agree : execute ''' " Clean Environment Sector" ''' in the FLASH MENU
-if you do not want to lose the warranty, you must run ''' " Clean Environment Sector" ''' in the FLASH MENU
-[[br]]
-----
-'''4.6.1 Main categories''''  [=#point4.6.1] [#point4.6 (back)]
-----
-Please select an item below to see more information.
-[#point4.6.2 (Menu Flash)]
-[#point4.6.3 (Settings)]
-[#point4.6.4 (Menu Misc)]
-[#point4.6.5 (Menu Net)] (not present in av700/7000)
-== Subcategories ==
-----
-'''4.6.2 Menu Flash ''' [=#point4.6.2] [#point4.6 (back)]
- ||'''USB IRDupdt Image''' ||flash (depending on SETTINGS > Select USB / SATA dev 1-4) via USB stick or USB HDD from sda1 (standard).||
- ||'''USBirds list''' ||If several ird Image's are on the USB stick, you can display them, select and then flash the desired one. ||
- ||'''Clean environment Sector''' ||Resets the bootargs and resets Iboot to the default settings this disables __"Expert Mode"__. ||
- ||'''Clean flash ! Include swap''' ||Deletes the entire image, including the swap area, so all settings, plugins, backups, etc.... are removed. ||
- ||'''SATA IRDupdt''' ||look for an ird image on the internal or an external SATA hdd / flash stick (not present in av700/7000). ||
- ||'''list SATAirds''' ||When multiple ird Images are stored on the internal or external SATA hdd / flash stick, you can display them select and then flash the desired one (not present in av700/7000). ||
- ||'''7 . Allow Iboot Update''' ||This is a developer option included in development bootloaders so you just can flash the ird image ignoring the included boot loader if you wish this setting is not present in av700/7000). ||
-[[br]]
-----
-'''4.6.3 Menu Settings ''' [=#point4.6.3] [#point4.6 (back)]
- ||'''Turbosw'''||Select overclocking speeds available settings are (0)265, (1)265, (2)297, (3)297, (4)333, (5)333, (6)364, (7)364. ||
- ||'''Timeout'''||Delay befor selecting the default boot option. ||
- ||'''USB Sleep'''||???. ||
- ||'''Scroll Speed'''||How fast the VFDisplay module moves. ||
-[[br]]
-----
-'''4.6.4 Menu Misc''' [=#point4.6.4] [#point4.6 (back)]
- ||'''Disclaimer''' ||Shows the info on the bootloader. ||
- ||'''Serial Console''' ||Enables Bootloader serial debugging. ||
- ||'''Reset Board'''||Resets the Receiver and restarts boot process. ||
-[[br]]
-----
-''' Menu Net ''' [=#point4.6.5] [#point4.6 (back)]
-Please note menu item has been superceded and now has no function and it can be ignored. [[br]]
-Due to image updates the network setting does not need to be passed on by the bootloader.
-[[br]]
-----
-'''4.7 TitanNit Web-IF (Htmlapi)''' [=#point4.7] ([#point4 top of the page])
-----
-[[Image(source:/wiki/Wiki-Pictures/IT/Web_Control.jpg)]][[br]]
-The section contains information on the operation and control of your decoder from the Htmlapi.
-[[br]]
-TitanNit provides its own Htmlapi that is freely distributed so that other developers may interface with a receiver running titan.
-The Htmlapi is very simple to implement an example message structure is as follows:
- * query?param&param&... for html output
- * queryraw?param&param&... for raw-struct output
-For example if you would wish to send a RC remote keypress of the "Mute" key the message format would be as follows:
- * __query?sendrc&rcmute__
-if you would like to retrieve a list of all the current satelites the format would be as follows:
- * __queryraw?getsat__
-the output message back from the Receiver would be as follows:
- * __satname#orbitalpos__
-and an example raw output would be:
-> {{{Optus_d2#160}}}[[br]]
-> {{{Optus_d1#166}}}[[br]]
-> {{{Intelsat_IS19#156}}}[[br]]
-''more information on the protocol and the query strings can be found here [http://sbnc.dyndns.tv/trac/browser/titan/doc/htmlapi.txt htmlapi.txt]''
-[[br]]
-----
-'''4.8 FTP (File Transfer Protocol)''' [=#point4.8] ([#point4 top of the page])
-----
-[[Image(source:/wiki/Wiki-Pictures/IT/Filezilla.jpg)]][[br]]
-The section contains information on how to setup a FTP connection to your TitanNit Receiver.
-[[br]]
-Titan Has an inbuilt FTP Server that is able to be used to transfer files to and from your Receiver.
-To connect to your receiver you can connect via your browser in windows or use a dedicated FTP program as with many linux programs the default password and user name is "root" and port 21 is the default FTP interface port.
-You connect to your receiver via internet explorer on your pc to do this you need to find the IP address fo the decoder from the system information menu [wiki:System-info-Network#point3.7.8.4 Network Information] of your receiver and type it into the address bas as follows:
-{{{ftp://Username:Password@Ip_Address:Port_Number}}}
-{{{ftp://root:root@192.168.0.1:21}}}
-if you Wish to use a dedicated FTP program please read the documentation supplied with your program for information on setup of the FTP connection, Below is a screen shot of Filezilla a popular Free FTP client Program with a sample loggin details of my Receiver.
-[[Image(source:/wiki/Wiki-Pictures/IT/FileZilla-Setup.jpg)]][[br]]
-----
- '''4.9 autostart scripting (usercmd)''' [=#point4.9] ([#point4 top of the page])
-----
-If you wish to run a script on startup of the Receiver you can install commands in the usercmd.sh to be proformed at the startup of the receiver.
-a sample of the usercmd.sh is below:
-{{{
-#!python
-#! / bin / sh
- # Start the user commands here
-echo " [ usercmd.sh ] start"
- # insert code here
- exit
-}}}
-the {{{__"# insert code here"__}}} section must be replaced by your commands.
-If you place the following code in to the usercmd.sh it will delete every time shift file on the internal hdd on startup of the receiver:
-{{{
-#!python
-rm -f /media/hdd/movie/timeshift*.ts
-}}}
-If you place the following code in to the usergmd.sh it will autostart the FTDI driver.
-{{{
-#!python
-mknod / dev.static/ttyUSB0 c 188 0"
-}}}
-[[br]]
-the full path to the file is:
-__"/mnt/config/usercmd.sh"__

wiki/pages/it/Restore-Default-Settings

-                      r37662
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.13 Restore Default Settings''' [=#point3.6.13] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Restore_Default_Settings.jpg)]][[BR]]
+>
->here you can return your device to the default settings.
-[[br]]
- ||'''Restore Default Settings:''' ||This will restore the settings to the factory default condition.||
- ||'''Format MNT With Backup / Restore:''' ||This will format the Mount partition after preforming a backup thern it will restore the restore the backup retaining your settings.||
- ||'''Format MNT (all):''' ||This will format the Mount partition deleting all settings to default condition.||
- To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
-[[br]]
-----

wiki/pages/it/Rotor-Settings

-                      r37662
+                      r39712
-[[TranslatedPages]]
->----
->'''3.5.1.4 Rotor Settings''' [=#point3.5.1.4] ([wiki:Channel-Service#point3.5.1 Channel-Service (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Rotor-Settings.jpg)]][[br]]
+>
-Here you can adjust your rotor settings
-[[br]]
- ||'''Move''' || Select move mode.||
- ||'''Fine Move:''' || Select fine move.||
- ||'''Limit:''' || Select satellite motor limits.||
- ||'''Go to start pos:''' || Goto the satellite starting position.||
- ||'''storage position:''' || Select storage position.||
- To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
- '''Coloured Button's Functions'''
- The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in rotor settings.
-  Please see below for more info on the functions of these buttons these functions depend on the selected menu item as follows:.
-'''During Move'''
- ||'''Red Button: (Move West)''' ||Set the sort method for the files listed in the file list display.||
- ||'''Green Button: (Search west)''' ||Play the selected media file.||
- ||'''Yellow button: (search east)''' ||Show the EPG information on the current selected media file (If present)||
- ||'''Blue button: (move east)''' ||Set the sort method for the files listed in the file list display.||
-'''During Fine Move'''
- ||'''Green Button: (Step west)''' ||Play the selected media file.||
- ||'''Yellow Button: (Step East)''' ||Show the EPG information on the current selected media file (If present)||
-'''During Limit'''
- ||'''Red Button: (limit Off)''' ||Set the sort method for the files listed in the file list display.||
- ||'''Green Button: (limit West)''' ||Play the selected media file.||
- ||'''Yellow button: (limit East)''' ||Show the EPG information on the current selected media file (If present)||
- ||'''Blue button: (limit On)''' ||Set the sort method for the files listed in the file list display.||
-'''During goto start position'''
- ||'''Red Button: (Start Position)''' ||go to the selected start position.||
-'''During Storage Position'''
- ||'''Green Button: (Storage Position)''' ||store selected storage position.||
- ||'''Yellow Button: (Goto Position)''' ||move dish to the stored position||

wiki/pages/it/Sat-Finder

-                      r37662
+                      r39712
-[[TranslatedPages]]
->----
->'''3.5.1.5 Sat Finder''' [=#point3.5.1.5] ([wiki:Channel-Service#point3.5.1 Channel-Service (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Sat-Finder.jpg)]][[br]]
+>
-Here you can check your signal info for the current selected channel.
-[[br]]

wiki/pages/it/Screensaver-Adjust

-                      r37662
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.8 Screensaver Adjust''' [=#point3.6.8] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Screensaver_Adjust.jpg)]][[BR]]
+>
->Here you can setup your screen saver
-[[br]]
- ||'''Screensaver''' ||enable or disable the screensaver display||
- ||'''Screensaver Delay:''' ||Set the delat time before the screen saver is displayed.||
- ||'''Screensaver Interval:''' ||Set the display time of the Screensaver in multi Pic Mode.||
- ||'''Screensaver Type:''' ||Select the type of Screensaver to display on the screen.||
- ||'''Screensaver Background:''' ||Select the background during display of the Screensaver.||
- ||'''Screensaver Pic:''' ||IN Image mode select the picture to Display as the Screensaver.||
- To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
-[[br]]
-----

wiki/pages/it/Service

-                      r37419
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.1 Service''' [=#point3.7.1] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Service.jpg)]][[BR]]
+>
-> here you view information on the currently selected service.
-[[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: (Service)''' ||This will display the current service info on the display.||
- ||'''Green Button: (PIDs)''' ||This will display the PID info on the display.||
- ||'''Yellow Button: (Tuner)''' ||This will display the current Tuner Configuration info on the display.||

wiki/pages/it/Settings-Backup-Restore

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.5.9 Settings Backup Restore''' [=#point3.5.9] ([wiki:Interface-Operation#point3.5 System (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/system_Settings_Backup_Restore.jpg)]][[BR]]
+>
-> here you can backup and restore your settings.
-[[br]]
-To Exit from the menu press __"Exit"__ to cancel backup restore.
-'''Coloured Button's Functions"
- The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the backup restore menu. [[BR]]
- please see below for more info on the functions of these buttons:.
- ||'''Red Button: (Restore)''' ||Press this button to preform a restore from your previously saved settings.||
- ||'''Green Button: (Backup)''' ||Press this button to save your settings.||
- ||'''Yellow Button: (Log)''' ||Press this button to see the backup restore log.||

wiki/pages/it/Single-EPG

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.1.2 Single EPG''' [=#point3.1.2] ([wiki:Interface-Operation#point3.1 Records and EPG(Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Single_EPG.jpg)]][[BR]]
+>
-Single EPG is a small easy to read vertical epg of a single channel that shows the information of the currently selected program.
-[[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.||
-For information on setting up a timer Recording using the red button see ([wiki:Records Records]) for more info.
-For information on setting proforming an EPG search using the 0 Key see ([wiki:EPG-Search#point103.10.5 EPG Search]) for more info.

wiki/pages/it/Skin

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.16 Skin''' [=#point3.6.16] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Skin.jpg)]][[BR]]
+>
->here you can select your skin
-[[br]]

wiki/pages/it/Skin-Adjust

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.7 Skin Adjust''' [=#point3.6.7] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Skin_Adjust.jpg)]][[BR]]
+>
->Here you can edit your skin display settings
-[[br]]
- ||'''Font Zize Adjust in Pixel''' ||Adjust the size of the fonts in the GUI.||
- ||'''Listbox Select:''' ||Select the display mode of the listbox select bar.||
- ||'''OSD Transparancy:''' ||Set the transpancy of the OSD when it is overlaying the TV display.||
- ||'''OSD Left Overscan:''' ||Set the value of the OSD overscan on the left edge of the display.||
- ||'''OSD Right Overscan:''' ||Set the value of the OSD overscan on the right edge of the display.||
- ||'''OSD Top Overscan:''' ||Set the value of the OSD overscan on the top edge of the display.||
- ||'''OSD Bottom Overscan:''' ||Set the value of the OSD overscan on the bottom edge of the display.||
- ||'''Show Hdd Freespace:''' ||show the Hdd Free space in the OSD. ||
- ||'''Listbox Select Colour:''' ||Press the red button to bring up a colour selection to display for the listbox select bar. ||
- To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
-[[br]]
-----

wiki/pages/it/Smart-Card-Reader

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.5.3 Smart Card Reader''' [=#point3.5.3] ([wiki:Interface-Operation#point3.5 System (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/system-Smart_Card_Reader.jpg)]][[BR]]
+>
-here you can setup your smart card.
-[[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: (Reset)''' ||This will reset the selected Smart Card.||

wiki/pages/it/Streaming

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.4 Streaming''' [=#point3.7.4] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0.2 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Streaming.jpg)]][[BR]]
+>
-> here you can view information on service info being streamed to another device.
-[[br]]

wiki/pages/it/Supported-Receivers

-                      r39063
+                      r39712
-[[TranslatedPages]]
-----
-'''7 Compatible Receivers''' [=#point7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0.2 Main page])
-----
-Titan was originally releaced for SH4 based hardware from Atemio and Katherin, since the advent and popularity of TitanNit on the SH4 platform it has been releaced to the Mips platform also for instalation the latest Atemio recievers.
-The Atemio 5200 is the first reciever to include a mips based processor and will be the first officially supported reciever not of the SH4 chipset, and marks a new era for TitanNit.
-The current offerings of sh4 based recievers are a lot less powerfull than some of the mips devices out there, part of the reason why titan was developed for the SH4, with titan running on mips hardware we expect to see a very fast very capable feature packed system that we will all look forward to.
-Titan is also in development for the vu+ recievers and may be releaced in the future.
-TitanNit has also been made available for a variety of non-Atemio recievers manufactured by fortis, Atemio identical SH4 Fortis manufactured Receivers.
-=== Currently, the following receivers are directly supported: ===
-'''SH4 Atemio'''    ([http://www.atemio.de Atemio homepage])
- * Atemio 510
- * Atemio 520
- * Atemio 530
- * Atevio 700
- * Atevio 7000
- * Atemio 7600
-'''SH4 Fortis'''  ([http://www.fortis.co.kr Fortis homepage])
- * [#point7.2 Fortis Clones hardware detection]
- * Fortis FS-9000
- * Fortis FS-9200
- * Fortis HS-9510
- * Fortis HX-8200
- * Fortis HS-7810
-'''SH4 Homecast'''    ([http://www.myhomecast.nl/ Homecast homepage])
- * Homecast Pro
- '''SH4 IPBox''' ([http://www.abipbox.com/ AB IPBox homepage])
- * Ipbox91
- * Ipbox900
- * Ipbox910
- * Ipbox9000
-'''SH4 Katherin'''   ([http://www.kathrein-gmbh.at kathrein homepage])
- * Kathrein UFS 910
- * Kathrein UFS 912 (license charges may apply)
- * Katherin UFS 922 (license charges may apply)
- * Katherin UFS 960
-'''SH4 Fulan/ Spark'''   ([http://www.spark-tv.com Spark homepage)]
- * [#point7.6 Fulan Clones hardware detection]
- * Spark7111
- * Spark7162
-'''Mips Atemio'''   ([http://www.atemio.de Atemio homepage])
- * Atemio 5000 (AKA Nemisis)
- * Atemio 5200
- * Atemio 6000
- * Atemio 6100
- * Atemio 6200
-'''Mips Beyonwiz'''   ([Mips Beyonwiz Beyonwiz homepage])
- * Beyonwiz T4
-'''Mips Golden Interstar'''   ([http://www.golden-interstar.pl Golden Interstar homepage])
- * Xpeedlx1
- * Xpeedlx2
- * Xpeedlx3
-'''Mips Miraclebox'''   ([http://www.miraclebox.se/ Miraclebox homepage])
- * MBUltra
- * MBMini
-'''Mips Sezam'''([http://www.sezam-club.ru/ homepage])
- * Sezam-Marvel
-----
-'''SH4 Fortis based clone receiver detection (hardware profile)''' [=#point7.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-This list will help you select the correct clone hardware model 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.
-This list has not yet been confirmed and some of these models may be incompatible with TitanNit.
-If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated.
-Please Note:
-  * Due to differences between the VFDisplay programming and the supplied Remote Control units delivered with your Receiver a remapping of the remote control Layout may be necessary.
-  * Pre-Release Versions with the loader version 1.19 had problems when installing versions 1.21 and 1.54 and demand a replacement of the VF-Display in order for the Receiver to boot. Fault is an inbedded security feature. Therefor it is unknown if iboot will actually function with the Receivers. If you have one of these Receivers it would be advisable to take caution installing iboot.
-This table shows the last gen SH4 based receivers manufactured by fortis if you look in your manual of your reciever it will display the specifications and you may use the below table find out the base fortis model it is styled on to verify the compatibility with the corect Atemio/Atevio model.
-{{{#!div style="width: 1000px; margin: auto"
-||'''Model System'''||'''Tuner'''||'''CPU'''||'''RAM'''||'''ROM (Flash)'''||'''USB'''||'''PVR Funktion'''||'''CardReader'''||'''Common interface'''||'''Width'''||'''Display'''||'''features'''||
-||[#point7.3 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||11-segment||43 cm|| ||
-||[#point7.3 Fortis FS-9200 HD PVR]||DVB-S/S2 2||STI_7101 266 Mhz||192MB||32MB||2||eSATA & USB||1 (*2)||2||11-segment||34 cm|| ||
-||[#point7.2 Fortis HS-9510]||DVB-S/S2 1||STI_7101 266 Mhz||192MB||32MB||1||USB||1 (*2)||2||11- segment||34 cm|| ||
-||[#point7.4 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||11-segment||34 cm||Plug&Play Tuner, Youtube, Browser, FreeTV+||
-||[#point7.5 Fortis HS-7810 HD PVR]||DVB-S/S2 1||STI_7110 450 Mhz||256MB||32MB||2||USB||1||2||4-segment||26 cm||YouTube, Browser, FreeTV+||
-}}}
-----
-'''Atevio AV 700 HD simular hardware:''' [=#point7.2]
-----
-Single tuner no no built in YouTube, Browser or FreeTV+
-Fortis base model HS-9510HD PVR and possibly identical boxes:
-  * Fortis HS- 9510 HD PVR 20000300 Korea.
-  * Rebox RE- 4000HD PVR 20010300 Netherlands.
-  * Octagon SF- 1008 20020300 Germany.
-  * Octagon SF -1008 SE 20020303 Germany.
-  * HD Box FS- 9100HD 20030300 Czech Republic.
-  * Ultra Plus HD 980 20050300 New Zealand.
-  * Openbox S5 HD PVR 20060302 Ukraine.
-  * Tiviar S1 eco HD PVR 20070300 U.S.A. Switzerland .
-  * Astro ASR 1100 Single HD 20110300 and 20110303 Germany .
-  * Dreamsky DSR- 9600HD PVR 20120302 Belarus.
-  * Skyway Classic 20130302 Russia.
-  * I.Com HD -9000 DIVX 20140300 Syria.
-  * I.Com HD -9000 DIVX II 20140702 Syria.
-  * I.Com HD -9100 DIVX II 20140602 Syria.
-  * XSPEED HD -9500 DIVX II 20140612 Syria.
-  * Optibox Koala HD 20150300 Hungary.
-  * Xcruiser XDSR400HD 20160302 Dubai.
-  * VisionNet FS- 9510 HD PVR 20170302 Israel.
-  * Gold Master HD -1060 HD PVR HD PVR -1070 -1080 PVR 20180302 Turkey
-  * Powersat PO - 1000HD PVR 20190301
-  * Star Track SRT 2010 HD 20210302 Dubai
-  * O2 SRT 2012 HD 20210301 Dubai
-  * Forever HS- 9510HD PVR 20220302 Algeria
-  * Dynavision DV -9500 HDPVR 20230302 Dubai
-  * Dynavision DV -9600 HDPVR 20230301 Dubai
-  * GI S- 8290 HD PVR 20240602 Romania
-  * Miraclebox 8 HD TWIN PVR 20250600 Sweden
-  * Diginor 8800 HD 20260600 Sweden
-  * Media Star ( Powers) HD 1200s 20270600 Australia
-  * MaxFly 9500 HD 20280602 Syria
-  * SuperBox SX 9518 HD 20300302 Moldova
-  * Elcomax Elux I 20310301 Iran
-[#point7 Top of Page]
-----
-'''Atevio AV 7000 HD simular hardware:''' [=#point7.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Fortis base model FS-9000 and FS-9200 differ due to option of including an internal harddisk.
-FS- 9000 HD PVR and possibly identical boxes"
-  * Fortis FS- 9000HD 20000000 Korea
-  * Rebox RE- 9000HD 20010000 Netherlands
-  * Octagon SF 1018 20020000 Germany
-  * HD Box FS -9300 HD 20030000 Czech Republic
-  * Ultra Plus F- 9000HD 20050000 New Zealand        ''' Confirmed by ''' ([http://www.aaf-digital.info/forum/member.php?24970-professor_jonny Professor_Jonny])
-  * Openbox S8 HD PVR 20060000 Ukraine
-  * Tiviar F1 HD PVR USA 20070000 Switzerland
-  * Icecrypt S4000 HDPVR 20080000 England
-  * Skyway Diamond 20130000 Russia
-  * Dynavision DV -9000 HDPVR 200230000 Dubai
-FS- 9200 HD PVR and possibly identical boxes:
-  * Fortis FS- 9200HD PVR 20000100 Korea
-  * Rebox RE- 8000HD 20010100 Netherlands
-  * HD Box FS- 9200HD 20030100 Czech Republic
-  * Arcon Titan 2010HD 20040100 Germany
-  * Openbox S7 HD PVR 20060100 Ukraine
-  * Tiviar T1 HD PVR 20070100 Switzerland
-  * Astro ASR 1200 Twin HD 20110100 Germany
-  * Dreamsky DSR- 9700HD PVR 20120100 Belarus
-  * Skyway Platinum 20130100 Russia
-  * I.Com Twin HD -9200 DIVX 20140100 Syria
-  * I.Com Twin HD -9200 DIVX II 20140101 Syria
-  * Gold Master 1090 HD PVR 20180100 Turkey
-  * Dynavision DV -9200 HDPVR 20230100 Dubai
-[#point7 Top of Page]
-----
-'''Atevio/ Atemio AV 7500 7600 HD simular hardware:''' [=#point7.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-This model has a removable tuner and has YouTube, Browser, FreeTV+
-Fortis base model HX -8200 HD PVR and possibly identical boxes:
-  * Fortis HX -8200 HD PVR 230000X0 Korea
-  * Rebox RE -8500 HD PVR 230100X0 Netherlands
-  * Octagon SF 1028P Noblence 230200X0 Germany
-  * Skyway Droid 230400X0 Russia
-  * Openbox S9 HD PVR 230500X0 Ukraine
-  * Icecrypt STC6000HDPVR 230600X0 UK
-  * Miraclebox 9 HD TWIN PVR 230700X0 Sweden
-  * Xcruiser XDSR600HD 230900X0 Dubai
-  * Ultra Plus X - 9200HD PVR 231200X0 New Zealand
-  * Skys @ t Royal HD PVR 231500X0 Bulgaria
-  * SuperBox PRO HD 9818 231600x0 Moldova
-  * Optibox Raptor HD 231800X0 Hungary
-  * Forever HD PVR 8200 231900X0 Algeria
-  * Media Star ( Powers) HD 8200S 232700X0 Australia
-[#point7 Top of Page]
-----
-'''Atemio AV 500/510 HD simular hardware:''' [=#point7.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-This model has a removable tuner and has YouTube, Browser, FreeTV+
-Fortis base model HS -7110 HD PVR and possibly identical boxes:
-  * Fortis HS -7110 HD PVR ? korea
-  * Optibox Gekko HD 250102X0 Hungary
-  * Octagon SF 918 SE + 250202X0 Germany
-  * Rebox RE -2200 HD PVR 250302X0 Netherlands
-  * Skyway LIGHT 250502X0 Russia & Belarus
-  * HD Box FS- 7110HD 250602X0 Czech Republic
-  * Openbox S4 HD PVR 250902X0 Ukraine
-  * Icom HD 1070P DIVX 251002X0 Syria
-  * Gold Master HD -1040 HD PVR -1045 PVR 251102X0 Turkey
-  * Dynavision DV -5000 HDPVR 251202X0 Dubai
-  * GI S8580 251302X0 Romania
-  * Xcruiser XDSR 380HD 251802X0 Dubai
-  * Dreamsky HD4 252002X0 Belarus
-  * ? Supermax 7100 252102X0 ?
-  * Skys @ t Mini HD PVR 252202X0 Bulgaria
-  * Icecrypt S3500 HDCCI 252502X0 UK
-  * Miraclebox 6 HD TWIN PVR 252602X0 Sweden
-  * Vegasat X1 252802X0 Morocco
-  * Ultraplus 900 HD PVR ? New Zealand
-[[br]][#point7 Top of Page]
-----
-'''Fulan based clone receiver detection (hardware profile)''' [=#point7.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-This list will help you select the correct clone hardware model 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.
-This list has not yet been confirmed and some of these models may be incompatible with TitanNit.
-If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated.
-This table shows the last gen SH4 based receivers manufactured by Fulan if you look in your manual of your reciever it will display the specifications and you may use the below table find out the base Fulan model it is styled on to verify the compatibility with the Fulan model.
-{{{#!div style="width: 1000px; margin: auto"
-||'''Model System'''||'''Tuner'''||'''CPU'''||'''RAM'''||'''ROM (Flash)'''||'''USB'''||'''PVR Funktion'''||'''CardReader'''||'''Common interface'''||'''Width'''||'''Display'''||'''features'''||
-||[#point7.7 Fulan 7162]||DVB-S/S2 1,2,3||STI_7162 266 Mhz|| || || || || || || || || ||
-||[#point7.8 Spark 7111]||DVB-S/S2 1||STI_7111 266 Mhz|| || || || || || || || || ||
-}}}
-----
-'''Fulan/Spark 7162 simular hardware:''' [=#point7.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-This model has a STI 7162 Processor, tuner varies by reseller either one two or three tuners
-Fulan/Spark 7162 and possibly identical boxes:
- * Golden Media Spark Triplex 0C 00 07 00
- * Golden Media Spark One 0C 00 07 00
- * SAB Unix Triple HD 0C 00 0E 00
- * Amiko Alien 2 0C 00 0A 00
- * Galaxy Innovations Avatar 2 0C 00 0B 00
- * Galaxy Innovations Avatar 3 0C 00 0B 00
- * Visionnet Falcon 0C 00 21 00
- * Icecrypt S3700 CHD 0C 00 2B 00
- * Truman Top Box 2 Tuners 0C 00 03 00
- * Samsat Linux 2 0C 00 20 00
- * Satcom 7162 0C 00 1D 00
- * Dynavision 7162 0C 00 0D 00
- * Superbox Z500 0C 00 15 00
- * Delta 0C 00 04 00
- * Startrack SRT 2020 HD Plus 0C 00 05 00
- * Sogno Spark Triple 0C 00 43 00
-----
-'''Fulan/Spark 7111 simular hardware:'''   [=#point7.8]
-----
-This model has a STI 7111 Processor, all models seem to have a single DVB-S2 tuner.
-Fulan/Spark 7111 and possibly identical boxes:
- * Amiko Alien SHD 8900, 09 00 0A 00
- * Golden Media 990 CR HD PVR Spark LX 09 00 07 00
- * Golden Media Spark Reloaded 09 00 07 00
- * Edision Argus Pingulux 09 00 08 00
- * Edision Argus Pingulux Plus 09 00 08 00
- * Galaxy Innovations GI S8120 09 00 0B 00
- * SAB Unix F+ Solo (S902) 09 00 0E 00
- * Dynavision Spark 09 00 0D 00
- * Dynavision Spark Plus 09 00 0D 00
- * Fulan Spark I+ 09 00 1D 00
- * Truman Premier 1+ 09 00 03 00
- * Samsat Linux 1 09 00 20 00
- * Startrack SRT 2020 HD 09 00 21 00
- * FullHD FH 2020 HD 09 00 ?? 00
- * Yumatu Spark 09 00 ?? 00
- * Visionnet Hammer 5400 09 00 21 00
- * Visionnet Fireball 101 09 00 21 00
- * Superbox S750 09 00 15 00
- * Sogno Spark Revolution 09 00 43 00

wiki/pages/it/Supported-Recievers

-                      r39063
+                      r39712
-----
-'''7 Compatable Revievers''' [=#point7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0.2 Main page])
-----
-=== Currently, the following receivers are supported: ===
-  * Atemio 510/520/530
-  * Atemio 7600
-  * Atevio 700/7000
-  * Kathrein UFS 910
-  * Kathrein UFS 912/922 (license charges may apply)
-Recently TitanNit has been made available for a variety of non-Atemio Receivers. Identical SH4 Fortis Receivers may work with TitanNit.
-This list has not yet been confirmed and some of these models may be incompatible with TitanNit.
-If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated.
-Please Note:
-  * Due to differences between the VFDisplay programming and the supplied Remote Control units delivered with your Receiver a remapping of the remote control Layout may be necessary.
-  * Pre-Release Versions with the loader version 1.19 had problems when installing versions 1.21 and 1.54 and demand a replacement of the VF-Display in order for the Receiver to boot. Fault is an inbedded security feature. Therefor it is unknown if iboot will actually function with the Receivers. If you have one of these decoders it would be advisable to take caution installing iboot.
-=== Atevio AV 500 HD: ===
-Model HS- 9510HD PVR and possibly identical boxes:
-  * Fortis HS- 9510 HD PVR 20000300 Korea.
-  * Rebox RE- 4000HD PVR 20010300 Netherlands.
-  * Octagon SF- 1008 20020300 Germany.
-  * Octagon SF -1008 SE 20020303 Germany.
-  * HD Box FS- 9100HD 20030300 Czech Republic.
-  * Ultra Plus HD 980 20050300 New Zealand.
-  * Openbox S5 HD PVR 20060302 Ukraine.
-  * Tiviar S1 eco HD PVR 20070300 U.S.A. Switzerland .
-  * Astro ASR 1100 Single HD 20110300 and 20110303 Germany .
-  * Dreamsky DSR- 9600HD PVR 20120302 Belarus.
-  * Skyway Classic 20130302 Russia.
-  * I.Com HD -9000 DIVX 20140300 Syria.
-  * I.Com HD -9000 DIVX II 20140702 Syria.
-  * I.Com HD -9100 DIVX II 20140602 Syria.
-  * XSPEED HD -9500 DIVX II 20140612 Syria.
-  * Optibox Koala HD 20150300 Hungary.
-  * Xcruiser XDSR400HD 20160302 Dubai.
-  * VisionNet FS- 9510 HD PVR 20170302 Israel.
-  * Gold Master HD -1060 HD PVR HD PVR -1070 -1080 PVR 20180302 Turkey
-  * Powersat PO - 1000HD PVR 20190301
-  * Star Track SRT 2010 HD 20210302 Dubai
-  * O2 SRT 2012 HD 20210301 Dubai
-  * Forever HS- 9510HD PVR 20220302 Algeria
-  * Dynavision DV -9500 HDPVR 20230302 Dubai
-  * Dynavision DV -9600 HDPVR 20230301 Dubai
-  * GI S- 8290 HD PVR 20240602 Romania
-  * Miraclebox 8 HD TWIN PVR 20250600 Sweden
-  * Diginor 8800 HD 20260600 Sweden
-  * Media Star ( Powers) HD 1200s 20270600 Australia
-  * MaxFly 9500 HD 20280602 Syria
-  * SuperBox SX 9518 HD 20300302 Moldova
-  * Elcomax Elux I 20310301 Iran
-[#point7 Top of Page]
-=== Atevio AV 7000 HD: ===
-The models FS- 9000 and FS -9200 differ due to option of including an internal harddisk.
-FS- 9000 HD PVR and possibly identical boxes
-  * Fortis FS- 9000HD 20000000 Korea
-  * Rebox RE- 9000HD 20010000 Netherlands
-  * Octagon SF 1018 20020000 Germany
-  * HD Box FS -9300 HD 20030000 Czech Republic
-  * Ultra Plus F- 9000HD 20050000 New Zealand        ''' Confirmed by ''' ([http://www.aaf-digital.info/forum/member.php?24970-professor_jonny Professor_Jonny])
-  * Openbox S8 HD PVR 20060000 Ukraine
-  * Tiviar F1 HD PVR USA 20070000 Switzerland
-  * Icecrypt S4000 HDPVR 20080000 England
-  * Skyway Diamond 20130000 Russia
-  * Dynavision DV -9000 HDPVR 200230000 Dubai
-FS- 9200 HD PVR and possibly identical boxes
-  * Fortis FS- 9200HD PVR 20000100 Korea
-  * Rebox RE- 8000HD 20010100 Netherlands
-  * HD Box FS- 9200HD 20030100 Czech Republic
-  * Arcon Titan 2010HD 20040100 Germany
-  * Openbox S7 HD PVR 20060100 Ukraine
-  * Tiviar T1 HD PVR 20070100 Switzerland
-  * Astro ASR 1200 Twin HD 20110100 Germany
-  * Dreamsky DSR- 9700HD PVR 20120100 Belarus
-  * Skyway Platinum 20130100 Russia
-  * I.Com Twin HD -9200 DIVX 20140100 Syria
-  * I.Com Twin HD -9200 DIVX II 20140101 Syria
-  * Gold Master 1090 HD PVR 20180100 Turkey
-  * Dynavision DV -9200 HDPVR 20230100 Dubai
-[#point7 Top of Page]
-=== Atevio / Atemio AV 7500/7600 HD: ===
-Model HX -8200 HD PVR and possibly identical boxes
-  * Fortis HX -8200 HD PVR 230000X0 Korea
-  * Rebox RE -8500 HD PVR 230100X0 Netherlands
-  * Octagon SF 1028P Noblence 230200X0 Germany
-  * Skyway Droid 230400X0 Russia
-  * Openbox S9 HD PVR 230500X0 Ukraine
-  * Icecrypt STC6000HDPVR 230600X0 UK
-  * Miraclebox 9 HD TWIN PVR 230700X0 Sweden
-  * Xcruiser XDSR600HD 230900X0 Dubai
-  * Ultra Plus X - 9200HD PVR 231200X0 New Zealand
-  * Skys @ t Royal HD PVR 231500X0 Bulgaria
-  * SuperBox PRO HD 9818 231600x0 Moldova
-  * Optibox Raptor HD 231800X0 Hungary
-  * Forever HD PVR 8200 231900X0 Algeria
-  * Media Star ( Powers) HD 8200S 232700X0 Australia
-[#point7 Top of Page]
-=== Atemio AM 500/510 HD: ===
-Model HS -7110 HD PVR and possibly identical boxes
-  * Optibox Gekko HD 250102X0 Hungary
-  * Octagon SF 918 SE + 250202X0 Germany
-  * Rebox RE -2200 HD PVR 250302X0 Netherlands
-  * Skyway LIGHT 250502X0 Russia & Belarus
-  * HD Box FS- 7110HD 250602X0 Czech Republic
-  * Openbox S4 HD PVR 250902X0 Ukraine
-  * Icom HD 1070P DIVX 251002X0 Syria
-  * Gold Master HD -1040 HD PVR -1045 PVR 251102X0 Turkey
-  * Dynavision DV -5000 HDPVR 251202X0 Dubai
-  * GI S8580 251302X0 Romania
-  * Xcruiser XDSR 380HD 251802X0 Dubai
-  * Dreamsky HD4 252002X0 Belarus
-  * ? Supermax 7100 252102X0 ?
-  * Skys @ t Mini HD PVR 252202X0 Bulgaria
-  * Icecrypt S3500 HDCCI 252502X0 UK
-  * Miraclebox 6 HD TWIN PVR 252602X0 Sweden
-  * Vegasat X1 252802X0 Morocco
-[[br]][#point7 Top of Page]

wiki/pages/it/Swap

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8.6.6 Swap''' [=#point3.7.8.6.6] ([wiki:System-Info#point3.70.8.6 System Infos (Back])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Swap.jpg)]][[br]]
+>
-Here you can view the detailed info on the swap.
-[[br]]
-[[br]]

wiki/pages/it/System-Info

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8 System Info''' [=#point3.7.8] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/System_Info_main.jpg)]][[BR]]
+>
-> here you can view system wide information.
-[[br]]
- * ([wiki:System-Status#point3.7.8.1 System Status])
- * ([wiki:Free-Space#point3.7.8.2 Free Space])
- * ([wiki:Kernel#point3.7.8.3 Kernel])
- * ([wiki:Mounts#point3.7.8.4 Mounts])
- * ([wiki:System-info-Network#point3.7.8.5 Network])
- * ([wiki:Ram#point3.7.8.5 Ram])
- * ([wiki:System-Infos#point3.7.8.6 System Infos])
-[[br]]

wiki/pages/it/System-Infos

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8.6 System Info''' [=#point3.7.8.6] ([wiki:System-Info#point3.7.8.6 System Infos (Back])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/System-Info-System-Infos.jpg)]][[BR]]
+>
-> here you can view system wide information.
-[[br]]
- * ([wiki:CPU#point3.7.8.6.1 Cpu])
- * ([wiki:Memory#point3.7.8.6.2 Memory])
- * ([wiki:MTD#point3.7.8.6.3 MTD])
- * ([wiki:Module#point3.7.8.6.4 Module])
- * ([wiki:Devices#point3.7.8.6.5 Devices])
- * ([wiki:Swap#point3.7.8.6.6 Swap])
- * ([wiki:Top#point3.7.8.6.7 Top])
- * ([wiki:prozesslist#point3.7.8.6.8 prozesslist])
- * ([wiki:USB#point3.7.8.6.9 USB])
-[[br]]

wiki/pages/it/System-Status

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8.1 System Status''' [=#point3.7.8.1] ([wiki:System-Info#point3.7.8 System Info (Back])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/System-Status.jpg)]][[br]]
+>
-Here you can view the system status of the receiver.
-[[br]]
-[[br]]

wiki/pages/it/System-Update

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.5.7 System Update''' [=#point3.5.7] ([wiki:Interface-Operation#point3.5 System (Back)])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/system-System_Update.jpg)]][[BR]]
+>
->here you can proform a system update
-[[br]]
- ||'''Flashupdate (Online):''' ||Update flashmemory from online Library.||
- ||'''Flashupdate (tmp):''' ||Update Flashmemory from tmp.||
- ||'''USBupdate (tmp):''' ||Update USB device from tmp.||
- To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
-[[br]]

wiki/pages/it/System-info-Network

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8.4 Network''' [=#point3.7.8.4] ([wiki:System-Info#point3.7.8 System Info (Back)])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/System-info-Network.jpg)]][[br]]
+>
-Here you can view info on you network interface.
-[[br]]
-[[br]]

wiki/pages/it/Testpage

-                      r39063
+                      r39712
-[[TranslatedPages]]
-Test code:
-[[CollapsibleStart]]
-nested text.
-[[CollapsibleEnd]]

wiki/pages/it/Timeshift-Settings

-                      r39063
+                      r39712
-[[TranslatedPages]]
->----
->'''3.6.7 Timeshift Settings''' [=#point3.6.7] ([wiki:Interface-Operation#point3.6 Settings (Back)])
+>
->Menu Picture place holder:
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/Timeshift_Settings.jpg)]][[BR]]
+>
-Here you can edit your timeshift settings
-[[br]]
- ||'''Timeshift Type''' ||Select the operation mode of the timeshift function.||
- ||'''After Timshift:''' ||If timshift is stopped what function that should the reciever do.||
- ||'''Ask on channel switch:''' ||Ask what to do with the timeshift file on channel change.||
- ||'''Use Numeric Keys:''' ||use the numeric keys to control the timeshift skip and jump functions.||
- To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
-[[br]]
-----

wiki/pages/it/prozesslist

-                      r37425
+                      r39712
-[[TranslatedPages]]
->----
->'''3.7.8.6.8 Prozesslist''' [=#point3.7.8.6.8] ([WikiStart#point3.7.8.6 System Infos (Back])
+>
+>
->[[Image(source:/wiki/Wiki-Pictures/IT/prozesslist.jpg)]][[br]]
+>
-Here you can view the detailed Process info.
-[[br]]
-[[br]]

wiki/pages/ru/Hard-Disk

-                      r37425
+                      r39712
-[[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/RU/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/ru/Installation-Recovery-SH4-Fortis

-                      r37425
+                      r39712
-[[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/ru/Installation-Recovery-SH4-Spark

-                      r37425
+                      r39712
-[[TranslatedPages]]
-----
-'''8.051 SPARK''' [=#point8.050] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-Spark is a reseller of the Fulan 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 hardware.
-'''SH4 Spark Contents'''
- * [#point8.051 8.051 SPARK (7111)]
- * [#point8.052 8.052 SPARK (7162)]
-'''Additional Info'''
- * [#point8.053 8.053 Uninstallation]
- * [#point8.054 8.054 Update TitanNit]
- * [#point8.055 8.055 IRD Download Location]
-----
-'''8.051 SPARK (7111)''' [=#point8.051] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-'' How do I install a Spark (7111) Update Image? ''
-  * Visit the AAF digital forum and download the latest TitanNit firmware .  ([#point8.15 IRD Download Locations])
-  * Extract the zip file
-  * Copy the unzipped firmware update file to a formatted to FAT32 USB stick and copy the file e2jffs2.img and uImage into a folder called "enigma2"
-     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 device.
-  * Connect the USB stick with the update file
-  * hold the "OK" button and switch on the(mains plug) and hold it down (about 5 seconds) until "Forc" appears,
-    then the installation will begin, when you see "U LD" in the display release the "OK" button.
-      Note: If the installation does not start, use a different USB stick.
-  * After installation "SUCC" appears in the display boot the receiver and the new image should appear.
-[[br]]
-[#point8.050 Top of Page]
-[[br]]
-----
-'''8.052 SPARK7162''' [=#point8.052] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-'' How do I install a Spark (7162) Update Image? ''
-  * Visit the AAF digital forum and download the latest TitanNit firmware .  ([#point8.15 IRD Download Locations])
-  * Extract the zip file
-  * Copy the unzipped firmware update file to a formatted to FAT32 USB stick and copy the file e2jffs2.img and uImage into a folder called "enigma2"
-     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 device.
-  * Connect the USB stick with the update file
-  * hold the "OK" button and switch on the(mains plug) and hold it down (about 5 seconds) until "Forc" appears,
-    then the installation will begin, when you see "U LD" in the display release the "OK" button.
-      Note: If the installation does not start, use a different USB stick.
-  * After installation "SUCC" appears in the display boot the receiver and the new image should appear.
-[[br]]
-[#point8.050 Top of Page]
-[[br]]
-----
-'''8.053 Uninstalling Titan''' [=#point8.053] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
-----
-If you have an Atemio/Atevio or UFS receiver all you have to do is i

Context Navigation

Legend: