Changeset 43921 for wiki

wiki/pages/CamelCase

-                      r43268
+                      r43921
 = !CamelCase
 New wiki links are automatically created when concatenating capitalized words, such that for example the word 'Camel' and the word 'Case' concatenated form a link to this CamelCase page.
 !CamelCase is the original wiki convention for creating hyperlinks, with the additional requirement that the capitals are followed by a lower-case letter; hence “AlabamA” and “ABc” will not be links.
+!CamelCase is the original wiki convention for creating hyperlinks, with the additional requirement that the capitals are followed by a lower-case letter; hence "AlabamA" and "ABc" will not be links.
 == Customizing the Wiki behavior
 While Trac remains faithful to the original Wiki style, it provides a number of ways to accommodate users with different preferences:
  * To prevent the creation of a new link of a camel-cased word, prefix with '!': `!CamelCase`.
  * To ignore links to missing pages when the link is written using the CamelCase style, that word can instead be replaced by a gray link followed by a question mark. This is useful in cases when CamelCase style is used to name code artifacts like class names and there's no corresponding page for them. This option can be set in `ignore_missing_pages` in the [wiki:TracIni#wiki-section "[wiki]"] section of TracIni.
  * There's an option (`split_page_names` in the  [wiki:TracIni#wiki-section "[wiki]"] section of TracIni) to automatically insert space characters between the words of a CamelCase link when rendering the link.
