* Set exec bit for *_frontends (Closes: #510441), thanks to Torsten Landschoff for the patch. * Move python-psycopg2 and python-mysql from Suggests to Depends as alternative to python-psqlite2 (Closes: #513117). * Use debhelper 7 (Closes: #497862). * Don't compress *-hook files and don't install MS-Windows *.cmd files (Closes: #526142), thanks to Jan Dittberner for the patch. * Add README.source to point to dpatch.
Since version 0.9, Trac supports [PluginList plugins] that extend the built-in functionality. The plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture].
4
Since version 0.9, Trac supports [trac:PluginList plugins] that extend the built-in functionality. The plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture].
5
5
6
6
== Requirements ==
7
7
70
70
}}}
71
71
72
72
==== Enabling the plugin ====
73
Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This is done in the `[components]` section of the configuration file, for example:
73
Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This also applies to plugins installed in the path specified in the `[inherit] plugins_dir` configuration option. This is done in the `[components]` section of the configuration file, for example:
74
74
{{{
75
75
[components]
76
76
tracspamfilter.* = enabled
97
97
98
98
== Setting up the Plugin Cache ==
99
99
100
Some plugins will need to be extracted by the Python eggs runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory in which they are extracted defaults to the home directory of the current user, which may or may not be a problem. You can however override the default location using the `PYTHON_EGG_CACHE` environment variable.
100
Some plugins will need to be extracted by the Python eggs runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory in which they are extracted defaults to '.python-eggs' in the home directory of the current user, which may or may not be a problem. You can however override the default location using the `PYTHON_EGG_CACHE` environment variable.
101
101
102
102
To do this from the Apache configuration, use the `SetEnv` directive as follows:
103
103
{{{
123
123
</Location>
124
124
}}}
125
125
126
''Note: this requires the `mod_env` module''
126
''Note: !SetEnv requires the `mod_env` module which needs to be activated for Apache. In this case the !SetEnv directive can also be used in the `mod_python` Location block.''
127
127
128
128
For [wiki:TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables.
129
129
130
''Note: that if you already use -initial-env to set the project directory for either a single project or parent you will need to add atleast one environment variable inside trac.fcgi as expressed in the example on [wiki:TracFastCgi TracFastCgi].
130
''Note: that if you already use -initial-env to set the project directory for either a single project or parent you will need to add an additional -initial-env directive to the !FastCgiConfig directive. I.e.
If you install a plugin globally (i.e. ''not'' inside the `plugins` directory of the Trac project environment) you will have to explicitly enable it in [TracIni trac.ini]. Make sure that:
156
161
* you actually added the necessary line(s) to the `[components]` section
157
162
* the package/module names are correct
167
172
168
173
=== Verify you have proper permissions ===
169
174
170
Some plugins require you have special permissions in order to use them. WebAdmin, for example, requires the user to have TRAC_ADMIN permissions for it to show up on the navigation bar.
175
Some plugins require you have special permissions in order to use them. [trac:WebAdmin WebAdmin], for example, requires the user to have TRAC_ADMIN permissions for it to show up on the navigation bar.
171
176
172
177
=== Is the wrong version of the plugin loading? ===
173
178
179
184
180
185
=== If all of the above failed ===
181
186
182
OK, so the logs don't mention plugins, the egg is readable, the python version is correct ''and'' the egg has been installed globally (and is enabled in the trac.ini) and it still doesn't work or give any error messages or any other indication as to why? Hop on the IrcChannel and ask away.
187
OK, so the logs don't mention plugins, the egg is readable, the python version is correct ''and'' the egg has been installed globally (and is enabled in the trac.ini) and it still doesn't work or give any error messages or any other indication as to why? Hop on the [trac:IrcChannel IrcChannel] and ask away.
183
188
184
189
----
185
190
See also TracGuide, [trac:PluginList plugin list], [trac:TracDev/ComponentArchitecture component architecture]