Changeset 39721 for wiki


Ignore:
Timestamp:
Jan 12, 2017, 3:05:54 AM (3 years ago)
Author:
obi
Message:

reset wiki 39680

Location:
wiki/pages
Files:
219 edited

Legend:

Unmodified
Added
Removed
  • wiki/pages/SandBox

    r39712 r39721  
     1= The Sandbox =
     2
     3This is just a page to practice and learn WikiFormatting.
     4
     5Go ahead, edit it freely.
  • wiki/pages/TicketQuery

    r39712 r39721  
     1= !TicketQuery Wiki Macro
     2
     3The !TicketQuery macro lets you display information on tickets within wiki pages.
     4The query language used by the `[[TicketQuery]]` macro is described in [TracQuery#UsingtheTicketQueryMacro TracQuery] page.
     5
     6== Usage
     7
     8[[MacroList(TicketQuery)]]
     9
     10== Example
     11
     12||= **Example** =||= **Result** =||= **Macro** =||
     13|-----------------------------------------------------------
     14||=Number of [query:status=new&milestone= Triage tickets]: =||\
     15|| **[[TicketQuery(status=new&milestone=,count)]]**||\
     16|| `[[TicketQuery(status=new&milestone=,count)]]` ||
     17|-----------------------------------------------------------
     18||=Number of new tickets: =||\
     19|| **[[TicketQuery(status=new,count)]]**||\
     20|| `[[TicketQuery(status=new,count)]]` ||
     21|-----------------------------------------------------------
     22||=Number of reopened tickets: =||\
     23|| **[[TicketQuery(status=reopened,count)]]**||\
     24|| `[[TicketQuery(status=reopened,count)]]` ||
     25|-----------------------------------------------------------
     26||=Number of assigned tickets: =||\
     27|| **[[TicketQuery(status=assigned,count)]]**||\
     28|| `[[TicketQuery(status=assigned,count)]]` ||
     29|-----------------------------------------------------------
     30||=Number of invalid tickets: =||\
     31|| **[[TicketQuery(status=closed,resolution=invalid,count)]]**||\
     32|| `[[TicketQuery(status=closed,resolution=invalid,count)]]` ||
     33|-----------------------------------------------------------
     34||=Number of worksforme tickets: =||\
     35|| **[[TicketQuery(status=closed,resolution=worksforme,count)]]**||\
     36|| `[[TicketQuery(status=closed,resolution=worksforme,count)]]` ||
     37|-----------------------------------------------------------
     38||=Number of duplicate tickets: =||\
     39|| **[[TicketQuery(status=closed,resolution=duplicate,count)]]**||\
     40|| `[[TicketQuery(status=closed,resolution=duplicate,count)]]` ||
     41|-----------------------------------------------------------
     42||=Number of wontfix tickets: =||\
     43|| **[[TicketQuery(status=closed,resolution=wontfix,count)]]**||\
     44|| `[[TicketQuery(status=closed,resolution=wontfix,count)]]` ||
     45|-----------------------------------------------------------
     46||=Number of fixed tickets: =||\
     47|| **[[TicketQuery(status=closed,resolution=fixed,count)]]**||\
     48|| `[[TicketQuery(status=closed,resolution=fixed,count)]]` ||
     49|-----------------------------------------------------------
     50||=Total number of tickets: =||\
     51|| **[[TicketQuery(count)]]**||\
     52|| `[[TicketQuery(count)]]` ||
     53|-----------------------------------------------------------
     54||=Number of tickets reported **or** owned by current user: =||\
     55|| **[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]**||\
     56|| `[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]` ||
     57|-----------------------------------------------------------
     58||=Number of tickets created this month: =||\
     59|| **[[TicketQuery(created=thismonth..,count)]]**||\
     60|| `[[TicketQuery(created=thismonth..,count)]]` ||
     61|-----------------------------------------------------------
     62||=Last 3 modified tickets: =||\
     63||**[[TicketQuery(max=3,order=modified,desc=1,compact)]]**||\
     64|| `[[TicketQuery(max=3,order=modified,desc=1,compact)]]` ||
     65|-----------------------------------------------------------
     66{{{#!th rowspan=2, style="text-align: left;"
     67Details of ticket #1:
     68}}}
     69{{{#!td style="border-bottom: 0;"
     70}}}
     71{{{#!td
     72`[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]`
     73}}}
     74|-
     75{{{#!td colspan=2, style="border-top: 0;"
     76[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]
     77}}}
     78|-----------------------------------------------------------
     79
     80== Using the `[[TicketQuery]]` Macro
     81
     82The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
     83
     84Example:
     85{{{
     86[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
     87}}}
     88
     89This is displayed as:
     90  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
     91
     92Just 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:
     93{{{
     94[[TicketQuery(id=123)]]
     95}}}
     96
     97This is displayed as:
     98  [[TicketQuery(id=123)]]
     99
     100A more compact representation without the ticket summaries is:
     101{{{
     102[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
     103}}}
     104
     105This is displayed as:
     106  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
     107
     108Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter:
     109{{{
     110[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
     111}}}
     112
     113This is displayed as:
     114  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
     115
     116----
     117See also: TracQuery, TracTickets, TracReports, TracGuide
  • wiki/pages/TitleIndex

    r39712 r39721  
     1''' Index by Title ''' | ''' [RecentChanges Index by Date] '''
     2
     3[[TitleIndex(format=group,min=4)]]
  • wiki/pages/TracAccessibility

    r39712 r39721  
     1= Accessibility Support in Trac =
     2
     3Not 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.
     4
     5Trac 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.
     6 - on Linux platforms, press any of the keys listed below in combination with the `<Alt>` key
     7 - on a Mac, use the `<Ctrl>` + `<Opt>` key instead
     8 - on Windows, you need to hit `<Shift> + <Alt> + <Key>`. This works for the most common browsers, such as Firefox, Chrome, Safari and Internet Explorer
     9
     10== Global Access Keys ==
     11
     12 * `1` - WikiStart
     13 * `2` - [TracTimeline Timeline]
     14 * `3` - [TracRoadmap Roadmap]
     15 * `4` - [TracSearch Search]
     16 * `6` - [TracGuide Trac Guide / Documentation]
     17 * `7` - [TracTickets New Ticket]
     18 * `9` - [/about About Trac]
     19 * `e` - Edit (wiki or report)
     20 * `r` - Preview (wiki or ticket)
     21 * `f` - Search
     22
     23
     24----
     25See also: TracGuide
  • wiki/pages/TracAdmin

    r39712 r39721  
     1= TracAdmin
     2
     3[[PageOutline(2-5, Contents, floated)]]
     4[[TracGuideToc]]
     5
     6Trac 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.
     7
     8Some of those operations can also be performed via the web administration module.
     9
     10== Usage
     11
     12For 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:
     13{{{
     14trac-admin /path/to/projenv wiki list
     15}}}
     16
     17The 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.
     18Also, `trac-admin --version` will tell you about the Trac version (e.g. 0.12) corresponding to the program.
     19
     20If you want to get a comprehensive list of the available commands and sub-commands, you need to specify an existing environment:
     21{{{
     22trac-admin /path/to/projenv help
     23}}}
     24
     25Some commands have a more detailed help, which you can access by specifying the command's name as a subcommand for `help`:
     26
     27{{{
     28trac-admin /path/to/projenv help <command>
     29}}}
     30
     31=== `trac-admin <targetdir> initenv` === #initenv
     32
     33This 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.
     34
     35[[TracAdminHelp(initenv)]]
     36
     37It 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.
     38See TracIni#GlobalConfiguration.
     39
     40Note 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.
     41
     42== Interactive Mode
     43
     44When passing the environment path as the only argument, `trac-admin` starts in interactive mode.
     45Commands can then be executed on the selected environment using the prompt, which offers tab-completion
     46(on non-Windows environments, and when the Python `readline` module is available) and automatic repetition of the last command issued.
     47
     48Once you're in interactive mode, you can also get help on specific commands or subsets of commands:
     49
     50For example, to get an explanation of the `resync` command, run:
     51{{{
     52> help resync
     53}}}
     54
     55To get help on all the Wiki-related commands, run:
     56{{{
     57> help wiki
     58}}}
     59
     60== Full Command Reference
     61
     62You'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.
     63
     64[[TracAdminHelp()]]
     65
     66----
     67See also: TracGuide, TracBackup, TracPermissions, TracEnvironment, TracIni, [trac:TracMigrate TracMigrate]
  • wiki/pages/TracBackup

    r39712 r39721  
     1= Trac Backup
     2
     3[[TracGuideToc]]
     4
     5Backups 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].
     6
     7'''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.
     8
     9== Creating a Backup
     10
     11To create a backup of a live TracEnvironment simply run:
     12{{{#!sh
     13$ trac-admin /path/to/projenv hotcopy /path/to/backupdir
     14}}}
     15
     16[wiki:TracAdmin trac-admin] will lock the database while copying.
     17
     18The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.
     19
     20Please 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].
     21
     22=== Restoring a Backup
     23
     24To 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.
     25
     26To restore a PostgreSQL database backup, use the command:
     27{{{#!sh
     28psql -U <user> -d <database> -f postgresql.dump
     29}}}
     30The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//.
     31
     32----
     33See also: TracAdmin, TracEnvironment, TracGuide, [trac:TracMigrate TracMigrate]
  • wiki/pages/TracBatchModify

    r39712 r39721  
     1= Trac Ticket Batch Modification =
     2[[TracGuideToc]]
     3
     4Trac supports modifying a batch of tickets in one request from [TracQuery custom query] results .
     5
     6To perform a batch modification, select the tickets you wish to modify and set the new field values using the section underneath the query results.
     7
     8== List fields
     9
     10The `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.
     11
     12== Excluded fields
     13
     14Multi-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

    r39712 r39721  
     1= The Trac Repository Browser
     2
     3[[TracGuideToc]]
     4
     5The Trac repository browser can be used to browse specific revisions of directories and files stored in the repositories associated with the Trac environment.
     6
     7At the top-level of the repository browser is the '''Repository Index''', listing all the configured repositories.
     8Each repository has a name which is used as a path prefix in a "virtual" file hierarchy encompassing all the available repositories.
     9One 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.
     10
     11Directory 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.
     12
     13The browser can be used to navigate through the directory structure by clicking on the directory names.
     14Clicking on a file name will show the contents of the file.
     15Clicking on the revision number of a file or directory will take you to the TracRevisionLog for that file.
     16Note that there's also a ''Revision Log'' navigation link that will do the same for the path currently being examined.
     17Clicking on the ''diff'' icon after revision number will display the changes made to the files modified in that revision.
     18Clicking on the ''Age'' of the file - will take you to that changeset in the timeline.
     19
     20It'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.
     21
     22The 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].
     23
     24At 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.
     25This is sometimes referred to as the ''browser quickjump'' facility.
     26The precise meaning and content of this menu depends on your repository backend.
     27For 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.
     28
     29If 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:
     30 - use `j` and `k` to select the next or previous entry, starting with the first
     31 - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected
     32   directory or for visiting the selected file
     33 - `v` ('''v'''iew, '''v'''isit) and `<Enter>`, same as above
     34 - `r` can be used to force the '''r'''eload of an already expanded directory
     35 - `a` can be used to directly visit a file in '''a'''nnotate (blame) mode
     36 - `l` to view the '''l'''og for the selected entry
     37If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse.
     38
     39For the Subversion backend, some advanced additional features are available:
     40 - The `svn:needs-lock` property will be displayed.
     41 - Support for the `svn:mergeinfo` property showing the merged and eligible information.
     42 - Support for browsing the `svn:externals` property, which can be [TracIni#svn:externals-section configured].
     43 - 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].
     44{{{#!comment
     45MMM: I found this section a bit hard to understand. I changed the first item as I understood that well.
     46but I think the other items could be changed also
     47 cboos: in the meantime, I've added the ''advanced'' word as a hint this can be a bit complex...
     48}}}
     49
     50----
     51See also: TracGuide, TracChangeset, TracFineGrainedPermissions
  • wiki/pages/TracCgi

    r39712 r39721  
     1= Installing Trac as CGI
     2[[TracGuideToc]]
     3[[PageOutline]]
     4
     5{{{#!div class=important
     6 ''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.''
     7}}}
     8
     9CGI 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.
     10
     11== Apache web-server configuration
     12
     13In [http://httpd.apache.org/ Apache] there are two ways to run Trac as CGI:
     14
     15 1. Use a `ScriptAlias` directive that maps an URL to the `trac.cgi` script (recommended)
     16 1. 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.
     17
     18To make Trac available at `http://yourhost.example.org/trac` add `ScriptAlias` directive to Apache configuration file, changing `trac.cgi` path to match your installation:
     19{{{#!apache
     20ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.cgi
     21}}}
     22
     23 ''Note that this directive requires enabled `mod_alias` module.''
     24
     25If you're using Trac with a single project you need to set its location using the `TRAC_ENV` environment variable:
     26{{{#!apache
     27<Location "/trac">
     28  SetEnv TRAC_ENV "/path/to/projectenv"
     29</Location>
     30}}}
     31
     32Or to use multiple projects you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` variable:
     33{{{#!apache
     34<Location "/trac">
     35  SetEnv TRAC_ENV_PARENT_DIR "/path/to/project/parent/dir"
     36</Location>
     37}}}
     38
     39 ''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 ...":''
     40
     41{{{#!python
     42    import os
     43    os.environ['TRAC_ENV'] = "/path/to/projectenv"
     44}}}
     45
     46 '' Or for TRAC_ENV_PARENT_DIR: ''
     47
     48{{{#!python
     49    import os
     50    os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
     51}}}
     52
     53If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [trac:ApacheSuexec].
     54
     55On 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).
     56
     57=== Using WSGI
     58
     59You 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.
     60
     61== Mapping Static Resources
     62
     63See TracInstall#MappingStaticResources.
     64
     65== Adding Authentication
     66
     67See TracInstall#ConfiguringAuthentication.
     68
     69----
     70See also:  TracGuide, TracInstall, [wiki:TracModWSGI], TracFastCgi, TracModPython
  • wiki/pages/TracChangeLog

    r39712 r39721  
     1[[PageOutline(2-3)]]
     2= Change Log
     3This is a rough list of changes between released versions.
     4
     5To see where Trac is going in future releases, see the [trac:roadmap Roadmap].
     6
     7
     8== 1.1.x Releases
     9// 1.1.x releases are development releases leading eventually to Trac 1.2. See them as kind of snapshots of [trac:source:trunk].
     10
     11** No guarantees of feature and API compatibility is made from one 1.1.x release to the next. //
     12
     13=== 1.1.6
     14
     15//(July 17, 2015)//
     16
     17Trac 1.1.6 contains more than a half dozen minor fixes and enhancements.
     18
     19For more information see the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
     20release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.6]] and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.7]]
     21(as 1.1.6 contains all the fixes done for 1.0.7).
     22
     23[trac:source:/tags/trac-1.1.6 View Tag] | [trac:milestone:1.1.6 View Milestone]
     24
     25
     26=== 1.1.5
     27
     28//(May 18, 2015)//
     29
     30Highlights of the changes:
     31
     32 - Corrected highlighting of unmodified values in //Config// section of the //About Trac// page ([trac:#6551]).
     33 - New helper methods on `DatabaseManager` class for plugins to upgrade the database ([trac:#8172]).
     34 - New `[notification-subscriber]` config section for general configuration of notification subscription defaults and `SubscriberList` macro ([trac:#11875]).
     35 - Removed dependency on `ConfigObj` for TracFineGrainedPermissions ([trac:#11982]).
     36 - `Image` macro supports InterWiki prefixes ([trac:#12025]).
     37
     38See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
     39release 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]]
     40(as 1.1.5 contains all the fixes done for 1.0.6 and 0.12.7).
     41
     42[trac:source:/tags/trac-1.1.5 View Tag] | [trac:milestone:1.1.5 View Milestone]
     43
     44=== 1.1.4
     45
     46//(March 24, 2015)//
     47
     48Highlights of the changes:
     49
     50 - Performance improvements with MySQL/MariaDB ([trac:#3676]).
     51 - Click on //Permissions// Admin page table row toggles all
     52   checkboxes in the row ([trac:#11417]).
     53 - Configuration sections are written to trac.ini when enabling a
     54   component through TracAdmin or the web administration module
     55   ([trac:#11437]).
     56 - Subscription rules can be reordered by drag and drop ([trac:#11941]).
     57
     58See also the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
     59release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.1.4]]
     60and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.4/1.0.5]]
     61(as 1.1.4 contains all the fixes done for 1.0.4 and 1.0.5).
     62
     63[trac:source:/tags/trac-1.1.4 View Tag] | [trac:milestone:1.1.4 View Milestone]
     64
     65=== 1.1.3
     66
     67//(January 13, 2015)//
     68
     69The following list contains highlights of the changes:
     70
     71 - The ticket creation step can be configured in the TracWorkflow and the
     72   workflow controls are present on the !NewTicket page ([trac:#2045]).
     73 - New notification system that can be extended by plugins ([trac:#3517]).
     74 - New preferences panel for notification subscriptions ([trac:#4056]).
     75 - Wiki page version comments can be edited by users with `WIKI_ADMIN` ([trac:#6573]).
     76 - Improved positioning of //Add Comment// section and //author// field
     77   on the ticket form ([trac:#10207]).
     78 - The delete confirmation pages warn if attachments will also be deleted
     79   ([trac:#11542]).
     80 - Removed support for [trac:SilverCity], Enscript and !PhpRenderer syntax
     81   highlighters ([trac:#11795]).
     82 - Combined //Date & Time// and //Language// preference panels as
     83   //Localization// ([trac:#11813]).
     84 - Groups and permissions can be used in the workflow `set_owner` attribute
     85   ([trac:#11839]).
     86
     87See 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
     88for 1.0.3).
     89
     90[trac:source:/tags/trac-1.1.3 View Tag] | [trac:milestone:1.1.3 View Milestone]
     91
     92=== 1.1.2
     93
     94//(October 23, 2014)//
     95
     96The following list contains highlights of the changes:
     97
     98 - 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]).
     99 - 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]).
     100 - The new option `[ticket]` `optional_fields` specifies ticket select fields that are treated as optional (i.e. an empty value is allowed) ([trac:#10772]).
     101 - Line number and row highlighting annotations can be specified for !WikiProcessor code blocks ([trac:#10834]).
     102 - 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]).
     103 - Attachments can't be added to read-only wiki pages ([trac:#11244]).
     104 - Tables on the admin pages have a //Select all// checkbox in the header ([trac:#10994]).
     105 - Submit buttons are disabled if the required items are not selected ([trac:#11056]).
     106 - The Admin //Permissions// page has a //Copy Permissions// form for copying permissions between users and groups ([trac:#11099]).
     107 - 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]).
     108 - The //retarget// select is not shown when closing or deleting a milestone which has no tickets associated with it ([trac:#11366]).
     109 - //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]).
     110 - The `TitleIndex` macro supports relative path prefixes when used on wiki pages ([trac:#11455]).
     111 - [trac:CommitTicketUpdater] will recognize a ticket reference that includes a trailing `#comment:N` or `#comment:description` ([trac:#11622]).
     112 - 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]).
     113 - Authz policy can be used to restrict access to the //Report List// page using the resource id `-1` ([trac:#11697]).
     114
     115See 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).
     116
     117[trac:source:/tags/trac-1.1.2 View Tag] | [trac:milestone:1.1.2 View Milestone]
     118
     119=== 1.1.1
     120
     121//(February 3, 2013)//
     122
     123Trac 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.
     124
     125The following list contains only a few highlights:
     126
     127 - Added support for custom ticket fields of type time ([trac:#1942])
     128 - In new tickets, custom time ticket fields may default to an absolute or relative date / time ([trac:#10853])
     129 - In TracBatchModify, custom time ticket fields can be changed with a date(time)picker popup control ([trac:#10854])
     130 - Optionally display the component of tickets in their timeline entries (`[timeline]` `ticket_show_component` setting) ([trac:#10885])
     131 - Fixed batch modification when no fields are changed ([trac:#10924])
     132 - Dynamic variables can be used in the report title and description ([trac:#10979])
     133 - jQuery upgraded to 1.8.3, jQuery UI upgraded to 1.9.2 and jQuery UI Timepicker upgraded to 1.1.1 ([trac:#10976])
     134 - 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 ;-) )//
     135
     136See 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).
     137
     138[trac:source:/tags/trac-1.1.1 View Tag] | [trac:milestone:1.1.1 View Milestone]
     139
     140== 1.0.x Releases ==
     141
     142=== 1.0.7
     143
     144//(July 17, 2015)//
     145
     146Trac 1.0.7 contains more than a dozen minor fixes and enhancements, including the following highlights:
     147 - Custom `svn:keywords` definitions are expanded in Subversion 1.8 and later ([trac:#11364]).
     148 - Fixed MySQL performance regression in query with custom fields ([trac:#12113]).
     149
     150See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.7]].
     151
     152[trac:source:/tags/trac-1.0.7 View Tag] | [trac:milestone:1.0.7 View Milestone]
     153
     154=== 1.0.6
     155
     156//(May 20, 2015)//
     157
     158Trac 1.0.6 provides more than 20 fixes and enhancements. The following are some highlights:
     159 - Hash changeset ids and branch names can be used in revision ranges ([trac:#11050])
     160 - Improved rendering performance using chunked response when `[trac]` `use_chunked_encoding` is `True` ([trac:#11802])
     161 - Improved performance of Git repositories ([trac:#11971]).
     162 - 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]).
     163 - Symbolic link can be used for `conf/trac.ini` in environment directory ([trac:#12000]).
     164 - Hyphen character can be used in !WikiProcessor parameter name ([trac:#12023]).
     165
     166See 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).
     167
     168[trac:source:/tags/trac-1.0.6 View Tag] | [trac:milestone:1.0.6 View Milestone]
     169
     170=== 1.0.5
     171
     172//(March 24, 2015)//
     173
     174Trac 1.0.5 provides several fixes. The following are some highlights:
     175
     176 - Images are not rendered in the timeline ([trac:#10751]).
     177 - Git tags are shown in the browser view ([trac:#11964]).
     178 - Added support for `journal_mode` and `synchronous` pragmas in `sqlite:` database connection string ([trac:#11967]).
     179
     180See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.5]].
     181
     182[trac:source:/tags/trac-1.0.5 View Tag] | [trac:milestone:1.0.5 View Milestone]
     183
     184=== 1.0.4
     185
     186//(February 8, 2015)//
     187
     188Trac 1.0.4 contains a few fixes, including a fix for a regression in 1.0.3.
     189
     190 - Workflow action labels were not displayed unless name attribute
     191   was explicitly defined ([trac:#11930]).
     192
     193See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.4]].
     194
     195[trac:source:/tags/trac-1.0.4 View Tag] | [trac:milestone:1.0.4 View Milestone]
     196
     197=== 1.0.3
     198
     199//(January 13, 2015)//
     200
     201Trac 1.0.3 is a maintenance release containing numerous fixes and minor
     202enhancements. The following are a few of the highlights:
     203
     204The following list contains only a few highlights:
     205
     206 - Notification is sent when adding an attachment to a ticket ([trac:#2259]).
     207 - Stylesheets and scripts are loaded during autopreview, resulting in proper
     208   syntax highlighting when code WikiProcessors are added ([trac:#10470]) and display
     209   of Workflow graphs without explicit autopreview ([trac:#10674]).
     210 - Merge changesets are shown as differences against first parent, resulting
     211   in less noisy changesets ([trac:#10740]).
     212 - Pygments 2.0 is supported ([trac:#11796]).
     213 - Fixed error when completing the `initenv` TracAdmin command ([trac:#11797]).
     214 - Performance improvement on systems with many thousands of authenticated
     215   users due to caching of Environment.get_known_users ([trac:#11868]).
     216 - Distribution metadata of wheel package is supported and displayed on the
     217   About page ([trac:#11877]).
     218 - … and more than 3 dozen total fixes!
     219
     220See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.3]].
     221
     222[trac:source:/tags/trac-1.0.3 View Tag] | [trac:milestone:1.0.3 View Milestone]
     223
     224
     225=== 1.0.2
     226
     227//(October 23, 2014)//
     228
     229Trac 1.0.2 contains a number of bug fixes and minor enhancements, as well as a major update for many translations.
     230
     231The following list contains only a few highlights:
     232
     233 - Subversion keywords are expanded and EOL substitutions made when viewing a file in the repository browser and when downloading a file ([trac:#717]).
     234 - Notification email is sent to the old owner when a ticket is reassigned ([trac:#2311]).
     235 - Ticket change history is updated when renaming and deleting a milestone, and when retargeting tickets to another milestone ([trac:#4582], [trac:#5658]).
     236 - 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.
     237 - Multiple forms submits are disallowed ([trac:#10138]).
     238 - `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]).
     239 - Wiki toolbars can be disabled through a configuration setting ([trac:#10837])
     240 - The number of entries in a table is shown next to heading on applicable admin pages ([trac:#11027]).
     241 - //Cancel// buttons are consistently located on all pages ([trac:#11076]).
     242 - Focus is placed on a text element when an edit page is loaded ([trac:#11084]).
     243 - The //Edit conflict// and //Merge// warning messages are always visible in side-by-side edit mode ([trac:#11102]).
     244 - Improvements to the layout of the Report ([trac:#11106], [trac:#11664]) and Ticket pages ([trac:#11471]).
     245 - Genshi 0.7 compatibility ([trac:#11218]).
     246 - Numerous minor fixes for Git repository support.
     247 - … and more than a hundred more fixes!
     248
     249See 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).
     250
     251[trac:source:/tags/trac-1.0.2 View Tag] | [trac:milestone:1.0.2 View Milestone]
     252
     253
     254=== 1.0.1
     255
     256//(February 1, 2013)//
     257
     258Trac 1.0.1 contains a number of bug fixes and minor enhancements, as well as a major update for many translations.
     259
     260The following list contains only a few highlights:
     261
     262 - Fix zip source download for large directories in Subversion repositories ([trac:#10840])
     263 - Performance improvement for the Roadmap, by caching milestone properties ([trac:#10879])
     264 - Added a ''select all'' checkbox to table of components for each plugin on the Plugins admin panel ([trac:#9609])
     265 - Restore the ''Modify'' link at the top of the ticket page, as it was in Trac 0.12 ([trac:#10856])
     266 - `ListOption` keeps values other than empty string and None in raw list as default ([trac:#10541])
     267 - Prevent possibility of multiple identical info or warning messages being presented to the user ([trac:#10987])
     268 - The !BatchModify select-all checkboxes are toggled with tri-state behavior when the ticket checkboxes are toggled ([trac:#10992])
     269 - Update the ticket changetime to the current time when deleting a ticket comment ([trac:#10486])
     270
     271See 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).
     272
     273[trac:source:/tags/trac-1.0.1 View Tag] | [trac:milestone:1.0.1 View Milestone]
     274
     275
     276=== '''1.0 'Cell' '''
     277
     278//(September 7, 2012)//
     279
     280Trac 1.0 is a major release adding refreshed user interface and improved DVCS repository support as the most visible changes.
     281
     282The following list contains only a few highlights:
     283 - 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)
     284 - 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
     285 - As a consequence, the Subversion support has been moved below `tracopt.versioncontrol` as well
     286 - The Git and Mercurial log view feature a visualization of the branching structure
     287 - Usability improvements for the tickets, with a better support for conflict detection and resolution
     288 - Integration of the [TH:BatchModifyPlugin], contributed by Brian Meeker (many thanks!) and is now maintained there as a default component
     289 - jQuery/UI integration, featuring a date picker for date fields
     290 - Improved integration with Pygments syntax highlighting
     291 - ... and numerous smaller features added and bugs fixed since 0.12!
     292
     293See the full list in [trac:wiki:TracDev/ReleaseNotes/1.0 1.0].
     294
     295[[trac:source:/tags/trac-1.0 View Tag]] | [[trac:milestone:1.0 View Milestone]]
     296
     297== 0.12.x Releases
     298
     299=== 0.12.7
     300
     301//(May 20, 2015)//
     302
     303Trac 0.12.7 fixes a minor security issue, as well as a half dozen other minor issues:
     304 - InterWiki filters links through `[wiki] safe_schemes` option if `[wiki] render_unsafe_content` is disabled ([trac:#12053]).
     305
     306See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.7]].
     307
     308[trac:source:/tags/trac-0.12.7 View Tag] | [trac:milestone:0.12.7 View Milestone]
     309
     310=== 0.12.6
     311
     312//(October 23, 2014)//
     313
     314Trac 0.12.6 contains fixes for a few issues:
     315 - 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]).
     316 - Improved performance rendering `svn:mergeinfo` properties in browser view ([trac:#8459]) and changeset view ([trac:#11219]).
     317 - Query with many custom fields would fail ([trac:#11140]).
     318 - Zip archive had a timestamp with no timezone information ([trac:#11162]).
     319 - Failure or incorrect ranges rendering log TracLinks ([trac:#11308], [trac:#11346]).
     320 - Textareas in ticket view did not wrap correctly in IE 11 ([trac:#11376]).
     321 - Emails were not being obfuscated in owner field on CSV export from ticket and query pages ([trac:#11594]).
     322 - Locale data was not being included in egg in Distribute 0.6.29 and later ([trac:#11640]).
     323 - Deleting a milestone would not delete its attachments ([trac:#11672]).
     324 - Added support for Babel 1.0 and later ([trac:#11258], [trac:#11345]).
     325 - Added support for `ConfigObj` 5.0 and later ([trac:#11498]).
     326 - … and dozens more fixes!
     327
     328See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.6]].
     329
     330[trac:source:/tags/trac-0.12.6 View Tag] | [trac:milestone:0.12.6 View Milestone]
     331
     332=== 0.12.5
     333
     334//(January 15, 2013)//
     335
     336Trac 0.12.5 contains fixes for a few issues:
     337 - upload of .mht files ([Wikipedia:MHTML] web page archive files) now works ([trac:#9880])
     338 - more robust parsing of attachment URLs ([trac:#10280]) and uploaded file names ([trac:#10850])
     339 - 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])
     340 - no longer generate invalid JSON encoded data with Python 2.4 and 2.5 ([trac:#10877])
     341 - ... and fix a couple more minor defects ([trac:#10967], [trac:#10892], [trac:#10923], [trac:#10858], [trac:#10835])
     342
     343[trac:source:/tags/trac-0.12.5 View Tag] | [trac:milestone:0.12.5 View Milestone]
     344
     345=== 0.12.4
     346
     347//(September 7, 2012)//
     348
     349Trac 0.12.4 contains only a handful of minor fixes.
     350
     351[trac:source:/tags/trac-0.12.4 View Tag] | [trac:milestone:0.12.4 View Milestone]
     352
     353=== 0.12.3 ===
     354
     355//(February 6, 2012)//
     356
     357Trac 0.12.3 contains a few minor fixes and a few minor features.
     358 - compatibility with Subversion 1.7 ([trac:#10414])
     359 - easier troubleshooting of common startup errors ([trac:#10024])
     360 - jQuery upgraded to 1.4.4 ([trac:#10001])
     361 - improve fine-grained permission handling in the source browser ([trac:#9976], [trac:#10208], [trac:#10110])
     362 - added compatibility with MySQL 5.5.3 utf8mb4 databases ([trac:#9766])
     363 - ... and dozens more fixes!
     364
     365[trac:source:/tags/trac-0.12.3 View Tag] | [trac:milestone:0.12.3 View Milestone]
     366
     367=== 0.12.2
     368
     369//(January 31, 2011)//
     370
     371Trac 0.12.2 contains a few minor fixes and a few minor features.
     372
     373This list contains only a few highlights:
     374 - install: improved robustness of Trac installation if Babel is
     375   installed after the fact ([trac:#9439], [trac:#9595], [trac:#9961])
     376 - notifications: support for Asian character width ([trac:#4717])
     377 - roadmap: fix display of progress bar in some corner cases ([trac:#9718])
     378   and respect the overall_completion milestone group setting ([trac:#9721])
     379 - reports: reports and queries look much better, as the columns now
     380   keep the same width across groups; the absence of word wrapping in
     381   reports has been fixed ([trac:#9825])
     382 - web admin: improved layout ([trac:#8866], [trac:#9963])
     383 - web: it's now possible to log in different Trac instances sharing
     384   the same URL prefix (e.g. /project and /project-test) ([trac:#9951])
     385
     386[trac:source:/tags/trac-0.12.2 View Tag] | [trac:milestone:0.12.2 View Milestone]
     387
     388=== 0.12.1
     389
     390//(October 9, 2010)//
     391
     392Trac 0.12.1 contains a few important performance improvements, some minor fixes and a few minor features.
     393
     394This list contains only a few highlights:
     395 - db: improve concurrency behavior ([trac:#9111])
     396 - 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)
     397 - svn authz: improve compatibility with svn 1.5 format ([trac:#8289])
     398 - milestone: allow to set the time for the due date ([trac:#6369], [trac:#9582])
     399 - ticket: fixes for the CC: property ([trac:#8597], [trac:#9522])
     400 - notification: improved the formatting of ticket fields in notification e-mails ([trac:#9484], [trac:#9494])
     401 - i18n: added a configuration option to set the default language ([trac:#8117])
     402 - several fixes for upgrade ([trac:#9400], [trac:#9416], [trac:#9483], [trac:#9556])
     403
     404[trac:source:/tags/trac-0.12.1 View Tag] | [trac:milestone:0.12.1 View Milestone]
     405
     406=== ''' 0.12 'Babel' '''
     407
     408//(June 13, 2010)//
     409
     410Trac 0.12 is a major release introducing i18n and multiple repository support as the most visible changes.
     411
     412The following list contains only a few highlights:
     413 - The user interface is translated in a dozen of languages, provided the [Babel:] package is installed
     414 - Multiple repositories can be associated to a single Trac environment; the repositories can be of heterogeneous types (svn, hg, git, darcs...)
     415 - Usability improvements for the Wiki, with a nice side-by-side edit mode with automatic preview
     416 - Richer Wiki syntax, with much improved support for tables, partial [trac:WikiCreole] compatibility and numerous smaller improvements
     417 - Usability improvements for the Ticket module, with automatic preview of comments while you type and possibility to edit or remove them later
     418 - Improved Custom Queries (time fields, multiple disjoint conditions, a.k.a. OR queries)
     419 - Timeline filtering by user
     420 - ... and numerous smaller features added and bugs fixed since 0.11!
     421
     422[trac:source:/tags/trac-0.12 View Tag] | [trac:milestone:0.12 View Milestone]
     423
     424== Older Releases
     425
     426For releases prior to 0.12, see [trac:TracChangeLog@95].
  • wiki/pages/TracChangeset

    r39712 r39721  
     1= Trac Changeset Module =
     2[[TracGuideToc]]
     3
     4Trac has a built-in functionality for visualizing “diffs”, or changes to files.
     5
     6There 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.
     7
     8The changeset view consists of two parts, the ''header'' and the ''diff views''.
     9
     10== Changeset Header ==
     11
     12The header shows an overview of the whole changeset.
     13Here you will find information such as:
     14
     15 * Timestamp — When the changeset was commited
     16 * Author — Who commited the changeset
     17 * Message — A brief description from the author (the commit log message)
     18 * Location — Parent directory of all files affected by this changeset
     19 * Files — A list of files affected by this changeset
     20
     21If more than one revision is involved in the set of changes being displayed, the ''Timestamp'', ''Author'' and ''Message'' fields will not be shown.
     22
     23A colored rectangle indicates how the file is affected by the changeset:
     24 
     25 [[span(style=background:#bfb;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Green: Added \\
     26 [[span(style=background:#f88;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Red: Removed \\
     27 [[span(style=background:#fd8;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Yellow: Modified \\
     28 [[span(style=background:#88f;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Blue: Copied \\
     29 [[span(style=background:#ccc;border:1px solid #999;font-size:80%;margin-right:.5em,''  '')]] Gray: Moved \\
     30The color legend is located below the header as a reminder.
     31
     32== Diff Views ==
     33
     34Below 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:
     35
     36 * 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.
     37 * 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.
     38
     39In addition, various advanced options are available in the preferences form for adjusting the display of the diffs:
     40 * 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.
     41 * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly.
     42
     43== The Different Ways to Get a Diff ==
     44
     45=== Examining a Changeset ===
     46
     47When 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.
     48
     49There will be also navigation links to the ''Previous Changeset'' to and ''Next Changeset''.
     50
     51=== Examining Differences Between Revisions ===
     52
     53Often 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.
     54
     55=== Examining Differences Between Branches ===
     56
     57One 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.
     58
     59Using 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.
     60
     61For 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.
     62
     63=== Checking the Last Change ===
     64
     65Another way to examine changes is to use the ''Last Change'' link provided by the TracBrowser.
     66
     67This 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.
     68
     69----
     70See also: TracGuide, TracBrowser
  • wiki/pages/TracEnvironment

    r39712 r39721  
     1= The Trac Environment
     2
     3[[TracGuideToc]]
     4[[PageOutline(2-5)]]
     5
     6Trac uses a directory structure and a database for storing project data. The directory is referred to as the environment.
     7
     8== Creating an Environment
     9
     10A new Trac environment is created using [TracAdmin#initenv trac-admin's initenv]:
     11{{{#!sh
     12$ trac-admin /path/to/myproject initenv
     13}}}
     14
     15`trac-admin` will ask you for the name of the project and the database connection string, see below.
     16
     17=== Useful Tips
     18
     19 - 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.
     20
     21 - 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.
     22 
     23 - `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.
     24
     25 - Non-ascii environment paths are not supported.
     26 
     27 - Also, it seems that project names with spaces can be problematic for authentication, see [trac:#7163].
     28
     29 - 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.
     30
     31{{{#!div style="border: 1pt dotted; margin: 1em"
     32**Caveat:** don't confuse the //Trac environment directory// with the //source code repository directory//.
     33
     34This is a common beginners' mistake.
     35It 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.
     36}}}
     37
     38== Database Connection Strings
     39
     40Trac 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.
     41
     42Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded.
     43
     44=== SQLite Connection String
     45
     46The connection string for an SQLite database is:
     47{{{
     48sqlite:db/trac.db
     49}}}
     50where `db/trac.db` is the path to the database file within the Trac environment.
     51
     52=== PostgreSQL Connection String
     53
     54If 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:
     55{{{
     56postgres://johndoe:letmein@localhost/trac
     57}}}
     58
     59If PostgreSQL is running on a non-standard port, for example 9342, use:
     60{{{
     61postgres://johndoe:letmein@localhost:9342/trac
     62}}}
     63
     64On UNIX, you might want to select a UNIX socket for the transport, either the default socket as defined by the PGHOST environment variable:
     65{{{
     66postgres://user:password@/database
     67}}}
     68
     69or a specific one:
     70{{{
     71postgres://user:password@/database?host=/path/to/socket/dir
     72}}}
     73
     74Note that with PostgreSQL you will have to create the database before running `trac-admin initenv`.
     75
     76See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL].
     77Generally, the following is sufficient to create a database user named `tracuser` and a database named `trac`:
     78{{{#!sh
     79$ createuser -U postgres -E -P tracuser
     80$ createdb -U postgres -O tracuser -E UTF8 trac
     81}}}
     82
     83When 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.
     84
     85Under some default configurations (Debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user:
     86{{{#!sh
     87$ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
     88$ sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac'
     89}}}
     90
     91Trac uses the `public` schema by default, but you can specify a different schema in the connection string:
     92{{{
     93postgres://user:pass@server/database?schema=yourschemaname
     94}}}
     95
     96=== MySQL Connection String
     97
     98The 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`:
     99{{{
     100mysql://johndoe:letmein@localhost:3306/trac
     101}}}
     102
     103== Source Code Repository
     104
     105A 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.
     106
     107There 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.
     108
     109== Directory Structure
     110
     111An environment directory will usually consist of the following files and directories:
     112
     113 * `README` - Brief description of the environment.
     114 * `VERSION` - Environment version identifier.
     115 * `files`
     116  * `attachments` - Attachments to wiki pages and tickets.
     117 * `conf`
     118  * `trac.ini` - Main configuration file. See TracIni.
     119 * `db`
     120  * `trac.db` - The SQLite database, if you are using SQLite.
     121 * `htdocs` - Directory containing web resources, which can be referenced in Genshi templates using `/chrome/site/...` URLs.
     122 * `log` - Default directory for log files, if `file` logging is enabled and a relative path is given.
     123 * `plugins` - Environment-specific [wiki:TracPlugins plugins].
     124 * `templates` - Custom Genshi environment-specific templates.
     125  * `site.html` - Method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance.
     126
     127----
     128See also: TracAdmin, TracBackup, TracIni, TracGuide
  • wiki/pages/TracFastCgi

    r39712 r39721  
     1= Trac with FastCGI
     2
     3[[TracGuideToc]]
     4[[PageOutline(2-5, Contents, floated)]]
     5
     6[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.
     7
     8Note 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.
     9
     10'''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].
     11
     12== Simple Apache configuration
     13
     14There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and
     15`mod_fcgid` (preferred). The latter is more up-to-date.
     16
     17The following sections focus on the FCGI specific setup, see also [wiki:TracModWSGI#ConfiguringAuthentication] for configuring the authentication in Apache.
     18
     19Regardless 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.
     20
     21=== Set up with `mod_fastcgi`
     22
     23`mod_fastcgi` uses `FastCgiIpcDir` and `FastCgiConfig` directives that should be added to an appropriate Apache configuration file:
     24{{{
     25# Enable fastcgi for .fcgi files
     26# (If you're using a distro package for mod_fcgi, something like
     27# this is probably already present)
     28<IfModule mod_fastcgi.c>
     29   AddHandler fastcgi-script .fcgi
     30   FastCgiIpcDir /var/lib/apache2/fastcgi
     31</IfModule>
     32LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so
     33}}}
     34Setting `FastCgiIpcDir` is optional if the default is suitable. Note that the `LoadModule` line must be after the `IfModule` group.
     35
     36Configure `ScriptAlias` or similar options as described in TracCgi, but
     37calling `trac.fcgi` instead of `trac.cgi`.
     38
     39Add the following to the Apache configuration file (below the `FastCgiIpcDir` line) if you intend to set up the `TRAC_ENV` as an overall default:
     40{{{
     41FastCgiConfig -initial-env TRAC_ENV=/path/to/env/trac
     42}}}
     43
     44Alternatively, you can serve multiple Trac projects in a directory by adding this:
     45{{{
     46FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects
     47}}}
     48
     49=== Set up with `mod_fcgid`
     50
     51Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` instead of `trac.cgi`:
     52{{{
     53ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.fcgi/
     54}}}
     55Note the slash at the end.
     56
     57To 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.
     58
     59{{{
     60DefaultInitEnv TRAC_ENV /path/to/env/trac/
     61}}}
     62
     63=== alternative environment setup
     64
     65A 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:
     66{{{
     67import os
     68os.environ['TRAC_ENV'] = "/path/to/projectenv"
     69}}}
     70or:
     71{{{
     72import os
     73os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
     74}}}
     75
     76With this method different projects can be supported by using different `.fcgi` scripts with different `ScriptAliases`.
     77
     78See [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:
     79{{{
     80ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/
     81}}}
     82
     83== Simple Cherokee Configuration
     84
     85The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process.
     86You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down.
     87First set up an information source in cherokee-admin with a local interpreter:
     88
     89{{{
     90Host:
     91localhost:4433
     92
     93Interpreter:
     94/usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/
     95}}}
     96
     97If 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''.
     98
     99After 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.
     100The 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).
     101
     102Note:\\
     103If 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.\\
     104Python-flup is a dependency which provides trac with SCGI capability. You can install it on debian based systems with:
     105{{{
     106sudo apt-get install python-flup
     107}}}
     108
     109== Simple Lighttpd Configuration
     110
     111The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.lighttpd.net/ Lighttpd].
     112
     113Lighttpd 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.
     114
     115For using `trac.fcgi`(prior to 0.11) / fcgi_frontend.py (0.11) with Lighttpd add the following to your lighttpd.conf:
     116{{{
     117#var.fcgi_binary="/usr/bin/python /path/to/fcgi_frontend.py" # 0.11 if installed with easy_setup, it is inside the egg directory
     118var.fcgi_binary="/path/to/cgi-bin/trac.fcgi" # 0.10 name of prior fcgi executable
     119fastcgi.server = ("/trac" =>
     120   
     121                   ("trac" =>
     122                     ("socket" => "/tmp/trac-fastcgi.sock",
     123                      "bin-path" => fcgi_binary,
     124                      "check-local" => "disable",
     125                      "bin-environment" =>
     126                        ("TRAC_ENV" => "/path/to/projenv")
     127                     )
     128                   )
     129                 )
     130}}}
     131
     132Note 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.
     133
     134Note 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.
     135
     136For using two projects with lighttpd add the following to your `lighttpd.conf`:
     137{{{
     138fastcgi.server = ("/first" =>
     139                   ("first" =>
     140                    ("socket" => "/tmp/trac-fastcgi-first.sock",
     141                     "bin-path" => fcgi_binary,
     142                     "check-local" => "disable",
     143                     "bin-environment" =>
     144                       ("TRAC_ENV" => "/path/to/projenv-first")
     145                    )
     146                  ),
     147                  "/second" =>
     148                    ("second" =>
     149                    ("socket" => "/tmp/trac-fastcgi-second.sock",
     150                     "bin-path" => fcgi_binary,
     151                     "check-local" => "disable",
     152                     "bin-environment" =>
     153                       ("TRAC_ENV" => "/path/to/projenv-second")
     154                    )
     155                  )
     156                )
     157}}}
     158
     159Note 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.
     160Note that the above will result in different processes in any event, even if both are running from the same `trac.fcgi` script.
     161
     162{{{
     163#!div class=important
     164'''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.
     165}}}
     166
     167For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules:
     168{{{
     169server.modules              = (
     170...
     171  "mod_auth",
     172...
     173)
     174
     175auth.backend               = "htpasswd"
     176
     177# Separated password files for each project
     178# See "Conditional Configuration" in
     179# http://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/configuration.txt
     180
     181$HTTP["url"] =~ "^/first/" {
     182  auth.backend.htpasswd.userfile = "/path/to/projenv-first/htpasswd.htaccess"
     183}
     184$HTTP["url"] =~ "^/second/" {
     185  auth.backend.htpasswd.userfile = "/path/to/projenv-second/htpasswd.htaccess"
     186}
     187
     188# Enable auth on trac URLs, see
     189# http://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/authentication.txt
     190
     191auth.require = ("/first/login" =>
     192                ("method"  => "basic",
     193                 "realm"   => "First project",
     194                 "require" => "valid-user"
     195                ),
     196                "/second/login" =>
     197                ("method"  => "basic",
     198                 "realm"   => "Second project",
     199                 "require" => "valid-user"
     200                )
     201               )
     202
     203}}}
     204Note that Lighttpd (v1.4.3) stops if the password file doesn't exist.
     205
     206Note that Lighttpd doesn't support 'valid-user' in versions prior to 1.3.16.
     207
     208Conditional configuration is also useful for mapping static resources, ie serving out images and CSS directly instead of through FastCGI:
     209{{{
     210# Aliasing functionality is needed
     211server.modules += ("mod_alias")
     212
     213# Set up an alias for the static resources
     214alias.url = ("/trac/chrome/common" => "/usr/share/trac/htdocs")
     215
     216# Use negative lookahead, matching all requests that ask for any resource under /trac, EXCEPT in
     217# /trac/chrome/common, and use FastCGI for those
     218$HTTP["url"] =~ "^/trac(?!/chrome/common)" {
     219# Even if you have other fastcgi.server declarations for applications other than Trac, do NOT use += here
     220fastcgi.server = ("/trac" =>
     221                   ("trac" =>
     222                     ("socket" => "/tmp/trac-fastcgi.sock",
     223                      "bin-path" => fcgi_binary,
     224                      "check-local" => "disable",
     225                      "bin-environment" =>
     226                        ("TRAC_ENV" => "/path/to/projenv")
     227                     )
     228                   )
     229                 )
     230}
     231}}}
     232
     233The 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.
     234Also 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:
     235{{{
     236#  This is for handling multiple projects
     237  alias.url       = ( "/trac/" => "/path/to/trac/htdocs/" )
     238
     239  fastcgi.server += ("/projects"  =>
     240                      ("trac" =>
     241                        (
     242                          "socket" => "/tmp/trac.sock",
     243                          "bin-path" => fcgi_binary,
     244                          "check-local" => "disable",
     245                          "bin-environment" =>
     246                            ("TRAC_ENV_PARENT_DIR" => "/path/to/parent/dir/of/projects/" )
     247                        )
     248                      )
     249                    )
     250#And here starts the global auth configuration
     251  auth.backend = "htpasswd"
     252  auth.backend.htpasswd.userfile = "/path/to/unique/htpassword/file/trac.htpasswd"
     253  $HTTP["url"] =~ "^/projects/.*/login$" {
     254    auth.require = ("/" =>
     255                     (
     256                       "method"  => "basic",
     257                       "realm"   => "trac",
     258                       "require" => "valid-user"
     259                     )
     260                   )
     261  }
     262}}}
     263
     264Changing date/time format also supported by lighttpd over environment variable LC_TIME:
     265{{{
     266fastcgi.server = ("/trac" =>
     267                   ("trac" =>
     268                     ("socket" => "/tmp/trac-fastcgi.sock",
     269                      "bin-path" => fcgi_binary,
     270                      "check-local" => "disable",
     271                      "bin-environment" =>
     272                        ("TRAC_ENV" => "/path/to/projenv",
     273                        "LC_TIME" => "ru_RU")
     274                     )
     275                   )
     276                 )
     277}}}
     278For details about languages specification see [trac:TracFaq TracFaq] question 2.13.
     279
     280Other important information like the [wiki:TracInstall#MappingStaticResources mapping static resources advices] are useful for non-fastcgi specific installation aspects.
     281]
     282
     283Relaunch Lighttpd and browse to `http://yourhost.example.org/trac` to access Trac.
     284
     285Note 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.
     286
     287== Simple !LiteSpeed Configuration
     288
     289The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed].
     290
     291!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.
     292
     293 1. Please make sure you have a working install of a Trac project. Test install with "tracd" first.
     294
     295 2. 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:
     296{{{
     297http://yourdomain.com/trac/
     298}}}
     299
     300 3. Go "!TracVhost → External Apps" tab and create a new "External Application".
     301{{{
     302Name: MyTracFCGI       
     303Address: uds://tmp/lshttpd/mytracfcgi.sock
     304Max Connections: 10
     305Environment: TRAC_ENV=/fullpathto/mytracproject/ <--- path to root folder of trac project
     306Initial Request Timeout (secs): 30
     307Retry Timeout (secs): 0
     308Persistent Connection   Yes
     309Connection Keepalive Timeout: 30
     310Response Bufferring: No
     311Auto Start: Yes
     312Command: /usr/share/trac/cgi-bin/trac.fcgi  <--- path to trac.fcgi
     313Back Log: 50
     314Instances: 10
     315}}}
     316
     317 4. Optional: If you need to use htpasswd based authentication. Go to "!TracVhost → Security" tab and create a new security Realm.
     318
     319{{{
     320DB Type: Password File
     321Realm Name: MyTracUserDB               <--- any name you wish and referenced later
     322User DB Location: /fullpathto/htpasswd <--- path to your htpasswd file
     323}}}
     324
     325If 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.
     326
     327 5. Go to "!PythonVhost → Contexts" and create a new FCGI Context.
     328
     329{{{
     330URI: /trac/                              <--- URI path to bind to python fcgi app we created   
     331Fast CGI App: [VHost Level] MyTractFCGI  <--- select the trac fcgi extapp we just created
     332Realm: TracUserDB                        <--- only if (4) is set. select realm created in (4)
     333}}}
     334
     335 6. Modify `/fullpathto/mytracproject/conf/trac.ini`
     336
     337{{{
     338#find/set base_rul, url, and link variables
     339base_url = http://yourdomain.com/trac/ <--- base url to generate correct links to
     340url = http://yourdomain.com/trac/      <--- link of project
     341link = http://yourdomain.com/trac/     <--- link of graphic logo
     342}}}
     343
     344 7. Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
     345
     346{{{
     347http://yourdomain.com/trac/
     348}}}
     349
     350== Simple Nginx Configuration
     351
     352Nginx is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately.
     353
     354 1. Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32
     355 {{{
     356    server {
     357        listen       10.9.8.7:443;
     358        server_name  trac.example;
     359
     360        ssl                  on;
     361        ssl_certificate      /etc/ssl/trac.example.crt;
     362        ssl_certificate_key  /etc/ssl/trac.example.key;
     363
     364        ssl_session_timeout  5m;
     365
     366        ssl_protocols  SSLv2 SSLv3 TLSv1;
     367        ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
     368        ssl_prefer_server_ciphers   on;
     369
     370        # it makes sense to serve static resources through Nginx (or ``~ [/some/prefix]/chrome/(.*)``)
     371        location ~ /chrome/(.*) {
     372             alias /home/trac/instance/static/htdocs/$1;
     373        }
     374
     375        # You can copy this whole location to ``location [/some/prefix](/login)``
     376        # and remove the auth entries below if you want Trac to enforce
     377        # authorization where appropriate instead of needing to authenticate
     378        # for accessing the whole site.
     379        # (Or ``~ location /some/prefix(/.*)``.)
     380        location ~ (/.*) {
     381            auth_basic            "trac realm";
     382            auth_basic_user_file /home/trac/htpasswd;
     383
     384            # socket address
     385            fastcgi_pass   unix:/home/trac/run/instance.sock;
     386
     387            # python - wsgi specific
     388            fastcgi_param HTTPS on;
     389
     390            ## WSGI REQUIRED VARIABLES
     391            # WSGI application name - trac instance prefix.
     392            # (Or ``fastcgi_param  SCRIPT_NAME  /some/prefix``.)
     393            fastcgi_param  SCRIPT_NAME        "";
     394            fastcgi_param  PATH_INFO          $1;
     395
     396            ## WSGI NEEDED VARIABLES - trac warns about them
     397            fastcgi_param  REQUEST_METHOD     $request_method;
     398            fastcgi_param  SERVER_NAME        $server_name;
     399            fastcgi_param  SERVER_PORT        $server_port;
     400            fastcgi_param  SERVER_PROTOCOL    $server_protocol;
     401            fastcgi_param  QUERY_STRING       $query_string;
     402
     403            # For Nginx authentication to work - do not forget to comment these
     404            # lines if not using Nginx for authentication
     405            fastcgi_param  AUTH_USER          $remote_user;
     406            fastcgi_param  REMOTE_USER        $remote_user;
     407
     408            # for ip to work
     409            fastcgi_param REMOTE_ADDR         $remote_addr;
     410
     411            # For attchments to work
     412            fastcgi_param    CONTENT_TYPE     $content_type;
     413            fastcgi_param    CONTENT_LENGTH   $content_length;
     414        }
     415    }
     416}}}
     417 1. Modified trac.fcgi:
     418 {{{
     419#!/usr/bin/env python
     420import os
     421sockaddr = '/home/trac/run/instance.sock'
     422os.environ['TRAC_ENV'] = '/home/trac/instance'
     423
     424try:
     425     from trac.web.main import dispatch_request
     426     import trac.web._fcgi
     427
     428     fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request,
     429          bindAddress = sockaddr, umask = 7)
     430     fcgiserv.run()
     431
     432except SystemExit:
     433    raise
     434except Exception, e:
     435    print 'Content-Type: text/plain\r\n\r\n',
     436    print 'Oops...'
     437    print
     438    print 'Trac detected an internal error:'
     439    print
     440    print e
     441    print
     442    import traceback
     443    import StringIO
     444    tb = StringIO.StringIO()
     445    traceback.print_exc(file=tb)
     446    print tb.getvalue()
     447
     448}}}
     449 1. reload nginx and launch trac.fcgi like that:
     450 {{{#!sh
     451trac@trac.example ~ $ ./trac-standalone-fcgi.py
     452}}}
     453
     454The above assumes that:
     455 * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory
     456 * `/home/trac/instance` contains a trac environment
     457 * `/home/trac/htpasswd` contains authentication information
     458 * `/home/trac/run` is owned by the same group the nginx runs under
     459  * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`)
     460  * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time
     461
     462Unfortunately nginx does not support variable expansion in fastcgi_pass directive.
     463Thus it is not possible to serve multiple Trac instances from one server block.
     464
     465If you worry enough about security, run Trac instances under separate users.
     466
     467Another way to run Trac as a FCGI external application is offered in ticket #T6224
     468
     469----
     470See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
  • wiki/pages/TracFineGrainedPermissions

    r39712 r39721  
     1= Fine grained permissions =
     2[[PageOutline(2-5, Contents, floated)]]
     3[[TracGuideToc]]
     4
     5There 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.
     6
     7That 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.
     8
     9== Permission Policies ==
     10
     11A great diversity of permission policies can be implemented and Trac comes with a few examples.
     12
     13Which policies are currently active is determined by a configuration setting in TracIni:
     14
     15{{{#!ini
     16[trac]
     17permission_policies = ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
     18}}}
     19This 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.
     20
     21Among the optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See
     22[trac:source:branches/1.0-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.
     23
     24Another 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.
     25
     26See also [trac:source:branches/1.0-stable/sample-plugins/permissions sample-plugins/permissions] for more examples.
     27
     28=== !AuthzPolicy ===
     29==== Configuration ====
     30* 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.
     31* Update your `trac.ini`:
     32  1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section:
     33{{{#!ini
     34[trac]
     35...
     36permission_policies = AuthzPolicy, ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
     37}}}
     38  1. add a new `[authz_policy]` section:
     39{{{#!ini
     40[authz_policy]
     41authz_file = /some/trac/env/conf/authzpolicy.conf
     42}}}
     43  1. enable the plugin through [/admin/general/plugin WebAdmin] or by editing the `[components]` section:
     44{{{#!ini
     45[components]
     46tracopt.perm.authz_policy.* = enabled
     47}}}
     48
     49==== Usage Notes ====
     50
     51Note the order in which permission policies are specified: policies are implemented in the sequence provided and therefore may override earlier policy specifications.
     52
     53A 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.
     54
     55NOTE: 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.
     56
     57The `authzpolicy.conf` file is a `.ini` style configuration file:
     58{{{#!ini
     59[wiki:PrivatePage@*]
     60john = WIKI_VIEW, !WIKI_MODIFY
     61jack = WIKI_VIEW
     62* =
     63}}}
     64* Each section of the config is a glob pattern used to match against a Trac resource descriptor. These descriptors are in the form:
     65{{{
     66<realm>:<id>@<version>[/<realm>:<id>@<version> ...]
     67}}}
     68
     69Resources 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:
     70{{{#!ini
     71[wiki:*]
     72[wiki:WikiStart*]
     73[wiki:WikiStart@*]
     74[wiki:WikiStart]
     75}}}
     76
     77Example: Match the attachment `wiki:WikiStart@117/attachment:FOO.JPG@*` on WikiStart:
     78{{{#!ini
     79[wiki:*]
     80[wiki:WikiStart*]
     81[wiki:WikiStart@*]
     82[wiki:WikiStart@*/attachment:*]
     83[wiki:WikiStart@117/attachment:FOO.JPG]
     84}}}
     85
     86* Sections are checked against the current Trac resource descriptor '''IN ORDER''' of appearance in the configuration file. '''ORDER IS CRITICAL'''.
     87
     88* Once a section matches, the current username is matched against the keys (usernames) of the section, '''IN ORDER'''.
     89  * If a key (username) is prefixed with a `@`, it is treated as a group.
     90  * If a value (permission) is prefixed with a `!`, the permission is denied rather than granted.
     91
     92The 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. ||
     93
     94For example, if the `authz_file` contains:
     95{{{#!ini
     96[wiki:WikiStart@*]
     97* = WIKI_VIEW
     98
     99[wiki:PrivatePage@*]
     100john = WIKI_VIEW
     101* = !WIKI_VIEW
     102}}}
     103and the default permissions are set like this:
     104{{{
     105john           WIKI_VIEW
     106jack           WIKI_VIEW
     107# anonymous has no WIKI_VIEW
     108}}}
     109
     110Then:
     111  * All versions of WikiStart will be viewable by everybody, including anonymous
     112  * !PrivatePage will be viewable only by john
     113  * other pages will be viewable only by john and jack
     114
     115Groups:
     116{{{#!ini
     117[groups]
     118admins = john, jack
     119devs = alice, bob
     120
     121[wiki:Dev@*]
     122@admins = TRAC_ADMIN
     123@devs = WIKI_VIEW
     124* =
     125
     126[*]
     127@admins = TRAC_ADMIN
     128* =
     129}}}
     130
     131Then:
     132- everything is blocked (whitelist approach), but
     133- admins get all TRAC_ADMIN everywhere and
     134- devs can view wiki pages.
     135
     136Some repository examples (Browse Source specific):
     137{{{#!ini
     138# A single repository:
     139[repository:test_repo@*]
     140john = BROWSER_VIEW, FILE_VIEW
     141# John has BROWSER_VIEW and FILE_VIEW for the entire test_repo
     142
     143# The default repository (requires Trac 1.0.2 or later):
     144[repository:@*]
     145john = BROWSER_VIEW, FILE_VIEW
     146# John has BROWSER_VIEW and FILE_VIEW for the entire default repository
     147
     148# All repositories:
     149[repository:*@*]
     150jack = BROWSER_VIEW, FILE_VIEW
     151# Jack has BROWSER_VIEW and FILE_VIEW for all repositories
     152}}}
     153
     154Very granular repository access:
     155{{{#!ini
     156# John has BROWSER_VIEW and FILE_VIEW access to trunk/src/some/location/ only
     157[repository:test_repo@*/source:trunk/src/some/location/*@*]
     158john = BROWSER_VIEW, FILE_VIEW
     159
     160# John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of all files at trunk/src/some/location only
     161[repository:test_repo@*/source:trunk/src/some/location/*@1]
     162john = BROWSER_VIEW, FILE_VIEW
     163
     164# John has BROWSER_VIEW and FILE_VIEW access to all revisions of 'somefile' at trunk/src/some/location only
     165[repository:test_repo@*/source:trunk/src/some/location/somefile@*]
     166john = BROWSER_VIEW, FILE_VIEW
     167
     168# John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of 'somefile' at trunk/src/some/location only
     169[repository:test_repo@*/source:trunk/src/some/location/somefile@1]
     170john = BROWSER_VIEW, FILE_VIEW
     171}}}
     172
     173Note: In order for Timeline to work/visible for John, we must add CHANGESET_VIEW to the above permission list.
     174
     175==== Missing Features ====
     176Although 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].
     177
     178You cannot do the following:
     179{{{#!ini
     180[groups]
     181team1 = a, b, c
     182team2 = d, e, f
     183team3 = g, h, i
     184departmentA = team1, team2
     185}}}
     186
     187Permission groups are not supported either, so you cannot do the following:
     188{{{#!ini
     189[groups]
     190permission_level_1 = WIKI_VIEW, TICKET_VIEW
     191permission_level_2  = permission_level_1, WIKI_MODIFY, TICKET_MODIFY
     192[*]
     193@team1 = permission_level_1
     194@team2 = permission_level_2
     195@team3 = permission_level_2, TICKET_CREATE
     196}}}
     197
     198=== !AuthzSourcePolicy  (mod_authz_svn-like permission policy) === #AuthzSourcePolicy
     199
     200At 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.
     201
     202That kind of granular permission control needs a definition file, which is the one used by Subversion's mod_authz_svn.
     203More 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.
     204
     205Example:
     206{{{#!ini
     207[/]
     208* = r
     209
     210[/branches/calc/bug-142]
     211harry = rw
     212sally = r
     213
     214[/branches/calc/bug-142/secret]
     215harry =
     216}}}
     217
     218 * '''/''' = ''Everyone has read access by default''
     219 * '''/branches/calc/bug-142''' = ''harry has read/write access, sally read only''
     220 * '''/branches/calc/bug-142/secret''' = ''harry has no access, sally has read access (inherited as a sub folder permission)''
     221
     222==== Trac Configuration ====
     223
     224To 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.
     225
     226{{{#!ini
     227[svn]
     228authz_file = /path/to/svnaccessfile
     229}}}
     230
     231If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add:
     232
     233{{{#!ini
     234authz_module_name = modulename
     235}}}
     236
     237where ''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:
     238
     239{{{ #!ini
     240[svn]
     241authz_file = /path/to/svnaccessfile
     242authz_module_name = somemodule
     243...
     244[repositories]
     245somemodule.dir = /srv/active/svn/somemodule
     246}}}
     247
     248where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[somemodule:/some/path]}}}.
     249
     250'''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac.
     251
     252As 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.
     253
     254{{{#!ini
     255[trac]
     256permission_policies = AuthzSourcePolicy, ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
     257}}}
     258
     259==== Subversion Configuration ====
     260
     261The same access file is typically applied to the corresponding Subversion repository using an Apache directive like this:
     262{{{#!apache
     263<Location /repos>
     264  DAV svn
     265  SVNParentPath /usr/local/svn
     266
     267  # our access control policy
     268  AuthzSVNAccessFile /path/to/svnaccessfile
     269</Location>
     270}}}
     271
     272For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess].
     273
     274=== ReadonlyWikiPolicy
     275
     276Since 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:
     277{{{
     278[trac]
     279permission_policies = ReadonlyWikiPolicy,
     280 DefaultPermissionPolicy,
     281 LegacyAttachmentPolicy
     282}}}
     283
     284When 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.
     285
     286**!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.
     287
     288The `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.
     289
     290When 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.
     291{{{
     292[trac]
     293permission_policies = AuthzPolicy,
     294 ReadonlyWikiPolicy,
     295 DefaultPermissionPolicy,
     296 LegacyAttachmentPolicy
     297}}}
     298
     299The placement of [#AuthzSourcePolicy] relative to `ReadonlyWikiPolicy` does not matter since they don't perform checks on the same realms.
     300
     301For 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.
     302
     303== Debugging permissions
     304In trac.ini set:
     305{{{#!ini
     306[logging]
     307log_file = trac.log
     308log_level = DEBUG
     309log_type = file
     310}}}
     311
     312Display the trac.log to understand what checks are being performed:
     313{{{#!sh
     314tail -n 0 -f log/trac.log | egrep '\[perm\]|\[authz_policy\]'
     315}}}
     316
     317See the sourced documentation of the plugin for more info.
     318
     319----
     320See also: TracPermissions,
     321[http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin TracHacks:FineGrainedPageAuthzEditorPlugin] for a simple editor plugin.
  • wiki/pages/TracGuide

    r39712 r39721  
     1= The Trac User and Administration Guide =
     2[[TracGuideToc]]
     3{{{#!span style="font-size:90%"
     4//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.//
     5}}}
     6
     7== Introduction
     8
     9Trac 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.
     10
     11It provides an interface to Subversion (and other version control systems), an integrated Wiki and convenient reporting facilities.
     12
     13Trac 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.
     14== User Guide
     15   * Using the Wiki subsystem
     16     * TracWiki — How to use the built-in Wiki.
     17     * WikiFormatting — Reference to the wiki syntax used throughout.
     18   * Using the Version Control subsystem
     19     * TracBrowser — Browsing source code with Trac.
     20     * TracChangeset — Viewing changes to source code.
     21     * TracRevisionLog — Viewing change history.
     22   * Using the Ticket subsystem
     23     * TracTickets — Using the issue tracker.
     24     * TracRoadmap — The roadmap helps tracking project progress.
     25     * TracReports — Writing and using reports.
     26     * TracQuery — Executing custom ticket queries.
     27     * TracBatchModify - Modifying a batch of tickets in one request.
     28   * Other modules and general topics
     29     * TracSearch — Full text search in all content.
     30     * TracTimeline — The timeline provides a historic perspective on a project.
     31     * TracRss — RSS content syndication in Trac.
     32     * TracAccessibility — Accessibility keys support
     33
     34
     35== Administrator Guide
     36   * Installation and upgrade
     37     * TracInstall — How to install and run Trac.
     38     * TracUpgrade — How to upgrade existing installations.
     39     * TracImport — Importing tickets from other bug databases.
     40     * TracPlugins — Installing and managing Trac extensions.
     41   * Configuration and customization
     42     * TracIni — Trac configuration file reference.
     43     * TracPermissions — Access control and permissions.
     44     * TracNavigation — Customize main navigation menus.
     45     * TracInterfaceCustomization — Customizing the Trac interface.
     46     * TracLogging — The Trac logging facility.
     47   * Administering the Version Control subsystem
     48     * TracRepositoryAdmin — Management of Source Code Repositories.
     49   * Administering the Ticket subsystem
     50     * TracTicketsCustomFields — Expanding tickets with customized fields.
     51     * TracNotification — Email notification.
     52     * TracWorkflow — Configurable Ticket Workflow.
     53   * Reference
     54     * TracEnvironment — All you need to know about Trac environments
     55     * TracAdmin — Administering a Trac project via the command-line.
     56
     57== Support and Other Sources of Information ==
     58
     59 * [trac:TracFaq Trac FAQ] — A collection of Frequently Asked Questions (on the project website).
     60 * [trac:TracDev] and [trac:TracDev/ApiDocs API docs] — Trac Developer documentation
     61 * TracSupport — How to get more information
     62
     63If 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

    r39712 r39721  
     1= Importing ticket data =
     2[[PageOutline]]
     3
     4To 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.
     5
     6== !TicketImportPlugin ==
     7
     8[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'''.
     9
     10== !ExportImportXlsPlugin ==
     11
     12[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.
     13
     14== Bugzilla ==
     15
     16[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.
     17
     18{{{
     19$ bugzilla2trac.py
     20bugzilla2trac - Imports a bug database from Bugzilla into Trac.
     21
     22Usage: bugzilla2trac.py [options]
     23
     24Available Options:
     25  --db <MySQL dbname>              - Bugzilla's database
     26  --tracenv /path/to/trac/env      - full path to Trac db environment
     27  -h | --host <MySQL hostname>     - Bugzilla's DNS host name
     28  -u | --user <MySQL username>     - effective Bugzilla's database user
     29  -p | --passwd <MySQL password>   - Bugzilla's user password
     30  -c | --clean                     - remove current Trac tickets before importing
     31  --help | help                    - this help info
     32
     33Additional configuration options can be defined directly in the script.
     34}}}
     35
     36Currently, the following data is imported from Bugzilla:
     37  * bugs
     38  * bug activity (field changes)
     39  * bug attachments
     40  * user names and passwords (put into a htpasswd file)
     41
     42The script provides a number of features to ease the conversion, such as:
     43  * PRODUCT_KEYWORDS: Trac has no concept of products, so the script provides the ability to attach a ticket keyword instead.
     44  * IGNORE_COMMENTS: Don't import Bugzilla comments that match a certain regexp.
     45  * 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.
     46
     47For more details on the available options, see the configuration section at the top of the script.
     48
     49=== Known Issues ===
     50{{{
     51#!comment
     52                   Don't merge this section in the default page
     53}}}
     54[[TicketQuery(keywords=~bugzilla,status=!closed)]]
     55
     56The 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.
     57
     58== Jira ==
     59
     60[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:
     61  - Parses the Jira backup XML file.
     62  - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin].
     63  - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords.
     64
     65== Mantis ==
     66
     67[http://trac-hacks.org/wiki/MantisImportScript MantisImportScript]: script to import the following data from Mantis into Trac:
     68  * bugs
     69  * bug comments
     70  * bug activity (field changes)
     71  * attachments (as long as the files live in the mantis db, not on the filesystem) .
     72
     73== !PlanetForge ==
     74
     75[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.
     76
     77== Scarab ==
     78
     79[http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript]: script that migrates Scarab issues to Trac tickets. Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
     80
     81== Sourceforge ==
     82
     83[http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript]: importer of !SourceForge's new backup file (originated from #Trac3521).
     84Also, 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.
     85
     86== Other ==
     87
     88Since 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.
     89
     90=== Comma delimited file - CSV ===
     91See [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.
     92Comments 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.
     93
     94----
     95See also:
     96 * to import/export wiki pages: TracAdmin,
     97 * to export tickets: TracTickets, TracQuery
  • wiki/pages/TracIni

    r39712 r39721  
     1= The Trac Configuration File
     2
     3[[TracGuideToc]]
     4[[PageOutline]]
     5
     6Trac 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.
     7
     8Trac 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.
     9
     10== Global Configuration
     11
     12Configuration 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:
     13{{{#!ini
     14[inherit]
     15file = /path/to/global/trac.ini
     16}}}
     17Multiple files can be specified using a comma-separated list.
     18
     19Note 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.
     20
     21There 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.
     22
     23Note 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.
     24
     25== Reference for settings
     26
     27This is a brief reference of available configuration options, and their default settings.
     28
     29Documentation 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.
     30{{{ #!comment
     31Please 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.
     32}}}
     33[[TracIni]]
     34
     35----
     36See also: TracGuide, TracAdmin, TracEnvironment
  • wiki/pages/TracInstall

    r39712 r39721  
     1= Trac Installation Guide for 1.1
     2[[TracGuideToc]]
     3
     4Trac 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.
     5
     6Trac 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.
     7
     8If 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].
     9
     10What 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.
     11
     12[[PageOutline(2-3,Installation Steps,inline)]]
     13
     14== Dependencies
     15=== Mandatory Dependencies
     16To install Trac, the following software packages must be installed:
     17
     18 * [http://www.python.org/ Python], version >= 2.6 and < 3.0
     19   (note that we dropped the support for Python 2.5 in this release)
     20 * [http://pypi.python.org/pypi/setuptools setuptools], version >= 0.6
     21 * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6
     22
     23You also need a database system and the corresponding python bindings. The database can be either SQLite, PostgreSQL or MySQL.
     24
     25==== For the SQLite database #ForSQLite
     26
     27As 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).
     28
     29Optionally, 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.
     30
     31==== For the PostgreSQL database #ForPostgreSQL
     32
     33You need to install the database and its Python bindings:
     34 * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later
     35 * [http://pypi.python.org/pypi/psycopg2 psycopg2], version 2.0 or later
     36
     37See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
     38
     39==== For the MySQL database #ForMySQL
     40
     41Trac works well with MySQL, provided you follow the guidelines:
     42
     43 * [http://mysql.com/ MySQL], version 5.0 or later
     44 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later
     45
     46Given the caveats and known issues surrounding MySQL, read carefully the [trac:MySqlDb] page before creating the database.
     47
     48=== Optional Dependencies
     49
     50==== Subversion
     51
     52[http://subversion.apache.org/ Subversion], 1.6.x or later and the '''''corresponding''''' Python bindings.
     53
     54There 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.)
     55
     56For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page.
     57
     58{{{#!div style="border: 1pt dotted; margin: 1em"
     59**Note:**
     60* Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], nor does it work yet with the newer `ctype`-style bindings.
     61* If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
     62}}}
     63
     64==== Git
     65
     66[http://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page.
     67
     68==== Other Version Control Systems
     69
     70Support for other version control systems is provided via third-party plugins. See [trac:PluginList#VersionControlSystems] and [trac:VersionControlSystem].
     71
     72==== Web Server
     73A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below.
     74
     75Alternatively you can configure Trac to run in any of the following environments:
     76 * [http://httpd.apache.org/ Apache] with
     77   - [https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi], see [wiki:TracModWSGI] and
     78     [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac].
     79   - [http://modpython.org/ mod_python 3.5.0], see TracModPython
     80 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
     81 * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
     82   server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
     83 * Microsoft IIS with FastCGI and a FastCGI-to-WSGI gateway (see [trac:CookBook/Installation/TracOnWindowsIisWfastcgi IIS with FastCGI])
     84 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script
     85   is highly discouraged''', better use one of the previous options.
     86   
     87
     88==== Other Python Packages
     89
     90 * [http://babel.edgewall.org Babel], version 0.9.6 or >= 1.3,
     91   needed for localization support
     92 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
     93   for WikiRestructuredText.
     94 * [http://pygments.org Pygments] for
     95   [TracSyntaxColoring syntax highlighting].
     96 * [http://pytz.sf.net pytz] to get a complete list of time zones,
     97   otherwise Trac will fall back on a shorter list from
     98   an internal time zone implementation.
     99
     100{{{#!div style="border: 1pt dotted; margin: 1em"
     101**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].
     102}}}
     103
     104Please 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''.
     105
     106== Installing Trac
     107
     108The [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.
     109
     110=== Using `easy_install`
     111Trac can be installed from PyPI or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].
     112
     113A few examples:
     114
     115 - Install Trac 1.0:
     116   {{{#!sh
     117   easy_install Trac==1.0
     118   }}}
     119 - Install latest development version:
     120   {{{#!sh
     121   easy_install Trac==dev
     122   }}}
     123   Note that in this case you won't have the possibility to run a localized version of Trac;
     124   either use a released version or install from source
     125
     126More information can be found on the [trac:setuptools] page.
     127
     128{{{#!div style="border: 1pt dotted; margin: 1em"
     129**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].
     130}}}
     131
     132=== Using `pip`
     133'pip' is an easy_install replacement that is very useful to quickly install python packages.
     134To get a Trac installation up and running in less than 5 minutes:
     135
     136Assuming you want to have your entire pip installation in `/opt/user/trac`
     137
     138 -
     139 {{{#!sh
     140pip install trac psycopg2
     141}}}
     142or
     143 -
     144 {{{#!sh
     145pip install trac mysql-python
     146}}}
     147
     148Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings.
     149
     150pip 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`.
     151
     152All 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)
     153
     154Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip.
     155
     156=== From source
     157Using 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.
     158
     159{{{#!sh
     160$ python ./setup.py install
     161}}}
     162
     163''You will need root permissions or equivalent for this step.''
     164
     165This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory
     166of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`.
     167
     168If 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):
     169{{{#!sh
     170$ python ./setup.py install
     171}}}
     172Alternatively, 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`).
     173
     174=== Using installer
     175
     176On 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.
     177
     178=== Using package manager
     179
     180Trac 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.
     181
     182=== Advanced `easy_install` Options
     183
     184To install Trac to a custom location, or find out about other advanced installation options, run:
     185{{{#!sh
     186easy_install --help
     187}}}
     188
     189Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information.
     190
     191Specifically, you might be interested in:
     192{{{#!sh
     193easy_install --prefix=/path/to/installdir
     194}}}
     195or, if installing Trac on a Mac OS X system:
     196{{{#!sh
     197easy_install --prefix=/usr/local --install-dir=/Library/Python/2.6/site-packages
     198}}}
     199
     200{{{#!div style="border: 1pt dotted; margin: 1em"
     201**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.
     202
     203The `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.
     204}}}
     205
     206== Creating a Project Environment
     207
     208A [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.
     209
     210A new environment is created using [TracAdmin trac-admin]:
     211{{{#!sh
     212$ trac-admin /path/to/myproject initenv
     213}}}
     214
     215[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.
     216
     217Using 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.
     218
     219Also note that the values you specify here can be changed later using TracAdmin or directly editing the [TracIni conf/trac.ini] configuration file.
     220
     221{{{#!div style="border: 1pt dotted; margin: 1em"
     222**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.
     223}}}
     224
     225Finally, 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:
     226{{{#!sh
     227$ chown -R apache:apache /path/to/myproject
     228}}}
     229
     230The 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).
     231
     232{{{#!div class=important
     233'''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there.
     234}}}
     235
     236== Deploying Trac
     237
     238=== Running the Standalone Server
     239
     240After having created a Trac environment, you can easily try the web interface by running the standalone server [TracStandalone tracd]:
     241{{{#!sh
     242$ tracd --port 8000 /path/to/myproject
     243}}}
     244
     245Then, 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:
     246{{{#!sh
     247$ tracd -s --port 8000 /path/to/myproject
     248}}}
     249
     250{{{#!div style="border: 1pt dotted; margin: 1em"
     251**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.
     252
     253To 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`.
     254{{{#!sh
     255export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1
     256}}}
     257
     258Alternatively, the variable can be set in the shell before executing `tracd`:
     259{{{#!sh
     260$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
     261}}}
     262}}}
     263
     264=== Running Trac on a Web Server
     265
     266Trac provides various options for connecting to a "real" web server:
     267 - [TracFastCgi FastCGI]
     268 - [wiki:TracModWSGI mod_wsgi]
     269 - [TracModPython mod_python]
     270 - //[TracCgi CGI] (should not be used, as the performance is far from optimal)//
     271
     272Trac 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.
     273
     274==== Generating the Trac cgi-bin directory #cgi-bin
     275
     276In 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].
     277
     278There 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:
     279{{{#!sh
     280mkdir -p /usr/share/trac/projects/my-project
     281trac-admin /usr/share/trac/projects/my-project initenv
     282trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
     283mv /tmp/deploy/* /usr/share/trac
     284}}}
     285Don't forget to check that the web server has the execution right on scripts in the `/usr/share/trac/cgi-bin` directory.
     286
     287==== Mapping Static Resources
     288
     289Out 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).
     290
     291Web 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.
     292
     293There 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.
     294
     295Note 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:
     296[[TracAdminHelp(deploy)]]
     297
     298The target `<directory>` will then contain an `htdocs` directory with:
     299 - `site/` - a copy of the environment's directory `htdocs/`
     300 - `common/` - the static resources of Trac itself
     301 - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
     302
     303===== Example: Apache and `ScriptAlias` #ScriptAlias-example
     304
     305Assuming the deployment has been done this way:
     306{{{#!sh
     307$ trac-admin /var/trac/env deploy /path/to/shared/trac
     308}}}
     309
     310Add 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:
     311{{{#!apache
     312Alias /trac/chrome/common /path/to/trac/htdocs/common
     313Alias /trac/chrome/site /path/to/trac/htdocs/site
     314
     315<Directory "/path/to/www/trac/htdocs">
     316  Order allow,deny
     317  Allow from all
     318</Directory>
     319}}}
     320
     321If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
     322{{{#!apache
     323<Location "/trac/chrome/common/">
     324  SetHandler None
     325</Location>
     326}}}
     327
     328Note 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.
     329
     330Similarly, 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):
     331{{{#!apache
     332Alias /trac/chrome/site /path/to/projectenv/htdocs
     333
     334<Directory "/path/to/projectenv/htdocs">
     335  Order allow,deny
     336  Allow from all
     337</Directory>
     338}}}
     339
     340Alternatively 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:
     341{{{#!ini
     342[trac]
     343htdocs_location = http://static.example.org/trac-common/
     344}}}
     345Note 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]).
     346
     347Of 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:
     348{{{#!sh
     349$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
     350}}}
     351
     352==== Setting up the Plugin Cache
     353
     354Some 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.
     355
     356== Configuring Authentication
     357
     358Trac 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.
     359
     360The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.
     361
     362Please refer to one of the following sections:
     363 * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`.
     364 * [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`.
     365 * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
     366
     367[trac:TracAuthenticationIntroduction] also contains some useful information for beginners.
     368
     369== Granting admin rights to the admin user
     370Grant admin rights to user admin:
     371{{{#!sh
     372$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
     373}}}
     374
     375This user will have an //Admin// navigation item that directs to pages for administering your Trac project.
     376
     377== Configuring Trac
     378
     379TracRepositoryAdmin provides information on configuring version control repositories for your project.
     380
     381== Using Trac
     382
     383Once 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.
     384
     385Keep 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.
     386
     387'' Enjoy! ''
     388
     389[trac:TracTeam The Trac Team]
     390
     391----
     392See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade, TracPermissions
  • wiki/pages/TracInterfaceCustomization

    r39712 r39721  
     1= Customizing the Trac Interface
     2[[TracGuideToc]]
     3[[PageOutline]]
     4
     5== Introduction
     6This 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.
     7
     8== Project Logo and Icon
     9The 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].
     10
     11The logo or icon image should be put in a folder named "htdocs" in your project's environment folder. ''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder''.
     12
     13 '''Note''': you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.
     14
     15Now configure the appropriate section of your [wiki:TracIni trac.ini]:
     16
     17=== Logo
     18Change 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'.
     19
     20{{{#!ini
     21[header_logo]
     22src = site/my_logo.gif
     23alt = My Project
     24width = 300
     25height = 100
     26}}}
     27
     28=== Icon
     29Icons 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:
     30
     31{{{#!ini
     32[project]
     33icon = site/my_icon.ico
     34}}}
     35
     36== Custom Navigation Entries
     37The 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.
     38
     39In 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:
     40{{{#!ini
     41[mainnav]
     42wiki.label = Home
     43tickets.href = /report/24
     44
     45[metanav]
     46help = disabled
     47}}}
     48
     49See also TracNavigation for a more detailed explanation of the mainnav and metanav terms.
     50
     51== Site Appearance == #SiteAppearance
     52
     53Trac 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`:
     54
     55{{{#!xml
     56<html xmlns="http://www.w3.org/1999/xhtml"
     57      xmlns:py="http://genshi.edgewall.org/"
     58      py:strip="">
     59
     60  <!--! Add site-specific style sheet -->
     61  <head py:match="head" py:attrs="select('@*')">
     62    ${select('*|comment()|text()')}
     63    <link rel="stylesheet" href="${href.chrome('site/style.css')}" />
     64  </head>
     65
     66  <body py:match="body" py:attrs="select('@*')">
     67    <!--! Add site-specific header -->
     68    <div id="siteheader">
     69      <!--! Place your header content here... -->
     70    </div>
     71
     72    ${select('*|text()')}
     73
     74    <!--! Add site-specific footer -->
     75    <div id="sitefooter">
     76      <!--! Place your footer content here... -->
     77    </div>
     78  </body>
     79</html>
     80}}}
     81
     82Notice 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.
     83
     84`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.
     85See [http://groups.google.com/group/trac-users/browse_thread/thread/70487fb2c406c937/ this thread] for a detailed explanation of the above example `site.html`.
     86A `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.
     87
     88Example snippet of adding introduction text to the new ticket form (but not shown during preview):
     89
     90{{{#!xml
     91<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')">
     92  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
     93    <p>Please make sure to search for existing tickets before reporting a new one!</p>
     94  </py:if>
     95  ${select('*')}
     96</form>
     97}}}
     98
     99This 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.
     100
     101More examples snippets for `site.html` can be found at [trac:wiki:CookBook/SiteHtml CookBook/SiteHtml].
     102
     103Example snippets for `style.css` can be found at [trac:wiki:CookBook/SiteStyleCss CookBook/SiteStyleCss].
     104
     105Note 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.
     106
     107== Project List == #ProjectList
     108
     109You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects. 
     110
     111The 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:
     112
     113{{{#!text/html
     114<!DOCTYPE html
     115    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     116    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
     117<html xmlns="http://www.w3.org/1999/xhtml"
     118      xmlns:py="http://genshi.edgewall.org/"
     119      xmlns:xi="http://www.w3.org/2001/XInclude">
     120  <head>
     121    <title>Available Projects</title>
     122  </head>
     123  <body>
     124    <h1>Available Projects</h1>
     125    <ul>
     126      <li py:for="project in projects" py:choose="">
     127        <a py:when="project.href" href="$project.href"
     128           title="$project.description">$project.name</a>
     129        <py:otherwise>
     130          <small>$project.name: <em>Error</em> <br /> ($project.description)</small>
     131        </py:otherwise>
     132      </li>
     133    </ul>
     134  </body>
     135</html>
     136}}}
     137
     138Once 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):
     139
     140For [wiki:TracModWSGI mod_wsgi]:
     141{{{#!python
     142os.environ['TRAC_ENV_INDEX_TEMPLATE'] = '/path/to/template.html'
     143}}}
     144
     145For [wiki:TracFastCgi FastCGI]:
     146{{{#!apache
     147FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \
     148              -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     149}}}
     150
     151For [wiki:TracModPython mod_python]:
     152{{{#!apache
     153PythonOption TracEnvParentDir /parent/dir/of/projects
     154PythonOption TracEnvIndexTemplate /path/to/template
     155}}}
     156
     157For [wiki:TracCgi CGI]:
     158{{{#!apache
     159SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template
     160}}}
     161
     162For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd:
     163 - Unix
     164   {{{#!sh
     165$ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     166   }}}
     167 - Windows
     168   {{{#!sh
     169$ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     170   }}}
     171
     172== Project Templates
     173
     174The 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.
     175
     176With 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.
     177
     178However, do not edit templates or site resources inside the Trac egg. Reinstalling Trac overwrites your modifications. Instead use one of these alternatives:
     179 * For a modification to one project only, copy the template to project `templates` directory.
     180 * 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.
     181
     182Trac resolves requests for a template by first looking inside the project, then in any inherited templates location, and finally inside the Trac egg.
     183
     184Trac caches templates in memory by default to improve performance. To apply a template you need to restart the web server.
     185
     186----
     187See also TracGuide, TracIni
  • wiki/pages/TracLanguages

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

    r39712 r39721  
     1= Trac Links =
     2[[TracGuideToc]]
     3
     4TracLinks 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.
     5
     6TracLinks are generally of the form '''type:id''' (where ''id'' represents the
     7number, name or path of the item) though some frequently used kinds of items
     8also have short-hand notations.
     9
     10== Where to use TracLinks ==
     11You can use TracLinks in:
     12
     13 * Source code (Subversion) commit messages
     14 * Wiki pages
     15 * Full descriptions for tickets, reports and milestones
     16
     17and any other text fields explicitly marked as supporting WikiFormatting.
     18
     19== Overview ==
     20
     21||= Wiki Markup =||= Display =||
     22{{{#!td
     23 Wiki pages :: `CamelCase` or `wiki:CamelCase`
     24 Parent page :: `[..]`
     25 Tickets :: `#1` or `ticket:1`
     26 Ticket comments :: `comment:1:ticket:2`
     27 Reports :: `{1}` or `report:1`
     28 Milestones :: `milestone:1.0`
     29 Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
     30 Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`, `[1/repository]`
     31 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
     32 Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
     33          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
     34          or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
     35 Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
     36}}}
     37{{{#!td
     38 Wiki pages :: CamelCase or wiki:CamelCase
     39 Parent page :: [..]
     40 Tickets :: #1 or ticket:1
     41 Ticket comments :: comment:1:ticket:2
     42 Reports :: {1} or report:1
     43 Milestones :: milestone:1.0
     44 Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
     45 Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository]
     46 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
     47 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
     48          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
     49          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
     50 Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
     51}}}
     52
     53'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
     54pages whose names do not follow WikiPageNames rules, i.e., single words,
     55non-alphabetic characters, etc. See WikiPageNames for more about features specific
     56to links to Wiki page names.
     57
     58
     59{{{#!table class=""
     60|||| Trac links using the full (non-shorthand) notation can also be given a custom link title like this: ||
     61{{{#!td
     62{{{
     63[ticket:1 This is a link to ticket number one] or
     64[[ticket:1|This is another link to ticket number one]].
     65}}}
     66}}}
     67{{{#!td
     68[ticket:1 This is a link to ticket number one] or
     69[[ticket:1|This is another link to ticket number one]].
     70}}}
     71|--------------------------------------------------------------------------------------
     72|||| If the title is omitted, only the id (the part after the colon) is displayed:  ||
     73{{{#!td
     74{{{
     75[ticket:1] or [[ticket:2]]
     76}}}
     77}}}
     78{{{#!td
     79[ticket:1] or [[ticket:2]]
     80}}}
     81|--------------------------------------------------------------------------------------
     82|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
     83{{{#!td
     84{{{
     85[SandBox the sandbox] or
     86[[SandBox|the sandbox]]
     87}}}
     88}}}
     89{{{#!td
     90[SandBox the sandbox] or
     91[[SandBox|the sandbox]]
     92}}}
     93|--------------------------------------------------------------------------------------
     94|||| The short form ''realm:target'' can also be wrapped within a <...> pair, [[br]] which allow for arbitrary characters (i.e. anything but >)  ||
     95{{{#!td
     96{{{
     97<wiki:Strange(page@!)>
     98}}}
     99}}}
     100{{{#!td
     101<wiki:Strange(page@!)>
     102}}}
     103}}}
     104
     105TracLinks 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.
     106
     107
     108== Advanced use of TracLinks ==
     109
     110=== Relative links ===
     111
     112To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
     113{{{
     114 WikiPage/SubWikiPage or ./SubWikiPage
     115}}}
     116
     117To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
     118{{{
     119  [..] or [[..]]
     120}}}
     121  [..] or [[..]]
     122
     123To link from a [trac:SubWiki SubWiki] page to a [=#sibling sibling] page, use a '../':
     124{{{
     125  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
     126}}}
     127  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
     128
     129But in practice you often won't need to add the `../` prefix to link to a sibling page.
     130For resolving the location of a wiki link, it's the target page closest in the hierarchy
     131to the page where the link is written which will be selected. So for example, within
     132a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
     133This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
     134
     135In order to link explicitly to a [=#toplevel toplevel] Wiki page,
     136use 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.
     137
     138=== Link anchors ===
     139
     140To create a link to a specific anchor in a page, use '#':
     141{{{
     142 [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
     143}}}
     144  [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
     145
     146Hint: 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.
     147
     148To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':
     149{{{
     150 [#/Milestone first occurrence of Milestone] or
     151 [#?Milestone last occurrence of Milestone]
     152}}}
     153 [#/Milestone first occurrence of Milestone] or
     154 [#?Milestone last occurrence of Milestone]
     155This 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':
     156{{{
     157 [#/Milestone/i first occurrence of Milestone or milestone] or
     158 [#?Milestone/i last occurrence of Milestone or milestone]
     159}}}
     160 [#/Milestone/i first occurrence of Milestone or milestone] or
     161 [#?Milestone/i last occurrence of Milestone or milestone]
     162
     163''(since Trac 1.0)''
     164
     165Such anchors can be very useful for linking to specific lines in a file in the source browser:
     166{{{
     167 [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
     168 [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
     169}}}
     170 [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
     171 [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
     172(Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.)
     173
     174Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead:
     175{{{
     176 [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
     177 [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
     178}}}
     179 [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
     180 [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
     181
     182=== InterWiki links ===
     183
     184Other 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.
     185
     186=== InterTrac links ===
     187
     188This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
     189
     190Any 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.
     191
     192A 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].
     193See InterTrac for the complete details.
     194
     195=== Server-relative links ===
     196
     197It is often useful to be able to link to objects in your project that
     198have no built-in Trac linking mechanism, such as static resources, `newticket`,
     199a shared `/register` page on the server, etc.
     200
     201To link to resources inside the project, use either an absolute path from the project root,
     202or a relative link from the URL of the current page (''Changed in 0.11''):
     203
     204{{{
     205[/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
     206[/ home] or [[/|home]]
     207}}}
     208
     209Display: [/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
     210[/ home] or [[/|home]]
     211
     212To link to another location on the server (possibly outside the project but on the same host), use the `//` prefix (''Changed in 0.11''):
     213
     214{{{
     215[//register Register Here] or [[//register|Register Here]]
     216}}}
     217
     218Display: [//register Register Here] or [[//register|Register Here]]
     219
     220=== Quoting space in TracLinks ===
     221
     222Immediately after a TracLinks prefix, targets containing space characters should
     223be enclosed in a pair of quotes or double quotes.
     224Examples:
     225 * !wiki:"The whitespace convention"
     226 * !attachment:'the file.txt' or
     227 * !attachment:"the file.txt"
     228 * !attachment:"the file.txt:ticket:123"
     229
     230Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
     231 * ![[The whitespace convention]]
     232 * ![[attachment:the file.txt]]
     233
     234=== Escaping Links ===
     235
     236To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
     237{{{
     238 !NoLinkHere.
     239 ![42] is not a link either.
     240}}}
     241
     242Display:
     243 !NoLinkHere.
     244 ![42] is not a link either.
     245
     246
     247=== Parameterized Trac links ===
     248
     249Many 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.
     250
     251Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
     252 - `wiki:WikiStart?format=txt`
     253 - `ticket:1?version=1`
     254 - `[/newticket?component=module1 create a ticket for module1]`
     255 - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`
     256
     257
     258== TracLinks Reference ==
     259The following sections describe the individual link types in detail, as well as notes on advanced usage of links.
     260
     261=== attachment: links ===
     262
     263The link syntax for attachments is as follows:
     264 * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
     265 * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
     266 * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753
     267
     268Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.
     269
     270If 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:`.
     271
     272This 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.
     273
     274See also [#export:links].
     275
     276=== comment: links ===
     277
     278When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
     279It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
     280 - `comment:3:ticket:123`
     281 - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
     282It is also possible to link to the ticket's description using one of the following syntax:
     283 - `comment:description` (within the ticket)
     284 - `comment:description:ticket:123`
     285 - `ticket:123#comment:description`
     286
     287=== htdocs: links ===
     288
     289Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
     290
     291=== query: links ===
     292
     293See TracQuery#UsingTracLinks and [#ticket:links].
     294
     295=== search: links ===
     296
     297See TracSearch#SearchLinks
     298
     299=== ticket: links ===
     300 ''alias:'' `bug:`
     301
     302Besides 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.
     303
     304Example:
     305 - `ticket:5000-6000`
     306 - `ticket:1,150`
     307
     308=== timeline: links ===
     309
     310Links 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.
     311
     312Examples:
     313 - `timeline:2008-01-29`
     314 - `timeline:2008-01-29T15:48`
     315 - `timeline:2008-01-29T15:48Z`
     316 - `timeline:2008-01-29T16:48+01`
     317 - `timeline:2008-01-29T16:48+0100`
     318 - `timeline:2008-01-29T16:48+01:00`
     319
     320=== wiki: links ===
     321
     322See 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.
     323
     324=== Version Control related links ===
     325
     326It 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).
     327
     328For 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'`.
     329
     330==== source: links ====
     331 ''aliases:'' `browser:`, `repos:`
     332
     333The default behavior for a `source:/some/path link` is to open the browser in that directory directory
     334if the path points to a directory or to show the latest content of the file.
     335
     336It's also possible to link directly to a specific revision of a file like this:
     337 - `source:/some/file@123` - link to the file's revision 123
     338 - `source:/some/file@head` - link explicitly to the latest revision of the file
     339
     340If the revision is specified, one can even link to a specific line number:
     341 - `source:/some/file@123#L10`
     342 - `source:/tag/0.10@head#L10`
     343
     344Finally, one can also highlight an arbitrary set of lines:
     345 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
     346 - 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
     347
     348Note 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)''
     349
     350==== export: links ====
     351
     352To 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:
     353 * `export:/some/file` - get the HEAD revision of the specified file
     354 * `export:123:/some/file` - get revision 123 of the specified file
     355 * `export:/some/file@123` - get revision 123 of the specified file
     356
     357This 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.
     358
     359If 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`).
     360
     361==== log: links ====
     362
     363The `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.
     364 - `log:/` - the latest revisions starting at the root of the repository
     365 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
     366 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
     367 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
     368 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
     369
     370There are short forms for revision ranges as well:
     371 - `[20788,20791:20795]`
     372 - `[20788,20791:20795/trunk/tools]`
     373 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
     374
     375Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`.
     376
     377In 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]`.
     378
     379----
     380See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki
     381 
  • wiki/pages/gr/Plugins-Channel-Lists

    r39712 r39721  
     1[[TranslatedPages]]
     2'''10.6 Channel Lists''' [=#point10.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     3
     4Channel list's are provided by other users.[[br]]
     5They contain complete satellite listings aswell as sorted favourites to make it[[br]]
     6easier for you to use on your receiver.
     7[[br]]
     8A list of the current channel lists provided are:
     9
     10Satellite:
     11 * Hotbird 13.0
     12 * Astra 19.2
     13 * Astra 28.2
     14
     15Cable:
     16 * Cable germany
     17 * Cable BW
     18 * Cable Unitymedia
     19 * Primacom Cable
     20
     21If you wish to provide your own satellite configurations please post them in the [http://aaf-digital.info AAF forum].
     22----
     23||= '''Default Kabel''' =||= '''Default Sat''' =||= '''Matze70 Neues Design''' =||= '''Matze70 Sat''' =||
     24||= [[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)]] =||
     25[[br]]
     26||= '''Bulldog 3xsat''' =||= '''Sofa Kabel-BW''' =||= '''Uljanow Sat''' =||= '''Unitymedia Cable''' =||
     27||= [[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)]] =||
     28[[br]]
     29||= '''Primacom Kabel''' =||= '''Settings Eutelsat 36.0''' =||= '''Kabel Deutschland UH-Kreis''' =||= '''Sat Astra ORF''' =||
     30||= [[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)]] =||
     31[[br]]
     32||= '''Kabelplus ORF''' =||= '''Astra 19.2 KabelD''' =||= '''Bulldog 2xsat''' =||= '''Bulldog 1xsat''' =||
     33||= [[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)]] =||
     34[[br]]
     35||= '''SAT/Cable 19.2 13.0 KabelD''' =||
     36||= [[Image(source:/ipk/source/settings_andy_2xSat_KabelD_1_0/preview/prev.png)]] =||
     37[#point10.6 Top of Page]
  • wiki/pages/it/Plugins-Screensavers

    r39712 r39721  
    1717||= [[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)]]
    1818[[br]]
    19 ||= '''HDR Pictures''' =||= '''Hotgirls 1''' =||= '''Hotgirls 2''' =||= '''Inspirational''' =||= '''
     19||= '''HDR Pictures''' =||= '''Hotgirls 1''' =||= '''Hotgirls 2''' =||= '''Inspirational''' =||= '''Love''' =||= '''Movies''' =||
     20||= [[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)]]
     21[[br]]
     22||= '''Nature Landscape''' =||= '''Others''' =||= '''Photography''' =||= '''Planes''' =||= '''Radio''' =||= '''Sports''' =||
     23||= [[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)]]
     24[[br]]
     25||= '''Travel World''' =||
     26||= [[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)]] =||
     27[[br]]
     28([#point10.1 Top of Pge])
  • wiki/pages/it/Plugins-Skins

    r39712 r39721  
     1[[TranslatedPages]]
     2----
     3'''10.14 Skins''' [=#point10.14] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4----
     5
     6Installing one of the follwing skins will change the look of the titan interface you may select and install skins from the online extentions.[[br]]
     7
     8||= '''0Acht5Zehn''' =||= '''0Acht5Zehnblack''' =||= '''0Acht5Zehnwhite''' =||= '''Cool''' =||= '''CoolMiniTV''' =||= '''Default''' =||
     9||= [[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)]]
     10=||
     11[[br]]
     12||= '''Default no MiniTV''' =||= '''Megastyle-Blue''' =||= '''Megastyle-Blue-MiniTV''' =||= '''MegaStyle-Grey''' =||= '''MegaStyle-Grey-MiniTV''' =||= '''MetrixHD''' =||
     13||= [[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)]]
     14=||
     15[[br]]
     16||= '''NoGfx''' =||= '''NoGfx Grey''' =||= '''SmartTV''' =||= '''tobayer01''' =||= '''ufs912''' =||
     17||= [[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)]]
     18=||
     19
     20([#point10.14 Top of Page])
  • wiki/pages/it/Plugins-Tools

    r39712 r39721  
     1[[TranslatedPages]]
     2----
     3'''10.16 Tools''' [=#point10.16] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4----
     5
     6
     7{{{#!th rowspan=0 align=left style="border: none"
     8[[Image(source:/ipk/source.sh4/tools_autotimer/preview/prev.png)]] 
     9}}}
     10|----------------
     11{{{#!td style="border: none"
     12 '''Auto timer'''
     13
     14 Set repeat timers for timer recordings to automatically record[[br]]
     15 the same program in future (i.e. serials) or automatic channel switch
     16
     17}}}
     18([#point10.16 Top of Page])
     19[[BR]]
     20
     21{{{#!th rowspan=0 align=left style="border: none"
     22[[Image(source:/ipk/source.sh4/tools_callmonitor/preview/prev.png)]]
     23}}}
     24|----------------
     25{{{#!td style="border: none"
     26 '''Callmonitor'''
     27
     28 Incoming / outgoing phone calls are displayed on the screen.
     29
     30}}}
     31([#point10.16 Top of Page])
     32[[BR]]
     33
     34{{{#!th rowspan=0 align=left style="border: none"
     35[[Image(source:/ipk/source.sh4/tools_filemanager/preview/prev.png)]]
     36}}}
     37|----------------
     38{{{#!td style="border: none"
     39 '''Filemanager'''
     40
     41 Access your files on the receiver and external drives[[br]]
     42 move/copy/delete them.
     43
     44}}}
     45([#point10.16 Top of Page])
     46[[BR]]
     47
     48{{{#!th rowspan=0 align=left style="border: none"
     49[[Image(source:/ipk/source.sh4/tools_IP-Kamera/preview/prev.png)]]
     50}}}
     51|----------------
     52{{{#!td style="border: none"
     53 '''IP Camera'''
     54
     55 An in-network IP camera can be displayed on the screen.[[br]]
     56 Movement of the camera is possible if the camera supports it.
     57
     58}}}
     59([#point10.16 Top of Page])
     60[[BR]]
     61
     62{{{#!th style="border: none" rowspan=0 align=left
     63[[Image(source:/ipk/source.sh4/tools_lcdpearl1/preview/prev.png)]]
     64}}}
     65|----------------
     66{{{#!td style="border: none"
     67 '''LCD-Pearl'''
     68
     69 Viewing EPG info, station logos, on the small external Pearl-USB picture frame.[[br]]
     70 Additional Skin informationcan be found at ([wiki:Plugins-LcdPearlSkins#point110.8 10.8 LCD Pearl Skins]).
     71}}}
     72([#point10.16 Top of Page])
     73[[BR]]
     74
     75
     76{{{#!th rowspan=0 align=left style="border: none"
     77[[Image(source:/ipk/source.sh4/tools_lcdsamsung/preview/prev.png)]]
     78}}}
     79|----------------
     80{{{#!td style="border: none"
     81  '''LCD-Samsung'''
     82
     83 Viewing EPG info, station logos, on the small external Samsung-USB picture frame.[[br]]
     84 Additional Skin informationcan be found at ([wiki:Plugins-LcdSamsungSkins#point110.9 10.9 LCD Samsung Skins]).
     85
     86}}}
     87([#point10.16 Top of Page])
     88[[BR]]
     89
     90{{{#!th rowspan=0 align=left style="border: none"
     91[[Image(source:/ipk/source.sh4/tools_optimize/preview/prev.png)]]
     92}}}
     93|----------------
     94{{{#!td style="border: none"
     95 '''Optimize'''[[BR]][[BR]]
     96 A tool to optimize the channel lists in TitanNit. Redundant transmitters[[br]]
     97 and transponders can be removed here.[[br]]
     98 The speed when scrolling through the channel list increases.
     99
     100}}}
     101([#point10.16 Top of Page])
     102[[BR]]
     103
     104
     105{{{#!th rowspan=0 align=left style="border: none"
     106[[Image(source:/ipk/source.sh4/tools_parted/preview/prev.png)]]
     107}}}
     108|----------------
     109{{{#!td style="border: none"
     110 '''Parted'''
     111
     112 Parted is neccessary to format a Harddisk with a capacity larger 2TB. After installing[[br]]
     113 the plugin it is active so you can setup your Haiddisk straight away.
     114
     115}}}
     116([#point10.16 Top of Page])
     117[[BR]]
     118
     119
     120{{{#!th rowspan=0 align=left style="border: none"
     121[[Image(source:/ipk/source.sh4/tools_PermanentTime/preview/prev.png)]]
     122}}}
     123|----------------
     124{{{#!td style="border: none"
     125 '''Permanent Time'''
     126
     127 Activate it and the time is shown permanently on your screen[[br]]
     128 until you call up the function again to deactivate it.
     129
     130}}}
     131([#point10.16 Top of Page])
     132[[BR]]
     133
     134{{{#!th rowspan=0 align=left style="border: none"
     135[[Image(source:/ipk/source.sh4/tools_tsschnitt/preview/prev.png)]]
     136}}}
     137|----------------
     138{{{#!td style="border: none"
     139 '''Record cut'''
     140
     141 With 'Record cut' You can edit the recordings in titan by cutting the beginning and end.[[br]]
     142 Start the desired movie with the internal player, at the desired start-point and End-point[[br]]
     143 press the -0- Key on your Remote Control. To view the set markers press -5- on your Remote Control.[[br]]
     144 'Record cut' is now started and by pressing the -Green- button select the movie and with the -Blue- button[[br]]
     145 By pressing the -Yeelow- button the cutting process can be executed in the backbround.[[br]]
     146 After the Process has finished an information is shown on the TV-screen.[[br]]
     147 The Process can be watched or abborted by pressing the -Red- button.
     148
     149}}}
     150([#point10.16 Top of Page])
     151[[BR]]
     152
     153{{{#!th rowspan=0 align=left style="border: none"
     154[[Image(source:/ipk/source.sh4/tools_rgui/preview/prev.png)]]
     155}}}
     156|----------------
     157{{{#!td style="border: none"
     158 '''RGUI'''
     159
     160 With Rgui you can access a different Titan Receiver.[[br]]
     161 You may also access the TV Program of the other receiver.[[br]]
     162 Streaming between both receivers is also possible.
     163}}}
     164([#point10.16 Top of Page])
     165[[BR]]
     166
     167{{{#!th rowspan=0 align=left style="border: none"
     168[[Image(source:/ipk/source.sh4/tools_scriptexec/preview/prev.png)]]
     169}}}
     170|----------------
     171{{{#!td style="border: none"
     172 '''Scriptexec'''
     173
     174 A small plugin to execute code on the receiver.
     175
     176}}}
     177([#point10.16 Top of Page])
     178[[BR]]
     179
     180{{{#!th rowspan=0 align=left style="border: none"
     181[[Image(source:/ipk/source.sh4/tools_stopifnotused/preview/prev.png)]]
     182}}}
     183|----------------
     184{{{#!td style="border: none"
     185 '''stop if not used'''
     186
     187 Your receiver is automatically turned off after a set time should no further Key be pressed.[[br]]
     188
     189 Autostart = yes / no - Time to Action (min) = 30/60/90/120/180/240 - Action = standby / off
     190
     191}}}
     192([#point10.16 Top of Page])
     193[[BR]]
     194
     195
     196{{{#!th rowspan=0 align=left style="border: none"
     197[[Image(source:/ipk/source.sh4/tools_usbreset/preview/prev.png)]]
     198}}}
     199|----------------
     200{{{#!td style="border: none"
     201 '''USB Reset'''
     202
     203 Attached USB devices are re-read.
     204}}}
     205([#point10.16 Top of Page])
     206[[BR]]
     207
     208{{{#!th rowspan=0 align=left style="border: none"
     209[[Image(source:/ipk/source.sh4/tools_zapback/preview/prev.png)]]
     210}}}
     211|----------------
     212{{{#!td style="border: none"
     213 '''Zapback'''
     214
     215 Zapback will after a given time automatically switch back to a pre-set channel .
     216
     217}}}
     218([#point10.16 Top of Page])
  • wiki/pages/it/Plugins-Wlan

    r39712 r39721  
     1[[TranslatedPages]]
     2----
     3'''10.17 WLAN Module''' [=#point10.17] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4----
     5
     6TitanNit is compatable with several usb Wireless lan devices below is a list of compatable wireless modules chipset's:
     7
     8 * Realtek RTL8192SE (802.11N)
     9 * Realtek RTL8712U (802.11N)
     10 * Ralink RT2870STA (802.11N)
     11 * Ralink RT3070STA (802.11N)
     12 * Ralink RT5370STA (802.11N)
     13
     14Drivers can be installed from any of the above devices from the online extentions ([wiki:TPK-Install#point3.4.4 TPK Install (Online)])
     15
     16||= '''WLAN 8192 driver''' =||= '''WLAN Driver 8172u''' =||= '''WLAN Driver rt2870sta''' =||= '''WLAN Driver rt3070sta''' =||= '''WLAN Driver rt5370sta''' =||
     17||= [[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

    r39712 r39721  
     1[[TranslatedPages]]
     2----
     3'''10.13 Channel logos (Picons)''' [=#point10.13] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4----
     5'''picons_transparent'''
     6
     7[[Image(source:/ipk/source/picons_transparent_SAT13_0/preview/prev.png)]]
     8[[Image(source:/ipk/source/picons_transparent_SAT19_2/preview/prev.png)]]
     9[[Image(source:/ipk/source/picons_transparent_SAT23_5/preview/prev.png)]]
     10[[Image(source:/ipk/source/picons_transparent_SAT28_2/preview/prev.png)]]
     11[[BR]]
     12[[br]]
     13([#point110.13 Top of Page])
     14
     15'''picons_black3d'''
     16
     17[[Image(source:/ipk/source/picons_black3d_SAT13_0/preview/prev.png)]]
     18[[Image(source:/ipk/source/picons_black3d_SAT19_2/preview/prev.png)]]
     19[[Image(source:/ipk/source/picons_black3d_SAT23_5/preview/prev.png)]]
     20[[BR]]
     21[[br]]
     22([#point10.13 Top of Page])
     23
     24'''picons_gold'''
     25
     26[[Image(source:/ipk/source/picons_gold_SAT13_0/preview/prev.png)]]
     27[[Image(source:/ipk/source/picons_gold_SAT19_2/preview/prev.png)]]
     28[[Image(source:/ipk/source/picons_gold_SAT23_5/preview/prev.png)]]
     29[[Image(source:/ipk/source/picons_gold_SAT28_2/preview/prev.png)]]
     30[[BR]]
     31[[br]]
     32([#point10.13 Top of Page])
     33
     34'''picons_Kabel'''
     35
     36[[Image(source:/ipk/source/picons_KabelBW/preview/prev.png)]]
     37[[Image(source:/ipk/source/picons_KabelDblack3d/preview/prev.png)]]
     38[[Image(source:/ipk/source/picons_KabelDtransparent/preview/prev.png)]]
     39[[Image(source:/ipk/source/picons_spiegel_SAT19_2/preview/prev.png)]]
     40[[BR]]
     41[[br]]
     42([#point10.13 Top of Page])
     43
     44'''picons_transparent_small_black'''
     45
     46[[Image(source:/ipk/source/picons_transparent_small_black_SAT19_2/preview/prev.png)]]
     47[[BR]]
     48[[br]]
     49([#point10.13 Top of Page])
     50
     51'''picons_white3d'''
     52
     53[[Image(source:/ipk/source/picons_white3d_SAT13_0/preview/prev.png)]]
     54[[Image(source:/ipk/source/picons_white3d_SAT19_2/preview/prev.png)]]
     55[[Image(source:/ipk/source/picons_white3d_SAT23_5/preview/prev.png)]]
     56[[Image(source:/ipk/source/picons_white3d_SAT28_2/preview/prev.png)]]
     57[[BR]]
     58[[br]]
     59([#point110.13 Top of Page])
     60
     61'''picons_white70'''
     62
     63[[Image(source:/ipk/source/picons_white70_SAT13_0/preview/prev.png)]]
     64[[Image(source:/ipk/source/picons_white70_SAT19_2/preview/prev.png)]]
     65[[Image(source:/ipk/source/picons_white70_SAT23_5/preview/prev.png)]]
     66[[Image(source:/ipk/source/picons_white70_SAT28_2/preview/prev.png)]]
     67[[BR]]
     68[[br]]
     69([#point10.13 Top of Page])
     70
     71'''picons_X_LightTransparen'''
     72
     73[[Image(source:/ipk/source/picons_X_LightTransparent_SAT13_0/preview/prev.png)]]
     74[[Image(source:/ipk/source/picons_X_LightTransparent_SAT19_2/preview/prev.png)]]
     75[[Image(source:/ipk/source/picons_X_LightTransparent_SAT23_5/preview/prev.png)]]
     76[[Image(source:/ipk/source/picons_X_LightTransparent_SAT28_2/preview/prev.png)]]
     77[[BR]]
     78[[br]]
     79([#point110.13 Top of Page])
     80
     81'''picons_X_LightTransparent_SAT19_2_small'''
     82
     83[[Image(source:/ipk/source/picons_X_LightTransparent_SAT19_2_small/preview/prev.png)]]
     84[[BR]]
     85[[br]]
     86([#point10.13 Top of Page])
     87
  • wiki/pages/it/Power-Off-Timer

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''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])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Power-Off-Timer.jpg)]][[br]]
     8>
     9> here you change your shutdown settings such as fixed shutdown timer.
     10
     11[[br]]
     12
  • wiki/pages/it/Quick-Start-Guide

    r39712 r39721  
     1[[TranslatedPages]]
     2
     3----
     4'''Quick Start Guide''' [=#point0] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     5New Gui section work in progress expect dead links or missing data.
     6----
     7
     8TitanNit 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.
     9This 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.
     10
     11Note: 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]
     12be aware that as TitanNit has been developed for multiple hardware devices the precedures outlined below may not be the same as your reciever.
     13
     14You may select a skip to a specific setup topic or scroll down to read the complete guide.
     15----
     16{{{#!div style="width: 1100px; margin: auto"
     17 {{{#!table style="border: none"
     18  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     19  {{{#!div style="float: left"
     20[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_Up_the_Language.png,align=left,link=[#point0.1])]]
     21  }}}
     22  '''([#point0.1 Setting Up the language])'''[[br]]
     23  {{{#!div style="float: left
     24click here to find info on setting up the language
     25  }}}
     26  }}}
     27  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     28  {{{#!div style="float: left"
     29[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up_the_Network.png,align=left,link=[#point0.2])]]
     30  }}}
     31  '''([#point0.2 Setting Up the Network])'''[[br]]
     32  {{{#!div style="float: left
     33click here to find info on setting up the Network
     34  }}}
     35  }}}
     36  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     37  {{{#!div style="float: left"
     38[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up_the_HDD.png,align=left,link=[#point0.3])]]
     39  }}}
     40  '''([#point0.3 Setting Up the Hdd])'''[[br]]
     41  {{{#!div style="float: left
     42click here to find info on setting up the HDD
     43  }}}
     44  }}}
     45  |---
     46  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     47  {{{#!div style="float: left"
     48[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up-the_Tuner.png,align=left,link=[#point0.4])]]
     49  }}}
     50  '''([#point0.4 Setting Up the Tuner])'''[[br]]
     51  {{{#!div style="float: left
     52click here to find info on Setting Up the Tuner
     53  }}}
     54  }}}
     55  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     56  {{{#!div style="float: left"
     57[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Preforming_a_Scan.png,align=left,link=[#point0.5])]]
     58  }}}
     59  '''([#point0.5 Proforming a Scan])'''[[br]]
     60  {{{#!div style="float: left
     61click here to find info Proforming a Scan
     62  }}}
     63  }}}
     64  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     65  {{{#!div style="float: left"
     66[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Orginising_Your_Channels.png,align=left,link=[#point0.6])]]
     67  }}}
     68  '''([#point0.6 Orginising Your Channels])'''[[br]]
     69  {{{#!div style="float: left
     70click here to find info on Orginising Your Channels
     71  }}}
     72  }}}
     73  |---
     74  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     75  {{{#!div style="float: left"
     76[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Setting_up_Media.png,align=left,link=[#point0.7])]]
     77  }}}
     78  '''([#point0.7 Setting Up a Media])'''[[br]]
     79  {{{#!div style="float: left
     80click here to find info on Setting Up a Media
     81  }}}
     82  }}}
     83  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     84  {{{#!div style="float: left"
     85[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Playing_Back_Media.png,align=left,link=[#point0.8])]]
     86  }}}
     87  '''([#point0.8 Playing Back Media])'''[[br]]
     88  {{{#!div style="float: left
     89click here to find info Playing Back Media
     90  }}}
     91  }}}
     92  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     93  {{{#!div style="float: left"
     94[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Conclusion.png,align=left,link=[#point0.9])]]
     95  }}}
     96  '''([#point0.9 Conclusion])'''[[br]]
     97  {{{#!div style="float: left
     98Conclusion/ what to do next after stting up Titan
     99  }}}
     100  }}}
     101  |----
     102  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     103  {{{#!div style="float: left"
     104[[Image(source:/wiki/Wiki-Pictures/Common/Icons/quick-start-guide/Apendixcies.png,align=left,link=[#point0.10])]]
     105  }}}
     106  '''([#point0.10 Apendixcies])'''[[br]]
     107  {{{#!div style="float: left
     108Apendixcies/ references [[br]]to other setup related topics.
     109  }}}
     110  }}}
     111}}}
     112}}}
     113[[br]]
     114[[br]]
     115
     116
     117
     118
     119
     120
     121
     122
     123----
     124''' Welcome to TitanNit! '''
     125----
     126 
     127Congratulations 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.
     128 
     129
     130----
     131'''Setting Up the Language''' [=#point0.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     132----
     133By default the language of the TitanNit interface is in German and must be switched on setup to your language.
     134To 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.
     135
     136[[Image(source:/wiki/Wiki-Pictures/IT/Language.jpg, 50%)]][[BR]]
     137[[br]]
     138[[br]]
     139
     140----
     141'''Setting Up the Network''' [=#point0.2] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     142----
     143To Set Up the Network Interface of the receiver go into the __"Menu"__ and select > __"System"__ > __"Network"__
     144
     145[[Image(source:/wiki/Wiki-Pictures/IT/system-Network.jpg, 50%)]][[BR]]
     146
     147If you wish to setup a wired network select __"LAN Interface Setup"__ and press the red button.
     148you 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.
     149
     150If you wish to setup a wireless network select __"WLAN"__
     151if 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.
     152you will then need to set your security type and key using the remote and press the __"green button"__ to start the network connection.
     153[[br]]
     154[[br]]
     155
     156----
     157'''Setting Up the Hdd''' [=#point0.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     158----
     159If 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.
     160
     161To 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.)
     162
     163you 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.
     164
     165[[Image(source:/wiki/Wiki-Pictures/IT/Format-Hdd.jpg, 50%)]][[br]]
     166
     167Now that the Hdd is formatted you may set it up, go into the __"Menu"__ and select > __"System"__ > __"Storage Device"__ and select __"Configure device"__
     168
     169Select 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.
     170I suggest you enable all options.
     171[[br]]
     172[[br]]
     173
     174----
     175'''Setting up the Tuner''' [=#point0.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     176----
     177
     178Before 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.
     179
     180As 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.
     181
     182Before 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.
     183
     184''Setting up the default transponder/satellite lists''
     185
     186Programming 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.
     187(Note that these transponder lists may not allways be 100% correct as services may change)
     188
     189[[Image(source:/wiki/Wiki-Pictures/IT/Create-Transponder-List.jpg, 50%)]][[br]]
     190 
     191Go 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.
     192
     193
     194Alternativly 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.
     195
     196Proform these steps in this sequence to import a list of satellites on to your receiver:
     197
     198 * Download a satellite xml file for the satellites you wish to receive from an [[http://satellites-xml.eu/ | Online xml generator]]
     199 * Download and install [wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor] to your pc and set up a connection to your receiver.
     200 * Import the xml file.
     201
     202[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/Import-Satellite.png)]]
     203
     204
     205 * Upload the satellite.xml file to your receiver
     206
     207[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/6.png)]]
     208
     209The reciever will then reboot if it does not then reboot manually to comit the changes.
     210
     211''Setting up the tuner''
     212
     213To Set up the Tuner of the receiver go into the __"Menu"__ and select > __"System"__ > __"Channel setup"__
     214
     215 * 1 Select tuner 0/0 and press the sideways key and select __"Tuner looped to 0/1"__
     216 * 2 Select tuner 0/1 and press the sideways key and select __"Tuner looped to 0/0"__
     217 * 3 Select tuner 0/0 and press the __"Red Button"__ to configuere the tuner
     218 * 4 Select the satellite type press sideways and select __"Single Lnb"__.
     219 * 5 Scroll down and select __"SAT 1"__ press the sideways key and select the satellite you wish to receive.
     220 * 6 Scroll down to Lnb/Unicable and press the __"Red Button"__ to configure the lnb type.
     221 * 7 scroll down to LOF/Unicable press the sideways key and select universal.
     222 * 8 Press ok button twice to store the lnb type and tuner configuration.
     223 * Repeat steps 4-8 on tuner 0/1
     224
     225your lnb is now set up and if all was done correctly you should now be able to scan for stations on the selected satellite.
     226[[br]]
     227[[br]]
     228
     229----
     230'''Proforming a Scan''' [=#point0.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     231----
     232
     233Before you can watch TV you must preform a scan of the transponders for available channels
     234
     235To 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.
     236
     237[[Image(source:/wiki/Wiki-Pictures/IT/Automatic-Search.jpg, 50%)]]
     238
     239Once 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.
     240
     241[[br]]
     242[[br]]
     243
     244----
     245'''Orginising Your Scanned Channels''' [=#point0.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     246----
     247Now 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.
     248but 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.
     249The easyest way to do this is with the [wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor].
     250
     251 * Download and install [wiki:External-Software-SatChannelListEditor#point9.3 SatChannelListEditor] to your pc and set up a connection to your receiver.
     252 * Read in the channel data as follows :
     253
     254[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/6.png)]]
     255
     256[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/7.png)]]
     257
     258
     259'' Favourites setup ''
     260
     261All TV and Radio channels are displayed in the tab "TV" and "Radio" in the main window[[br]]
     262of SCLE. Normally there are several hundreds or thousands of channels in this list.
     263[[BR]] To simplify navigation on your Receiver you may add the channels to more than one Favourites list.[[br]]
     264The Favourites also determine the channel number for easier and direct access with your remote control.
     265[[BR]] Create new favourites by clicking the right mouse button within the tree of favourites:
     266
     267[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/8.png)]]
     268
     269After creating the new Favourites entry assign the desired Name:
     270
     271[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/9.png)]]
     272
     273You may now add channels to your favourites by drag & drop of the channels[[br]]
     274onto the Favourites entry or by clicking the right mouse button on the desired channel[[br]]
     275and selecting Add to Favourites and selecting the Favourites Entry from the drop-down-menu:
     276
     277[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/10.png)]]
     278
     279Once a channel has been added to the favourites, a channel number is assigned.[[br]]
     280The first channel in the first favourites is channel number 1:
     281
     282[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/11.png)]]
     283
     284When a channel is assigned to more than one favourites list, it additionally[[br]]
     285obtains further channel numbers:
     286
     287[[Image(source:/wiki/Wiki-Pictures/IT/SCLE/12.png)]]
     288[[br]]
     289[[br]]
     290
     291----
     292'''Setting Up a Media Source''' [=#point0.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     293----
     294To Set up a media source to be acessable from the reciever of the receiver go into the __"Menu"__ and select > __"System"__ > __"Network"__> __"Network Browser"__
     295
     296[[Image(source:/wiki/Wiki-Pictures/IT/Network-Browser.jpg, 50%)]][[br]]
     297
     298now press the __"Red"__ button to add a source and you will be presented with a list of share options.
     299set up your share type adress and details for your media server and press __OK"__ to store it in.
     300
     301your share will now be mounted and it will now show up in the media/net/ directory
     302
     303[[br]]
     304[[br]]
     305
     306----
     307'''Playing Back Media''' [=#point0.8] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     308----
     309To 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.
     310You may play media from your network share by browsing to the media/net if you wish.
     311
     312[[Image(source:/wiki/Wiki-Pictures/IT/Internal-Player-OSD.jpg, 50%)]][[br]]
     313[[br]]
     314[[br]]
     315
     316----
     317'''Conclusion''' [=#point0.9] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     318----
     319Conclusion
     320 
     321Thanks 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.
     322
     323[[br]]
     324[[br]]
     325
     326----
     327'''Apendixcies''' [=#point0.10] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     328----
     329Please see below for more advanced topics and information
     330
     331 * [wiki:Interface-Operation#point3 Interface and Operation]
     332 * [wiki:Remote-Device-Control#point3.9 Remote/ Device Control]
     333 * [wiki:Installation-Recovery#point8 Installation / Recovery]
     334 * [wiki:External-Software#point9 External Software]
     335 * [wiki:Plugins-Contents#point10 Plugins]
     336 * [wiki:Troubleshooting#point12 Troubleshooting]
     337
     338We 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.
     339
     340Oh and by the way as a final remark thanks for choosing TitanNit!.
     341[[br]]
     342[[br]]
     343
  • wiki/pages/it/Ram

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8.6 Ram''' [=#point3.7.8.6] ([wiki:System-Info#point3.7.8 System Info (Back])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/System-Info-Ram.jpg)]][[br]]
     7>
     8Here you can view the memory information.
     9
     10[[br]]
     11
     12
     13[[br]]
  • wiki/pages/it/Receiver-Unlock

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.5.10 Receiver Unlock''' [=#point3.5.10] ([wiki:Interface-Operation#point3.5 System (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/system_receiver_unlock.jpg)]][[br]]
     8>
     9>Here you can unlock the special features of the decoder after purchase.
     10
     11[[br]]
  • wiki/pages/it/Record-Path

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.8 Record Path''' [=#point3.6.8] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Record_Path.jpg)]][[BR]]
     8>
     9> here you can recording directorys.
     10
     11[[br]]
     12
     13 ||'''Movie  Path''' ||This is the path to the Movie Directory.||
     14 ||'''Timer Record Path:''' ||This is the path to the directory where the timer recordings are stored.||
     15 ||'''Record Patht''' ||This is the path to the directory where the manual recordings are stored.||
     16 ||'''Timeshift Path:''' ||This is the path to the directory where the Timeshift files are stored.||
     17 ||'''Stream Path''' ||This is the path to the directory where temporary Streams are stored.||
     18 
     19 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     20 
     21[[br]]
     22----
     23
     24 '''Coloured Button's Functions"
     25
     26 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
     27 please see below for more info on the functions of these buttons:.
     28 
     29 ||'''Red Button: (Edit)''' ||This button allows editing of the above paths it will bring up an onscreen keyboard to edit the string selected.||
     30 
  • wiki/pages/it/Records

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.1.5 Records''' [=#point3.1.5] ([wiki:Interface-Operation#point3.1 Records and EPG(Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Records.jpg)]][[BR]]
     8>
     9>Recordings is where you can set up and edit timer set recordings.
     10
     11
     12[[br]]
     13
     14----
     15
     16 '''Coloured Button's Functions"
     17
     18 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
     19 please see below for more info on the functions of these buttons:.
     20 
     21 ||'''Red Button: (Del)''' ||This will delete the currently selected timer or recording.||
     22 ||'''Green Button: (Add)''' ||this will add a new timer recording.||
     23 ||'''Yellow Button: (Stop/ Start)''' ||this will stop or start the currently selected timer recording.||
     24 ||'''Blue Button: (log)''' ||This will show you the past log file for the past timer recordings.||
     25
  • wiki/pages/it/Red-Button

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.4 Red Button''' [=#point3.6.4] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0.2 Contents]) ([WikiStart#point0 Main page])
     4
     5>
     6>Menu Picture place holder:
     7>
     8>[[Image(source:/wiki/Wiki-Pictures/IT/Red_Button.jpg)]][[BR]]
     9>
     10>here you can configure what happens with the press of the red button
     11
     12
     13[[br]]
  • wiki/pages/it/Remote-Device-Control

    r39712 r39721  
     1[[TranslatedPages]]
     2----
     3'''4 Remote/ Device control''' [=#point4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4New Gui section work in progress expect dead links or missing data.
     5----
     6== Remote/ Device control ==
     7
     8This 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.
     9
     10
     11 ''Please select a menu item from the GUI for more information''
     12
     13----
     14{{{#!div style="width: 1100px; margin: auto"
     15 {{{#!table style="border: none"
     16  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     17  {{{#!div style="float: left"
     18[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Remote_Control.png,align=left,link=[#point4.1])]]
     19  }}}
     20  '''[wiki:Remote-Device-Control#point4.1 4.1 RC Remote control]'''[[br]]
     21  {{{#!div style="float: left
     22click here to find info on setting up the language
     23  }}}
     24  }}}
     25  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     26  {{{#!div style="float: left"
     27[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/On_Device_control.png,align=left,link=[#point4.2])]]
     28  }}}
     29  '''[wiki:Remote-Device-Control#point4.2 4.2 On Device Control]'''[[br]]
     30  {{{#!div style="float: left
     31click here to find info on setting up the Network
     32  }}}
     33  }}}
     34  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     35  {{{#!div style="float: left"
     36[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Web_Interface.png,align=left,link=[#point4.3])]]
     37  }}}
     38  '''[wiki:Remote-Device-Control#point4.3 4.3 Web Interface]'''[[br]]
     39  {{{#!div style="float: left
     40click here to find info on setting up the HDD
     41  }}}
     42  }}}
     43  |---
     44  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     45  {{{#!div style="float: left"
     46[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Telnet_Control.png,align=left,link=[#point4.4])]]
     47  }}}
     48  '''[wiki:Remote-Device-Control#point4.4 4.4 Telnet Control]'''[[br]]
     49  {{{#!div style="float: left
     50click here to find info on Setting Up the Tuner
     51  }}}
     52  }}}
     53  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     54  {{{#!div style="float: left"
     55[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Rgui.png,align=left,link=[#point4.5])]]
     56  }}}
     57  '''[wiki:Remote-Device-Control#point4.5 4.5 Rgui]'''[[br]]
     58  {{{#!div style="float: left
     59click here to find info Proforming a Scan
     60  }}}
     61  }}}
     62  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     63  {{{#!div style="float: left"
     64[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Bootloader.png,align=left,link=[#point4.6])]]
     65  }}}
     66  '''[wiki:Remote-Device-Control#point4.6 4.6 Bootloader]'''[[br]]
     67  {{{#!div style="float: left
     68click here to find info on Orginising Your Channels
     69  }}}
     70  }}}
     71  |---
     72  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     73  {{{#!div style="float: left"
     74[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/TitanNit_WebIF.png,align=left,link=[#point4.7])]]
     75  }}}
     76  '''[wiki:Remote-Device-Control#point4.7 4.7 TitanNit WebIF]'''[[br]]
     77  {{{#!div style="float: left
     78click here to find info on Setting Up a Media
     79  }}}
     80  }}}
     81  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     82  {{{#!div style="float: left"
     83[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/FTP.png,align=left,link=[#point4.8])]]
     84  }}}
     85  '''[wiki:Remote-Device-Control#point4.8 4.8 FTP (File Transfer Protocol)]'''[[br]]
     86  {{{#!div style="float: left
     87click here to find info Playing Back Media
     88  }}}
     89  }}}
     90  {{{#!td align=center valign=top style="border: none; font-size: 115%"
     91  {{{#!div style="float: left"
     92[[Image(source:/wiki/Wiki-Pictures/Common/Icons/Remote-Device-Control/Autostart_Scripting.png,align=left,link=[#point4.9])]]
     93  }}}
     94  '''[wiki:Remote-Device-Control#point4.9 4.9 Autostart Scripting (usercmd.sh)]'''[[br]]
     95  {{{#!div style="float: left
     96Conclusion/ what to do next after stting up Titan
     97  }}}
     98  }}}
     99 
     100}}}
     101}}}
     102[[br]]
     103[[br]]
     104
     105
     106
     107----
     108'''4.1 RC Remote Control''' [=#point4.1] ([#point4 top of the page])
     109
     110----
     111 * ([#point4.1.1 RC Atevio700])
     112 * ([#point4.1.2 RC Atevio7000, Atevio7500, Atemio7600])
     113 * ([#point4.1.3 RC Atemio500, Atemio510])
     114 * ([#point4.1.4 RC Atemio520])
     115 * ([#point4.1.5 RC Atemio520-V2])
     116 * ([#point4.1.6 RC Atemio530])
     117
     118 * ([#point4.1.7 RC UFS910])
     119 * ([#point4.1.8 RC UFS912])
     120 * ([#point4.1.9 RC UFS922])
     121
     122[[BR]]
     123[[BR]]
     124[[BR]]
     125
     126
     127
     128
     129'''4.1.1 RC Remote Control Atevio700''' [=#point4.1.1]  ([#point4.1 back])
     130[[BR]]
     131{{{#!th rowspan=0 align=left style="border: none"
     132[[Image(source:/titan/web/img/rc.atevio700.png)]][[br]]
     133}}}
     134|----------------
     135{{{#!td style="border: none"
     136 
     137'''TEXT RC Atevio 700'''
     138
     139}}}
     140
     141[[br]]
     142[[br]]
     143[[br]]
     144
     145
     146
     147'''4.1.2 RC Remote Control Atevio7000, Atevio7500, Atemio7600''' [=#point4.1.2]  ([#point4.1 back])
     148[[BR]]
     149{{{#!th rowspan=0 align=left style="border: none"
     150[[Image(source:/titan/web/img/rc.atevio7000.png)]][[br]]
     151}}}
     152|----------------
     153{{{#!td style="border: none"
     154 The section contains information on the functions and operation of your remote control unit.
     155
     156 '''Special Function Buttons operation during channel streaming'''
     157
     158 
     159 ||'''Resolution:''' ||This Key Switches the videomode.||
     160 ||'''V.Format:''' ||This Key Switches the Video format.||
     161 ||'''Recall:''' ||This key can bring up the recent channel history so you can jump easily between programs.||
     162 ||'''Info:''' ||This Button displays the infobar.||
     163 ||'''fav:''' ||This button brings up the favourite and Bouquet lists to easily select programs.||
     164 ||'''Menu:''' ||This key opens the menu.||
     165 ||'''Sleep:''' ||This Key can setup the sleep timer.||
     166 ||'''Help:''' ||This key can display detailed information and help text's.||
     167 ||'''Exit:''' ||This key exits menus and popups .||
     168 ||'''text:''' ||This key shows the teletext display.||
     169 ||'''Ok:''' ||This button confirms menu items and popups.||
     170
     171[[br]]
     172
     173'''Programming the universal remote to operate a supported TV'''
     174
     175This section explains how to automatically search and program your universal remote control to operate your tv
     176
     177NOTE: If there are no inputs for 10 seconds during setting the TV RC code the setting mode is terminated.
     178
     179'''Automatic code search '''
     180
     181 * Press the TV / Atevio button on the remote (for at least 3 seconds) until the LED flashes twice.
     182
     183   Enter the code 001. The LED flashes twice to confirm the entry.
     184
     185 * Press and hold the "ON / OFF" button until the TV turns off.
     186   
     187   Note: The LED flashes every 1.5 seconds and sends a new TV power rc code.
     188
     189 * Release the button immediately then press the "OK" button to store the TV code.
     190
     191  (This can take up to 15 minutes to cycle all the tv's pre programmed in to the remote from the factory)
     192
     193   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.
     194
     195 * 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.
     196
     197 * 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.
     198
     199'''Reset remote to factory programming'''
     200
     201This 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.
     202
     203 * Press the TV / Atevio button on the remote (for at least 3 seconds) until the LED flashes twice.
     204
     205 * Enter the code 000.
     206 
     207 * The LED flashes twice to confirm the entry. The remote control will now be reset (no code programmed)
     208
     209
     210}}}
     211
     212[[br]]
     213[[br]]
     214[[br]]
     215
     216'''4.1.3 RC Remote Control Atemio 500 / Atemio 510''' [=#point4.1.3]  ([#point4.1 back])
     217[[BR]]
     218{{{#!th rowspan=0 align=left style="border: none"
     219[[Image(source:/titan/web/img/rc.atemio510.png)]][[br]]
     220}}}
     221|----------------
     222{{{#!td style="border: none"
     223 
     224'''TEXT RC Atemio 500/510'''
     225
     226}}}
     227
     228[[br]]
     229[[br]]
     230[[br]]
     231
     232'''4.1.4 RC Remote Control Atemio 520''' [=#point4.1.4]  ([#point4.1 back])
     233[[BR]]
     234{{{#!th rowspan=0 align=left style="border: none"
     235[[Image(source:/titan/web/img/rc.atemio520.png)]][[br]]
     236}}}
     237|----------------
     238{{{#!td style="border: none"
     239 
     240'''TEXT RC Atemio 520'''
     241
     242}}}
     243
     244[[br]]
     245[[br]]
     246[[br]]
     247
     248'''4.1.5 RC Remote Control Atemio 520 V2''' [=#point4.1.5]  ([#point4.1 back])
     249[[BR]]
     250{{{#!th rowspan=0 align=left style="border: none"
     251[[Image(source:/titan/web/img/rc.atemio520-V2.png)]][[br]]
     252}}}
     253|----------------
     254{{{#!td style="border: none"
     255 
     256'''TEXT RC Atemio 520-V2'''
     257
     258}}}
     259
     260[[br]]
     261[[br]]
     262[[br]]
     263
     264'''4.1.6 RC Remote Control Atemio 530''' [=#point4.1.6]  ([#point4.1 back])
     265[[BR]]
     266{{{#!th rowspan=0 align=left style="border: none"
     267[[Image(source:/titan/web/img/rc.atemio530.png)]][[br]]
     268}}}
     269|----------------
     270{{{#!td style="border: none"
     271 
     272'''TEXT RC Atemio 530'''
     273
     274}}}
     275
     276[[br]]
     277[[br]]
     278[[br]]
     279
     280
     281'''4.1.7 RC Remote Control Kathrein UFS910''' [=#point4.1.7]  ([#point4.1 back])
     282[[BR]]
     283{{{#!th rowspan=0 align=left style="border: none"
     284[[Image(source:/titan/web/img/rc.ufs910.png)]][[br]]
     285}}}
     286|----------------
     287{{{#!td style="border: none"
     288 
     289'''TEXT RC UFS 910'''
     290
     291}}}
     292
     293[[br]]
     294[[br]]
     295[[br]]
     296
     297
     298
     299
     300'''4.1.8 RC Remote Control Kathrein UFS912''' [=#point4.1.8]  ([#point4.1 back])
     301[[BR]]
     302{{{#!th rowspan=0 align=left style="border: none"
     303[[Image(source:/titan/web/img/rc.ufs912.png)]][[br]]
     304}}}
     305|----------------
     306{{{#!td style="border: none"
     307 
     308'''TEXT RC UFS912'''
     309
     310}}}
     311
     312[[br]]
     313[[br]]
     314[[br]]
     315
     316
     317
     318'''4.1.9 RC Remote Control Kathrein UFS922''' [=#point4.1.9]  ([#point4.1 back])
     319[[BR]]
     320{{{#!th rowspan=0 align=left style="border: none"
     321[[Image(source:/titan/web/img/rc.ufs922.png)]][[br]]
     322}}}
     323|----------------
     324{{{#!td style="border: none"
     325 
     326'''TEXT RC UFS922'''
     327
     328}}}
     329
     330[[br]]
     331[[br]]
     332[[br]]
     333
     334
     335
     336[[br]]
     337----
     338'''4.2 On Device Control''' [=#point4.2] ([#point4 top of the page])
     339
     340----
     341
     342
     343[[Image(source:/wiki/Wiki-Pictures/IT/On_Device_Control.jpg)]][[br]]
     344
     345The section contains information on the functions and operation of your Receiver from the onboard buttons.
     346Please note: the control is very limited from the on device controls but simple menu and tv control's can be made:
     347
     348'''Device Controll keys'''
     349
     350 
     351 ||'''Power''' ||This Key Switches to the power menu or shuts down depending on the "power action" see ([#point3.6.6 Adjust]) for more info. ||
     352 ||'''Menu:''' ||This Key brongs up the on screen display/ menu. ||
     353 ||'''Ok:''' ||This key accept on screen prompts. ||
     354 ||'''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. ||
     355
     356----
     357'''4.3 Web Interface''' [=#point4.3] ([#point4 top of the page])
     358----
     359
     360[[Image(source:/wiki/Wiki-Pictures/IT/Web_Control.jpg)]][[br]]
     361
     362The section contains information on the functions and operation of your Receiver from the web interface over LWAN, LAN or wifi.
     363
     364[[br]]
     365
     366----
     367'''4.3.1 Channel list''' [=#point4.3.1] ([#point4 top of the page])
     368----
     369
     370[[br]]
     371
     372 ||'''All''' ||Show All Channels from all Bouquets .||
     373 ||'''Sat''' ||Sort channels By Satellite.||
     374 ||'''provider:''' ||Sort channels By provider.||
     375 ||'''A-Z:''' ||Sort channels Alphabetically.||
     376 ||'''Bouquets:''' ||Sort channels By Boquet.||
     377
     378
     379[[br]]
     380----
     381'''4.3.2 Box Control''' [=#point4.3.2] ([#point4 top of the page])
     382----
     383
     384[[br]]
     385 
     386 ||'''Power Control:''' ||This brings up the links to control the power settings (shutdown, restart, etc....)||
     387 ||'''Message:''' ||Send a message to the display of the tv.||
     388 ||'''Remote:''' ||Bring up the remote on the web page for control of the decoder.||
     389 ||'''Screenshot OSD:''' ||Take a screen shot of the OSD.||
     390 ||'''Play Movie (URL:''' ||Play a movie from the selected url.||
     391
     392[[br]]
     393----
     394'''4.3.3 Movies''' [=#point4.3.3] ([#point4 top of the page])
     395----
     396
     397[[br]]
     398
     399This will bring up a list of the movie directory on the receiver please see ([#point3.12.5 Web Controls]) for more information
     400
     401[[br]]
     402----
     403'''4.3.4 Timer''' [=#point4.3.4] ([#point4 top of the page])
     404----
     405
     406[[br]]
     407 
     408 ||'''Timer List:''' ||Show a list of the timer Recordings.||
     409 ||'''Timer Archive:''' ||Show a list of all the completed timer recordings.||
     410 ||'''Add Timer:''' ||Add a timer recording.||
     411
     412[[br]]
     413----
     414'''4.3.5 System''' [=#point4.3.5] ([#point4 top of the page])
     415----
     416
     417[[br]]
     418 
     419 ||'''Extensions:''' ||Show a list of alailable extensions and plugins to install.||
     420 ||'''System update:''' ||Update the system  software.||
     421 ||'''System Backup:''' ||backup the system to an image file.||
     422 ||'''Settings Backup/ restore:''' ||Take/ restore a backup of the current settings and config.||
     423
     424[[br]]
     425----
     426'''4.3.6 Settings''' [=#point4.3.6] ([#point4 top of the page])
     427----
     428
     429[[br]]
     430
     431 ||'''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.||
     432 ||'''Oscam web interface:''' ||Shows config http information for the oscam plugin (if installed).||
     433 ||'''Xupnpd:''' ||Shows information on the Xupnpd media streaming plugin.||
     434
     435[[br]]
     436----
     437'''4.3.7 Information''' [=#point4.3.7] ([#point4 top of the page])
     438----
     439[[br]]
     440
     441This section contains detailed config and system info about your reciever and TitanNit.
     442Please see the below links for more information on the items contained with in this menu.
     443
     444 * ([wiki:Service#point3.7.1 Service])
     445 * ([wiki:News-letter#point3.7.2 News letter])
     446 * ([wiki:About#point3.7.3 About])
     447 * ([wiki:Streaming#point3.7.4 Streaming])
     448 * ([wiki:Atemio-Hotline#point3.7.5 Atemio (Hotline)])
     449 * ([wiki:Titan-Changelog#point3.7.6 Titan Changelog])
     450 * ([wiki:Git-Changelog#point3.7.7 Git Changelog])
     451 * ([wiki:System-Info#point3.7.8 System Info])
     452 * ([wiki:Log#point3.7.9 Log])
     453
     454[[br]]
     455----
     456'''4.3.8 Help''' [=#point4.3.8] ([#point4 top of the page])
     457----
     458
     459[[br]]
     460 
     461 ||'''Offline help:''' ||Currently this has no function and is for future use.||
     462 ||'''Online help:''' ||Shows this wiki from the web interface for help and support.||
     463
     464
     465[[br]]
     466----
     467'''4.3.9 Web Controls''' [=#point4.3.9] ([#point4 top of the page])
     468----
     469
     470[[br]]
     471
     472'''Filelist Display Web Buttons'''
     473
     474This section explains the functions and discriptions of the icons displayed on the web page along side the file list display.
     475
     476 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Webstream.png)]] ||This button plays the selected program (web Stream) ||
     477 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Stream.png)]] ||This button plays the selected program (Stream) ||
     478 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Delete.png)]] ||This button deletes the selected program ||
     479 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Edit.png)]] ||This button downloads the selected program ||
     480 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Singleepg.png)]] ||This button displays the (EPG) ||
     481 ||[[Image(source:/wiki/Wiki-Pictures/IT/web_radio.png)]] ||This button shows the selected channel is audio only (radio)||
     482 ||[[Image(source:/wiki/Wiki-Pictures/IT/web_tv.png)]] ||This button shows the selected channel is audio and video (TV)||
     483 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Cross.png)]] ||This button shows the selected channel is not available ||
     484 
     485
     486'''Other Web Buttons'''
     487
     488This section explains the functions and discriptions icons displayed on the web page title area.
     489
     490 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Rcopen.png)]] ||This button shows or hides the onscreen remote control ||
     491 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Poweroff.png)]] ||This button turns off the Receiver ||
     492 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Restart.png)]] ||This button restarts the Receiver ||
     493 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Guirestart.png)]] ||This button restarts the GUI ||
     494 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Standby.png)]] ||This button puts the receiver into standby ||
     495 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Speak_On.png)]] ||This button mute's the sound ||
     496 ||[[Image(source:/wiki/Wiki-Pictures/IT/web_led_on.png)]] ||These buttons select the volume 10 to 100% (left to right) ||
     497 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Record.png)]] ||This button starts a Recording ||
     498 ||[[Image(source:/wiki/Wiki-Pictures/IT/Web_Signal.png)]] ||This button shows the signal info's ||
     499 ||EPG Search ||This box enables you to search the EPG type your test into the box and press enter. ||
     500
     501[[br]]
     502----
     503
     504To 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.
     505
     506http:// IP.of.receiver
     507
     508[[br]]
     509
     510
     511----
     512'''4.4 Telnet Control''' [=#point4.4] ([#point4 top of the page])
     513----
     514
     515
     516[[Image(source:/wiki/Wiki-Pictures/IT/Telnet_Control.jpg)]][[br]]
     517
     518The section contains information on the operation of your Receiver over a telnet session.
     519
     520'''Telnet Setup'''
     521
     522 * Eithernet Interface Telnet Setup
     523
     524  1 A Network connection must be active
     525
     526  2 Install the client found here: ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty]).
     527
     528  3 Find the IP address from the system info ([wiki:Network#point3.7.8.5 Network]) section
     529
     530  4 Insert the IP address info into the telnet client
     531
     532  5 Click connect.
     533
     534[[br]]
     535 
     536 * Serial Interface Telnet Setup
     537
     538  1 Connect a null modem cable between the Receiver and PC
     539
     540  2 Install the client found here: ([http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty])
     541
     542  3 Set up the serial port connection parameters
     543
     544  4 Click connect.
     545
     546After 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.
     547
     548after 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]
     549
     550'''Remote RC debugging'''
     551{{{
     552#!python
     553killall -9 evremote2
     554evremote2
     555}}}
     556[[br]]
     557
     558'''Start FTDI driver'''
     559{{{
     560#!python
     561mknod / dev.static/ttyUSB0 c 188 0"
     562}}}
     563[[br]]
     564
     565'''Test FTDI driver commands'''
     566{{{
     567#!python
     568ls-al / dev/ttyUSB0
     569}}}
     570[[br]]
     571
     572{{{
     573#!python
     574cat /proc/bus/usb/devices
     575}}}
     576[[br]]
     577
     578{{{
     579#!python
     580lsmod | grep usbserial
     581}}}
     582[[br]]
     583
     584'''Take a screen shot'''
     585{{{
     586#!python
     587/sbin/grab -j 100 -r 960 /tmp/000.jpg
     588}}}
     589
     590----
     591'''4.5 Rgui''' [=#point4.5] ([#point4 top of the page])
     592----
     593[[br]]
     594
     595[[Image(source:/wiki/Wiki-Pictures/IT/Mainmenu.jpg)]][[br]]
     596
     597
     598RGui is a TitanNit plugin which allows you to operate your Receiver from a different Receiver. Only the Gui is completely transmitted.
     599
     600Thus one can operate the receiver remotely, but not stream the TV signal.
     601
     602[[br]]
     603
     604
     605
     606 
     607
     608----
     609'''4.6 Bootloader''' [=#point4.6] ([#point4 top of the page])
     610----
     611[[br]]
     612
     613[[Image(source:/wiki/Wiki-Pictures/IT/On_Device_Control.jpg)]][[br]]
     614
     615
     616== Iboot is a boot loader. ==
     617
     618"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]]
     619Please note that there is differences between the Iboot menu structure on the different models of decoders.
     620
     621''' Functions of the boot loader:'''
     622
     623* Identification of the Hardware
     624* Starting the Image
     625
     626
     627''' Iboot early startup menu '''
     628
     629To enter the Iboot startup menu shutdown the receiver and power up pressing the __"Menu"__ button on the remote control.
     630Iboot 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.
     631
     632
     633----
     634''' Expert Mode ''' (not present in av700/7000)
     635----
     636
     637[[br]]
     638
     639Expert 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.
     640
     641To switch Iboot into __"Expert Mode"__ Shutdown the receiver and power up pressing the __"Menu"__ button on the remote control .
     642Iboot will then startup showing __"Flash Menu"__ on the VFDisplay
     643
     644now using D-pad left / right select __"SETTINGS"__  and with up / down button select __"set OSD color"__ and click __"OK"__
     645now using the left and right D-pad buttons  left / right to change the colors
     646with up / down set the colors individually to
     647
     648for the '''AM 510/AM520 ''' the code is
     649
     650 * Red = 11
     651
     652 * Green = 47
     653
     654 * Blue = 11
     655
     656for the '''AM 7500/7600 ''' the code is
     657 
     658 * Red = 7
     659
     660 * Green = 10
     661
     662 * Blue = 5
     663
     664
     665Then press the __"Exit"__ button twice to return to the menu __"Flash"__ the display on the TV screen should now show:
     666
     667''' ! YOU ACTIVATED EXPERT MODE ! ''' - expert mode enabled
     668
     669''' ! NO WARRANTY ----- USE AT YOUR OWN RISK ! ''' No warranty - use at your own risk
     670
     671if you dont agree : execute ''' " Clean Environment Sector" ''' in the FLASH MENU
     672
     673if you do not want to lose the warranty, you must run ''' " Clean Environment Sector" ''' in the FLASH MENU
     674
     675[[br]]
     676
     677----
     678'''4.6.1 Main categories''''  [=#point4.6.1] [#point4.6 (back)]   
     679----
     680Please select an item below to see more information.
     681
     682[#point4.6.2 (Menu Flash)]
     683
     684[#point4.6.3 (Settings)]
     685
     686[#point4.6.4 (Menu Misc)]
     687
     688[#point4.6.5 (Menu Net)] (not present in av700/7000)
     689
     690
     691== Subcategories ==
     692
     693----
     694'''4.6.2 Menu Flash ''' [=#point4.6.2] [#point4.6 (back)]
     695
     696 ||'''USB IRDupdt Image''' ||flash (depending on SETTINGS > Select USB / SATA dev 1-4) via USB stick or USB HDD from sda1 (standard).||
     697 ||'''USBirds list''' ||If several ird Image's are on the USB stick, you can display them, select and then flash the desired one. ||
     698 ||'''Clean environment Sector''' ||Resets the bootargs and resets Iboot to the default settings this disables __"Expert Mode"__. ||
     699 ||'''Clean flash ! Include swap''' ||Deletes the entire image, including the swap area, so all settings, plugins, backups, etc.... are removed. ||
     700 ||'''SATA IRDupdt''' ||look for an ird image on the internal or an external SATA hdd / flash stick (not present in av700/7000). ||
     701 ||'''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). ||
     702 ||'''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). ||
     703
     704[[br]]
     705
     706----
     707'''4.6.3 Menu Settings ''' [=#point4.6.3] [#point4.6 (back)]
     708
     709 ||'''Turbosw'''||Select overclocking speeds available settings are (0)265, (1)265, (2)297, (3)297, (4)333, (5)333, (6)364, (7)364. ||
     710 ||'''Timeout'''||Delay befor selecting the default boot option. ||
     711 ||'''USB Sleep'''||???. ||
     712 ||'''Scroll Speed'''||How fast the VFDisplay module moves. ||
     713
     714[[br]]
     715
     716----
     717'''4.6.4 Menu Misc''' [=#point4.6.4] [#point4.6 (back)]
     718
     719 ||'''Disclaimer''' ||Shows the info on the bootloader. ||
     720 ||'''Serial Console''' ||Enables Bootloader serial debugging. ||
     721 ||'''Reset Board'''||Resets the Receiver and restarts boot process. ||
     722
     723
     724
     725
     726
     727[[br]]
     728
     729----
     730''' Menu Net ''' [=#point4.6.5] [#point4.6 (back)]
     731
     732Please note menu item has been superceded and now has no function and it can be ignored. [[br]]
     733Due to image updates the network setting does not need to be passed on by the bootloader.
     734
     735[[br]]
     736
     737
     738----
     739'''4.7 TitanNit Web-IF (Htmlapi)''' [=#point4.7] ([#point4 top of the page])
     740----
     741
     742[[Image(source:/wiki/Wiki-Pictures/IT/Web_Control.jpg)]][[br]]
     743
     744The section contains information on the operation and control of your decoder from the Htmlapi.
     745
     746[[br]]
     747
     748TitanNit provides its own Htmlapi that is freely distributed so that other developers may interface with a receiver running titan.
     749
     750
     751The Htmlapi is very simple to implement an example message structure is as follows:
     752
     753 * query?param&param&... for html output
     754
     755 * queryraw?param&param&... for raw-struct output
     756
     757
     758For example if you would wish to send a RC remote keypress of the "Mute" key the message format would be as follows:
     759
     760 * __query?sendrc&rcmute__
     761
     762
     763if you would like to retrieve a list of all the current satelites the format would be as follows:
     764
     765 * __queryraw?getsat__
     766
     767
     768the output message back from the Receiver would be as follows:
     769
     770 * __satname#orbitalpos__
     771and an example raw output would be:
     772
     773> {{{Optus_d2#160}}}[[br]]
     774> {{{Optus_d1#166}}}[[br]]
     775> {{{Intelsat_IS19#156}}}[[br]]
     776
     777''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]''
     778
     779[[br]]
     780
     781----
     782'''4.8 FTP (File Transfer Protocol)''' [=#point4.8] ([#point4 top of the page])
     783----
     784
     785[[Image(source:/wiki/Wiki-Pictures/IT/Filezilla.jpg)]][[br]]
     786
     787The section contains information on how to setup a FTP connection to your TitanNit Receiver.
     788
     789[[br]]
     790
     791Titan Has an inbuilt FTP Server that is able to be used to transfer files to and from your Receiver.
     792
     793To 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.
     794
     795You 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:
     796
     797{{{ftp://Username:Password@Ip_Address:Port_Number}}}
     798
     799{{{ftp://root:root@192.168.0.1:21}}}
     800
     801if 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.
     802
     803[[Image(source:/wiki/Wiki-Pictures/IT/FileZilla-Setup.jpg)]][[br]]
     804
     805----
     806 '''4.9 autostart scripting (usercmd)''' [=#point4.9] ([#point4 top of the page])
     807----
     808
     809If 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.
     810
     811a sample of the usercmd.sh is below:
     812
     813{{{
     814#!python
     815#! / bin / sh
     816 # Start the user commands here
     817echo " [ usercmd.sh ] start"
     818 # insert code here
     819 exit
     820}}}
     821
     822the {{{__"# insert code here"__}}} section must be replaced by your commands.
     823
     824If 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:
     825
     826{{{
     827#!python
     828rm -f /media/hdd/movie/timeshift*.ts
     829}}}
     830
     831If you place the following code in to the usergmd.sh it will autostart the FTDI driver.
     832{{{
     833#!python
     834mknod / dev.static/ttyUSB0 c 188 0"
     835}}}
     836[[br]]
     837
     838
     839the full path to the file is:
     840__"/mnt/config/usercmd.sh"__
     841
     842
     843
     844
     845
     846
  • wiki/pages/it/Restore-Default-Settings

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.13 Restore Default Settings''' [=#point3.6.13] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Restore_Default_Settings.jpg)]][[BR]]
     8>
     9>here you can return your device to the default settings.
     10
     11[[br]]
     12
     13 ||'''Restore Default Settings:''' ||This will restore the settings to the factory default condition.||
     14 ||'''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.||
     15 ||'''Format MNT (all):''' ||This will format the Mount partition deleting all settings to default condition.||
     16 
     17 
     18 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     19 
     20[[br]]
     21----
  • wiki/pages/it/Rotor-Settings

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''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])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/Rotor-Settings.jpg)]][[br]]
     7>
     8Here you can adjust your rotor settings
     9
     10[[br]]
     11
     12 ||'''Move''' || Select move mode.||
     13 ||'''Fine Move:''' || Select fine move.||
     14 ||'''Limit:''' || Select satellite motor limits.||
     15 ||'''Go to start pos:''' || Goto the satellite starting position.||
     16 ||'''storage position:''' || Select storage position.||
     17   
     18 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     19
     20 '''Coloured Button's Functions'''
     21
     22 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in rotor settings.
     23  Please see below for more info on the functions of these buttons these functions depend on the selected menu item as follows:.
     24
     25'''During Move'''
     26 
     27 ||'''Red Button: (Move West)''' ||Set the sort method for the files listed in the file list display.||
     28 ||'''Green Button: (Search west)''' ||Play the selected media file.||
     29 ||'''Yellow button: (search east)''' ||Show the EPG information on the current selected media file (If present)||
     30 ||'''Blue button: (move east)''' ||Set the sort method for the files listed in the file list display.||
     31
     32'''During Fine Move'''
     33
     34 ||'''Green Button: (Step west)''' ||Play the selected media file.||
     35 ||'''Yellow Button: (Step East)''' ||Show the EPG information on the current selected media file (If present)||
     36
     37'''During Limit'''
     38 
     39 ||'''Red Button: (limit Off)''' ||Set the sort method for the files listed in the file list display.||
     40 ||'''Green Button: (limit West)''' ||Play the selected media file.||
     41 ||'''Yellow button: (limit East)''' ||Show the EPG information on the current selected media file (If present)||
     42 ||'''Blue button: (limit On)''' ||Set the sort method for the files listed in the file list display.||
     43 
     44
     45'''During goto start position'''
     46 
     47 ||'''Red Button: (Start Position)''' ||go to the selected start position.||
     48
     49
     50'''During Storage Position'''
     51 
     52 ||'''Green Button: (Storage Position)''' ||store selected storage position.||
     53 ||'''Yellow Button: (Goto Position)''' ||move dish to the stored position||
  • wiki/pages/it/Sat-Finder

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''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])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/Sat-Finder.jpg)]][[br]]
     7>
     8Here you can check your signal info for the current selected channel.
     9
     10[[br]]
     11
  • wiki/pages/it/Screensaver-Adjust

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.8 Screensaver Adjust''' [=#point3.6.8] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/Screensaver_Adjust.jpg)]][[BR]]
     7>
     8>Here you can setup your screen saver
     9
     10[[br]]
     11
     12
     13
     14 ||'''Screensaver''' ||enable or disable the screensaver display||
     15 ||'''Screensaver Delay:''' ||Set the delat time before the screen saver is displayed.||
     16 ||'''Screensaver Interval:''' ||Set the display time of the Screensaver in multi Pic Mode.||
     17 ||'''Screensaver Type:''' ||Select the type of Screensaver to display on the screen.||
     18 ||'''Screensaver Background:''' ||Select the background during display of the Screensaver.||
     19 ||'''Screensaver Pic:''' ||IN Image mode select the picture to Display as the Screensaver.||
     20 
     21 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     22 
     23[[br]]
     24----
  • wiki/pages/it/Service

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.1 Service''' [=#point3.7.1] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Service.jpg)]][[BR]]
     8>
     9> here you view information on the currently selected service.
     10
     11[[br]]
     12
     13'''Coloured Button's Functions"
     14
     15 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
     16 please see below for more info on the functions of these buttons:.
     17 
     18 ||'''Red Button: (Service)''' ||This will display the current service info on the display.||
     19 ||'''Green Button: (PIDs)''' ||This will display the PID info on the display.||
     20 ||'''Yellow Button: (Tuner)''' ||This will display the current Tuner Configuration info on the display.||
     21
     22
     23
  • wiki/pages/it/Settings-Backup-Restore

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.5.9 Settings Backup Restore''' [=#point3.5.9] ([wiki:Interface-Operation#point3.5 System (Back)]) ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/system_Settings_Backup_Restore.jpg)]][[BR]]
     7>
     8> here you can backup and restore your settings.
     9
     10[[br]]
     11
     12To Exit from the menu press __"Exit"__ to cancel backup restore.
     13
     14
     15'''Coloured Button's Functions"
     16
     17 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the backup restore menu. [[BR]]
     18 please see below for more info on the functions of these buttons:.
     19 
     20 ||'''Red Button: (Restore)''' ||Press this button to preform a restore from your previously saved settings.||
     21 ||'''Green Button: (Backup)''' ||Press this button to save your settings.||
     22 ||'''Yellow Button: (Log)''' ||Press this button to see the backup restore log.||
  • wiki/pages/it/Single-EPG

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''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])
     4>
     5>[[Image(source:/wiki/Wiki-Pictures/IT/Single_EPG.jpg)]][[BR]]
     6>
     7Single EPG is a small easy to read vertical epg of a single channel that shows the information of the currently selected program.
     8
     9
     10
     11[[br]]
     12
     13
     14 '''Coloured and Extra Button's Functions"
     15
     16 The __"Coloured and Extra Buttons"__ along the bottom of the display bring up additional menus and options with in the Single EPG menu.
     17 please see below for more info on the functions of these buttons:.
     18 
     19 ||'''Red Button: (Timer)''' ||This will bring up the recording timer menu to set up a timer.||
     20 ||'''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.||
     21
     22For information on setting up a timer Recording using the red button see ([wiki:Records Records]) for more info.
     23
     24For 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

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.16 Skin''' [=#point3.6.16] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Skin.jpg)]][[BR]]
     8>
     9>here you can select your skin
     10
     11
     12[[br]]
  • wiki/pages/it/Skin-Adjust

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.7 Skin Adjust''' [=#point3.6.7] ([wiki:Interface-Operation#point3.6 Settings (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Skin_Adjust.jpg)]][[BR]]
     8>
     9>Here you can edit your skin display settings
     10
     11[[br]]
     12
     13 ||'''Font Zize Adjust in Pixel''' ||Adjust the size of the fonts in the GUI.||
     14 ||'''Listbox Select:''' ||Select the display mode of the listbox select bar.||
     15 ||'''OSD Transparancy:''' ||Set the transpancy of the OSD when it is overlaying the TV display.||
     16 ||'''OSD Left Overscan:''' ||Set the value of the OSD overscan on the left edge of the display.||
     17 ||'''OSD Right Overscan:''' ||Set the value of the OSD overscan on the right edge of the display.||
     18 ||'''OSD Top Overscan:''' ||Set the value of the OSD overscan on the top edge of the display.||
     19 ||'''OSD Bottom Overscan:''' ||Set the value of the OSD overscan on the bottom edge of the display.||
     20 ||'''Show Hdd Freespace:''' ||show the Hdd Free space in the OSD. ||
     21 ||'''Listbox Select Colour:''' ||Press the red button to bring up a colour selection to display for the listbox select bar. ||
     22
     23 
     24 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     25 
     26[[br]]
     27----
  • wiki/pages/it/Smart-Card-Reader

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.5.3 Smart Card Reader''' [=#point3.5.3] ([wiki:Interface-Operation#point3.5 System (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/system-Smart_Card_Reader.jpg)]][[BR]]
     8>
     9here you can setup your smart card.
     10
     11[[br]]
     12
     13----
     14
     15 '''Coloured Button's Functions"
     16
     17 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
     18 please see below for more info on the functions of these buttons:.
     19 
     20 ||'''Red Button: (Reset)''' ||This will reset the selected Smart Card.||
  • wiki/pages/it/Streaming

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.4 Streaming''' [=#point3.7.4] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0.2 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Streaming.jpg)]][[BR]]
     8>
     9> here you can view information on service info being streamed to another device.
     10
     11[[br]]
     12
  • wiki/pages/it/Supported-Receivers

    r39712 r39721  
     1[[TranslatedPages]]
     2
     3----
     4'''7 Compatible Receivers''' [=#point7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0.2 Main page])
     5----
     6
     7Titan 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.
     8
     9The 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.
     10
     11The 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.
     12
     13Titan is also in development for the vu+ recievers and may be releaced in the future.
     14
     15TitanNit has also been made available for a variety of non-Atemio recievers manufactured by fortis, Atemio identical SH4 Fortis manufactured Receivers.
     16
     17
     18=== Currently, the following receivers are directly supported: ===
     19
     20
     21'''SH4 Atemio'''    ([http://www.atemio.de Atemio homepage])
     22
     23 * Atemio 510
     24 * Atemio 520
     25 * Atemio 530
     26 * Atevio 700
     27 * Atevio 7000
     28 * Atemio 7600
     29
     30'''SH4 Fortis'''  ([http://www.fortis.co.kr Fortis homepage])
     31
     32 * [#point7.2 Fortis Clones hardware detection]
     33 * Fortis FS-9000
     34 * Fortis FS-9200
     35 * Fortis HS-9510
     36 * Fortis HX-8200
     37 * Fortis HS-7810
     38
     39'''SH4 Homecast'''    ([http://www.myhomecast.nl/ Homecast homepage])
     40
     41 * Homecast Pro
     42
     43 '''SH4 IPBox''' ([http://www.abipbox.com/ AB IPBox homepage])
     44
     45 * Ipbox91
     46 * Ipbox900
     47 * Ipbox910
     48 * Ipbox9000
     49
     50'''SH4 Katherin'''   ([http://www.kathrein-gmbh.at kathrein homepage])
     51
     52 * Kathrein UFS 910
     53 * Kathrein UFS 912 (license charges may apply)
     54 * Katherin UFS 922 (license charges may apply)
     55 * Katherin UFS 960
     56
     57'''SH4 Fulan/ Spark'''   ([http://www.spark-tv.com Spark homepage)]
     58
     59 * [#point7.6 Fulan Clones hardware detection]
     60 * Spark7111
     61 * Spark7162
     62
     63'''Mips Atemio'''   ([http://www.atemio.de Atemio homepage])
     64
     65 * Atemio 5000 (AKA Nemisis)
     66 * Atemio 5200
     67 * Atemio 6000
     68 * Atemio 6100
     69 * Atemio 6200
     70
     71'''Mips Beyonwiz'''   ([Mips Beyonwiz Beyonwiz homepage])
     72
     73 * Beyonwiz T4
     74
     75'''Mips Golden Interstar'''   ([http://www.golden-interstar.pl Golden Interstar homepage])
     76
     77 * Xpeedlx1
     78 * Xpeedlx2
     79 * Xpeedlx3
     80
     81'''Mips Miraclebox'''   ([http://www.miraclebox.se/ Miraclebox homepage])
     82
     83 * MBUltra
     84 * MBMini
     85
     86
     87
     88'''Mips Sezam'''([http://www.sezam-club.ru/ homepage])
     89
     90 * Sezam-Marvel
     91
     92
     93
     94----
     95'''SH4 Fortis based clone receiver detection (hardware profile)''' [=#point7.1] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     96----
     97
     98This 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.
     99This list has not yet been confirmed and some of these models may be incompatible with TitanNit.
     100
     101If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated.
     102
     103Please Note:
     104  * 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.
     105
     106  * 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.
     107
     108This 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.
     109
     110{{{#!div style="width: 1000px; margin: auto"
     111||'''Model System'''||'''Tuner'''||'''CPU'''||'''RAM'''||'''ROM (Flash)'''||'''USB'''||'''PVR Funktion'''||'''CardReader'''||'''Common interface'''||'''Width'''||'''Display'''||'''features'''||
     112||[#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|| ||
     113||[#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|| ||
     114||[#point7.2 Fortis HS-9510]||DVB-S/S2 1||STI_7101 266 Mhz||192MB||32MB||1||USB||1 (*2)||2||11- segment||34 cm|| ||
     115||[#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+||
     116||[#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+||
     117}}}
     118
     119
     120----
     121'''Atevio AV 700 HD simular hardware:''' [=#point7.2]
     122----
     123Single tuner no no built in YouTube, Browser or FreeTV+
     124
     125Fortis base model HS-9510HD PVR and possibly identical boxes:
     126 
     127  * Fortis HS- 9510 HD PVR 20000300 Korea.
     128  * Rebox RE- 4000HD PVR 20010300 Netherlands.
     129  * Octagon SF- 1008 20020300 Germany.
     130  * Octagon SF -1008 SE 20020303 Germany.
     131  * HD Box FS- 9100HD 20030300 Czech Republic.
     132  * Ultra Plus HD 980 20050300 New Zealand.
     133  * Openbox S5 HD PVR 20060302 Ukraine.
     134  * Tiviar S1 eco HD PVR 20070300 U.S.A. Switzerland .
     135  * Astro ASR 1100 Single HD 20110300 and 20110303 Germany .
     136  * Dreamsky DSR- 9600HD PVR 20120302 Belarus.
     137  * Skyway Classic 20130302 Russia.
     138  * I.Com HD -9000 DIVX 20140300 Syria.
     139  * I.Com HD -9000 DIVX II 20140702 Syria.
     140  * I.Com HD -9100 DIVX II 20140602 Syria.
     141  * XSPEED HD -9500 DIVX II 20140612 Syria.
     142  * Optibox Koala HD 20150300 Hungary.
     143  * Xcruiser XDSR400HD 20160302 Dubai.
     144  * VisionNet FS- 9510 HD PVR 20170302 Israel.
     145  * Gold Master HD -1060 HD PVR HD PVR -1070 -1080 PVR 20180302 Turkey
     146  * Powersat PO - 1000HD PVR 20190301
     147  * Star Track SRT 2010 HD 20210302 Dubai
     148  * O2 SRT 2012 HD 20210301 Dubai
     149  * Forever HS- 9510HD PVR 20220302 Algeria
     150  * Dynavision DV -9500 HDPVR 20230302 Dubai
     151  * Dynavision DV -9600 HDPVR 20230301 Dubai
     152  * GI S- 8290 HD PVR 20240602 Romania
     153  * Miraclebox 8 HD TWIN PVR 20250600 Sweden
     154  * Diginor 8800 HD 20260600 Sweden
     155  * Media Star ( Powers) HD 1200s 20270600 Australia
     156  * MaxFly 9500 HD 20280602 Syria
     157  * SuperBox SX 9518 HD 20300302 Moldova
     158  * Elcomax Elux I 20310301 Iran
     159
     160[#point7 Top of Page]
     161
     162----
     163'''Atevio AV 7000 HD simular hardware:''' [=#point7.3] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     164----
     165Fortis base model FS-9000 and FS-9200 differ due to option of including an internal harddisk.
     166
     167FS- 9000 HD PVR and possibly identical boxes"
     168
     169  * Fortis FS- 9000HD 20000000 Korea
     170  * Rebox RE- 9000HD 20010000 Netherlands
     171  * Octagon SF 1018 20020000 Germany
     172  * HD Box FS -9300 HD 20030000 Czech Republic
     173  * Ultra Plus F- 9000HD 20050000 New Zealand        ''' Confirmed by ''' ([http://www.aaf-digital.info/forum/member.php?24970-professor_jonny Professor_Jonny])
     174
     175  * Openbox S8 HD PVR 20060000 Ukraine
     176  * Tiviar F1 HD PVR USA 20070000 Switzerland
     177  * Icecrypt S4000 HDPVR 20080000 England
     178  * Skyway Diamond 20130000 Russia
     179  * Dynavision DV -9000 HDPVR 200230000 Dubai
     180 
     181FS- 9200 HD PVR and possibly identical boxes:
     182
     183  * Fortis FS- 9200HD PVR 20000100 Korea
     184  * Rebox RE- 8000HD 20010100 Netherlands
     185  * HD Box FS- 9200HD 20030100 Czech Republic
     186  * Arcon Titan 2010HD 20040100 Germany
     187  * Openbox S7 HD PVR 20060100 Ukraine
     188  * Tiviar T1 HD PVR 20070100 Switzerland
     189  * Astro ASR 1200 Twin HD 20110100 Germany
     190  * Dreamsky DSR- 9700HD PVR 20120100 Belarus
     191  * Skyway Platinum 20130100 Russia
     192  * I.Com Twin HD -9200 DIVX 20140100 Syria
     193  * I.Com Twin HD -9200 DIVX II 20140101 Syria
     194  * Gold Master 1090 HD PVR 20180100 Turkey
     195  * Dynavision DV -9200 HDPVR 20230100 Dubai
     196 
     197[#point7 Top of Page]
     198
     199----
     200'''Atevio/ Atemio AV 7500 7600 HD simular hardware:''' [=#point7.4] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     201----
     202This model has a removable tuner and has YouTube, Browser, FreeTV+
     203
     204Fortis base model HX -8200 HD PVR and possibly identical boxes:
     205
     206  * Fortis HX -8200 HD PVR 230000X0 Korea
     207  * Rebox RE -8500 HD PVR 230100X0 Netherlands
     208  * Octagon SF 1028P Noblence 230200X0 Germany
     209  * Skyway Droid 230400X0 Russia
     210  * Openbox S9 HD PVR 230500X0 Ukraine
     211  * Icecrypt STC6000HDPVR 230600X0 UK
     212  * Miraclebox 9 HD TWIN PVR 230700X0 Sweden
     213  * Xcruiser XDSR600HD 230900X0 Dubai
     214  * Ultra Plus X - 9200HD PVR 231200X0 New Zealand 
     215  * Skys @ t Royal HD PVR 231500X0 Bulgaria
     216  * SuperBox PRO HD 9818 231600x0 Moldova
     217  * Optibox Raptor HD 231800X0 Hungary
     218  * Forever HD PVR 8200 231900X0 Algeria
     219  * Media Star ( Powers) HD 8200S 232700X0 Australia
     220
     221[#point7 Top of Page]
     222
     223----
     224'''Atemio AV 500/510 HD simular hardware:''' [=#point7.5] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     225----
     226This model has a removable tuner and has YouTube, Browser, FreeTV+
     227
     228Fortis base model HS -7110 HD PVR and possibly identical boxes:
     229
     230  * Fortis HS -7110 HD PVR ? korea
     231  * Optibox Gekko HD 250102X0 Hungary
     232  * Octagon SF 918 SE + 250202X0 Germany
     233  * Rebox RE -2200 HD PVR 250302X0 Netherlands
     234  * Skyway LIGHT 250502X0 Russia & Belarus
     235  * HD Box FS- 7110HD 250602X0 Czech Republic
     236  * Openbox S4 HD PVR 250902X0 Ukraine
     237  * Icom HD 1070P DIVX 251002X0 Syria
     238  * Gold Master HD -1040 HD PVR -1045 PVR 251102X0 Turkey
     239  * Dynavision DV -5000 HDPVR 251202X0 Dubai
     240  * GI S8580 251302X0 Romania
     241  * Xcruiser XDSR 380HD 251802X0 Dubai
     242  * Dreamsky HD4 252002X0 Belarus
     243  * ? Supermax 7100 252102X0 ?
     244  * Skys @ t Mini HD PVR 252202X0 Bulgaria
     245  * Icecrypt S3500 HDCCI 252502X0 UK
     246  * Miraclebox 6 HD TWIN PVR 252602X0 Sweden
     247  * Vegasat X1 252802X0 Morocco
     248  * Ultraplus 900 HD PVR ? New Zealand
     249
     250[[br]][#point7 Top of Page]
     251
     252----
     253'''Fulan based clone receiver detection (hardware profile)''' [=#point7.6] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     254----
     255
     256This 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.
     257This list has not yet been confirmed and some of these models may be incompatible with TitanNit.
     258
     259If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated.
     260
     261This 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.
     262
     263{{{#!div style="width: 1000px; margin: auto"
     264||'''Model System'''||'''Tuner'''||'''CPU'''||'''RAM'''||'''ROM (Flash)'''||'''USB'''||'''PVR Funktion'''||'''CardReader'''||'''Common interface'''||'''Width'''||'''Display'''||'''features'''||
     265||[#point7.7 Fulan 7162]||DVB-S/S2 1,2,3||STI_7162 266 Mhz|| || || || || || || || || ||
     266||[#point7.8 Spark 7111]||DVB-S/S2 1||STI_7111 266 Mhz|| || || || || || || || || ||
     267}}}
     268
     269
     270
     271----
     272'''Fulan/Spark 7162 simular hardware:''' [=#point7.7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     273----
     274This model has a STI 7162 Processor, tuner varies by reseller either one two or three tuners 
     275
     276Fulan/Spark 7162 and possibly identical boxes:
     277
     278
     279 * Golden Media Spark Triplex 0C 00 07 00
     280 * Golden Media Spark One 0C 00 07 00
     281 * SAB Unix Triple HD 0C 00 0E 00
     282 * Amiko Alien 2 0C 00 0A 00
     283 * Galaxy Innovations Avatar 2 0C 00 0B 00
     284 * Galaxy Innovations Avatar 3 0C 00 0B 00
     285 * Visionnet Falcon 0C 00 21 00
     286 * Icecrypt S3700 CHD 0C 00 2B 00
     287 * Truman Top Box 2 Tuners 0C 00 03 00
     288 * Samsat Linux 2 0C 00 20 00
     289 * Satcom 7162 0C 00 1D 00
     290 * Dynavision 7162 0C 00 0D 00
     291 * Superbox Z500 0C 00 15 00
     292 * Delta 0C 00 04 00
     293 * Startrack SRT 2020 HD Plus 0C 00 05 00
     294 * Sogno Spark Triple 0C 00 43 00
     295
     296----
     297'''Fulan/Spark 7111 simular hardware:'''   [=#point7.8]
     298----
     299This model has a STI 7111 Processor, all models seem to have a single DVB-S2 tuner.
     300
     301Fulan/Spark 7111 and possibly identical boxes:
     302
     303 * Amiko Alien SHD 8900, 09 00 0A 00
     304 * Golden Media 990 CR HD PVR Spark LX 09 00 07 00
     305 * Golden Media Spark Reloaded 09 00 07 00
     306 * Edision Argus Pingulux 09 00 08 00
     307 * Edision Argus Pingulux Plus 09 00 08 00
     308 * Galaxy Innovations GI S8120 09 00 0B 00
     309 * SAB Unix F+ Solo (S902) 09 00 0E 00
     310 * Dynavision Spark 09 00 0D 00
     311 * Dynavision Spark Plus 09 00 0D 00
     312 * Fulan Spark I+ 09 00 1D 00
     313 * Truman Premier 1+ 09 00 03 00
     314 * Samsat Linux 1 09 00 20 00
     315 * Startrack SRT 2020 HD 09 00 21 00
     316 * FullHD FH 2020 HD 09 00 ?? 00
     317 * Yumatu Spark 09 00 ?? 00
     318 * Visionnet Hammer 5400 09 00 21 00
     319 * Visionnet Fireball 101 09 00 21 00
     320 * Superbox S750 09 00 15 00
     321 * Sogno Spark Revolution 09 00 43 00
     322
     323
  • wiki/pages/it/Supported-Recievers

    r39712 r39721  
     1----
     2'''7 Compatable Revievers''' [=#point7] ([wiki:Wiki#point0 Contents]) ([WikiStart#point0.2 Main page])
     3----
     4
     5=== Currently, the following receivers are supported: ===
     6
     7  * Atemio 510/520/530
     8  * Atemio 7600
     9  * Atevio 700/7000
     10  * Kathrein UFS 910
     11  * Kathrein UFS 912/922 (license charges may apply)
     12
     13Recently TitanNit has been made available for a variety of non-Atemio Receivers. Identical SH4 Fortis Receivers may work with TitanNit.
     14
     15This list has not yet been confirmed and some of these models may be incompatible with TitanNit.
     16
     17If you have successfully installed TitanNit on your Receiver please inform an admin member so this list can be updated.
     18
     19Please Note:
     20  * 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.
     21
     22  * 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.
     23
     24
     25=== Atevio AV 500 HD: ===
     26 
     27Model HS- 9510HD PVR and possibly identical boxes:
     28 
     29  * Fortis HS- 9510 HD PVR 20000300 Korea.
     30  * Rebox RE- 4000HD PVR 20010300 Netherlands.
     31  * Octagon SF- 1008 20020300 Germany.
     32  * Octagon SF -1008 SE 20020303 Germany.
     33  * HD Box FS- 9100HD 20030300 Czech Republic.
     34  * Ultra Plus HD 980 20050300 New Zealand.
     35  * Openbox S5 HD PVR 20060302 Ukraine.
     36  * Tiviar S1 eco HD PVR 20070300 U.S.A. Switzerland .
     37  * Astro ASR 1100 Single HD 20110300 and 20110303 Germany .
     38  * Dreamsky DSR- 9600HD PVR 20120302 Belarus.
     39  * Skyway Classic 20130302 Russia.
     40  * I.Com HD -9000 DIVX 20140300 Syria.
     41  * I.Com HD -9000 DIVX II 20140702 Syria.
     42  * I.Com HD -9100 DIVX II 20140602 Syria.
     43  * XSPEED HD -9500 DIVX II 20140612 Syria.
     44  * Optibox Koala HD 20150300 Hungary.
     45  * Xcruiser XDSR400HD 20160302 Dubai.
     46  * VisionNet FS- 9510 HD PVR 20170302 Israel.
     47  * Gold Master HD -1060 HD PVR HD PVR -1070 -1080 PVR 20180302 Turkey
     48  * Powersat PO - 1000HD PVR 20190301
     49  * Star Track SRT 2010 HD 20210302 Dubai
     50  * O2 SRT 2012 HD 20210301 Dubai
     51  * Forever HS- 9510HD PVR 20220302 Algeria
     52  * Dynavision DV -9500 HDPVR 20230302 Dubai
     53  * Dynavision DV -9600 HDPVR 20230301 Dubai
     54  * GI S- 8290 HD PVR 20240602 Romania
     55  * Miraclebox 8 HD TWIN PVR 20250600 Sweden
     56  * Diginor 8800 HD 20260600 Sweden
     57  * Media Star ( Powers) HD 1200s 20270600 Australia
     58  * MaxFly 9500 HD 20280602 Syria
     59  * SuperBox SX 9518 HD 20300302 Moldova
     60  * Elcomax Elux I 20310301 Iran
     61
     62[#point7 Top of Page]
     63
     64=== Atevio AV 7000 HD: ===
     65 
     66The models FS- 9000 and FS -9200 differ due to option of including an internal harddisk.
     67
     68FS- 9000 HD PVR and possibly identical boxes
     69
     70  * Fortis FS- 9000HD 20000000 Korea
     71  * Rebox RE- 9000HD 20010000 Netherlands
     72  * Octagon SF 1018 20020000 Germany
     73  * HD Box FS -9300 HD 20030000 Czech Republic
     74  * Ultra Plus F- 9000HD 20050000 New Zealand        ''' Confirmed by ''' ([http://www.aaf-digital.info/forum/member.php?24970-professor_jonny Professor_Jonny])
     75
     76  * Openbox S8 HD PVR 20060000 Ukraine
     77  * Tiviar F1 HD PVR USA 20070000 Switzerland
     78  * Icecrypt S4000 HDPVR 20080000 England
     79  * Skyway Diamond 20130000 Russia
     80  * Dynavision DV -9000 HDPVR 200230000 Dubai
     81 
     82FS- 9200 HD PVR and possibly identical boxes
     83
     84  * Fortis FS- 9200HD PVR 20000100 Korea
     85  * Rebox RE- 8000HD 20010100 Netherlands
     86  * HD Box FS- 9200HD 20030100 Czech Republic
     87  * Arcon Titan 2010HD 20040100 Germany
     88  * Openbox S7 HD PVR 20060100 Ukraine
     89  * Tiviar T1 HD PVR 20070100 Switzerland
     90  * Astro ASR 1200 Twin HD 20110100 Germany
     91  * Dreamsky DSR- 9700HD PVR 20120100 Belarus
     92  * Skyway Platinum 20130100 Russia
     93  * I.Com Twin HD -9200 DIVX 20140100 Syria
     94  * I.Com Twin HD -9200 DIVX II 20140101 Syria
     95  * Gold Master 1090 HD PVR 20180100 Turkey
     96  * Dynavision DV -9200 HDPVR 20230100 Dubai
     97 
     98[#point7 Top of Page]
     99
     100=== Atevio / Atemio AV 7500/7600 HD: ===
     101
     102Model HX -8200 HD PVR and possibly identical boxes
     103
     104  * Fortis HX -8200 HD PVR 230000X0 Korea
     105  * Rebox RE -8500 HD PVR 230100X0 Netherlands
     106  * Octagon SF 1028P Noblence 230200X0 Germany
     107  * Skyway Droid 230400X0 Russia
     108  * Openbox S9 HD PVR 230500X0 Ukraine
     109  * Icecrypt STC6000HDPVR 230600X0 UK
     110  * Miraclebox 9 HD TWIN PVR 230700X0 Sweden
     111  * Xcruiser XDSR600HD 230900X0 Dubai
     112  * Ultra Plus X - 9200HD PVR 231200X0 New Zealand 
     113  * Skys @ t Royal HD PVR 231500X0 Bulgaria
     114  * SuperBox PRO HD 9818 231600x0 Moldova
     115  * Optibox Raptor HD 231800X0 Hungary
     116  * Forever HD PVR 8200 231900X0 Algeria
     117  * Media Star ( Powers) HD 8200S 232700X0 Australia
     118
     119[#point7 Top of Page]
     120
     121=== Atemio AM 500/510 HD: ===
     122 
     123Model HS -7110 HD PVR and possibly identical boxes
     124
     125  * Optibox Gekko HD 250102X0 Hungary
     126  * Octagon SF 918 SE + 250202X0 Germany
     127  * Rebox RE -2200 HD PVR 250302X0 Netherlands
     128  * Skyway LIGHT 250502X0 Russia & Belarus
     129  * HD Box FS- 7110HD 250602X0 Czech Republic
     130  * Openbox S4 HD PVR 250902X0 Ukraine
     131  * Icom HD 1070P DIVX 251002X0 Syria
     132  * Gold Master HD -1040 HD PVR -1045 PVR 251102X0 Turkey
     133  * Dynavision DV -5000 HDPVR 251202X0 Dubai
     134  * GI S8580 251302X0 Romania
     135  * Xcruiser XDSR 380HD 251802X0 Dubai
     136  * Dreamsky HD4 252002X0 Belarus
     137  * ? Supermax 7100 252102X0 ?
     138  * Skys @ t Mini HD PVR 252202X0 Bulgaria
     139  * Icecrypt S3500 HDCCI 252502X0 UK
     140  * Miraclebox 6 HD TWIN PVR 252602X0 Sweden
     141  * Vegasat X1 252802X0 Morocco
     142
     143[[br]][#point7 Top of Page]
  • wiki/pages/it/Swap

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8.6.6 Swap''' [=#point3.7.8.6.6] ([wiki:System-Info#point3.70.8.6 System Infos (Back])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Swap.jpg)]][[br]]
     8>
     9Here you can view the detailed info on the swap.
     10
     11[[br]]
     12
     13
     14[[br]]
  • wiki/pages/it/System-Info

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8 System Info''' [=#point3.7.8] ([wiki:Interface-Operation#point3.7 Information (Back)])([wiki:Wiki#point0 Contents]) ([WikiStart#point0 Main page])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/System_Info_main.jpg)]][[BR]]
     8>
     9> here you can view system wide information.
     10
     11[[br]]
     12
     13 * ([wiki:System-Status#point3.7.8.1 System Status])
     14 * ([wiki:Free-Space#point3.7.8.2 Free Space])
     15 * ([wiki:Kernel#point3.7.8.3 Kernel])
     16 * ([wiki:Mounts#point3.7.8.4 Mounts])
     17 * ([wiki:System-info-Network#point3.7.8.5 Network])
     18 * ([wiki:Ram#point3.7.8.5 Ram])
     19 * ([wiki:System-Infos#point3.7.8.6 System Infos])
     20
     21[[br]]
     22
  • wiki/pages/it/System-Infos

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8.6 System Info''' [=#point3.7.8.6] ([wiki:System-Info#point3.7.8.6 System Infos (Back])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/System-Info-System-Infos.jpg)]][[BR]]
     7>
     8> here you can view system wide information.
     9
     10[[br]]
     11
     12 * ([wiki:CPU#point3.7.8.6.1 Cpu])
     13 * ([wiki:Memory#point3.7.8.6.2 Memory])
     14 * ([wiki:MTD#point3.7.8.6.3 MTD])
     15 * ([wiki:Module#point3.7.8.6.4 Module])
     16 * ([wiki:Devices#point3.7.8.6.5 Devices])
     17 * ([wiki:Swap#point3.7.8.6.6 Swap])
     18 * ([wiki:Top#point3.7.8.6.7 Top])
     19 * ([wiki:prozesslist#point3.7.8.6.8 prozesslist])
     20 * ([wiki:USB#point3.7.8.6.9 USB])
     21
     22[[br]]
     23
  • wiki/pages/it/System-Status

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8.1 System Status''' [=#point3.7.8.1] ([wiki:System-Info#point3.7.8 System Info (Back])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/System-Status.jpg)]][[br]]
     7>
     8Here you can view the system status of the receiver.
     9
     10[[br]]
     11
     12
     13[[br]]
  • wiki/pages/it/System-Update

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.5.7 System Update''' [=#point3.5.7] ([wiki:Interface-Operation#point3.5 System (Back)])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/system-System_Update.jpg)]][[BR]]
     7>
     8>here you can proform a system update
     9
     10[[br]]
     11
     12
     13 ||'''Flashupdate (Online):''' ||Update flashmemory from online Library.||
     14 ||'''Flashupdate (tmp):''' ||Update Flashmemory from tmp.||
     15 ||'''USBupdate (tmp):''' ||Update USB device from tmp.||
     16 
     17 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     18 
     19[[br]]
  • wiki/pages/it/System-info-Network

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8.4 Network''' [=#point3.7.8.4] ([wiki:System-Info#point3.7.8 System Info (Back)])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/System-info-Network.jpg)]][[br]]
     7>
     8Here you can view info on you network interface.
     9
     10[[br]]
     11
     12
     13[[br]]
  • wiki/pages/it/Testpage

    r39712 r39721  
     1[[TranslatedPages]]
     2
     3
     4Test code:
     5
     6
     7[[CollapsibleStart]]
     8
     9nested text.
     10
     11[[CollapsibleEnd]]
     12
     13
     14
     15
  • wiki/pages/it/Timeshift-Settings

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.7 Timeshift Settings''' [=#point3.6.7] ([wiki:Interface-Operation#point3.6 Settings (Back)])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/IT/Timeshift_Settings.jpg)]][[BR]]
     8>
     9
     10Here you can edit your timeshift settings
     11
     12[[br]]
     13
     14 ||'''Timeshift Type''' ||Select the operation mode of the timeshift function.||
     15 ||'''After Timshift:''' ||If timshift is stopped what function that should the reciever do.||
     16 ||'''Ask on channel switch:''' ||Ask what to do with the timeshift file on channel change.||
     17 ||'''Use Numeric Keys:''' ||use the numeric keys to control the timeshift skip and jump functions.||
     18 
     19 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     20 
     21[[br]]
     22----
  • wiki/pages/it/prozesslist

    r39712 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.7.8.6.8 Prozesslist''' [=#point3.7.8.6.8] ([WikiStart#point3.7.8.6 System Infos (Back])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/IT/prozesslist.jpg)]][[br]]
     7>
     8Here you can view the detailed Process info.
     9
     10[[br]]
     11
     12
     13[[br]]
  • wiki/pages/pl/VFDisplay

    r39681 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.5.6 VFDisplay''' [=#point3.5.6] ([wiki:Interface-Operation#point3.5 System (Back)])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/PL/system-VFDisplay.jpg)]][[BR]]
     7>
     8>Here you can edit the settings of the VFDisplay
     9
     10[[br]]
     11
     12
     13 ||'''Brightness''' || use the D-pad keys to adjust the brightness of the VFD.||
     14 ||'''Standby Brightness:''' || use the D-pad keys to adjust the brightness of the VFD.||
     15 ||'''Show in VFD:''' ||What to show in the VFDisplay when the system is running.||
     16 ||'''Show in Standby:''' ||What to show in the VFDisplay when the system is in standby.||
     17 ||'''Behavior at Recording:''' ||What to show in the VFDisplay when the system is recording.||
     18 ||'''LED Brightness Running''' || set the brightness of the led when the system is running.||
     19 ||'''LED Brightness Standby'''  || set the brightness of the led when the system is in standby.||
     20 
     21 To __"Store"__ the settings Exit from the EPG Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     22 
     23[[br]]
  • wiki/pages/pl/Versions

    r39681 r39721  
    342342 - Library revised
    343343 - Panel Functions in the Image Settings
     344 - Shifted Flash labels down
     345 -  Installed Screenshoot with video -
     346 - Mediatheques local search built
     347 - Complete base image was updated
     348 - Vizcam, mod oscam and oscam away YMOD
     349 - Web browser favorites update
     350 - Fix mute button
     351 - Marker autoseek
     352 - Fix gbox config
     353 - Fixed TPK updates
     354 - Update the channel lists for TPK and default list
     355 - Adapted picons for new stations
     356 - Skins adapted for new functions in the menus
     357
     358[[br]]
     359
     360----
     361'''Titan 1.50iboot'''
     362----
     363The following ticket fixed:
     364 
     365 - Internal Player - rewind does not work
     366 - General - When updating the 520 one also sees the 5200 updates
     367 - General - Web interface rc rc code image and adaptable boxes mipsel for both missing
     368 - Audio - ac3 sound <- in tv mode has no influence lautstärle leveler
     369 - LCD - Display AM 5000
     370 - Ci - ci modules
     371 - Media Center - Desktop Wallpaper Media Center missing
     372 - General - plug-ins and settings will be lost after each update
     373 - External player - volume leveler no effective
     374 - Gui - showiframe still does not work
     375 - Tuner - Second Tuner ( plug-in) will not appear in the 5200 / recognized
     376 - General - Press CH up / down reversed
     377 - component1 - xupnpd as a DLNA server
     378 - Skins - ... infobar closed from tobayer
     379 - Gui - hdd format it will not be displayed dateisyteme closed
     380 - TitanNit - no record in standby
     381 - System - NTFSwrite parameter resume in closed settings
     382 - General - The wysiwyg display at the wiki editing brings erroneous entries
     383 - General - Protection of minors has no effect
     384 - General - [ Am520 ] flashing display for remote control operation
     385 - General - shift caused by transmitters reboot the box
     386 - General - scripts before and after shooting
     387 - System - menu item will change color saturation color temperature
     388 - General - Recovery time ( recoverrun ) is not saved
     389 - TiThek - No thumbnails of each video in the TiThek
     390 - General - Review Dutch translation
     391
     392[[br]]
     393
     394----
     395'''Titan 1.53iboot'''
     396----
     397The following ticket fixed:
     398 
     399all
     400 - Revised channel lists
     401 - Reworked skins
     402 - LCD perl fixed
     403 - Fix oscam nightly
     404 - online Library extended (FilmOn TV)
     405 - Improved channel search
     406 - Picon adapted and added new channels
     407 - deleted the 320x240 Picon Samsung LCD, please the X-Light install transparent.
     408   
     409mipsel
     410 - WLAN Fixed Atemio 5200
     411 - Allow for e2 Telnet and FTP Atemio 5200
     412
     413----
     414'''Titan 1.55iboot'''
     415----
     416Changelog:
     417 
     418 - Added language files
     419 - Fixed Skins
     420 - Fixed Library (eg, rtl, RTL2, Super RTL, rtlnitro, ntv, vox, etc.) and added new hoster and inserted an improved search function
     421 - Improved web interface (added online and off line help)
     422 - Added IP boxes
     423 - Added Ufs913
     424 - Extended transponder and Settings
     425 - Add PIP and installed Oled Skins for Atemio Nemesis
     426 - EMU installation removed in Flash and configs extended
  • wiki/pages/pl/Video-Player

    r39681 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.2.2 Video Player''' [=#point3.2.2]([wiki:Interface-Operation#point3.2 Media Center (Back)])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/PL/Video_Player.jpg)]][[BR]]
     8>
     9>here you can play movies.
     10
     11
     12
     13[[br]]
     14----
     15 '''Coloured Button's Functions'''
     16
     17 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
     18 please see below for more info on the functions of these buttons:.
     19 
     20 ||'''Red Button: (Sorting)''' ||Set the sort method for the files listed in the file list display.||
     21 ||'''Green Button: (Filelist-Mode)''' ||Switch between filelist mode and playlist mode.||
     22 ||'''Yellow Button: (Random)''' ||select random play mode.||
     23 ||'''Blue Button: (Repeat)''' ||Select Repeat play mode.||
     24 ||'''Menu Button: (Menu)''' ||This will show an advanced settings menu for the media player see below for more info on the functions contained with in this menu.||
     25
     26----
     27 '''Advanced Media Player Menu'''
     28
     29[[br]]
     30
     31 videos:
     32 ||'''Sort:''' ||Set the sort method for the files listed in the file list display.||
     33 ||'''View:''' ||Switch between filelist mode and playlist mode.||
     34 ||'''MediaDB Autoscan:''' ||Auto scan MediaDb in Background.||
     35 ||'''Default Directory:''' ||Set the default directory to display when the media player opens.||
     36 ||'''Use Last Directory:''' ||open the last used directory when the media player opens.||
     37 ||'''Backdrop Interval:''' ||sets the change time of the background picture||
     38
     39 '''Coloured Button's Functions'''
     40
     41
     42 ||'''Red Button: (Network)''' ||Set the sort method for the files listed in the file list display.||
     43 ||'''Green Button: (Edit)''' ||Switch between filelist mode and playlist mode.||
     44
     45----
     46
  • wiki/pages/pl/Video-Settings

    r39681 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.6.14 Video Settings''' [=#point3.6.14] ([wiki:Interface-Operation#point3.6 Settings (Back)])
     4>
     5>Menu Picture place holder:
     6>
     7>[[Image(source:/wiki/Wiki-Pictures/PL/Video_Settings.jpg)]][[BR]]
     8>
     9
     10here you can change your video display settings select a menu item and use the d pad left and right to adjust the setting see a list of a available settigs below.
     11
     12[[br]]
     13
     14 ||'''Brightness:''' ||Here you can edit the brightness of the display.||
     15 ||'''Contrast:''' ||Here you can edit the Contrast of the display.||
     16 ||'''Tint:''' ||Here you can edit the Tint of the display.||.||
     17 
     18 To __"Store"__ the settings Exit from the Video Settings Menu by pressing __"OK"__ or press __"Exit"__ to cancel changes.
     19 
     20[[br]]
     21----
     22
     23 '''Coloured Button's Functions"
     24
     25 The __"Coloured Buttons"__ along the bottom of the display bring up additional menus and options with in the epg settings menu.
     26 please see below for more info on the functions of these buttons:.
     27 
     28 ||'''Red Button: (Default)''' ||This will reset the Video settings to the default setting.||
  • wiki/pages/pl/WLAN-Settings

    r39681 r39721  
     1[[TranslatedPages]]
     2>----
     3>'''3.5.4.2 WLAN Settings''' [=#point3.5.4.2] ([wiki:Network#point3.5.4 network (Back])
     4>
     5>
     6>[[Image(source:/wiki/Wiki-Pictures/PL/WLAN-Settings.jpg)]]br]]
     7>
     8Here you can check and adjust the settings for your wireless interface.
     9
     10[[br]]
     11
     12
     13 ||'''SSID On Boot:''' ||Autostart the wireless interface on startup.||
     14 ||'''SSID:''' || this shows the current SSID press the __"text"__ button to edit.||
     15 ||'''Type:''' ||Set the security method.||
     16 ||'''KEY:''' ||this shows the current security key press the __"text"__ button to edit.||
     17