+ * To prevent the creation of a new link of a camel-cased word, prefix with an exclamation mark (`!`): `!CamelCase`.
+ * To ignore links to missing pages when the link is written using the CamelCase style, that word can instead be replaced by a gray link followed by a question mark. This is useful in cases when CamelCase style is used to name code artefacts like class names and there is no corresponding page for them. This option can be set in `ignore_missing_pages` in the [wiki:TracIni#wiki-section "[wiki]"] section of TracIni.
+ * To automatically insert space characters between the words of a CamelCase link when rendering the link, use `split_page_names` in the [wiki:TracIni#wiki-section "[wiki]"] section of TracIni.
  * Creation of explicit Wiki links is also easy, see WikiPageNames for details.
  * Wiki formatting can be disabled completely in some places, for example when rendering commit log messages. See `wiki_format_messages` in the [wiki:TracIni#changeset-section "[changeset]"] section of TracIni.

wiki/pages/InterMapTxt

-                      r38413
+                      r43921
 {{{
+PEP     http://www.python.org/peps/pep-$1.html                                       # Python Enhancement Proposal
+PEP     http://www.python.org/dev/peps/pep-$1/    # Python Enhancement Proposal
+PythonBug    http://bugs.python.org/issue$1       # Python Issue #$1
+Python-issue http://bugs.python.org/issue$1       # Python Issue #$1
+PythonWiki    https://wiki.python.org/moin/       # Python Wiki
 Trac-ML  http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/ # Message $1 in Trac Mailing List
 trac-dev http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/   # Message $1 in Trac Development Mailing List
+apidoc http://www.edgewall.org/docs/trac-trunk/html/$1.html # $1 in the API documentation for Trac
+apiref http://www.edgewall.org/docs/trac-trunk/epydoc/$1.html # $1 in the Epydoc API reference for Trac
+bitten   http://bitten.edgewall.org/intertrac/    # Bitten's Trac
 Mercurial http://www.selenic.com/mercurial/wiki/index.cgi/ # the wiki for the Mercurial distributed SCM
+RFC       http://rfc.net/rfc$1.html # IETF's RFC $1
+hg        http://www.selenic.com/hg/rev/$1?rev=$2          # Changeset $1 $2 in Mercurial repository
+hg-issue  http://mercurial.selenic.com/bts/issue           # Issue $1 in Mercurial BTS
+RFC       http://tools.ietf.org/html/rfc$1          # IETF's RFC $1
+ISO       http://en.wikipedia.org/wiki/ISO_         # ISO Standard $1 in Wikipedia
+kb        http://support.microsoft.com/kb/$1/en-us/ # Article $1 in Microsoft's Knowledge Base
+pypi        http://pypi.python.org/pypi/   # $1 package in the Python Package Index
+CheeseShop  http://pypi.python.org/pypi/           # $1 package in the Python Package Index
+peak        http://peak.telecommunity.com/DevCenter/     # $1 in Python Enterprise Application Kit's Wiki
+setuptools-issue http://bugs.python.org/setuptools/issue # issue$1 in legacy Setuptools tracker
+pypa-setuptools-issue https://bitbucket.org/pypa/setuptools/issue/ # issue #$1 in BitBucket Setuptools tracker
+SQLite      http://www.sqlite.org/cvstrac/wiki?p=$1     # $1 page in the CvsTrac for SQLite
+SQLiteTkt   http://www.sqlite.org/cvstrac/tktview?tn=$1 # Ticket $1 in the CvsTrac for SQLite
+mysql-bugs  http://bugs.mysql.com/bug.php?id=  # Bug #$1 in MySQL's bug database
+mysql-issue http://bugs.mysql.com/bug.php?id=  # Bug #$1 in MySQL's bug database
+MODPYTHON          http://issues.apache.org/jira/browse/MODPYTHON- # Issue $1 in mod_python's JIRA instance
+mod-python-issue   http://issues.apache.org/jira/browse/MODPYTHON- # Issue $1 in mod_python's JIRA instance
+SvnWiki     http://www.orcaware.com/svn/wiki/                        # Subversion Wiki
+svnissue    http://subversion.tigris.org/issues/show_bug.cgi?id=     # Subversion issue #$1
+svn-issue   http://subversion.tigris.org/issues/show_bug.cgi?id=     # Subversion issue #$1
+svncset     http://svn.collab.net/viewvc/svn?view=revision&revision= # Subversion [$1]
+mod-wsgi    http://code.google.com/p/modwsgi/wiki/                 # mod_wsgi Wiki on Google Code
+mod-wsgi-issue  http://code.google.com/p/modwsgi/issues/detail?id= # mod_wsgi Issue Tracker on Google Code
+chromium-issue  http://code.google.com/p/chromium/issues/detail?id=
+Django      http://code.djangoproject.com/intertrac/ # Django's Trac
+AgileTrac   http://www.agile-trac.org/intertrac/     # Plugin adding Iterations to Trac
+CreoleWiki   http://wikicreole.org/wiki/
+Creole1Wiki  http://wikicreole.org/wiki/
+Creole2Wiki  http://wiki.wikicreole.org/
+MediaWiki    http://www.mediawiki.org/wiki/
+SO  http://stackoverflow.com/questions/ # Question $1 in StackOverflow
+Transifex https://www.transifex.com/projects/p/trac/
+kwquery      /query?group=status&keywords=~  # Custom query for tickets matching keyword $1
+#
 …
 DebianBug        http://bugs.debian.org/
 DebianPackage    http://packages.debian.org/
+DebianPTS        http://packages.qa.debian.org/
 Dictionary       http://www.dict.org/bin/Dict?Database=*&Form=Dict1&Strategy=*&Query=
 Google           http://www.google.com/search?q=
+lmgtfy           http://lmgtfy.com/?q= # Well, just search for "$1", follow the link to see how to do it...
 GoogleGroups     http://groups.google.com/group/$1/msg/$2        # Message $2 in $1 Google Group
+gdiscussion      https://groups.google.com/d/topic/$1/$2/discussion # Discussion $2 in $1 Google
+gmessage         https://groups.google.com/d/msg/$1/$2 # Message $2 in $1 Google Group
+gforum           https://groups.google.com/forum/#!forum/$1 # Forum $1 in Google Groups
 JargonFile       http://downlode.org/perl/jargon-redirect.cgi?term=
 MeatBall         http://www.usemod.com/cgi-bin/mb.pl?
 MetaWiki         http://sunir.org/apps/meta.pl?
 MetaWikiPedia    http://meta.wikipedia.org/wiki/
+MoinMoin         http://moinmoin.wikiwikiweb.de/
+MoinMoin         http://moinmo.in/
+TracHacks        http://trac-hacks.org/wiki/
+OSM              http://www.openstreetmap.org/wiki/
 WhoIs            http://www.whois.sc/
 Why              http://clublet.com/c/c/why?
 c2Wiki             http://c2.com/cgi/wiki?
+c2Wiki           http://c2.com/cgi/wiki?
 WikiPedia        http://en.wikipedia.org/wiki/
 }}}
+----
+See also: InterWiki, InterTrac

wiki/pages/InterTrac

-                      r38413
+                      r43921
 == Link Syntax
 Simply use the name of the other Trac environment as a prefix, followed by a colon, ending with the resource located in the other environment.
+Simply use the name of the other Trac environment as a prefix, followed by a colon, ending with the resource located in the other environment:
 {{{
 …
 That target environment name is either the real name of the environment or an alias for it.
 The aliases are defined in `trac.ini` (see below).
+The aliases are defined in the `trac.ini` file, see below.
 The prefix is case insensitive.
 If the InterTrac link is enclosed in square brackets (like `[th:WikiExtrasPlugin]`), the InterTrac prefix is removed in the displayed link like a normal link resolver would be, ie the above would be displayed as `WikiExtrasPlugin`.
+If the InterTrac link is enclosed in square brackets, like `[th:WikiExtrasPlugin]`, the InterTrac prefix is removed in the displayed link like a normal link resolver would be, ie the above would be displayed as `WikiExtrasPlugin`.
 For convenience, there's also some alternative short-hand form, where one can use an alias as an immediate prefix for the identifier of a ticket, changeset or report, eg `#T234`, `[T1508]`, `[trac 1508]`.
+For convenience, there is also an alternative short-hand form, where an alias can be used as an immediate prefix for the identifier of a ticket, changeset or report, eg `#T234`, `[T1508]`, `[trac 1508]`.
 == Examples
 It is necessary to setup a configuration for the InterTrac facility.
 This configuration has to be done in the TracIni file, `[intertrac]` section.
+It is necessary to set up a configuration for the InterTrac facility.
+This configuration has to be done in the TracIni file, `[intertrac]` section, for example:
-Example configuration:
 {{{#!ini
 [intertrac]
 …
 This can be a relative URL in case that Trac environment is located on the same server.
 The `.title` information will be used for providing an useful tooltip when moving the cursor over an InterTrac links.
+The `.title` information is used in a tooltip, ie when hovering the cursor over an InterTrac link.
 Now, given the above configuration, one could create the following links:

wiki/pages/InterWiki

-                      r38413
+                      r43921
 An InterWiki link can be used for referring to a Wiki page located in another Wiki system, and by extension, to any object located in any other Web application, provided a simple URL mapping can be done.
 At the extreme, InterWiki prefixes can even be used to simply introduce links to new protocols, such as `tsvn:` used by [trac:TortoiseSvn TortoiseSvn].
+InterWiki prefixes can even be used to simply introduce links to new protocols, such as `tsvn:` used by [trac:TortoiseSvn TortoiseSvn].
 == Link Syntax
 …
 '''Example:'''
 {{{
+{{{#!ini
 [interwiki]
 MeatBall = http://www.usemod.com/cgi-bin/mb.pl?
 …
 Then,
  * `MoinMoin:InterWikiMap` should be rendered as MoinMoin:InterWikiMap and the ''title'' for that link would be "!InterWikiMap in !MoinMoin"
  * `Trac-ML:4346` should be rendered as Trac-ML:4346 and the ''title'' for that link would be "Message 4346 in Trac Mailing List"
+ * `MoinMoin:InterWikiMap` should be rendered as MoinMoin:InterWikiMap and the ''title'' for that link would be "!InterWikiMap in !MoinMoin".
+ * `Trac-ML:4346` should be rendered as Trac-ML:4346 and the ''title'' for that link would be "Message 4346 in Trac Mailing List".
 ----

wiki/pages/TicketQuery

-                      r40558
+                      r43921
   [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
 Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter:
+If you wish to receive only the number of defects that match the query, use the `count` parameter:
 {{{
 [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
 …
   [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
+A graphical use of the macro is with the `format=progress` attribute:
+{{{
+[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
+}}}
+For example for one of the upcoming milestones, bars are shown by ticket type:
+[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
 ----
 See also: TracQuery, TracTickets, TracReports, TracGuide

wiki/pages/TracAccessibility

-                      r40558
+                      r43921
 = Accessibility Support in Trac =
+= Accessibility Support in Trac
 Not every user has a graphic environment with a mouse or other pointing device. Some users rely on keyboard, alternative keyboard or voice input to navigate links, activate form controls, etc. In a Trac session, users can use devices other than a pointing device by enabling keyboard shortcuts through the [/prefs/keybindings Keyboard Shortcuts] preferences panel.
+Not every user has a graphic environment with a mouse or other pointing device. Some users rely on keyboard, alternative keyboard or voice input to navigate links and activate form controls. In a Trac session, users can use devices other than a pointing device by enabling keyboard shortcuts through the [/prefs/keybindings Keyboard Shortcuts] preferences panel.
 Trac supports accessibility keys for the most common operations. The access keys differ by browser and the following work for several browsers, but see [http://en.wikipedia.org/wiki/Access_key#Access_in_different_browsers access in different browsers] for more details.
+Trac supports accessibility keys for the most common operations. The access keys differ by browser and the following work for several browsers:
  - on Linux platforms, press any of the keys listed below in combination with the `<Alt>` key
  - on a Mac, use the `<Ctrl>` + `<Opt>` key instead
  - on Windows, you need to hit `<Shift> + <Alt> + <Key>`. This works for the most common browsers, such as Firefox, Chrome, Safari and Internet Explorer
+== Global Access Keys ==
+Also see [wikipedia:Access_key#Access_in_different_browsers access in different browsers] for more details.
+== Global Access Keys
  * `1` - WikiStart
 …
  * `f` - Search
+== TracBrowser Access Keys
+* `j` - Select next entry
+* `k` - Select previous entry
+* `o` - Expand folder/view file
+* `<Enter>` - Expand folder/view file
 ----

wiki/pages/TracAdmin

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

wiki/pages/TracBackup

-                      r40558
+                      r43921
 [[TracGuideToc]]
 Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command in [wiki:TracAdmin trac-admin].
+Trac backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the database. Backups can be created using the `hotcopy` command in [wiki:TracAdmin trac-admin].
 '''Note''': Trac uses the `hotcopy` nomenclature to match that of [http://subversion.tigris.org/ Subversion], to make it easier to remember when managing both Trac and Subversion servers.
 …
 Please note, the `hotcopy` command will not overwrite a target directory and when such exists, the operation ends with an error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].
 === Restoring a Backup
+== Restoring a Backup
 To restore an environment from a backup, stop the process running Trac, ie the Web server or [wiki:TracStandalone tracd], restore the contents of your backup (path/to/backupdir) to your [wiki:TracEnvironment project environment] directory and restart the service.
 …
 psql -U <user> -d <database> -f postgresql.dump
 }}}
 The `<database>` option is the same as the [TracEnvironment#DatabaseConnectionStrings database connection string] in the `[trac]` `database` option of //trac.ini//.

wiki/pages/TracBatchModify

r40558	r43921
2	2	[[TracGuideToc]]
3	3
4		Trac supports modifying a batch of tickets in one request from [TracQuery custom query] results .
	4	Trac supports modifying a batch of tickets in one request from [TracQuery custom query] results.
5	5
6	6	To perform a batch modification, select the tickets you wish to modify and set the new field values using the section underneath the query results.

wiki/pages/TracBrowser

r40558	r43921
27	27	For Subversion, this list contains by default the top-level trunk directory and sub-directories of the top-level branches and tags directories (`/trunk`, `/branches/`, and `/tags/`). This can be [TracIni#svn-section configured] for more advanced cases.
28	28
29		If you're using a Javascript enabled browser, you'll be able to expand and collapse directories in-place by clicking on the arrow head at the right side of a directory. Alternatively, the [trac:Trac~~Keys~~ keyboard] can also be used for this:
	29	If you're using a Javascript enabled browser, you'll be able to expand and collapse directories in-place by clicking on the arrow head at the right side of a directory. Alternatively, the [trac:TracAccessibility keyboard] can also be used for this:
30	30	- use `j` and `k` to select the next or previous entry, starting with the first
31	31	- `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected

wiki/pages/TracChangeLog

-                      r40558
+                      r43921
+== 1.2.x Releases
+=== 1.2 'Hermes'
+//(November 5, 2016)//
+Trac 1.2 is the first major release of Trac in more than 4 years.
+The following are some highlights from the release:
+* Extensible notification system ([trac:#3517])
+* Notification preference panel ([trac:#4056])
+* Usernames replaced with full names ([trac:#7339])
+* Restyled ticket changelog ([trac:#11835])
+* Workflow controls on the //New Ticket// page ([trac:#2045])
+* Editable wiki page version comments ([trac:#6573])
+* Datetime custom fields ([trac:#1942])
+For more information see the [trac:wiki:TracDev/ApiChanges/1.2 API changes] and the detailed
+release notes for [[trac:wiki:TracDev/ReleaseNotes/1.2#DevelopmentReleases | 1.2]] and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.8 through 1.0.13]]
+(as 1.2 contains all the fixes done for 1.0.8 through 1.0.13).
+[trac:source:/tags/trac-1.2 View Tag] | [trac:milestone:1.2 View Milestone]
 == 1.1.x Releases
 // 1.1.x releases are development releases leading eventually to Trac 1.2. See them as kind of snapshots of [trac:source:trunk].
 ** No guarantees of feature and API compatibility is made from one 1.1.x release to the next. //
+=== 1.2rc1
+//(September 14, 2016)//
+The first Trac 1.2 release candidate is the culmination of nearly 4 years of development.
+Highlights of the changes since 1.1.6:
+ - Pygments lexer options can be specified as [WikiProcessors WikiProcessor] arguments and defaults can be set in the environment configuration ([trac:#5654]).
+ - Usernames are replaced with full names when `[trac]` `show_full_names` is true ([trac:#7339]).
+ - Enum tables on the Ticket Admin pages can be reordered by drag and drop. ([trac:#11682]).
+ - Ticket changelog is restyled and has a new //Show comments// preference ([trac:#11835]).
+ - Authentication cookies can be shared across subdomains when `[trac]` `auth_cookie_domain` is configured ([trac:#12251]).
+For more information see the [trac:wiki:TracDev/ApiChanges/1.1 API changes] and the detailed
+release notes for [[trac:wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases | 1.2rc1]] and [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.8 through 1.0.13]]
+(as 1.2rc1 contains all the fixes done for 1.0.8 through 1.0.13).
+[trac:source:/tags/trac-1.2rc1 View Tag] | [trac:milestone:1.2 View Milestone]
 === 1.1.6
 …
 [trac:source:/tags/trac-1.1.1 View Tag] | [trac:milestone:1.1.1 View Milestone]
+== 1.0.x Releases ==
+== 1.0.x Releases
+=== 1.0.13
+//(September 11, 2016)//
+Trac 1.0.13 provides around a dozen bug fixes and minor
+enhancements. The following are some highlights:
+ - Use locale environment variables to negotiate locale
+   on console ([trac:#12418]).
+ - Fixed using incorrect revisions when downloading a zip
+   file via browser page from Git repository ([trac:#12557]).
+[trac:source:/tags/trac-1.0.13 View Tag] | [trac:milestone:1.0.13 View Milestone]
+=== 1.0.12
+//(July 4, 2016)//
+Trac 1.0.12 provides around 20 bug fixes and minor enhancements. The following are some highlights:
+ - Reconnect to PostgreSQL server after restarting it
+   ([trac:#4984]).
+ - Workflow actions on the batch modify form are sorted
+   by the default attribute ([trac:#12447]).
+ - Fixed Pygments stylesheet not found when style name
+   contained a dash ([trac:#12505]).
+ - Fixed incorrect parsing of projects list file by
+   `GitwebProjectsRepositoryProvider` ([trac:#12518]).
+ - `TracIni` macro displays option documentation as
+   multi-line rather than one-liner ([trac:#12522]).
+ - Fixed regression with `GitConnector` leading to
+   `IOError: Too many open files` ([trac:#12524]).
+[trac:source:/tags/trac-1.0.12 View Tag] | [trac:milestone:1.0.12 View Milestone]
+=== 1.0.11
+//(May 7, 2016)//
+Trac 1.0.11 provides more than 30 bug fixes and minor
+enhancements. As in 1.0.10, an area of focus has been to
+eliminate tracebacks in the logs due to invalid requests.
+The following are some additional highlights:
+ - Fixed resetting //Oldest first// after auto-preview of
+   ticket change log ([trac:#12381]).
+ - Trac is now distributed as wheel package ([trac:#12391]).
+ - Fixed database exceptions in query system when
+   ''milestones/versions/enums'' are not defined and a custom
+   field of the same name is added ([trac:#12399]).
+ - Custom field //milestone// was not shown when
+   standard //milestone// field was hidden ([trac:#12400]).
+ - Query system now sorts by `enum.value` rather than
+   `ticket.type` for `order=type` ([trac:#12402]).
+ - Added support for Babel 2.3.2 (2.3.0 and 2.3.1 should
+   not be used)  ([trac:#12445]).
+[trac:source:/tags/trac-1.0.11 View Tag] | [trac:milestone:1.0.11 View Milestone]
+=== 1.0.10
+//(February 20, 2016)//
+Trac 1.0.10 provides more than 30 bug fixes and minor enhancements. Two areas of focus
+have been fixing test failures on Windows and eliminating tracebacks in the logs due to
+invalid requests.
+See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.10]].
+[trac:source:/tags/trac-1.0.10 View Tag] | [trac:milestone:1.0.10 View Milestone]
+=== 1.0.9
+//(September 10, 2015)//
+Trac 1.0.9 provides more than a dozen minor fixes and enhancements, including significantly reduced memory usage by the Git repository connector.
+See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.9]].
+[trac:source:/tags/trac-1.0.9 View Tag] | [trac:milestone:1.0.9 View Milestone]
+=== 1.0.8
+//(July 24, 2015)//
+Trac 1.0.8 fixes a regression introduced in Trac 1.0.7: the session
+for an authenticated username containing non-alphanumeric characters
+could not be retrieved, resulting in the user being denied access to
+every realm and resource ([trac:#12129]).
+See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.8]].
+[trac:source:/tags/trac-1.0.8 View Tag] | [trac:milestone:1.0.8 View Milestone]
 === 1.0.7
 …
  - Hyphen character can be used in !WikiProcessor parameter name ([trac:#12023]).
 See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.6]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.7]] (as 1.0.6 contains all the changes in 0.12.7).
+See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.6]] and [[trac:wiki:TracDev/ReleaseNotes/0.12#MaintenanceReleases | 0.12.7]] (as 1.0.6 also contains the changes in 0.12.7).
 [trac:source:/tags/trac-1.0.6 View Tag] | [trac:milestone:1.0.6 View Milestone]
 …
  - Images are not rendered in the timeline ([trac:#10751]).
  - Git tags are shown in the browser view ([trac:#11964]).
+ - Added support for `journal_mode` and `synchronous` pragmas in `sqlite:` database connection string ([trac:#11967]).
+ - Added support for `journal_mode` and `synchronous` pragmas
+   in `sqlite:` database connection string ([trac:#11967]).
 See the detailed release notes for [[trac:wiki:TracDev/ReleaseNotes/1.0#MaintenanceReleases | 1.0.5]].
 …
 === 0.12.7
 //(May 20, 2015)//
+//(July 12, 2015)//
 Trac 0.12.7 fixes a minor security issue, as well as a half dozen other minor issues:

wiki/pages/TracChangeset

-                      r40558
+                      r43921
+= Trac Changeset Module =
+= Trac Changeset Module
 [[TracGuideToc]]
+[[PageOutline(2-5,Contents,pullout)]]
 Trac has a built-in functionality for visualizing “diffs”, or changes to files.
+Trac has a built-in functionality for visualizing "diffs", or changes to files.
 There are different kinds of ''change sets''.  Some correspond to revisions made in the repositories, others aggregate changes made in several revisions. Ultimately, any kind of difference can be shown.
 …
 The changeset view consists of two parts, the ''header'' and the ''diff views''.
 == Changeset Header ==
+== Changeset Header
 The header shows an overview of the whole changeset.
 …
 The color legend is located below the header as a reminder.
 == Diff Views ==
+== Diff Views
 Below the header is the main part of the changeset, the diff view. Each file is shown in a separate section, each of which contains only the regions of the file that are affected by the changeset. There are two different styles to display the diffs: ''inline'' or ''side-by-side''. You can switch between the styles using the preferences form:
 …
  * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly.
 == The Different Ways to Get a Diff ==
+== The Different Ways to Get a Diff
 === Examining a Changeset ===
+=== Examining a Changeset
 When viewing a repository check-in, such as when following a changeset [wiki:TracLinks link] or a changeset event in the [wiki:TracTimeline timeline], Trac will display the exact changes made by the check-in.
 …
 There will be also navigation links to the ''Previous Changeset'' to and ''Next Changeset''.
 === Examining Differences Between Revisions ===
+=== Examining Differences Between Revisions
 Often you want to look at changes made on a file or on a directory spanning multiple revisions. The easiest way to get there is from the TracRevisionLog, where you can select the ''old'' and the ''new'' revisions of the file or directory, and then click the ''View changes'' button.
 === Examining Differences Between Branches ===
+=== Examining Differences Between Branches
 One of the core features of version control systems is the possibility to work simultaneously on different ''Lines of Developments'', commonly called “branches”. Trac enables you to examine the exact differences between such branches.
+One of the core features of version control systems is the possibility to work simultaneously on different ''Lines of Developments'', commonly called "branches". Trac enables you to examine the exact differences between such branches.
 Using the '''View changes ...''' button in the TracBrowser allows you to enter ''From:'' and ''To:'' path/revision pairs. The resulting set of differences consist of the changes that should be applied to the ''From:'' content to get to the ''To:'' content.
 …
 For convenience, it is possible to invert the roles of the ''old'' and the ''new'' path/revision pairs by clicking the ''Reverse Diff'' link on the changeset page.
 === Checking the Last Change ===
+=== Checking the Last Change
 Another way to examine changes is to use the ''Last Change'' link provided by the TracBrowser.

wiki/pages/TracEnvironment

-                      r40558
+                      r43921
 [[TracGuideToc]]
 [[PageOutline(2-5)]]
+[[PageOutline(2-5,Contents,pullout)]]
 Trac uses a directory structure and a database for storing project data. The directory is referred to as the environment.
+Trac uses a directory structure and a database for storing project data. The directory is referred to as the '''environment'''.
+Trac supports [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] databases. With PostgreSQL and MySQL you have to create the database before running `trac-admin initenv`.
 == Creating an Environment
 A new Trac environment is created using [TracAdmin#initenv trac-admin's initenv]:
+A new Trac environment is created using the [TracAdmin#initenv initenv] command:
 {{{#!sh
 $ trac-admin /path/to/myproject initenv
 }}}
 `trac-admin` will ask you for the name of the project and the database connection string, see below.
+`trac-admin` will ask you for the name of the project and the [#DatabaseConnectionStrings database connection string].
 === Useful Tips
 …
  - The user under which the web server runs will require file system write permission to the environment directory and all the files inside. Please remember to set the appropriate permissions. The same applies to the source code repository, although the user under which Trac runs will only require write access to a Subversion repository created with the BDB file system; for other repository types, check the corresponding plugin's documentation.
  - `initenv`, when using an svn repository, does not imply that trac-admin will perform `svnadmin create` for the specified repository path. You need to perform the `svnadmin create` prior to `trac-admin initenv` if you're creating a new svn repository altogether with a new Trac environment; otherwise you will see a message "Warning: couldn't index the repository" when initializing the environment.
+ - `initenv` does not create a version control repository for the specified path. If you wish to specify a default repository using optional the arguments to `initenv` you must create the repository first, otherwise you will see a message when initializing the environment: //Warning: couldn't index the default repository//.
  - Non-ascii environment paths are not supported.
- - Also, it seems that project names with spaces can be problematic for authentication, see [trac:#7163].
  - TracPlugins located in a [TracIni#inherit-section shared plugins folder] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are currently not loaded during creation, and hence, if they need to create extra tables for example, you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment] before being able to use it.
+ - TracPlugins located in a [TracIni#inherit-section shared plugins folder] that is defined in an [TracIni#GlobalConfiguration inherited configuration] are not loaded during creation, and hence, if they need to create extra tables for example, you'll need to [TracUpgrade#UpgradetheTracEnvironment upgrade the environment]. Alternatively you can avoid the need to upgrade the environment by specifying a configuration file at the time the environment is created, using the `--config` option. See TracAdmin#FullCommandReference for more information.
 {{{#!div style="border: 1pt dotted; margin: 1em"
 …
 == Database Connection Strings
 Trac supports [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] database backends. The default is SQLite, which is probably sufficient for most projects. The database file is then stored in the environment directory, and can easily be [wiki:TracBackup backed up] together with the rest of the environment.
+You will need to specify a database connection string at the time the environment is created. The default is SQLite, which is probably sufficient for most projects. The SQLite database file is stored in the environment directory, and can easily be [wiki:TracBackup backed up] together with the rest of the environment.
 Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded.
 …
 === PostgreSQL Connection String
 If you want to use PostgreSQL instead, you'll have to use a different connection string. For example, to connect to a PostgreSQL database on the same machine called `trac` for user `johndoe` with the password `letmein` use:
+The connection string for PostgreSQL is a bit more complex. For example, to connect to a PostgreSQL database named `trac` on `localhost` for user `johndoe` and password `letmein`, use:
 {{{
 postgres://johndoe:letmein@localhost/trac
 …
 }}}
-Note that with PostgreSQL you will have to create the database before running `trac-admin initenv`.
 See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL].
 Generally, the following is sufficient to create a database user named `tracuser` and a database named `trac`:
 …
 When running `createuser` you will be prompted for the password for the user 'tracuser'. This new user will not be a superuser, will not be allowed to create other databases and will not be allowed to create other roles. These privileges are not needed to run a Trac instance. If no password is desired for the user, simply remove the `-P` and `-E` options from the `createuser` command. Also note that the database should be created as UTF8. LATIN1 encoding causes errors, because of Trac's use of unicode. SQL_ASCII also seems to work.
 Under some default configurations (Debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user:
+Under some default configurations (Debian), run the `createuser` and `createdb` scripts as the `postgres` user:
 {{{#!sh
 $ sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
 …
 === MySQL Connection String
 The format of the MySQL connection string is similar to those for PostgreSQL, with the `postgres` scheme being replaced by `mysql`. For example, to connect to a MySQL database on the same machine called `trac` for user `johndoe` with password `letmein`:
+The format of the MySQL connection string is similar to those for PostgreSQL, with the `postgres` scheme being replaced by `mysql`. For example, to connect to a MySQL database on `localhost` named `trac` for user `johndoe` with password `letmein`:
 {{{
 mysql://johndoe:letmein@localhost:3306/trac
 …
 == Source Code Repository
 A single environment can be connected to more than one repository. However, by default Trac is not connected to any source code repository, and the ''Browse Source'' toolbar item will not be displayed.
+A single environment can be connected to more than one repository. However, by default Trac is not connected to any source code repository, and the ''Browse Source'' navigation item will not be displayed.
 There are many different ways to connect repositories to an environment, see TracRepositoryAdmin. A single repository can be specified when the environment is created by passing the optional arguments `repository_type` and `repository_dir` to the `initenv` command.
 …
 == Directory Structure
 An environment directory will usually consist of the following files and directories:
+An environment consists of the following files and directories:
  * `README` - Brief description of the environment.

wiki/pages/TracFastCgi

-                      r40558
+                      r43921
 [[PageOutline(2-5, Contents, floated)]]
 [http://www.fastcgi.com/ FastCGI] interface allows Trac to remain resident much like with [wiki:TracModPython mod_python] or [wiki:TracModWSGI mod_wsgi]. It is faster than external CGI interfaces which must start a new process for each request.  Additionally, it is supported by much wider variety of web servers.
+[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 a much wider variety of web servers.
 Note that unlike mod_python, FastCGI supports [http://httpd.apache.org/docs/suexec.html Apache SuEXEC], ie run with different permissions than the web server runs with. `mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect.
 …
 '''Note for Windows:''' Trac's FastCGI does not run under Windows, as Windows does not implement `Socket.fromfd`, which is used by `_fcgi.py`. If you want to connect to IIS, you may want to try [trac:TracOnWindowsIisAjp AJP]/[trac:TracOnWindowsIisAjp ISAPI].
+== Simple Apache configuration
+There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and
+`mod_fcgid` (preferred). The latter is more up-to-date.
+== Apache configuration
+There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and `mod_fcgid` (preferred). The latter is more up-to-date.
 The following sections focus on the FCGI specific setup, see also [wiki:TracModWSGI#ConfiguringAuthentication] for configuring the authentication in Apache.
 Regardless of which cgi module is used, be sure the web server has executable permissions on the cgi-bin folder. While FastCGI will throw specific permissions errors, mod_fcgid will throw an ambiguous error if this has not been done. Connection reset by peer: mod_fcgid: error reading data from FastCGI server.
+Regardless of which cgi module is used, be sure the web server has executable permissions on the cgi-bin folder. While FastCGI will throw specific permissions errors, mod_fcgid will throw an ambiguous error if this has not been done: `Connection reset by peer: mod_fcgid: error reading data from FastCGI server`.
 === Set up with `mod_fastcgi`
 `mod_fastcgi` uses `FastCgiIpcDir` and `FastCgiConfig` directives that should be added to an appropriate Apache configuration file:
 {{{
+{{{#!apache
 # Enable fastcgi for .fcgi files
 # (If you're using a distro package for mod_fcgi, something like
 …
 LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so
 }}}
 Setting `FastCgiIpcDir` is optional if the default is suitable. Note that the `LoadModule` line must be after the `IfModule` group.
+Configure `ScriptAlias` or similar options as described in TracCgi, but
+calling `trac.fcgi` instead of `trac.cgi`.
+Configure `ScriptAlias` or similar options as described in TracCgi, but calling `trac.fcgi` instead of `trac.cgi`.
 Add the following to the Apache configuration file (below the `FastCgiIpcDir` line) if you intend to set up the `TRAC_ENV` as an overall default:
 {{{
+{{{#!apache
 FastCgiConfig -initial-env TRAC_ENV=/path/to/env/trac
 }}}
 Alternatively, you can serve multiple Trac projects in a directory by adding this:
 {{{
+{{{#!apache
 FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects
 }}}
 …
 Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` instead of `trac.cgi`:
 {{{
+{{{#!apache
 ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.fcgi/
 }}}
 Note the slash at the end.
+To set up Trac environment for `mod_fcgid` it is necessary to use `DefaultInitEnv` directive. It cannot be used in `Directory` or `Location` context, so if you need to support multiple projects, try alternative environment setup below.
+{{{
+To set up Trac environment for `mod_fcgid` it is necessary to use `DefaultInitEnv` directive. It cannot be used in `Directory` or `Location` context, so if you need to support multiple projects, try the alternative environment setup below:
+{{{#!apache
 DefaultInitEnv TRAC_ENV /path/to/env/trac/
 }}}
 === alternative environment setup
 A better method to specify path to the Trac environment is to embed the path into `trac.fcgi` script itself. That doesn't require configuration of the server environment variables, works for both [trac:FastCgi] modules as well as for [http://www.lighttpd.net/ lighttpd] and CGI:
 {{{
+=== Alternative environment setup
+A better method to specify the 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:
+{{{#!python
 import os
 os.environ['TRAC_ENV'] = "/path/to/projectenv"
 }}}
 or:
 {{{
+{{{#!python
 import os
 os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
 …
 See [https://coderanger.net/~coderanger/httpd/fcgi_example.conf this fcgid example config] which uses a !ScriptAlias directive with trac.fcgi with a trailing / like this:
 {{{
+{{{#!apache
 ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/
 }}}
 == Simple Cherokee Configuration
 The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process.
+You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down.
+== Cherokee Configuration
+Configuring [http://cherokee-project.com/ Cherokee] with Trac is straightforward, if you spawn Trac as an SCGI process. You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down.
 First set up an information source in cherokee-admin with a local interpreter:
 …
 After doing this, we will just have to create a new rule managed by the SCGI handler to access Trac. It can be created in a new virtual server, trac.example.net for instance, and will only need two rules. The '''default''' one will use the SCGI handler associated to the previously created information source.
+The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''$TRAC_LOCAL/htdocs/'' (where $TRAC_LOCAL is a directory defined by the user or the system administrator to place local trac resources).
+Note:\\
+If the tracd process fails to start up, and cherokee displays a 503 error page, you might be missing the [http://trac.saddi.com/flup python-flup] package.\\
+Python-flup is a dependency which provides trac with SCGI capability. You can install it on debian based systems with:
+{{{
+The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''$TRAC_LOCAL/htdocs/'' (where $TRAC_LOCAL is a directory defined by the user or the system administrator to place local Trac resources).
+'''Note:''' If the tracd process fails to start up, and Cherokee displays a 503 error page, you might be missing the [http://trac.saddi.com/flup python-flup] package ([trac:#9903]). Python-flup is a dependency which provides Trac with SCGI capability. You can install it on Debian based systems with:
+{{{#!sh
 sudo apt-get install python-flup
 }}}
 == Simple Lighttpd Configuration
+== Lighttpd Configuration
 The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.lighttpd.net/ Lighttpd].
 …
 }}}
 Note that field values are different. If you prefer setting the environment variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, eg to `first.fcgi` and `second.fcgi`, and reference them in the above settings.
+Note that the field values are different. If you prefer setting the environment variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, eg to `first.fcgi` and `second.fcgi`, and reference them in the above settings.
 Note that the above will result in different processes in any event, even if both are running from the same `trac.fcgi` script.
+{{{
+#!div class=important
+'''Note''' It's very important the order on which server.modules are loaded, if mod_auth is not loaded '''BEFORE''' mod_fastcgi, then the server will fail to authenticate the user.
+{{{#!div class=important
+'''Note:''' The order in which the server.modules are loaded is very important: if mod_auth is not loaded '''before''' mod_fastcgi, then the server will fail to authenticate the user.
 }}}
 …
 }}}
 Note that Lighttpd (v1.4.3) stops if the password file doesn't exist.
 …
 The technique can be easily adapted for use with multiple projects by creating aliases for each of them, and wrapping the fastcgi.server declarations inside conditional configuration blocks.
+Also there is another way to handle multiple projects and it's to use TRAC_ENV_PARENT_DIR instead of TRAC_ENV and use global auth, let's see an example:
+Also there is another way to handle multiple projects and it uses `TRAC_ENV_PARENT_DIR` instead of `TRAC_ENV` as well as global authentication:
 {{{
 #  This is for handling multiple projects
 …
+                 )
 }}}
 For details about languages specification see [trac:TracFaq TracFaq] question 2.13.
 Other important information like the [wiki:TracInstall#MappingStaticResources mapping static resources advices] are useful for non-fastcgi specific installation aspects.
+]
 Relaunch Lighttpd and browse to `http://yourhost.example.org/trac` to access Trac.
 …
 Note about running Lighttpd with reduced permissions: If nothing else helps and trac.fcgi doesn't start with Lighttpd settings `server.username = "www-data"`, `server.groupname = "www-data"`, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.
 == Simple !LiteSpeed Configuration
+== !LiteSpeed Configuration
 The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed].
 …
 . Please make sure you have a working install of a Trac project. Test install with "tracd" first.
+. Create a Virtual Host for this setup. From now on we will refer to this vhost as !TracVhost. For this tutorial we will be assuming that your Trac project will be accessible via:
+. Create a Virtual Host for this setup. From now on we will refer to this vhost as !TracVhost. For this tutorial we will be assuming that your Trac project will be accessible via:
 {{{
 http://yourdomain.com/trac/
 }}}
+. Go "!TracVhost → External Apps" tab and create a new "External Application".
+. Go "!TracVhost → External Apps" tab and create a new "External Application":
 {{{
 Name: MyTracFCGI
 …
 Instances: 10
 }}}
+. Optional: If you need to use htpasswd based authentication. Go to "!TracVhost → Security" tab and create a new security Realm.
+{{{
+. Optional: If you need to use htpasswd based authentication. Go to "!TracVhost → Security" tab and create a new security Realm:
+ {{{
 DB Type: Password File
 Realm Name: MyTracUserDB               <--- any name you wish and referenced later
 User DB Location: /fullpathto/htpasswd <--- path to your htpasswd file
 }}}
+If you don’t have a htpasswd file or don’t know how to create the entries within one, go to http://sherylcanter.com/encrypt.php, to generate the user:password combos.
+. Go to "!PythonVhost → Contexts" and create a new FCGI Context.
+{{{
+ If you don’t have a htpasswd file or don’t know how to create the entries within one, go to http://sherylcanter.com/encrypt.php, to generate the user:password combos.
+. Go to "!PythonVhost → Contexts" and create a new FCGI Context:
+ {{{
 URI: /trac/                              <--- URI path to bind to python fcgi app we created
 Fast CGI App: [VHost Level] MyTractFCGI  <--- select the trac fcgi extapp we just created
+Fast CGI App: [VHost Level] MyTractFCGI  <--- select the Trac fcgi extapp we just created
 Realm: TracUserDB                        <--- only if (4) is set. select realm created in (4)
 }}}
+. Modify `/fullpathto/mytracproject/conf/trac.ini`
+{{{
+. Modify `/fullpathto/mytracproject/conf/trac.ini`:
+ {{{
 #find/set base_rul, url, and link variables
 base_url = http://yourdomain.com/trac/ <--- base url to generate correct links to
 …
 link = http://yourdomain.com/trac/     <--- link of graphic logo
 }}}
+. Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
+{{{
+http://yourdomain.com/trac/
+}}}
+== Simple Nginx Configuration
+Nginx is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately.
+. Restart !LiteSpeed: `lswsctrl restart`, and access your new Trac project at {{{http://yourdomain.com/trac/}}}.
+== Nginx Configuration
+[http://nginx.org/en/ Nginx] is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately.
 . Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32
  {{{
+ {{{#!nginx
     server {
         listen       10.9.8.7:443;
 …
 }}}
 . Modified trac.fcgi:
  {{{
+ {{{#!python
 #!/usr/bin/env python
 import os
 …
 }}}
 . reload nginx and launch trac.fcgi like that:
+. Reload nginx and launch trac.fcgi:
  {{{#!sh
 trac@trac.example ~ $ ./trac-standalone-fcgi.py
 …
 The above assumes that:
  * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory
  * `/home/trac/instance` contains a trac environment
+ * There is a user named 'trac' for running Trac instances and keeping Trac environments in its home directory
+ * `/home/trac/instance` contains a Trac environment
  * `/home/trac/htpasswd` contains authentication information
  * `/home/trac/run` is owned by the same group the nginx runs under
+ * `/home/trac/run` is owned by the same group the Nginx runs under
   * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`)
   * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time
 Unfortunately nginx does not support variable expansion in fastcgi_pass directive.
+  * and patch from [trac:#7239] is applied, or you'll have to fix the socket file permissions every time
+Unfortunately Nginx does not support variable expansion in fastcgi_pass directive.
 Thus it is not possible to serve multiple Trac instances from one server block.
 If you worry enough about security, run Trac instances under separate users.
 Another way to run Trac as a FCGI external application is offered in ticket #T6224
+Another way to run Trac as a FCGI external application is offered in [trac:#6224].
 ----
 See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
+See also: TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]

wiki/pages/TracGuide

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

wiki/pages/TracImport

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

wiki/pages/TracIni

-                      r40558
+                      r43921
 [[TracGuideToc]]
 [[PageOutline]]
+[[PageOutline(2-5,Contents,pullout)]]
 Trac is configured by editing the **`trac.ini`** file, located in the `<projectenv>/conf` directory. The `trac.ini` configuration file and its parent directory should be writable by the web server.
+Trac is configured through the **`trac.ini`** file, located in the `<projectenv>/conf` directory. The `trac.ini` configuration file and its parent directory should be writable by the web server.
 Trac monitors the timestamp of the file to trigger a complete environment reload and flush its caches when the timestamp changes. Most changes to the configuration will be reflected immediately, though changes to the `[components]` or `[logging]` sections will require restarting the web server. You may also need to restart the web server after creating a [#GlobalConfiguration global configuration] file when none was previously present.
 …
 Multiple files can be specified using a comma-separated list.
 Note that you can also specify a global option file when creating a new project,  by adding the option `--inherit=/path/to/global/trac.ini` to [TracAdmin#initenv trac-admin]'s `initenv` command.  If you do not do this but nevertheless intend to use a global option file with your new environment, you will have to go through the newly generated `conf/trac.ini` file and delete the entries that will otherwise override those set in the global file.
+Note that you can also specify a global option file when creating a new project, by adding the option `--inherit=/path/to/global/trac.ini` to [TracAdmin#initenv trac-admin]'s `initenv` command. If you do not do this but nevertheless intend to use a global option file with your new environment, you will have to go through the newly generated `conf/trac.ini` file and delete the entries that will otherwise override those set in the global file.
 There are two more entries in the [[#inherit-section| [inherit] ]] section, `templates_dir` for sharing global templates and `plugins_dir`, for sharing plugins. Those entries can themselves be specified in the shared configuration file, and in fact, configuration files can even be chained if you specify another `[inherit] file` there.

wiki/pages/TracInstall

-                      r40558
+                      r43921
 As you must be using Python 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).
 Optionally, you may install a newer version of [pypi:pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details.
+Optionally, you may install a newer version of [http://pypi.python.org/pypi/pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details.
 ==== For the PostgreSQL database #ForPostgreSQL
 …
 The [TracAdmin trac-admin] command-line tool, used to create and maintain [TracEnvironment project environments], as well as the [TracStandalone tracd] standalone server are installed along with Trac. There are several methods for installing Trac.
+It is assumed throughout this guide that you have elevated permissions as the `root` user or by prefixing commands with `sudo`. The umask `0002` should be used for a typical installation on a Unix-based platform.
 === Using `easy_install`
 Trac can be installed from PyPI or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].
 …
 A few examples:
  - Install Trac 1.0:
    {{{#!sh
+   easy_install Trac==1.0
    }}}
+ - Install the latest stable version of Trac:
+ {{{#!sh
+$ easy_install Trac
+}}}
  - Install latest development version:
    {{{#!sh
+   easy_install Trac==dev
    }}}
+ {{{#!sh
+$ easy_install http://download.edgewall.org/trac/Trac-latest-dev.tar.gz
+}}}
    Note that in this case you won't have the possibility to run a localized version of Trac;
    either use a released version or install from source
 More information can be found on the [trac:setuptools] page.
 {{{#!div style="border: 1pt dotted; margin: 1em"
 **Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in the sections on [#RunningtheStandaloneServer Running The Standalone Server] and [#RunningTraconaWebServer Running Trac on a Web Server].
+More information can be found on the [trac:wiki:setuptools setuptools] page.
+{{{#!div style="border: 1pt dotted; margin: 1em"
+**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in [#DeployingTrac Deploying Trac].
 }}}
 …
 == Deploying Trac
+{{{#!div style="border: 1pt dotted; margin: 1em"
+**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation.
+If running `tracd`, the environment variable can be set system-wide or for just the user that runs the `tracd` process. There are several ways to accomplish this in addition to what is discussed here, and depending on the distribution of your OS.
+To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`. To be effective for a user session the `export` statement may be added to `~/.profile`.
+{{{#!sh
+export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1
+}}}
+Alternatively, the variable can be set in the shell before executing `tracd`:
+{{{#!sh
+$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
+}}}
+If running the Apache web server, !Ubuntu/Debian users should add the `export` statement to `/etc/apache2/envvars`. !RedHat/CentOS/Fedora should can add the `export` statement to `/etc/sysconfig/httpd`.
+}}}
 === Running the Standalone Server
 …
 {{{#!sh
 $ tracd -s --port 8000 /path/to/myproject
-}}}
-{{{#!div style="border: 1pt dotted; margin: 1em"
-**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. The environment variable can be set system-wide, or for just the user that runs the `tracd` process. There are several ways to accomplish this in addition to what is discussed here, and depending on the distribution of your OS.
-To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`. To be effective for a user session the `export` statement may be added to `~/.profile`.
-{{{#!sh
-export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1
-}}}
-Alternatively, the variable can be set in the shell before executing `tracd`:
-{{{#!sh
-$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
-}}}
 }}}
 …
 Trac provides various options for connecting to a "real" web server:
  - [TracFastCgi FastCGI]
  - [wiki:TracModWSGI mod_wsgi]
  - [TracModPython mod_python]
+ - [wiki:TracModWSGI Apache with mod_wsgi]
+ - [TracModPython Apache with mod_python]
  - //[TracCgi CGI] (should not be used, as the performance is far from optimal)//
 …
 ==== Mapping Static Resources
+Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance).
+Web servers such as [http://httpd.apache.org/ Apache] allow you to create “Aliases” to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself.
+There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything.
+Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the TracAdmin `deploy` command:
+Without additional configuration, Trac will handle requests for static resources such as stylesheets and images. For anything other than a TracStandalone deployment, this is not optimal as the web server can be set up to directly serve the static resources. For CGI setup, this is '''highly undesirable''' as it causes abysmal performance.
+Web servers such as [http://httpd.apache.org/ Apache] allow you to create //Aliases// to resources, giving them a virtual URL that doesn't necessarily reflect their location on the file system. We can map requests for static resources directly to directories on the file system, to avoid Trac processing the requests.
+There are two primary URL paths for static resources: `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible at the `/chrome/<plugin>` path.
+A single `/chrome` alias can used if the static resources are extracted for all plugins. This means that the `deploy` command must be executed after installing or updating a plugin that provides static resources, or after modifying resources in the `$env/htdocs` directory. This is probably appropriate for most installations but may not be what you want if, for example, you wish to upload plugins through the //Plugins// administration page.
+The resources are extracted using the [TracAdmin trac-admin]` <environment> deploy` command:
 [[TracAdminHelp(deploy)]]
+The target `<directory>` will then contain an `htdocs` directory with:
+ - `site/` - a copy of the environment's directory `htdocs/`
+ - `common/` - the static resources of Trac itself
+ - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
+===== Example: Apache and `ScriptAlias` #ScriptAlias-example
+Assuming the deployment has been done this way:
+{{{#!sh
+$ trac-admin /var/trac/env deploy /path/to/shared/trac
+}}}
+Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment:
+The target `<directory>` will contain an `htdocs` directory with:
+ - `common/` - the static resources of Trac
+ - `site/` - a copy of the environment's `htdocs/` directory
+ - `shared` - the static resources shared by multiple Trac environments, with a location defined by the `[inherit]` `htdocs_dir` option
+ - `<plugin>/` - one directory for each resource directory provided by the plugins enabled for this environment
+The example that follows will create a single `/chrome` alias. If that isn't the correct approach for your installation you simply need to create more specific aliases:
 {{{#!apache
 Alias /trac/chrome/common /path/to/trac/htdocs/common
 Alias /trac/chrome/site /path/to/trac/htdocs/site
+Alias /trac/chrome/shared /path/to/trac/htdocs/shared
+Alias /trac/chrome/<plugin> /path/to/trac/htdocs/<plugin>
+}}}
+===== Example: Apache and `ScriptAlias` #ScriptAlias-example
+Assuming the deployment has been done this way:
+{{{#!sh
+$ trac-admin /var/trac/env deploy /path/to/shared/trac
+}}}
+Add the following snippet to Apache configuration, changing paths to match your deployment. The snippet must be placed ''before'' the `ScriptAlias` or `WSGIScriptAlias` directive, because those directives map all requests to the Trac application:
+{{{#!apache
+Alias /trac/chrome /path/to/trac/htdocs
 <Directory "/path/to/www/trac/htdocs">
+  Order allow,deny
+  Allow from all
+  # For Apache 2.2
+  <IfModule !mod_authz_core.c>
+    Order allow,deny
+    Allow from all
+  </IfModule>
+  # For Apache 2.4
+  <IfModule mod_authz_core.c>
+    Require all granted
+  </IfModule>
 </Directory>
 }}}
 If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
+If using mod_python, add this too, otherwise the alias will be ignored:
 {{{#!apache
 <Location "/trac/chrome/common/">
+<Location "/trac/chrome/common">
   SetHandler None
 </Location>
 }}}
+Note that we mapped the `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources.
+Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):
+Alternatively, if you wish to serve static resources directly from your project's `htdocs` directory rather than the location to which the files are extracted with the `deploy` command, you can configure Apache to serve those resources. Again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation:
 {{{#!apache
 Alias /trac/chrome/site /path/to/projectenv/htdocs
 <Directory "/path/to/projectenv/htdocs">
+  Order allow,deny
+  Allow from all
+  # For Apache 2.2
+  <IfModule !mod_authz_core.c>
+    Order allow,deny
+    Allow from all
+  </IfModule>
+  # For Apache 2.4
+  <IfModule mod_authz_core.c>
+    Require all granted
+  </IfModule>
 </Directory>
 }}}
 Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[TracIni#trac-section| [trac] htdocs_location]] configuration setting:
+Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [[TracIni#trac-section| [trac] htdocs_location]] configuration setting:
 {{{#!ini
 [trac]
 htdocs_location = http://static.example.org/trac-common/
 }}}
+Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less]).
+Note that this makes it easy to have a dedicated domain serve those static resources, preferentially cookie-less.
 Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:

wiki/pages/TracInterfaceCustomization

-                      r40558
+                      r43921
 = Customizing the Trac Interface
 [[TracGuideToc]]
 [[PageOutline]]
+[[PageOutline(2-5,Contents,pullout)]]
-== Introduction
 This page gives suggestions on how to customize the look of Trac. Topics include editing the HTML templates and CSS files, but not the program code itself. The topics show users how they can modify the look of Trac to meet their specific needs. Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page.
 …
 The logo or icon image should be put in a folder named "htdocs" in your project's environment folder. ''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder''.
  '''Note''': you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.
+'''Note''': you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.
 Now configure the appropriate section of your [wiki:TracIni trac.ini]:
 === Logo
 Change the `src` setting to `site/` followed by the name of your image file. The `width` and `height` settings should be modified to match your image's dimensions. The Trac chrome handler uses "`site/`" for files within the project directory `htdocs`, and "`common/`" for the common `htdocs` directory belonging to a Trac installation. Note that 'site/' is not a placeholder for your project name, it is the literal prefix that should be used. For example, if your project is named 'sandbox', and the image file is 'red_logo.gif' then the 'src' setting would be 'site/red_logo.gif', not 'sandbox/red_logo.gif'.
+Change the `src` setting to `site/` followed by the name of your image file. The `width` and `height` settings should be modified to match your image's dimensions. The Trac chrome handler uses `site/` for files within the project directory `htdocs`, and `common/` for the common `htdocs` directory belonging to a Trac installation. Note that 'site/' is not a placeholder for your project name, it is the literal prefix that should be used. For example, if your project is named 'sandbox', and the image file is 'red_logo.gif' then the 'src' setting would be 'site/red_logo.gif', not 'sandbox/red_logo.gif'.
 {{{#!ini
 …
 See also TracNavigation for a more detailed explanation of the mainnav and metanav terms.
 == Site Appearance == #SiteAppearance
+== Site Appearance #SiteAppearance
 Trac is using [http://genshi.edgewall.org Genshi] as the templating engine. Say you want to add a link to a custom stylesheet, and then your own header and footer. Save the following content as `site.html` inside your projects `templates/` directory (each Trac project can have their own `site.html`), eg `/path/to/env/templates/site.html`:
 …
 {{{#!xml
 <form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')">
   <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
+  <py:if test="req.path_info == '/newticket' and (not 'preview' in req.args)">
     <p>Please make sure to search for existing tickets before reporting a new one!</p>
   </py:if>
 …
 }}}
 This example illustrates a technique of using `req.environ['PATH_INFO']` to limit scope of changes to one view only. For instance, to make changes in `site.html` only for timeline and avoid modifying other sections - use  `req.environ['PATH_INFO'] == '/timeline'` condition in `<py:if>` test.
+This example illustrates a technique of using `req.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.path_info == '/timeline'` condition in `<py:if>` test.
 More examples snippets for `site.html` can be found at [trac:wiki:CookBook/SiteHtml CookBook/SiteHtml].
 …
 Example snippets for `style.css` can be found at [trac:wiki:CookBook/SiteStyleCss CookBook/SiteStyleCss].
 Note that the `site.html`, despite its name, can be put in a shared templates directory, see the [[TracIni#inherit-section|[inherit] templates_dir]] option. This could provide easier maintainence (and a migration path from 0.10 for larger installations) as one new global `site.html` file can be made to include any existing header, footer and newticket snippets.
+Note that the `site.html`, despite its name, can be put in a shared templates directory, see the [[TracIni#inherit-section|[inherit] templates_dir]] option. This could provide easier maintainence as one new global `site.html` file can be made to include any existing header, footer and newticket snippets.
 == Project List == #ProjectList
+== Project List #ProjectList
 You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.
+You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.
 The following is the basic template used by Trac to display a list of links to the projects. For projects that could not be loaded, it displays an error message. You can use this as a starting point for your own index template:
 …
 }}}
 Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located (pls verify ... not yet changed to 0.11):
+Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located:
 For [wiki:TracModWSGI mod_wsgi]:
 …
 For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd:
  - Unix
+ - Unix:
    {{{#!sh
 $ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template
    }}}
  - Windows
+ - Windows:
    {{{#!sh
 $ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template
 …
 == Project Templates
 The appearance of each individual Trac environment, ie instance of a project, can be customized independently of other projects, even those hosted on the same server. The recommended way is to use a `site.html` template (see [#SiteAppearance]) whenever possible. Using `site.html` means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of `theme.html` or any other Trac template, you need to migrate your modifiations to the newer version. If not, new Trac features or bug fixes may not work as expected.
+The appearance of each individual Trac environment, ie instance of a project, can be customized independently of other projects, even those hosted on the same server. The recommended way is to use a `site.html` template whenever possible, see [#SiteAppearance]. Using `site.html` means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of `theme.html` or any other Trac template, you need to migrate your modifiations to the newer version. If not, new Trac features or bug fixes may not work as expected.
 With that word of caution, any Trac template may be copied and customized. The default Trac templates are located inside the installed Trac egg (`/usr/lib/pythonVERSION/site-packages/Trac-VERSION.egg/trac/templates, .../trac/ticket/templates, .../trac/wiki/templates, ...`). The [#ProjectList] template file is called `index.html`, while the template responsible for main layout is called `theme.html`. Page assets such as images and CSS style sheets are located in the egg's `trac/htdocs` directory.
+With that word of caution, any Trac template may be copied and customized. The default Trac templates are located inside the installed Trac egg, such as `/usr/lib/pythonVERSION/site-packages/Trac-VERSION.egg/trac/templates, ../trac/ticket/templates, ../trac/wiki/templates`. The [#ProjectList] template file is called `index.html`, while the template responsible for main layout is called `theme.html`. Page assets such as images and CSS style sheets are located in the egg's `trac/htdocs` directory.
 However, do not edit templates or site resources inside the Trac egg. Reinstalling Trac overwrites your modifications. Instead use one of these alternatives:

wiki/pages/TracLinks

-                      r40558
+                      r43921
+= Trac Links =
+= Trac Links
 [[TracGuideToc]]
+TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.
+TracLinks are generally of the form '''type:id''' (where ''id'' represents the
+number, name or path of the item) though some frequently used kinds of items
+also have short-hand notations.
+== Where to use TracLinks ==
+[[PageOutline(2-5,Contents,pullout)]]
+TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system — such as tickets, reports, changesets, Wiki pages, milestones, and source files — from anywhere where WikiFormatting is used.
+TracLinks are generally of the form '''type:id''' (where ''id'' represents the number, name or path of the item) though some frequently used kinds of items also have short-hand notations.
+== Where to use TracLinks
 You can use TracLinks in:
 …
 and any other text fields explicitly marked as supporting WikiFormatting.
 == Overview ==
+== Overview
 ||= Wiki Markup =||= Display =||
 …
 }}}
+'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
+pages whose names do not follow WikiPageNames rules, i.e., single words,
+non-alphabetic characters, etc. See WikiPageNames for more about features specific
+to links to Wiki page names.
+'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to pages whose names do not follow WikiPageNames rules, ie single words, non-alphabetic characters, etc. See WikiPageNames for more about features specific to links to Wiki page names.
 …
 TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
+== Advanced use of TracLinks ==
+=== Relative links ===
+== Advanced use of TracLinks
+=== Relative links
 To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
 …
 But in practice you often won't need to add the `../` prefix to link to a sibling page.
+For resolving the location of a wiki link, it's the target page closest in the hierarchy
+to the page where the link is written which will be selected. So for example, within
+a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
+For resolving the location of a wiki link, it's the target page closest in the hierarchy to the page where the link is written which will be selected. So for example, within a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
 This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
+In order to link explicitly to a [=#toplevel toplevel] Wiki page,
+use the `wiki:/` prefix. Be careful **not** to use the `/` prefix alone, as this corresponds to the [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` part in the resulting URL. A link such as `[../newticket]` will stay in the wiki namespace and therefore link to a sibling page.
+=== Link anchors ===
+To link explicitly to a [=#toplevel toplevel] Wiki page, use the `wiki:/` prefix. Be careful **not** to use the `/` prefix alone, as this corresponds to the [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` part in the resulting URL. A link such as `[../newticket]` will stay in the wiki namespace and therefore link to a sibling page.
+=== Link anchors
 To create a link to a specific anchor in a page, use '#':
 …
  [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
 === InterWiki links ===
 Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there's a more specialized way to register other Trac environments which offers greater flexibility.
 === InterTrac links ===
+=== InterWiki links
+Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there is a more specialized way to register other Trac environments which offers greater flexibility.
+=== InterTrac links
 This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
 …
 See InterTrac for the complete details.
+=== Server-relative links ===
+It is often useful to be able to link to objects in your project that
+have no built-in Trac linking mechanism, such as static resources, `newticket`,
+a shared `/register` page on the server, etc.
+To link to resources inside the project, use either an absolute path from the project root,
+or a relative link from the URL of the current page (''Changed in 0.11''):
+=== Server-relative links
+It is often useful to be able to link to objects in your project that have no built-in Trac linking mechanism, such as static resources, `newticket`, a shared `/register` page on the server, etc.
+To link to resources inside the project, use either an absolute path from the project root, or a relative link from the URL of the current page (''Changed in 0.11''):
 {{{
 …
 Display: [//register Register Here] or [[//register|Register Here]]
+=== Quoting space in TracLinks ===
+Immediately after a TracLinks prefix, targets containing space characters should
+be enclosed in a pair of quotes or double quotes.
+=== Quoting space in TracLinks
+Immediately after a TracLinks prefix, targets containing space characters should be enclosed in a pair of quotes or double quotes.
 Examples:
  * !wiki:"The whitespace convention"
 …
  * ![[attachment:the file.txt]]
 === Escaping Links ===
+=== Escaping Links
 To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
 …
  ![42] is not a link either.
+=== Parameterized Trac links ===
+=== Parameterized Trac links
 Many Trac resources have more than one way to be rendered, depending on some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.
 …
  - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`
+== TracLinks Reference ==
+== TracLinks Reference
 The following sections describe the individual link types in detail, as well as notes on advanced usage of links.
 === attachment: links ===
+=== attachment: links
 The link syntax for attachments is as follows:
 …
 See also [#export:links].
 === comment: links ===
+=== comment: links
 When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
 …
  - `ticket:123#comment:description`
 === htdocs: links ===
+=== htdocs: links
 Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
 === query: links ===
+=== query: links
 See TracQuery#UsingTracLinks and [#ticket:links].
 === search: links ===
+=== search: links
 See TracSearch#SearchLinks
+=== ticket: links ===
+ ''alias:'' `bug:`
+=== ticket: links
+ ''aliases:'' `bug:`, `issue:`
 Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets.
 …
  - `ticket:1,150`
 === timeline: links ===
+=== timeline: links
 Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but if you don't want to compute the UTC time, you can specify a local time followed by your timezone offset relative to UTC.
 …
  - `timeline:2008-01-29T16:48+01:00`
 === wiki: links ===
+=== wiki: links
 See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.
 === Version Control related links ===
 It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it (the default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator).
+=== Version Control related links
+It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it. The default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator.
 For example, `source:/trunk/COPYING` targets the path `/trunk/COPYING` in the default repository, whereas `source:/projectA/trunk/COPYING` targets the path `/trunk/COPYING` in the repository named `projectA`. This can be the same file if `'projectA'` is an alias to the default repository or if `''` (the default repository) is an alias to `'projectA'`.
+==== source: links ====
+==== source: links
  ''aliases:'' `browser:`, `repos:`
+The default behavior for a `source:/some/path link` is to open the browser in that directory directory
+if the path points to a directory or to show the latest content of the file.
+The default behavior for a `source:/some/path link` is to open the browser in that directory directory if the path points to a directory or to show the latest content of the file.
 It's also possible to link directly to a specific revision of a file like this:
  - `source:/some/file@123` - link to the file's revision 123
  - `source:/some/file@head` - link explicitly to the latest revision of the file
+ - `source:/some/file@named-branch` - link to latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial)
 If the revision is specified, one can even link to a specific line number:
  - `source:/some/file@123#L10`
  - `source:/tag/0.10@head#L10`
+ - `source:/some/file@named-branch#L10`
 Finally, one can also highlight an arbitrary set of lines:
  - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
  - or without version number (the `@` is still needed): `source:/some/file@:10-20,100,103#L99`. Version can be omitted when the path is pointing to a source file that will no longer change (like `source:/tags/...`), otherwise it's better to specify which lines of //which version// of the file you're talking about
+ - or without version number (the `@` is still needed): `source:/some/file@:10-20,100,103#L99`. Version can be omitted when the path is pointing to a source file that will no longer change (like `source:/tags/...`), otherwise it's better to specify which lines of //which version// of the file you're talking about.
 Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` (e.g. `source:reponame/trunk/README`). ''(since 0.12)''
 ==== export: links ====
+==== export: links
 To force the download of a file in the repository, as opposed to displaying it in the browser, use the `export` link.  Several forms are available:
 …
  * `export:123:/some/file` - get revision 123 of the specified file
  * `export:/some/file@123` - get revision 123 of the specified file
+ * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
 This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns.
 …
 If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of `source:/some/dir`).
 ==== log: links ====
+==== log: links
 The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions of the specified path, but it can also support displaying an arbitrary set of revisions.
 …
  - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
  - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
+ - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)
 There are short forms for revision ranges as well:
 …
 ----
 See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki

wiki/pages/TracModPython

-                      r40558
+                      r43921
 Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably, especially compared to [TracCgi CGI], and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy.
-These instructions are for Apache 2. If you are using Apache 1.3, you may have some luck with [trac:wiki:TracModPython2.7 TracModPython2.7], but that is a deprecated setup.
 [[PageOutline(2-3,Overview,inline)]]
 == Simple configuration: single project == #Simpleconfiguration
+== Simple configuration: single project #Simpleconfiguration
 If you just installed mod_python, you may have to add a line to load the module in the Apache configuration:
 …
 {{{#!apache
 <Location /mpinfo>
+   SetHandler mod_python
+   PythonInterpreter main_interpreter
+   PythonHandler mod_python.testhandler
+   Order allow,deny
+   Allow from all
+  SetHandler mod_python
+  PythonInterpreter main_interpreter
+  PythonHandler mod_python.testhandler
+  # For Apache 2.2
+  <IfModule !mod_authz_core.c>
+    Order allow,deny
+    Allow from all
+  </IfModule>
+  # For Apache 2.4
+  <IfModule mod_authz_core.c>
+    Require all granted
+  </IfModule>
 </Location>
 }}}
 …
 {{{#!apache
 <Location /projects/myproject>
+   SetHandler mod_python
+   PythonInterpreter main_interpreter
+   PythonHandler trac.web.modpython_frontend
+   PythonOption TracEnv /var/trac/myproject
+   PythonOption TracUriRoot /projects/myproject
+   Order allow,deny
+   Allow from all
+  SetHandler mod_python
+  PythonInterpreter main_interpreter
+  PythonHandler trac.web.modpython_frontend
+  PythonOption TracEnv /var/trac/myproject
+  PythonOption TracUriRoot /projects/myproject
+  # For Apache 2.2
+  <IfModule !mod_authz_core.c>
+    Order allow,deny
+    Allow from all
+  </IfModule>
+  # For Apache 2.4
+  <IfModule mod_authz_core.c>
+    Require all granted
+  </IfModule>
 </Location>
 }}}
 …
 '''Note''': For the above configuration to have any effect it must be put after the configuration of your project root location, ie {{{<Location /myproject />}}}.
 Also, setting `PythonOptimize On` seems to mess up the page headers and footers, in addition to hiding the documentation for macros and plugins (see #Trac8956). Considering how little effect the option has, leave it `Off`.
+**Note:** Do not enable python optimizations using the directive `PythonOptimize On`. When optimizations are enabled the page header/footer and documentation for macros and plugins will be hidden. An error will be raised in Trac 1.0.11 and later when optimizations are enabled.
 === HTTPS issues

wiki/pages/TracModWSGI

-                      r40558
+                      r43921
 == The `trac.wsgi` script
 Trac can be run on top of mod_wsgi with the help of an application script, which is just a Python file saved with a `.wsgi` extension.
+Trac can be run on top of mod_wsgi with the help of an application script, which is a Python file saved with a `.wsgi` extension.
 A robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin. The script should be sufficient for most installations and users not wanting more information can proceed to [#Mappingrequeststothescript configuring Apache].
 …
 {{{#!python
 def application(environ, start_request):
     # Add this to config when you have multiple projects
+    # Add this to config when you have multiple projects
     environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects')
     ..
 …
 === A very basic script
 In its simplest form, the script could be:
 …
 <Directory /usr/local/trac/mysite/apache>
     WSGIApplicationGroup %{GLOBAL}
+    Order deny,allow
+    Allow from all
+    # For Apache 2.2
+    <IfModule !mod_authz_core.c>
+        Order deny,allow
+        Allow from all
+    </IfModule>
+    # For Apache 2.4
+    <IfModule mod_authz_core.c>
+        Require all granted
+    </IfModule>
 </Directory>
 }}}
 …
 <Directory /usr/share/trac/cgi-bin>
     WSGIApplicationGroup %{GLOBAL}
+    Order deny,allow
+    Allow from all
+    # For Apache 2.2
+    <IfModule !mod_authz_core.c>
+        Order deny,allow
+        Allow from all
+    </IfModule>
+    # For Apache 2.4
+    <IfModule mod_authz_core.c>
+        Require all granted
+    </IfModule>
 </Directory>
 }}}
 …
 In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi. This is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash. After adding this configuration, restart Apache, and then it should work.
 To test the setup of Apache, mod_wsgi and Python itself (ie. without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
+To test the setup of Apache, mod_wsgi and Python itself (ie without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script):
 {{{#!python
 …
 }}}
 For more information about using the mod_wsgi specific directives, see the [http://code.google.com/p/modwsgi/wiki/ mod_wsgi's wiki] and more specifically the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac IntegrationWithTrac] page.
+For more information about using the mod_wsgi specific directives, see the [https://code.google.com/archive/p/modwsgi/wikis mod_wsgi's wiki] and more specifically the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki IntegrationWithTrac] page.
 == Configuring Authentication
 The following sections describe different methods for setting up authentication. See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
+The following sections describe different methods for setting up authentication. See also [http://httpd.apache.org/docs/2.4/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
 === Using Basic Authentication
 …
 }}}
+  ''See the man page for `htpasswd` for full documentation.''
+See the man page for `htpasswd` for full documentation.
 After you've created the users, you can set their permissions using TracPermissions.
 …
 </LocationMatch>
 }}}
+Note that neither a file nor a directory named 'login' needs to exist.[[BR]]
 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html mod_auth_basic] documentation.
+Note that neither a file nor a directory named 'login' needs to exist. See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_basic] documentation.
 === Using Digest Authentication
 For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”.
+For better security, it is recommended that you either enable SSL or at least use the "digest" authentication scheme instead of "Basic".
 You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
 …
 For multiple environments, you can use the same `LocationMatch` as described with the previous method.
 '''Note: `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity. '''
+'''Note''': `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity.
 Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system:
 …
 }}}
 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation.
+See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_digest] documentation.
 === Using LDAP Authentication
 Configuration for [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2.x and OpenLDAP: slapd 2.3.19).
+Configuration for [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2+ and OpenLDAP: slapd 2.3.19).
 . You need to load the following modules in Apache httpd.conf:
 …
   AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
 }}}
  You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plaintext in the config, you need to use an account specifically for this task:
+ You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plain text in the configuration, you need to use an account specifically for this task:
 {{{#!apache
   AuthLDAPBindDN ldap-auth-user@example.com
 …
 See also:
  - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
  - [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
  - [http://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
+ - [https://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
+ - [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
+ - [https://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
 === Using SSPI Authentication
 …
 See also [trac:TracOnWindows/Advanced].
+=== Using Apache authentication with the Account Manager plugin's Login form ===
+To begin with, see the basic instructions for using the Account Manager plugin's [http://trac-hacks.org/wiki/AccountManagerPlugin/Modules#LoginModule Login module] and its [http://trac-hacks.org/wiki/AccountManagerPlugin/AuthStores#HttpAuthStore HttpAuthStore authentication module].
+'''Note:''' If is difficult to get !HttpAuthStore to work with WSGI when using any Account Manager version prior to acct_mgr-0.4. Upgrading is recommended.
+Here is an example (from the !HttpAuthStore link) using acct_mgr-0.4 for hosting a single project:
+{{{#!ini
+[components]
+; be sure to enable the component
+acct_mgr.http.HttpAuthStore = enabled
+[account-manager]
+; configure the plugin to use a page that is secured with http authentication
+authentication_url = /authFile
+password_store = HttpAuthStore
+}}}
+This will generally be matched with an Apache config like:
+{{{#!apache
+<Location /authFile>
+   …HTTP authentication configuration…
+   Require valid-user
+</Location>
+}}}
+Note that '''authFile''' need not exist (unless you are using Account Manager older than 0.4). See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
+=== Using CA !SiteMinder Authentication
+Setup CA !SiteMinder to protect your Trac login URL, for example `/trac/login`. Also, make sure the policy is set to include the HTTP_REMOTE_USER variable. If your site allows it, you can set this in `LocalConfig.conf`:
+{{{#!apache
+RemoteUserVar="WHATEVER_IT_SHOULD_BE"
+SetRemoteUser="YES"
+}}}
+The specific variable is site-dependent. Ask your site administrator. If your site does not allow the use of `LocalConfig.conf` for security reasons, have your site administrator set the policy on the server to set REMOTE_USER.
+Also add a !LogOffUri parameter to the agent configuration, for example `/trac/logout`.
+Then modify the trac.wsgi script generated using `trac-admin <env> deploy <dir>` to add the following lines, which extract the `HTTP_REMOTE_USER` variable and set it to `REMOTE_USER`:
+{{{#!python
+def application(environ, start_request):
+    # Set authenticated username on CA SiteMinder to REMOTE_USER variable
+    # strip() is used to remove any spaces on the end of the string
+    if 'HTTP_SM_USER' in environ:
+        environ['REMOTE_USER'] = environ['HTTP_REMOTE_USER'].strip()
+    ...
+}}}
+You do not need any Apache "Location" directives.
 === Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host
 …
  - uses Apache basic authentication for Trac authentication.
 If you want your Trac to be served from e.g. !http://trac.my-proj.my-site.org, then from the folder e.g. `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
+If you want your Trac to be served from eg !http://trac.my-proj.my-site.org, then from the folder eg `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first:
 Create the htpasswd file:
 …
 htpasswd htpasswd seconduser
 }}}
 Keep the file above your document root for security reasons.
 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following content:
+Create this file for example `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` on Ubuntu with the following content:
 {{{#!apache
 …
 }}}
 Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
+For subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
 == Troubleshooting
 …
 === Use a recent version
 Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [http://code.google.com/p/modwsgi/issues/detail?id=100 #100] and [http://code.google.com/p/modwsgi/issues/detail?id=132 #132].
 ''Note: using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks''
+Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [https://code.google.com/archive/p/modwsgi/issues/100 #100] and [https://code.google.com/archive/p/modwsgi/issues/132 #132].
+'''Note''': using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks
 If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 3.4 or greater. See [trac:#10675] for details.
 …
 === Getting Trac to work nicely with SSPI and 'Require Group'
 If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'.
 This WSGI script 'fixes' that:
+If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your Apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'.
+This WSGI script fixes that:
 {{{#!python
 import os
 …
 Now Trac drops the connection after serving a page and the connection count on the database will be kept low.
+//This is not a recommended approach though. See also the notes at the bottom of the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac mod_wsgi's IntegrationWithTrac] wiki page.//
+//This is not a recommended approach though. See also the notes at the bottom of the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki mod_wsgi's IntegrationWithTrac] wiki page.//
+=== Missing Headers and Footers
+If python optimizations are enabled, then headers and footers will not be rendered. An error will be raised in Trac 1.0.11 and later when optimizations are enabled.
+In your WSGI configuration file, the `WSGIPythonOptimize` setting must be set to `0` (`1` or `2` will not work):
+{{{#!apache
+    WSGIPythonOptimize 0
+}}}
+On Ubuntu, the WSGI mod configuration is at `/etc/apache2/mods-enabled/wsgi.conf`.
+The same issue is seen with `PythonOptimize On` in [TracModPython#Pagelayoutissues ModPython].
 === Other resources
 For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [http://code.google.com/p/modwsgi/wiki/ApplicationIssues application issues] when using mod_wsgi. The wsgi page also has a [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac Integration With Trac] document.
+For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [https://code.google.com/archive/p/modwsgi/wikis/ApplicationIssues.wiki application issues] when using mod_wsgi. The wsgi page also has a [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki Integration With Trac] document.
 ----

wiki/pages/TracPlugins

-                      r40558
+                      r43921
 From the user's point of view, a plugin is either a standalone .py file or an .egg package. Trac looks for plugins in Python's `site-packages` directory, the [TracIni#GlobalConfiguration global shared] `plugins` directory and the [TracEnvironment project environment] `plugins` directory. Components defined in globally-installed plugins must be explicitly enabled in the [[TracIni#components-section| [components] ]] section of the `trac.ini` file. Components defined in the `plugins` directory of the project environment are enabled, unless explicitly disabled in the `[components]` section of the `trac.ini` file.
 == Requirements for Trac eggs
+== Requirements for Trac eggs #Requirements
 To use egg-based plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version >= 0.6) installed.
 …
 == Installing a Trac plugin
+The instructions below are applicable to a plugin packaged as an egg. Plugins implemented as a single `py` file should be downloaded and copied to the [TracEnvironment project environment] `plugins` directory or the [TracIni#GlobalConfiguration global shared] plugins directory.
 === For a single project
-Plugins are typically packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are .zip archives with the file extension `.egg`.
 If you have downloaded a source distribution of a plugin, and want to build the `.egg` file:
 …
 ==== With an .egg file
 Some plugins, such as [trac:SpamFilter SpamFilter], are downloadable as an `.egg` file that can be installed with `easy_install` or `pip`:
 {{{#!sh
 $ easy_install TracSpamFilter
 $ pip install TracSpamFilter
+Some plugins, such as [https://trac-hacks.org/wiki/TagsPlugin TracTags], are downloadable as an `.egg` file that can be installed with `easy_install` or `pip`:
+{{{#!sh
+$ easy_install TracTags
+$ pip install TracTags
 }}}
 …
 If Trac reports permission errors after installing a zipped egg, and you would rather not bother providing an egg cache directory writable by the web server, you can get around it by simply unzipping the egg. Just pass `--always-unzip` to `easy_install`:
 {{{#!sh
 $ easy_install --always-unzip TracSpamFilter-0.4.1_r10106-py2.6.egg
+$ easy_install --always-unzip TracTags
 }}}
 You should end up with a directory having the same name as the zipped egg, complete with `.egg` extension, and containing its uncompressed contents.
 …
 `easy_install` makes installing from source a snap. Just give it the URL to either a Subversion repository or a tarball/zip of the source:
 {{{#!sh
 $ easy_install http://svn.edgewall.com/repos/trac/plugins/0.12/spam-filter-captcha
+$ easy_install https://trac-hacks.org/svn/tagsplugin/trunk
 }}}
 …
 {{{#!ini
 [components]
 tracspamfilter.* = enabled
+tractags.* = enabled
 }}}
 …
 After installing the plugin, you must restart your web server.
+==== Upgrading the environment
+Some plugins may require an environment upgrade. This will typically be necessary for plugins that implement `IEnvironmentSetupParticipant`. Common reasons for requiring an environment upgrade are to add tables to the database or add configuration parameters to trac.ini. A notification will be displayed when accessing Trac for the first time after installing a plugin and restarting the web server. To upgrade the environment, run the command:
+{{{#!sh
+$ trac-admin /path/to/env upgrade
+}}}
+A database backup will be made before upgrading the environment, unless the `--no-backup` option is specified. For more information, refer to the documentation output by `trac-admin /path/to/env help upgrade`.
 ==== Uninstalling

wiki/pages/TracQuery

-                      r40558
+                      r43921
 After you have edited your filters, click the ''Update'' button to refresh your results.
+Some shortcuts can be used to manipulate //checkbox// filters.
+* Clicking on a filter row label toggles all checkboxes.
+* Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
+* Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.
+The modifier key is platform and browser dependent. On Mac the modified key is !Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.
 == Navigating Tickets

wiki/pages/TracRoadmap

-                      r40558
+                      r43921
 With appropriate permissions it is possible to add, modify and remove milestones using either the web interface (roadmap and milestone pages), web administration interface or by using `trac-admin`.
 '''Note:''' Milestone descriptions can not currently be edited using 'trac-admin'.
+'''Note:''' Milestone descriptions can not currently be edited using `trac-admin`.
 == iCalendar Support
 The Roadmap supports the [http://www.ietf.org/rfc/rfc2445.txt iCalendar] format to keep track of planned milestones and related tickets from your favorite calendar software. Many calendar applications support the iCalendar specification including
  * [http://www.apple.com/ical/ Apple iCal] for Mac OS X
  * the cross-platform [http://www.mozilla.org/projects/calendar/ Mozilla Calendar]
  * [http://chandlerproject.org Chandler]
  * [http://kontact.kde.org/korganizer/ Korganizer], the calendar application of the [http://www.kde.org/ KDE] project
  * [https://wiki.gnome.org/Apps/Evolution Evolution]
  * [http://office.microsoft.com/en-us/outlook/ Microsoft Outlook] can also read iCalendar files and appears as a new static calendar in Outlook
  * [https://www.google.com/calendar/ Google Calendar]
+The Roadmap supports the [http://www.ietf.org/rfc/rfc2445.txt iCalendar] format to keep track of planned milestones and related tickets from your favorite calendar software. Many calendar applications support the iCalendar specification including:
+ * [http://www.apple.com/ical/ Apple iCal] for Mac OS X.
+ * [http://www.mozilla.org/projects/calendar/ Mozilla Calendar], cross-platform.
+ * [http://kontact.kde.org/korganizer/ Korganizer], the calendar application of the [http://www.kde.org/ KDE] project.
+ * [https://wiki.gnome.org/Apps/Evolution Evolution], a contact manager, address manager and calendar for Gnome.
+ * [http://office.microsoft.com/en-us/outlook/ Microsoft Outlook] can also read iCalendar files and appears as a new static calendar in Outlook.
+ * [https://www.google.com/calendar/ Google Calendar].
+ * [http://chandlerproject.org Chandler], a personal and small-group task management and calendaring tool, Apache licensed and orphaned since 2009.
 To subscribe to the roadmap, copy the iCalendar link from the roadmap (found at the bottom of the page) and choose the "Subscribe to remote calendar" action (or similar) of your calendar application, and insert the URL just copied.
 …
 '''Note:''' For tickets to be included in the calendar as tasks, you need to be logged in when copying the link. You will only see tickets assigned to yourself and associated with a milestone.
 '''Note:''' To include the milestones in Google Calendar you might need to rewrite the URL.
 {{{
+'''Note:''' To include the milestones in Google Calendar you might need to rewrite the URL:
+{{{#!apache
 RewriteEngine on
 RewriteRule ([^/.]+)/roadmap/([^/.]+)/ics /$1/roadmap?user=$2&format=ics

wiki/pages/TracSearch

-                      r40558
+                      r43921
 == Quick searches
 For quick access to project resources, the quick-search field at the top of every page can be used to enter a [TracLinks wiki link], which will take you directly to the resource identified by that link:
 …
  * /repos1/trunk -- Opens the browser for the `trunk` directory in the `repos1` repository
-== Advanced
-=== Disabling Quickjump
 To disable the Quickjump feature for a keyword start the query with an exclamation mark (`!`): use `!TracGuide` to search for occurrences of the literal word !TracGuide.
+=== Search Links
+== Search TracLinks
 From the Wiki, it is possible to link to a specific search, using `search:` links:
  * `search:?q=crash` will search for the string "crash"
  * `search:?q=trac+link&wiki=on` will search for "trac" and "link" in wiki pages only
+== Search Filters
+On the search page, pressing the modifier key while selecting a search filter will unselect all other search filters.
 ----
 See also: TracGuide, TracLinks, TracQuery

wiki/pages/TracStandalone

-                      r40558
+                      r43921
 Tracd allows you to run Trac without the need for Apache, but you can take advantage of Apache's password tools (`htpasswd` and `htdigest`) to easily create a password file in the proper format for tracd to use in authentication. (It is also possible to create the password file without `htpasswd` or `htdigest`; see below for alternatives)
+Make sure you place the generated password files on a filesystem which supports sub-second timestamps, as Trac will monitor their modified time and changes happening on a filesystem with too coarse-grained timestamp resolution (like `ext2` or `ext3` on Linux, or HFS+ on OSX).
+{{{#!div style="border: 1pt dotted; margin: 1em"
+**Attention:** Make sure you place the generated password files on a filesystem which supports sub-second timestamps, as Trac will monitor their modified time and changes happening on a filesystem with too coarse-grained timestamp resolution (like `ext2` or `ext3` on Linux, or HFS+ on OSX).
+}}}
 Tracd provides support for both Basic and Digest authentication. Digest is considered more secure. The examples below use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the command line.
 …
 This section describes how to use `tracd` with Apache .htpasswd files.
   Note: It is necessary (at least with Python 2.6) to install the fcrypt package in order to
   decode some htpasswd formats.  Trac source code attempt an `import crypt` first, but there
   is no such package for Python 2.6. Only `SHA-1` passwords (since Trac 1.0) work without this module.
+  Note: On Windows It is necessary to install the [https://pypi.python.org/pypi/passlib passlib]
+  package in order to decode some htpasswd formats. Only `SHA-1` passwords (since Trac 1.0)
+  work without this module.
 To create a .htpasswd file use Apache's `htpasswd` command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache):
 …
 Run tracd:
 {{{#!sh
 tracd -p 8101 -r -s proxified --base-path=/project/proxified
+tracd -p 8101 -s proxified --base-path=/project/proxified
 }}}

wiki/pages/TracSupport

-                      r40558
+                      r43921
 Like in most [http://www.opensource.org/ open source projects], Trac support is available primarily through the [trac:MailingList mailing list] and the [trac: project wiki]. Both are maintained by the trac community. The [trac: project wiki] is the authoritative source for the TracGuide, consisting of the administrator and user guides for Trac.
+There is also an [trac:IrcChannel IRC channel] where online users can help out. Much of the 'live' development discussions also happen there.
+There is an [trac:IrcChannel IRC channel] where online users can help out. Much of the 'live' development discussions also happen there.
+You can search questions tagged with `trac` on [SO:tagged/trac Stack Overflow].
 Before you start a new support query, make sure you have done the appropriate searching:

wiki/pages/TracSyntaxColoring

-                      r40558
+                      r43921
 = Syntax Coloring of Source Code
 Trac supports language-specific syntax highlighting of source code within wiki formatted text in [WikiProcessors#CodeHighlightingSupport wiki processors] blocks and in the [TracBrowser repository browser]. Syntax coloring is provided using [http://pygments.pocoo.org/ Pygments], which covers a wide range of programming languages and other structured texts, and is actively supported. If Pygments is not available, Trac will display the content as plain text.
+Trac supports language-specific syntax highlighting of source code within wiki formatted text in [WikiProcessors#CodeHighlightingSupport wiki processors] blocks and in the [TracBrowser repository browser]. Syntax coloring is provided using [http://pygments.org/ Pygments], which covers a wide range of programming languages and other structured texts, and is actively supported. If Pygments is not available, Trac will display the content as plain text.
 …
 The Pygments default style can specified in the [TracIni#mimeviewer-section mime-viewer] section of trac.ini. The default style can be overridden by setting a //Style// preference on the [/prefs/pygments preferences page].
+[http://pygments.org/docs/lexers/ Pygments lexer] options can be specified as [WikiProcessors WikiProcessor] arguments and defaults can be set in the [TracIni#pygments-lexer-section environment configuration].
 == Syntax Coloring Support

wiki/pages/TracTickets

-                      r40558
+                      r43921
 = The Trac Ticket System =
+= The Trac Ticket System
 [[TracGuideToc]]
 The Trac ticket database provides simple but effective way to track issues and software bugs within a project.
+The Trac ticket system provides a simple but effective way to track issues and software bugs within a project.
 As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''', '''software support issues''' among others.
 As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible.
+As with the TracWiki, this subsystem has been designed to make user contribution and participation as simple as possible.
 An issue is assigned to a person who must resolve it or reassign the ticket to someone else. All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
 [=#edit-permissions]
 However, a Trac installation may place restrictions on who can change what. For example, the default installation doesn't permit to non-authenticated users ("anonymous" users) to change anything, even to comment on an issue, for obvious spam prevention reasons. Check the local contributing policy, which you can usually find on the front page WikiStart, or contact your local Trac administrator.
+However, a Trac installation may place restrictions on who can change what. For example, the default installation doesn't permit to non-authenticated users ("anonymous" users) to change anything, even to comment on an issue, for obvious spam prevention reasons. Check the local contributing policy, which you can usually find on the front page of WikiStart, or contact your local Trac administrator.
 == Ticket Fields ==
+== Ticket Fields
 A ticket contains the following information:
  * '''Reporter''' — The author of the ticket.
  * '''Type''' — The category of the ticket. The default types are `defect`,  `enhancement` and `task`.
  * '''Component''' — The project module or subsystem this ticket concerns.
+ * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`.
+ * '''Component''' — The project module or subsystem that this ticket concerns.
  * '''Version''' — Version of the project that this ticket pertains to.
  * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation.
  * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined.
  * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones.
+ * '''Keywords''' — Keywords that a ticket is tagged with. Useful for searching and report generation.
+ * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A dropdown list when multiple priorities are defined.
+ * '''Milestone''' — Due date of when this issue should be resolved. A dropdown list containing the milestones.
  * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
  * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.''
+ * '''Cc''' — A comma-separated list of other users or email addresses to notify. Note that this does not imply responsibility or any other policy.
  * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
  * '''Status''' — What is the current status? The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`.
 …
  - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
 == Changing and Commenting Tickets ==
+== Changing and Commenting Tickets
 With appropriate permissions, as already mentioned [#edit-permissions above], a ticket entered into Trac can at any time be modified by '''annotating'''.
 …
 Then, annotations like changes and comments to the ticket are logged as a part of the ticket itself. When viewing a ticket, the history of changes will appear below the main ticket area.
 Comment editing (available since 0.12) is meant to be used to make small corrections to comments, like fixing formatting, forgotten WikiFormatting or spelling errors, not major edits. For longer edits, you should be adding a new comment instead. Editing a comment will not produce a new entry on [/timeline] while entering a new comment or other changes will do.
+Comment editing (available since 0.12) is meant to be used to make small corrections to comments, like fixing formatting, forgotten WikiFormatting or spelling errors, not major edits. For longer edits, you should be adding a new comment instead. Editing a comment will not produce a new entry on [/timeline], while entering a new comment or other changes will do.
 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
 '''Notes:'''
 …
  - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
 == Default Values for Drop-Down Fields ==
+== Default Values for Drop-Down Fields
 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
  * `default_component`: Name of the component selected by default
  * `default_milestone`: Name of the default milestone
  * `default_priority`: Default priority value
  * `default_severity`: Default severity value
  * `default_type`: Default ticket type
  * `default_version`: Name of the default version
+ * `default_component`: Name of the component selected by default.
+ * `default_milestone`: Name of the default milestone.
+ * `default_priority`: Default priority value.
+ * `default_severity`: Default severity value.
+ * `default_type`: Default ticket type.
+ * `default_version`: Name of the default version.
  * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
 If any of these options are omitted, the default value will either be the first in the list, or an empty value, depending on whether the field in question is required to be set.  Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section, others can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`.
+If any of these options are omitted, the default value will either be the first in the list, or an empty value, depending on whether the field in question is required to be set. Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section, others can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`.
+== Hiding Fields and Adding Custom Fields ==
+== Hiding Fields and Adding Custom Fields
 Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through [wiki:TracAdmin trac-admin]. This of course only applies to drop-down fields, such as ''type'', ''priority'', ''severity'', ''component'', ''version'' and ''milestone''.
 …
 Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.
+== Assign-to as Drop-Down List
+== Assign-to as Drop-Down List ==
+If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to `true`. In that case, Trac will populate the list with all users who **have an authenticated session** and possess the `TICKET_MODIFY` [TracPermissions permissions].
+If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to `true`. In that case, Trac will populate the list with all users who have authenticated with the project and possess the  `TICKET_MODIFY` [TracPermissions permissions].
+An authenticated session will be created the first time a user authenticates with the project. You can manually add an authenticated session using the ["TracAdmin#?session add" trac-admin] `session add` command. The `:1` suffix on the session id (i.e. username) is the key to creating an authenticated session:
+{{{#!sh
+trac-admin /path/to/projenv session add <sid>:1 [name] [email]
+}}}
 You may find the dropdown list is //overpopulated// with users that are no longer active in the project. Revoking authentication privileges will not remove the session data that is used to populate the dropdown list. The [wiki:TracAdmin trac-admin] command can be used to list and remove sessions:
 …
 '''Notes:'''
+ - If you need serious flexibility and aren't afraid of a little plugin coding of your own, see [http://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo].
+ - If you need more flexibility and aren't afraid of a little plugin coding of your own, see the [https://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo plugin].
+ - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
+ -  Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
+== Preset Values for New Tickets ==
+== Preset Values for New Tickets
 To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with `variable=value` separated by `&`. Possible variables are:
  * '''type''' — The type droplist
  * '''reporter''' — Name or email of the reporter
  * '''summary''' — Summary line for the ticket
  * '''description''' — Long description of the ticket
  * '''component''' — The component droplist
  * '''version''' — The version droplist
  * '''severity''' — The severity droplist
  * '''keywords''' — The keywords
  * '''priority''' — The priority droplist
  * '''milestone''' — The milestone droplist
  * '''owner''' — The person responsible for the ticket
  * '''cc''' — The list of emails for notifying about the ticket change
+ * '''type''' — The type droplist.
+ * '''reporter''' — Name or email of the reporter.
+ * '''summary''' — Summary line for the ticket.
+ * '''description''' — Long description of the ticket.
+ * '''component''' — The component dropdown list.
+ * '''version''' — The version dropdown list.
+ * '''severity''' — The severity dropdown list.
+ * '''keywords''' — The keywords or tags.
+ * '''priority''' — The priority dropdown list.
+ * '''milestone''' — The milestone dropdown list.
+ * '''owner''' — The person responsible for the ticket.
+ * '''cc''' — The list of emails for notifying about the ticket change.
 Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''
+Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
 ----
 See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
+See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery

wiki/pages/TracUnicode

-                      r40558
+                      r43921
+= Unicode Support in Trac =
+= Unicode Support in Trac
 [[TracGuideToc]]
 Trac encodes all text using [http://en.wikipedia.org/wiki/UTF-8 UTF-8], including text in tickets and wiki pages. Internal processing of text uses true [http://en.wikipedia.org/wiki/Unicode Unicode] representations. As such, it supports most (all?) commonly used character encodings.
+Trac encodes all text using [wikipedia:UTF-8], including text in tickets and wiki pages. Internal processing of text uses true [wikipedia:Unicode] representations. As such, it supports most commonly used character encodings.
 If the default encoding in your source code repository is not UTF-8, you can specify it in the [TracIni#trac-section trac.ini]:
 {{{
+If the default encoding in your source code repository is not UTF-8, you can specify it in your [TracIni#trac-section trac.ini] file:
+{{{#!ini
 default_charset = gbk
 }}}
 …
 To convert your database to UTF-8, the easiest way is to create a dump of the database, convert it into UTF-8, for example using [http://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html iconv], and then import it back into the database.
 == Examples ==
+== Examples
+=== Arabic ===
+=== Arabic
 تراك يقوم بحفظ كل الكلمات باستخدام صيغة UTF-8، بما في ذلك الكلمات المستخدمة في صفحات  التيكت والويكي.
+=== Bulgarian ===
+=== Bulgarian
 Българският език работи ли?
+=== Česky ===
+=== Česky
 Čeština v kódování UTF-8, žádný problém.
+=== Chinese ===
+Traditional: 繁體中文, 漢字測試; Simplified: 简体中文，汉字测试
+=== Chinese
+=== Croatian ===
+Ako podržava srpski i slovenski mora podržavati i Hrvatski - čćžšđ ČĆŽŠĐ
+Traditional: 繁體中文, 漢字測試
+=== English ===
+Simplified: 简体中文，汉字测试
+=== Croatian
+Ako podržava srpski i slovenski mora podržavati i Hrvatski - čćžšđ ČĆŽŠĐ.
+=== English
 Yes indeed, Trac supports English. Fully.
+=== Français ===
+Il est possible d'écrire en Français : à, ç, û, ...
+=== Français
+=== German ===
+Trac-Wiki muß auch deutsche Umlaute richtig anzeigen: ö, ä, ü, Ä, Ö, Ü; und das scharfe ß
+Il est possible d'écrire en Français : à, ç, û.
+=== Greek ===
+=== German
+Trac-Wiki muß auch deutsche Umlaute richtig anzeigen: ö, ä, ü, Ä, Ö, Ü; und das scharfe ß.
+=== Greek
 Τα Ελληνικά υποστηρίζονται επαρκώς επίσης.
+=== Hebrew ===
+=== Hebrew
 אני יכול לאכול זכוכית וזה לא מזיק לי
+=== Hindi ===
+=== Hindi
 अब हिन्दी में।
+=== Hungarian ===
+Árvíztűrő tükörfúrógép
+=== Hungarian
+=== Icelandic ===
+Árvíztűrő tükörfúrógép.
+=== Icelandic
 Ævar sagði við ömmu sína: Sjáðu hvað ég er stór!
+=== Japanese ===
+=== Japanese
 漢字 ひらがな カタカナ ﾊﾝｶｸｶﾅ 日本語試験
+=== Korean ===
+이번에는 한글로 써보겠습니다. 잘 보이나요? 한글
+=== Korean
+=== Latvian ===
+이번에는 한글로 써보겠습니다. 잘 보이나요? 한글.
+=== Latvian
 Latviešu valoda arī strādā!
+=== Lithuanian ===
+Sudalyvaukime ir mes. Ar veikia lietuviškos raidės? ąčęėįšųūž ĄČĘĖĮŠŲŪŽ Žinoma, kad veikia :)
+Kas tie mes?
+=== Lithuanian
+=== Persian (Farsi) ===
+Sudalyvaukime ir mes. Ar veikia lietuviškos raidės? ąčęėįšųūž ĄČĘĖĮŠŲŪŽ Žinoma, kad veikia. Kas tie mes?
+=== Persian (Farsi)
 این یک متن فارسی است ولی امکان نوشتن مستقیم فارسی نیست چون حالت متن از راست به چپ و جود ندارد برای فارسی نوشتن باید از HTML استفاده کنید.
 {{{
 …
 }}}
+=== Polish ===
+Pchnąć w tę łódź jeża lub osiem skrzyń fig; Nocna gżegżółka zawsze dzienną przekuka.
+=== Polish
+=== Portuguese ===
+Pchnąć w tę łódź jeża lub osiem skrzyń fig. Nocna gżegżółka zawsze dzienną przekuka.
+=== Portuguese
 É possível guardar caracteres especias da língua portuguesa, incluindo o símbolo da moeda européia '€', trema 'ü', crase 'à', agudos 'áéíóú', circunflexos 'âêô', til 'ãõ', cedilha 'ç', ordinais 'ªº', grau '°¹²³'.
+=== Russian ===
+Проверка русского языка: кажется работает... И буква "ё" есть...
+=== Russian
+=== Serbian ===
+Проверка русского языка: кажется работает. И буква "ё" есть.
+=== Serbian
 Podržan, uprkos činjenici da se za njegovo pisanje koriste чак два алфабета.
+=== Slovenian ===
+=== Slovenian
 Ta suhi škafec pušča vodo že od nekdaj!
+=== Spanish ===
+Esto es un pequeño texto en Español, donde el veloz murciélago hindú comía cardlllo y kiwi
+=== Spanish
+=== Swedish ===
+Esto es un pequeño texto en Español, donde el veloz murciélago hindú comía cardillo y kiwi.
+=== Swedish
 Räven raskar över isen med luva på.
+=== Thai ===
+=== Thai
 Trac แสดงภาษาไทยได้อย่างถูกต้อง!
+=== Ukrainian ===
+Перевірка української мови...
+=== Ukrainian
+=== Urdu ===
+Перевірка української мови.
+=== Urdu
 ٹریک اردو بھی سپورٹ کرتا ہے۔
+=== Vietnamese ===
+=== Vietnamese
 Viết tiếng Việt cũng được.

wiki/pages/TracUpgrade

-                      r40558
+                      r43921
 === 2. Update the Trac Code #UpdatetheTracCode
+Get the new version as described in TracInstall, or your operating system specific procedure.
+If you already have a 0.12 version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation:
+{{{#!sh
+easy_install --upgrade Trac==1.0
+}}}
+If you do a manual (not operating system-specific) upgrade, you should also stop any running Trac servers before the installation. Doing "hot" upgrades is not advised, especially on Windows ([trac:#7265]).
+Get the new version as described in TracInstall, or through your operating system package manager.
+If you already an earlier version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation:
+{{{#!sh
+easy_install --upgrade Trac==1.2
+}}}
 You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac `.egg` files from former versions.
 …
  * on MacOSX: `/Library/Python/2.X/site-packages`
 You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac`. The exact location depends on your platform. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things.
+You may also want to remove the directory in which your static resources are [TracInstall#cgi-bin deployed]. The exact location depends on your platform. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things.
 === 3. Upgrade the Trac Environment #UpgradetheTracEnvironment
 …
 }}}
 This command will do nothing if the environment is already up-to-date.
+This command will not have any effect if the environment is already up-to-date.
 Note that a backup of your database will be performed automatically prior to the upgrade.
 This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade, run:
+This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade:
 {{{#!sh
 trac-admin /path/to/projenv upgrade --no-backup
 …
 trac-admin /path/to/env deploy /deploy/path
 }}}
+this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
+This will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
 Some web browsers (IE, Opera) cache CSS and Javascript files aggressively, so you may need to instruct your users to manually erase the contents of their browser's cache, a forced refreshed (`<F5>`) should be enough.
 …
 === 6. Steps specific to a given Trac version
 ==== Upgrading from Trac 1.0 to 1.1.x #to1.1.x
+==== Upgrading from Trac 1.0 to 1.2 #to1.2
 ===== Python 2.5 no longer supported
+Upgrade Python to at least 2.6, but not 3.0.
+===== New workflow actions
+The ticket creation step is now controlled with a workflow action. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page.
+Upgrade Python to at least 2.6 or 2.7, but not 3.0 or greater.
+===== Obsolete Plugins
+Trac has added functionality equivalent to the following plugins:
+* [https://trac-hacks.org/wiki/AdminEnumListPlugin AdminEnumListPlugin]
+* [https://trac-hacks.org/wiki/DateFieldPlugin DateFieldPlugin]: see the **time** [TracTicketsCustomFields#AvailableFieldTypesandOptions custom field type]
+* [https://trac-hacks.org/wiki/GroupBasedRedirectionPlugin GroupBasedRedirectionPlugin]: the default handler can set as a user preference.
+* [https://trac-hacks.org/wiki/LinenoMacro LinenoMacro]: see WikiProcessors#AvailableProcessors
+* [https://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin NeverNotifyUpdaterPlugin]: see [TracNotification#notification-subscriber-section notification subscribers]
+* [https://trac-hacks.org/wiki/QueryUiAssistPlugin QueryUiAssistPlugin]: see TracQuery#Filters.
+* [https://trac-hacks.org/wiki/TicketCreationStatusPlugin TicketCreationStatusPlugin]: see [#NewWorkflowActions]
+The plugins should be removed when upgrading Trac to 1.2.
+===== New workflow actions #NewWorkflowActions
+The ticket creation step is controlled with a workflow action. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page.
 ===== New permissions policy for read-only wiki pages
 Since 1.1.2 the read-only attribute of wiki pages is enabled and enforced only when `ReadonlyWikiPolicy` is in the list of active permission policies. If `[trac] permission_policy` has the default value `DefaultPermissionPolicy, LegacyAttachmentPolicy`, then `ReadonlyWikiPolicy` should be automatically appended to the list when upgrading the environment:
 {{{#!ini
 …
  LegacyAttachmentPolicy
 }}}
+If other permission policies are enabled, //trac.ini// will need to be edited to append `ReadonlyWikiPolicy` to the list of active `permission_policies`. See TracFineGrainedPermissions#ReadonlyWikiPolicy for additional details on the proper ordering.
+If other permission policies are enabled, `trac.ini` will need to have `ReadonlyWikiPolicy` appended to the list of active `permission_policies`. See TracFineGrainedPermissions#ReadonlyWikiPolicy for additional details on the proper ordering.
 ==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0
 ===== Python 2.4 no longer supported
 Upgrade Python to at least 2.5, but not 3.0.
+===== Obsolete Plugins
+Trac has added functionality equivalent to the following plugins:
+* [https://trac-hacks.org/wiki/BatchModifyPlugin BatchModifyPlugin]
+* [https://trac-hacks.org/wiki/GitPlugin GitPlugin]
+* [https://trac-hacks.org/wiki/OverrideEditPlugin OverrideEditPlugin]
+The plugins should be removed when upgrading Trac to 1.0.
 ===== Subversion components not enabled by default for new installations
 The Trac components for Subversion support are no longer enabled by default. To enable the svn support, you need to make sure the `tracopt.versioncontrol.svn` components are enabled, for example by setting the following in the TracIni:
 {{{#!ini
 …
 tracopt.versioncontrol.svn.* = enabled
 }}}
 The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled.
 ===== Attachments migrated to new location
 Another step in the automatic upgrade will change the way the attachments are stored. Create a backup of the `attachments` directory before upgrading. In case the `attachments` directory contains some files which are //not// attachments, the last step of the migration to the new layout will fail: the deletion of the now unused `attachments` directory can't be done if there are still files and folders in it. You may ignore this error, but better to move them elsewhere and remove the `attachments` directory manually. The attachments themselves are now all located in your environment below the `files/attachments` directory.
 ===== Behavior of `[ticket] default_owner` changed
 Prior to 1.0, the owner field of new tickets always defaulted to `[ticket] default_owner` when the value was not empty. If the value was empty, the owner field defaulted to to the Component's owner. In 1.0 and later, the `default_owner` must be set to `< default >` to make new tickets default to the Component's owner. This change allows the `default_owner` to be set to an empty value if no default owner is desired.
 …
 ===== Python 2.3 no longer supported
 The minimum supported version of Python is now 2.4.
 ===== SQLite v3.x required
 SQLite v2.x is no longer supported. If you still use a Trac database of this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details.
 ===== [trac:PySqlite] 2 required
 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
+===== Obsolete Plugins
+Trac has added functionality equivalent to the following plugins:
+* [https://trac-hacks.org/wiki/AutoQueryPlugin AutoQueryPlugin]
+* [https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch]
+* [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]: see WikiFormatting#SettingAnchors
+* [https://trac-hacks.org/wiki/TicketChangePlugin TicketChangePlugin]: see [TracPermissions#TicketSystem TICKET_EDIT_COMMENT permission]
+* [https://trac-hacks.org/wiki/TicketDeletePlugin TicketDeletePlugin]: see `tracopt.ticket.deleter`
+* [https://trac-hacks.org/wiki/SubversionLocationPlugin SubversionLocationPlugin]: see TracRepositoryAdmin#Repositories
+* [https://trac-hacks.org/wiki/WikiCreoleRendererPlugin WikiCreoleRendererPlugin]: see [trac:WikiCreole]
+* [https://trac-hacks.org/wiki/RepoRevisionSyntaxPlugin RepoRevisionSyntaxPlugin] (added in 0.12.1)
+The plugins should be removed when upgrading Trac to 0.12.
 ===== Multiple Repository Support
 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
 …
 ===== Improved repository synchronization
 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
 …
 ===== Authz permission checking
 The authz permission checking has been migrated to a fine-grained permission policy. If you use authz permissions (aka `[trac] authz_file` and `authz_module_name`), you must add `AuthzSourcePolicy` in front of your permission policies in `[trac] permission_policies`. You must also remove `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW` and `LOG_VIEW` from your global permissions with `trac-admin $ENV permission remove` or the "Permissions" admin panel.
 ===== Microsecond timestamps
 All timestamps in database tables, except the `session` table, have been changed from "seconds since epoch" to "microseconds since epoch" values. This change should be transparent to most users, except for custom reports. If any of your reports use date/time columns in calculations (e.g. to pass them to `datetime()`), you must divide the values retrieved from the database by 1'000'000. Similarly, if a report provides a calculated value to be displayed as a date/time (i.e. with a column named "time", "datetime", "changetime", "date", "created" or "modified"), you must provide a microsecond timestamp, that is, multiply your previous calculation with 1'000'000.
 ==== Upgrading from Trac 0.10 to Trac 0.11
 ===== Site Templates and Styles
 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
 …
 ===== Trac Macros, Plugins
 The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore due to the drop of [trac:ClearSilver] and the HDF. They need to be converted to the new-style macros, see WikiMacros. When they are converted to the new style, they need to be placed into the plugins directory instead and not wiki-macros, which is no longer scanned for macros or plugins.
 ===== For FCGI/WSGI/CGI users
 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
 {{{#!sh
 …
 ===== Web Admin plugin integrated
 If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
 ===== New Default Configurable Workflow
+When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10.
+Graphically, that looks like this:
+When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10:
 {{{#!Workflow width=500 height=240
 …
 === Wiki Upgrade
 `trac-admin` will not delete or remove default wiki pages that were present in a previous version but are no longer in the new version.
 …
 === Parent dir
 If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work.
 …
 === Changing Database Backend
 The [http://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases.
+The [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [https://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases.
 === Upgrading from older versions of Trac #OlderVersions

wiki/pages/TracWiki

-                      r40558
+                      r43921
 [[TracGuideToc]]
 Trac has a built-in wiki system which you can use for organizing knowledge and information in a very flexible way by [WikiNewPage creating pages] containing an intuitive and easy to learn textual markup. This text markup is also used in all other parts of the system, not only in [wiki:TitleIndex wiki pages], but also in [wiki:TracTickets ticket] description and comments, [wiki:TracChangeset check-in log messages], [wiki:TracRoadmap milestone] descriptions and [wiki:TracReports report] descriptions, even in third-party extensions.
+Trac has a built-in wiki system which you can use for organizing knowledge and information in a very flexible way by [WikiNewPage creating pages] containing an intuitive and easy to learn textual markup. The wiki markup is used throughout Trac, so not only in [wiki:TitleIndex wiki pages], but also in [TracTickets ticket] description and comments, [TracChangeset version control] log messages, [TracRoadmap milestone] descriptions, [TracReports report] descriptions  and even in third-party extensions.
 It allows for formatted text and hyperlinks in and between all Trac modules.
 Editing wiki text is easy, using any web browser and a simple [WikiFormatting formatting system], rather than more complex markup languages like HTML.  The reasoning behind its design is that HTML, with its large collection of nestable tags, is too complicated to allow fast-paced editing, and distracts from the actual content of the pages. Note though that Trac also supports [WikiHtml HTML], [WikiRestructuredText reStructuredText] and [http://www.textism.com/tools/textile/ Textile] as alternative markup formats, which can eventually be used in parts of a page (so called wiki “blocks”).
+Editing wiki text is easy, as compared to complex markup languages like HTML, using any web browser and simple [WikiFormatting formatting]. The motivation for wiki markup is that HTML, with its large collection of nestable tags, is too complicated to allow fast-paced editing, and distracts from the actual content of the pages. Note that Trac also supports [WikiHtml HTML], [WikiRestructuredText reStructuredText] and [https://txstyle.org Textile] as alternative markup formats, which can be used in parts of a page, so called wiki blocks.
 The main goal of the wiki is to make editing text easier and ''encourage'' people to contribute and annotate text content for a project. Trac also provides a simple toolbar to make formatting text even easier, and supports the [http://universaleditbutton.org/Universal_Edit_Button universal edit button] of your browser.
+The main goal of the wiki is to make editing text easy in order to ''encourage'' people to contribute to a project. Trac also provides a simple toolbar to make formatting text even easier, and supports the [http://universaleditbutton.org/Universal_Edit_Button universal edit button] of your browser.
 The wiki itself does not enforce any structure, but rather resembles a stack of empty sheets of paper, where you can organize information and documentation as you see fit, and later reorganize if necessary.
+As contributing to a wiki is essentially building hypertext,
+general advice regarding HTML authoring apply here as well.
+For example, the ''[http://www.w3.org/Provider/Style Style Guide for online hypertext]'' explains how to think about the
+[http://www.w3.org/Provider/Style/Structure.html overall structure of a work]
+and how to organize information [http://www.w3.org/Provider/Style/WithinDocument.html within each document]. One of the most important tips is “make your HTML page such that you can read it even if you don't follow any links.”
+As contributing to a wiki is essentially building hypertext, general advice regarding HTML authoring apply here as well.
+For example, the ''[https://www.w3.org/Provider/Style Style Guide for online hypertext]'' explains how to think about the [https://www.w3.org/Provider/Style/Structure.html overall structure of a work] and how to organize information [https://www.w3.org/Provider/Style/WithinDocument.html within each document]. One of the most important tips is to "make your HTML page such that you can read it, even if you don't follow any links".
 Learn more about:
  * WikiFormatting rules, including advanced topics like WikiMacros and WikiProcessors
  * How to use WikiPageNames and other forms of TracLinks which are used to refer in a precise way to any resource within Trac
+ * WikiFormatting rules, including advanced topics like WikiMacros and WikiProcessors.
+ * How to use WikiPageNames and other forms of TracLinks which are used to refer to any resource within Trac.
 If you want to practice editing, please use the SandBox. Note that not all Trac wikis are editable by anyone, this depends on the local policy; check with your Trac administrators.
+If you want to practice editing, please use the SandBox. Note that not all Trac wiki pages are editable by anyone, this depends on the local policy; check with your Trac administrators.
 Before saving your changes, you can ''Preview'' the page or ''Review the Changes'' you've made.
 You can get an automatic preview of the formatting as you type when you activate the ''Edit Side-by-side'' mode (you have to Preview the page for the setting to take effect). '' There is a [wiki:/TracIni#trac-section configurable delay] between when you make your edit and when the automatic preview will update.''
+Before saving your changes, you can ''Preview'' the page or ''Review Changes'' you have made.
+You can get an automatic preview of the formatting as you type when you activate the ''Edit Side-by-side'' mode. There is a [wiki:TracIni#/auto_preview_timeout configurable delay] between when you make your edit and when the automatic preview will update.
 Some more information about wikis on the web:
  * A definition of [http://wikipedia.org/wiki/Wiki Wiki], in a famous wiki encyclopedia
  * The [http://c2.com/cgi/wiki?WikiHistory History] of the original wiki
  * A wiki page explaining [http://www.usemod.com/cgi-bin/mb.pl?WhyWikiWorks why wiki works]
+ * A definition of [https://wikipedia.org/wiki/Wiki Wiki] according to Wikipedia.
+ * The [http://c2.com/cgi/wiki?WikiHistory history] behind the original wiki.
+ * A wiki page explaining [http://www.usemod.com/cgi-bin/mb.pl?WhyWikiWorks why wiki works].
 ----

wiki/pages/WikiDeletePage

-                      r40558
+                      r43921
 = Deleting a Wiki Page =
 Existing wiki pages can be completely deleted using the ''Delete Page'' or the ''Delete this Version'' buttons at the bottom of the wiki page. These buttons are only visible for users with `WIKI_DELETE` permissions.
+Wiki pages can be completely deleted using the //Delete page// or the //Delete this version// button at the bottom of the wiki page. These buttons are only visible for users that have the `WIKI_DELETE` permission.
 '''Note:''' Deleting a wiki page is an irreversible operation.
+If you want to delete a page because you actually re-created a new page with the same content but a different name, it is recommended to keep the page and use it as a redirection page instead of completely deleting it, as to not frustrate the visitor with broken links when coming to the site from a search engine.
+Deleting specific versions or even complete pages can make sense to remove spam or other abusive submissions.
+In this situation, chances are that you actually wanted to [[WikiNewPage#renaming|rename]] the page instead of doing a copy + delete.
+The ''Rename'' operation also offers you the possibility to create a redirection page.
+However, if you want to delete a page because you re-created a new page with the same content but a different name, it is recommended to keep the page and use it as a redirection page instead of completely deleting it. This will avoid frustrating the visitor with broken links, particularly when coming to the site from a search engine.
+In this situation, chances are that you actually wanted to [[WikiNewPage#renaming|rename]] the page instead of doing a copy and delete.
+The //Rename// operation offers you the possibility to create a redirection page.
 A redirection page is a short page that  contains a link such as  “See !SomeOtherPage”.
-However, deleting specific versions or even complete pages can make sense to remove spam or other abusive submissions.
 ----

wiki/pages/WikiFormatting

-                      r40558
+                      r43921
 Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and powerful whole.
 Trac has a built in small and powerful wiki rendering engine. This wiki engine implements an ever growing subset of the commands from other popular Wikis, especially [http://moinmo.in/ MoinMoin] and [trac:WikiCreole].
+Trac has a built-in small and powerful wiki rendering engine. This wiki engine implements a growing subset of the commands from other popular Wikis, especially [http://moinmo.in/ MoinMoin] and [trac:WikiCreole].
 This page will give you an in-depth explanation of the wiki markup available anywhere WikiFormatting is allowed.
 …
 A few other wiki pages present the advanced features of the Trac wiki markup in more depth:
  - TracLinks covers all the possible ways to refer precisely to any Trac resource or parts thereof
  - WikiPageNames covers the various names a wiki page can take, CamelCase or not
  - WikiMacros lists the macros available for generating dynamic content
  - WikiProcessors and WikiHtml details how parts of the wiki text can be processed in special ways
  - [trac:wiki:TracDev/Proposals/AdvancedWikiOperations AdvancedWikiOperations] provides some operations in uncommon or administrative scenarios
+ - TracLinks covers all the possible ways to refer precisely to any Trac resource or parts thereof.
+ - WikiPageNames covers the various names a wiki page can take, whether in CamelCase or not.
+ - WikiMacros lists the macros available for generating dynamic content.
+ - WikiProcessors and WikiHtml details how parts of the wiki text can be processed in special ways.
+ - [trac:wiki:TracDev/Proposals/AdvancedWikiOperations AdvancedWikiOperations] provides some operations in uncommon or administrative scenarios.
 == Common wiki markup
 …
 {{{#!td
  {{{
  == Level 2 ==
+ == Level 2
  === Level 3 ^([#hn note])^
  }}}
 }}}
 {{{#!td style="padding-left: 2em"
 == Level 2 ==
+== Level 2
 === Level 3 ^([#hn note])^
 }}}
 …
 {{{#!td
  {{{
  * bullets list
+ * bullet list
    on multiple lines
 . nested list
 …
 }}}
 {{{#!td
 * bullets list
+* bullet list
   on multiple lines
 . nested list
 …
  * {{{ ! }}} tells wiki parser to not take the following characters as wiki format, so pay attention to put a space after !, e.g. when ending bold.
  * all the font styles marks have to be used in opening/closing pairs,
    and they must nest properly (in particular, an `''` italic can't be paired
    with a `//` one, and `'''` can't be paired with `**`)
+   and they must nest properly; in particular, an `''` italic can't be paired
+   with a `//` one, and `'''` can't be paired with `**`.
 == Headings
 …
 [=#hn]
 The headline text can be followed by the same number of "=" characters, but this is no longer mandatory.
+The headline text can be followed by the same number of "=" characters, but this is not mandatory. That is, `=== Section3 ===` is identical to `=== Section3`.
 Finally, the heading might optionally be followed by an explicit id. If not, an implicit but nevertheless readable id will be generated.
 …
 == Discussion Citations
 To delineate a citation in an ongoing discussion thread, such as the ticket comment area, e-mail-like citation marks (">", ">>", etc.) may be used.
+To delineate a citation in an ongoing discussion thread, such as the ticket comment area, email-like citation marks (">", ">>", etc.) may be used.
 ||= Wiki Markup =||= Display =||
 …
 === Complex Tables
 If the possibilities offered by the simple "pipe"-based markup for tables described above are not enough for your needs, you can create more elaborated tables by using [#Processors-example-tables WikiProcessor based tables].
+If the possibilities offered by the simple pipe-based markup ('||') for tables described above are not enough for your needs, you can create more elaborate tables by using [#Processors-example-tables WikiProcessor based tables].
 == Links
 Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}.
+Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark ('!'), such as {{{!WikiPageLink}}}.
 ||= Wiki Markup =||= Display =||
 …
 }}}
 It's also very close to the syntax for the corresponding link to that anchor:
+It is also very close to the syntax for the corresponding link to that anchor:
 {{{
 [#point1]
 …
 }}}
 For more complex anchors (e.g. when a custom title is wanted), one can use the Span macro, e.g. `[[span(id=point2, class=wikianchor, title=Point 2, ^(2)^)]]`.
+For more complex anchors (eg when a custom title is wanted), you can use the Span macro: `[[span(id=point2, class=wikianchor, title=Point 2, ^(2)^)]]`.
 == Escaping Links, WikiPageNames and other Markup == #Escaping
 You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark).
+You may avoid making hyperlinks out of TracLinks by preceding an expression with a single exclamation mark ('!').
 ||= Wiki Markup =||= Display =||
 …
   Your comment for editors here
   }}}
   see ;-)
+  see.
   }}}
 }}}
 …
   Your comment for editors here
   }}}
   see ;-)
+  see.
 }}}
 == Miscellaneous
+An horizontal line can be used to separated different parts of your page:
+||= Wiki Markup =||= Display =||
+{{{#!td
+||= Wiki Markup =||= Display =||
+{{{#!td
+  Horizontal line:
   {{{
   Four or more dashes will be replaced
   by an horizontal line (<HR>)
+  by a horizontal line (<HR>)
   ----
   See?
 …
 {{{#!td
 Four or more dashes will be replaced
 by an horizontal line (<HR>)
+by a horizontal line (<HR>)
 ----
 See?
 …
 |----------------------------------
 {{{#!td
+  {{{
+  "macro" style [[br]] line break
+  }}}
+}}}
+{{{#!td
+"macro" style [[br]] line break
+  Two examples of line breaks:
+  {{{
+  "macro" style [[BR]] line break
+  }}}
+  or:
+  {{{
+  !WikiCreole style \\ line\\break
+  }}}
+}}}
+{{{#!td
+"macro" style [[BR]] line break
+!WikiCreole style \\ line\\break
 }}}
 |----------------------------------
-{{{#!td
-  {{{
-  !WikiCreole style \\ line\\break
-  }}}
-}}}
-{{{#!td
-!WikiCreole style \\ line\\break
-}}}

wiki/pages/WikiMacros

-                      r40558
+                      r43921
 = Trac Macros
 [[PageOutline]]
+[[PageOutline(2-5,Contents,pullout)]]
 Trac macros are plugins to extend the Trac engine with custom 'functions' written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting. Its syntax is `[[macro-name(optional-arguments)]]`.
+'''Trac macros''' extend the Trac engine with custom functionality. Macros are a special type of plugin and are written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting.
+The WikiProcessors are another kind of macros. They typically deal with alternate markup formats and transformation of larger "blocks" of information, like source code highlighting. They are used for processing the multiline `{{{#!wiki-processor-name ... }}}` blocks.
+The macro syntax is `[[macro-name(optional-arguments)]]`.
+'''WikiProcessors''' are another kind of macros. They are typically used for source code highlighting, such as `!#python` or `!#apache` and when the source code spans multiple lines, such as:
+{{{
+{{{#!wiki-processor-name
+...
+}}}
+}}}
 == Using Macros
 Macro calls are enclosed in two ''square brackets'' `[[..]]`. Like Python functions, macros can also have arguments, a comma separated list within parentheses `[[..(,)]]`.
+Macro calls are enclosed in double-square brackets `[[..]]`. Like Python functions, macros can have arguments, which is then a comma separated list within parentheses `[[..(,)]]`.
 === Getting Detailed Help
 …
 {{{#!td style="padding-left: 2em"
 {{{#!html
 <div style="font-size: 80%" class="trac-macrolist">
+<div class="trac-macrolist">
 <h3><code>[[Image]]</code></h3>Embed an image in wiki-formatted text.
 The first argument is the file …
+The first argument is the file, as in <code>[[Image(filename.png)]]</code>
 <h3><code>[[InterTrac]]</code></h3>Provide a list of known <a class="wiki" href="/wiki/InterTrac">InterTrac</a> prefixes.
 <h3><code>[[InterWiki]]</code></h3>Provide a description list for the known <a class="wiki" href="/wiki/InterWiki">InterWiki</a> prefixes.
 <h3><code>[[KnownMimeTypes]]</code></h3>List all known mime-types which can be used as <a class="wiki" href="/wiki/WikiProcessors">WikiProcessors</a>.
 Can be …</div>
+</div>
 }}}
 etc.
 …
 == Macros from around the world
 The [http://trac-hacks.org/ Trac Hacks] site provides a wide collection of macros and other Trac [TracPlugins plugins] contributed by the Trac community. If you are looking for new macros, or have written one that you would like to share with the world, don't hesitate to visit that site.
+The [http://trac-hacks.org/ Trac Hacks] site provides a wide collection of macros and other Trac [TracPlugins plugins] contributed by the Trac community. If you are looking for new macros, or have written one that you would like to share, please visit that site.
 == Developing Custom Macros
 …
 For more information about developing macros, see the [trac:TracDev development resources] on the main project site.
 Here are 2 simple examples showing how to create a Macro. Also, have a look at [trac:source:tags/trac-1.0.2/sample-plugins/Timestamp.py Timestamp.py] for an example that shows the difference between old style and new style macros and at the [trac:source:tags/trac-0.11/wiki-macros/README macros/README] which provides a little more insight about the transition.
+Here are 2 simple examples showing how to create a Macro. Also, have a look at [trac:source:tags/trac-1.0.2/sample-plugins/Timestamp.py Timestamp.py] for an example that shows the difference between old style and new style macros and at the [trac:source:tags/trac-0.11/wiki-macros/README macros/README] which provides more insight about the transition.
 === Macro without arguments
 To test the following code, you should saved it in a `timestamp_sample.py` file located in the TracEnvironment's `plugins/` directory.
+{{{
 #!python
+To test the following code, save it in a `timestamp_sample.py` file located in the TracEnvironment's `plugins/` directory.
+{{{#!python
 from datetime import datetime
 # Note: since Trac 0.11, datetime objects are used internally
 …
 === Macro with arguments
 To test the following code, you should save it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory.
+{{{
 #!python
+To test the following code, save it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory.
+{{{#!python
 from genshi.core import Markup
 …
 }}}
 Note that `expand_macro` optionally takes a 4^th^ parameter ''`args`''. When the macro is called as a [WikiProcessors WikiProcessor], it's also possible to pass `key=value` [WikiProcessors#UsingProcessors processor parameters]. If given, those are stored in a dictionary and passed in this extra `args` parameter. On the contrary, when called as a macro, `args` is  `None`. (''since 0.12'').
+Note that `expand_macro` optionally takes a 4^th^ parameter ''`args`''. When the macro is called as a [WikiProcessors WikiProcessor], it is also possible to pass `key=value` [WikiProcessors#UsingProcessors processor parameters]. If given, those are stored in a dictionary and passed in this extra `args` parameter. In the other case, when called as a macro, `args` is `None`. (''since 0.12'').
 For example, when writing:
 …
 [[HelloWorld(<Hello World!>)]]
 }}}
 One should get:
 {{{
 Hello World, text = <Hello World!> , args = {'style': u'polite', 'silent': False, 'verbose': True}
 Hello World, text = <Hello World!> , args = {}
 Hello World, text = <Hello World!> , args = None
+Hello World, text = <Hello World!>, args = {'style': u'polite', 'silent': False, 'verbose': True}
+Hello World, text = <Hello World!>, args = {}
+Hello World, text = <Hello World!>, args = None
 }}}
 Note that the return value of `expand_macro` is '''not''' HTML escaped. Depending on the expected result, you should escape it by yourself (using `return Markup.escape(result)`) or, if this is indeed HTML, wrap it in a Markup object (`return Markup(result)`) with `Markup` coming from Genshi, (`from genshi.core import Markup`).
+Note that the return value of `expand_macro` is '''not''' HTML escaped. Depending on the expected result, you should escape it yourself (using `return Markup.escape(result)`) or, if this is indeed HTML, wrap it in a Markup object (`return Markup(result)`) with `Markup` coming from Genshi (`from genshi.core import Markup`).
 You can also recursively use a wiki Formatter (`from trac.wiki import Formatter`) to process the `text` as wiki markup:
+{{{
+#!python
+{{{#!python
 from genshi.core import Markup
 from trac.wiki.macros import WikiMacroBase

wiki/pages/WikiNewPage

-                      r40558
+                      r43921
 [[TracGuideToc]]
+Note: make sure you actually have the rights to edit wiki pages. If you don't see the **Edit this page** button, read the information relative to the editing policy for your Trac installation (usually on the front page WikiStart), or contact your local Trac administrator.
+You can create a new wiki page by typing the CamelCase name of the page in the quick-search field at the top of the page, or by trying to view a wiki page of that name. Note that a page is "orphaned" by default until it is linked to from another page.
+. Choose a name for your new page. See WikiPageNames for naming conventions.
+. Edit an existing page (or any other resources that support WikiFormatting and add a [TracLinks link] to your new page. Save your changes.
+. Follow the link you created to take you to the new page. Trac will display a "describe !PageName here" message.
+. Click the "Edit this page" button to edit and add content to your new page. Save your changes.
+. All done. Your new page is published.
+You must be granted permission to create wiki pages. If you don't see the **Create this page** button when visiting a non-existent wiki page, you lack appropriate permission. Contact your local Trac administrator for more information.
+You can skip the second step by entering the CamelCase name of the page in the quick-search field at the top of the page. But note that the page will effectively be "orphaned" unless you link to it from somewhere else.
+A new wiki page can also be created as follows:
+. Choose a name for your new page. See WikiPageNames for naming conventions.
+. Edit an existing page or any other resource that support WikiFormatting and add a [TracLinks link] to your new page. If your page name is CamelCase, you can simply type the page name, provided the [TracIni#wiki-section ignore_missing_pages option] is `disabled` (the default).
+. Save your changes.
+. Follow the link you created to take you to the new page.
+. Click the **Create this page** button to enter edit mode and add content to your new page.
+. Save your changes to publish your page.
 == Rename a page #renaming
+While picking up good WikiPageNames is important, you can always change your mind
+and rename the page later.
+While choosing a good [WikiPageNames page name] is important for usability purposes, you can always rename the page later. You will need the WIKI_RENAME permission to rename pages.
+You'll need to ask for the WIKI_RENAME permission in order to be allowed to do this.
+When renaming a page, you'll be offered the possibility to create a redirection page, so that links pointing to the old location will not be left dangling.
+When renaming a page, you'll be offered the possibility to create a page at the old location that contains a link to the new page, so that links pointing to the old location are not "dangling" (i.e. pointing to a non-existent page).
 ----

wiki/pages/WikiPageNames

-                      r40558
+                      r43921
    and with a label: [wiki:"Space Matters" all about white space]
  * or simply: ["WikiPageName"]s
  * even better, the new [[WikiCreole link style]]
+ * even better, the [[WikiCreole link style]]
    and with a label: [[WikiCreole link style|WikiCreole style links]]
 }}}
 …
    and with a label: [wiki:"Space Matters" all about white space]
  * or simply: ["WikiPageName"]s
  * even better, the new [[WikiCreole link style]]
+ * even better, the [[WikiCreole link style]]
    and with a label: [[WikiCreole link style|WikiCreole style links]]
 It is possible to link to a specific ''version'' of a Wiki page as you would do for a specific version of a file, for example: WikiStart@1.
 You can also prevent a !CamelCase name from being interpreted as a [TracLinks link] by quoting it with an exclamation mark: `!CamelCase`. See TracLinks#EscapingLinks.
+You can prevent a !CamelCase name from being interpreted as a [TracLinks link] by quoting it with an exclamation mark: `!CamelCase`. See TracLinks#EscapingLinks.
+As in the example above, you can also append an anchor to a Wiki page name to link to a specific section within that page. The anchor can be seen by hovering the mouse over a section heading, then clicking on the [[html(&para;)]] sign that appears at its end. The anchor is usually generated automatically, but it is also possible to specify it explicitly: see WikiFormatting#using-explicit-id-in-heading.
+As in the example above, you can append an anchor to a Wiki page name to link to a specific section within that page. The anchor can be seen by hovering the mouse over a section heading, then clicking on the [[html(&para;)]] sign that appears at its end. The anchor is usually generated automatically, but it is also possible to specify it explicitly: see WikiFormatting#using-explicit-id-in-heading.
+There are a few options that govern the rendering of WikiPageNames:
+* CamelCase linking to missing pages can be disabled with the `ignore_missing_pages` [https://trac.edgewall.org/wiki/TracIni#wiki-section option]. Linking to missing pages is enabled by default.
+* The `split_page_names` option, when enabled, will split CamelCase words when rendering a link. For example, WikiStart will be rendered as [WikiStart Wiki Start].
 ----

wiki/pages/WikiProcessors

-                      r40558
+                      r43921
  - [#CodeHighlightingSupport syntax highlighting] or for rendering text verbatim
  - rendering [#HTMLrelated Wiki markup inside a context], like inside <div> blocks or <span> or within <td> or <th> table cells
  - using an alternative markup syntax, like [wiki:WikiHtml raw HTML] and [wiki:WikiRestructuredText Restructured Text] or [http://www.textism.com/tools/textile/ textile]
+ - using an alternative markup syntax, like [WikiHtml raw HTML] and [WikiRestructuredText Restructured Text] or [http://www.textism.com/tools/textile/ textile]
 == Using Processors
 …
 The following processors are included in the Trac distribution:
 || '''`#!default`''' || Present the text verbatim in a preformatted text block. This is the same as specifying ''no'' processor name (and no `#!`) ||
+|| '''`#!default`''' || Present the text verbatim in a preformatted text block. This is the same as specifying ''no'' processor name (and no `#!`). ||
 || '''`#!comment`''' || Do not process the text in this section, i.e. contents exist only in the plain text - not in the rendered page. ||
 || '''`#!rtl`''' || Introduce a Right-To-Left block with appropriate CSS direction and styling ''(since 0.12.2)'' ||
+|| '''`#!rtl`''' || Introduce a Right-To-Left block with appropriate CSS direction and styling. ''(since 0.12.2)'' ||
 |||| ||
 ||||= '''[=#HTMLrelated HTML related]''' =||
 || '''`#!html`''' || Insert custom HTML in a wiki page. ||
 || '''`#!htmlcomment`''' || Insert an HTML comment in a wiki page (''since 0.12''). ||
+|| '''`#!htmlcomment`''' || Insert an HTML comment in a wiki page. (''since 0.12'') ||
 || || Note that `#!html` blocks have to be ''self-contained'', i.e. you can't start an HTML element in one block and close it later in a second block. Use the following processors for achieving a similar effect.  ||
 || '''`#!div`''' || Wrap an arbitrary Wiki content inside a <div> element (''since 0.11''). ||
 || '''`#!span`''' || Wrap an arbitrary Wiki content inside a <span> element (''since 0.11''). ||
 || '''`#!td`''' || Wrap an arbitrary Wiki content inside a <td> element (''since 0.12'') ||
 || '''`#!th`''' || Wrap an arbitrary Wiki content inside a <th> element (''since 0.12'') ||
 || '''`#!tr`''' || Can optionally be used for wrapping `#!td` and `#!th` blocks, either for specifying row attributes or better visual grouping (''since 0.12'') ||
+|| '''`#!div`''' || Wrap wiki content inside a <div> element. ||
+|| '''`#!span`''' || Wrap wiki content inside a <span> element. ||
+|| '''`#!td`''' || Wrap wiki content inside a <td> element. (''since 0.12'') ||
+|| '''`#!th`''' || Wrap wiki content inside a <th> element. (''since 0.12'') ||
+|| '''`#!tr`''' || Can optionally be used for wrapping `#!td` and `#!th` blocks, either for specifying row attributes or better visual grouping. (''since 0.12'') ||
 || '''`#!table`''' || Can optionally be used for wrapping `#!tr`, `#!td` and `#!th` blocks, for specifying table attributes. One current limitation however is that tables cannot be nested. (''since 0.12'') ||
 || || See WikiHtml for example usage and more details about these processors. ||
 …
 |||| ||
 ||||= '''[=#CodeHighlightingSupport Code Highlighting Support]''' =||
 || '''`#!c`''' [[BR]] '''`#!cpp`''' (C++) [[BR]] '''`#!python`''' [[BR]] '''`#!perl`''' [[BR]] '''`#!ruby`''' [[BR]] '''`#!php`''' [[BR]] '''`#!asp`''' [[BR]] '''`#!java`''' [[BR]] '''`#!js`''' (Javascript) [[BR]] '''`#!sql`''' [[BR]] '''`#!xml`''' (XML or HTML) [[BR]] '''`#!sh`''' (!Bourne/Bash shell) [[BR]] '''etc.''' [[BR]] || Trac includes processors to provide inline syntax highlighting for source code in various languages. [[BR]] [[BR]] Trac relies on external software packages for syntax coloring, like [http://pygments.org Pygments]. [[BR]] [[BR]] See TracSyntaxColoring for information about which languages are supported and how to enable support for more languages. ||
 |||| ||
 Since 1.1.2 the default, coding highlighting and MIME-type processors support the argument `lineno` for adding line numbering to the code block. When a value is specified, as in `lineno=3`, the numbering will start at the specified value. When used in combination with the `lineno` argument, the `marks` argument is also supported for highlighting lines. A single line number, set of line numbers and range of line numbers are allowed. For example, `marks=3`, `marks=3-6`, `marks=3,5,7` and `marks=3-5,7` are all allowed. The specified values are relative to the numbered lines, so if `lineno=2` is specified to start the line numbering at 2, `marks=2` will result in the first line being highlighted.
+|| '''`#!c`''' [[BR]] '''`#!cpp`''' (C++) [[BR]] '''`#!python`''' [[BR]] '''`#!perl`''' [[BR]] '''`#!ruby`''' [[BR]] '''`#!php`''' [[BR]] '''`#!asp`''' [[BR]] '''`#!java`''' [[BR]] '''`#!js`''' (Javascript) [[BR]] '''`#!sql`''' [[BR]] '''`#!xml`''' (XML or HTML) [[BR]] '''`#!sh`''' (!Bourne/Bash shell) [[BR]] '''etc.''' [[BR]] || Trac includes processors to provide inline syntax highlighting for source code in various languages. [[BR]] [[BR]] Trac relies on [http://pygments.org Pygments] for syntax coloring. [[BR]] [[BR]] See TracSyntaxColoring for information about which languages are supported and how to enable support for more languages. ||
+|||| ||
+Since 1.1.2 the default, coding highlighting and MIME-type processors support the argument `lineno` for adding line numbering to the code block. When a value is specified, as in `lineno=3`, the numbering will start at the specified value. When used in combination with the `lineno` argument, the `marks` argument is also supported for highlighting lines. A single line number, set of line numbers and range of line numbers are allowed. For example, `marks=3`, `marks=3-6`, `marks=3,5,7` and `marks=3-5,7` are all allowed. The specified values are relative to the numbered lines, so if `lineno=2` is specified to start the line numbering at 2, `marks=2` will result in the first line being highlighted.
 Using the MIME type as processor, it is possible to syntax-highlight the same languages that are supported when browsing source code.
 …
 Some examples:
  {{{
+{{{
+#!text/html
+{{{#!text/html
 <h1>text</h1>
 }}}
 …
 {{{#!td
 The result will be syntax highlighted HTML code:
+ {{{#!text/html
+<h1>text</h1>
+ }}}
+The same is valid for all other [TracSyntaxColoring#SyntaxColoringSupport mime types supported].
+}}}
+}}}
+{{{#!td
  {{{
+#!text/html
+<h1>text</h1>
+ }}}
+The same is valid for all other [TracSyntaxColoring#SyntaxColoringSupport mime types supported].
+}}}
+}}}
+{{{#!td
+ {{{
+{{{
+#!diff
+{{{#!diff
 --- Version 55
 +++ Version 56
 …
 {{{#!td
 '''`#!diff`''' has a particularly nice renderer:
+ {{{
+#!diff
+ {{{#!diff
 --- Version 55
 +++ Version 56
 …
 }}}
 For more processor macros developed and/or contributed by users, visit the [th:WikiStart Trac Hacks] community site.
+For more processor macros developed and/or contributed by users, visit the [https://trac-hacks.org Trac Hacks] community site.
 Developing processors is no different from Wiki macros. In fact, they work the same way, only the usage syntax differs. See WikiMacros#DevelopingCustomMacros for more information.

wiki/pages/WikiRestructuredText

-                      r40558
+                      r43921
+= reStructuredText Support in Trac =
+= reStructuredText Support in Trac
+== Introduction
 Trac supports [http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html reStructuredText (RST)] as an alternative to wiki markup where WikiFormatting is used.
 From the reStucturedText webpage:
  "''reStructuredText is an easy-to-read, what-you-see-is-what-you-get plaintext markup syntax and parser   system. It is useful for in-line program documentation (such as Python docstrings), for quickly creating  simple web pages, and for standalone documents. reStructuredText is designed for extensibility for  specific application domains. ''"
 If you want a file from your Subversion repository to be displayed as reStructuredText in the Trac source browser, set `text/x-rst` as the value for the Subversion property `svn:mime-type`. See [trac:source:/trunk/INSTALL this example].
+=== Requirements ===
+To activate RST support in Trac, install the python docutils package: `easy_install docutils`. If not already available on your operating system, you can download it at the [http://docutils.sourceforge.net/rst.html RST Website].
+Do not use the package manager of your OS, eg `apt-get install python-docutils`, because Trac will not find docutils then.
+=== More information on RST ===
+ * reStructuredText Website -- http://docutils.sourceforge.net/rst.html
  * RST Quick Reference -- http://docutils.sourceforge.net/docs/rst/quickref.html
+----
+== Using RST in Trac ==
+ "reStructuredText is an easy-to-read, what-you-see-is-what-you-get plaintext markup syntax and parser system. It is useful for in-line program documentation (such as Python docstrings), for quickly creating simple web pages, and for standalone documents. reStructuredText is designed for extensibility for specific application domains."
+If you want a file from your Subversion repository to be displayed as reStructuredText in the Trac source browser, set `text/x-rst` as the value for the Subversion property `svn:mime-type`, or add the extension `rst` to the filename. See [trac:source:/trunk/INSTALL.rst this example].
+The examples will only be rendered as reStructuredText if docutils is installed. If Pygments is installed but docutils is not installed, the examples will be syntax-highlighted rather than rendered as reStructuredText.
+=== Requirements
+To activate RST support in Trac, install the python docutils package with the command `easy_install docutils`, or through your operating system package manager. If not already available on your operating system, you can download it from [https://pypi.python.org/pypi/docutils PyPI].
+=== More information on RST
+ * [http://docutils.sourceforge.net/rst.html reStructuredText Website]
+ * [http://docutils.sourceforge.net/docs/rst/quickref.html RST Quick Reference]
+== Using RST in Trac
 To specify that a block of text should be parsed using RST, use the ''rst'' processor.
 === TracLinks in reStructuredText ===
+=== TracLinks in reStructuredText
  * Trac provides a custom RST directive `trac::` to allow TracLinks from within RST text.
 …
    {{{#!td
      {{{
+     {{{#!rst
+     This is a reference to |a ticket|
+     .. |a ticket| trac:: #42
+     }}}
+     }}}
+   }}}
+   {{{#!td
+     {{{#!rst
+     This is a reference to |a ticket|
+     .. |a ticket| trac:: #42
+     }}}
+   }}}
+ * You can also use the custom `:trac:` role to create TracLinks in RST.
+   ||= Wiki Markup ||= Display ||
+   {{{#!td
      {{{
+     #!rst
+     This is a reference to |a ticket|
+     .. |a ticket| trac:: #42
+     }}}
+     }}}
+   }}}
+   {{{#!td
+     {{{
+     #!rst
+     This is a reference to |a ticket|
+     .. |a ticket| trac:: #42
+     }}}
+   }}}
+ * Trac allows an even easier way of creating TracLinks in RST, using the custom `:trac:` role.
+   ||= Wiki Markup ||= Display ||
+   {{{#!td
+     {{{
+     {{{
+     #!rst
+     {{{#!rst
      This is a reference to ticket `#12`:trac:
 …
    }}}
    {{{#!td
+     {{{
+     #!rst
+     {{{#!rst
      This is a reference to ticket `#12`:trac:
 …
    }}}
  For a complete example of all uses of the `:trac:` role, please see WikiRestructuredTextLinks.
 === Syntax highlighting in reStructuredText ===
+ For a complete example of all uses of the `:trac:` role, see WikiRestructuredTextLinks.
+=== Syntax highlighting in reStructuredText
 There is a directive for doing TracSyntaxColoring in RST as well. The directive is called code-block:
 …
 {{{#!td
   {{{
+  {{{
+  #!rst
+  {{{#!rst
   .. code-block:: python
 …
 }}}
 {{{#!td
+  {{{
+  #!rst
+  {{{#!rst
   .. code-block:: python
 …
 Note the need to indent the code at least one character after the `.. code-block` directive.
+=== Wiki Macros in reStructuredText ===
+To enable [WikiMacros Wiki Macros] in RST, you use the same directive as for syntax highlighting, ie code-block:
+=== Wiki Macros in reStructuredText
+To enable [WikiMacros Wiki Macros] in RST, you use the same `code-block` directive as for syntax highlighting:
+||= Wiki Markup ||= Display ||
+{{{#!td
+  {{{
+  {{{#!rst
+  .. code-block:: RecentChanges
+     Trac,3
+  }}}
+  }}}
+}}}
+{{{#!td
+  {{{#!rst
+  .. code-block:: RecentChanges
+     Trac,3
+  }}}
+}}}
+Or use the `:code-block:` role for a more concise Wiki Macro-like syntax:
 ||= Wiki Markup ||= Display ||
 …
   #!rst
-  .. code-block:: RecentChanges
-     Trac,3
-  }}}
-  }}}
-}}}
-{{{#!td
-  {{{
-  #!rst
-  .. code-block:: RecentChanges
-     Trac,3
-  }}}
-}}}
-Or a more concise Wiki Macro-like syntax is also available, using the `:code-block:` role:
-||= Wiki Markup ||= Display ||
-{{{#!td
-  {{{
-  {{{
-  #!rst
   :code-block:`RecentChanges:Trac,3`
   }}}
 …
 }}}
 {{{#!td
+  {{{
+  #!rst
+  {{{#!rst
   :code-block:`RecentChanges:Trac,3`
 …
 }}}
+=== Bigger RST Example ===
+=== Bigger RST Example
 The example below should be self-explanatory:
 ||= Wiki Markup ||= Display ||
 {{{#!td
+{{{
+#!html
+<pre class="wiki">{{{
+#!rst
+{{{#!html
+<pre class="wiki">{{{#!rst
 FooBar Header
 =============
 …
 }}}
 {{{#!td
+{{{
+#!rst
+{{{#!rst
 FooBar Header
 =============

wiki/pages/WikiRestructuredTextLinks

-                      r40558
+                      r43921
 {{{
+{{{
+#!rst
+{{{#!rst
 Examples:
 …
 Provided you have [http://docutils.sourceforge.net/ docutils] installed, the above block will render as:
 ----
+{{{
+#!rst
+{{{#!rst
 Examples:
 …
 Note that the above could have been written using substitution references and the `trac::` directive:
 {{{
+{{{
+#!rst
+{{{#!rst
 See |ticket123|.
 …
 ----
+{{{
+#!rst
+{{{#!rst
 See |ticket123|.

wiki/pages/WikiStart

-                      r40558
+                      r43921
+[[TranslatedPages]]
+{{{#!div align=center style="border: none; font-size: 300%"
+Willkommen im TitanNit Projekt[[br]]Welcome to the TitanNit Project
+}}}
+----
+= Welcome to Trac 1.2
+{{{#!div align=center style="border: none; font-size: 115%"
+ [=#point0]'''Bitte wählen Sie Ihre Sprache: \ please select your language''' :
+Trac is a '''minimalistic''' approach to '''web-based''' management of
+'''software projects'''. Its goal is to simplify effective tracking and
+handling of software issues, enhancements and overall progress.
+||= '''[wiki:de/Wiki#point0 Deutsch]''' =||= '''[wiki:en/Wiki#point0 English]''' =||= '''[wiki:fr/Wiki#point0 Français]''' =||= '''[wiki:gr/Wiki#point0 ελληνικός]''' =||= '''[wiki:it/Wiki#point0 Italiano]''' =||= '''[wiki:nl/Wiki#point0 Nederlands]''' =||= '''[wiki:pl/Wiki#point0 Polski]''' =||= '''[wiki:ru/Wiki#point0 Русский]''' =||= '''[wiki:vn/Wiki#point0 Vietnam]''' =||
+||= [[Image(source:/wiki/Wiki-Pictures/DE/de.png,link=wiki:de/Wiki#point0)]] =||= [[Image(source:/wiki/Wiki-Pictures/EN/en.png,link=wiki:en/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/FR/fr.png,link=wiki:fr/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/GR/gr.png,link=wiki:gr/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/IT/it.png,link=wiki:it/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/NL/nl.png,link=wiki:nl/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/PL/pl.png,link=wiki:pl/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/RU/ru.png,link=wiki:ru/Wiki#point0))]] =||= [[Image(source:/wiki/Wiki-Pictures/VN/vn.png,link=wiki:vn/Wiki#point0))]] =||
+[[br]]
+[[br]]
+}}}
+All aspects of Trac have been designed with the single goal to
+'''help developers write great software''' while '''staying out of the way'''
+and imposing as little as possible on a team's established process and
+culture.
+As all Wiki pages, this page is editable, this means that you can
+modify the contents of this page simply by using your
+web-browser. Simply click on the "Edit this page" link at the bottom
+of the page. WikiFormatting will give you a detailed description of
+available Wiki formatting commands.
+"[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
+a new Trac environment, containing a default set of wiki pages and some sample
+data. This newly created environment also contains
+[wiki:TracGuide documentation] to help you get started with your project.
+You can use [wiki:TracAdmin trac-admin] to configure
+[http://trac.edgewall.org/ Trac] to better fit your project, especially in
+regard to ''components'', ''versions'' and ''milestones''.
+TracGuide is a good place to start.
+''' [wiki:TitleIndex#point Title Index] '''[[br]]
+'''[wiki:Wiki-Help-Contents#point0 Wiki Help Contents]'''
+Enjoy! [[BR]]
+''The Trac Team''
+== Starting Points
+ * TracGuide --  Built-in Documentation
+ * [http://trac.edgewall.org/ The Trac project] -- Trac Open Source Project
+ * [http://trac.edgewall.org/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions
+ * TracSupport --  Trac Support
+For a complete list of local wiki pages, see TitleIndex.

Context Navigation

Legend:

Download in other formats: