| 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 | | |
| 6 | | Plugins can be either installed globally, in a shared plugins directory (see [TracIni#GlobalConfiguration Global Configuration]) or locally for specific TracEnvironment, in its `plugins` directory. |
| 7 | | Except for the later case, the components defined in a plugin should be explicitly enabled in the [[TracIni#components-section| [components] ]] section of the trac.ini file. |
| 8 | | |
| 9 | | == Requirements == |
| 10 | | |
| 11 | | To use egg based plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.6) installed. |
| | 4 | From version 0.9 onwards, Trac is extensible with [trac:PluginList plugins]. Plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture], with peculiarities described in the [TracDev/PluginDevelopment plugin development] page. |
| | 5 | |
| | 6 | == Plugin discovery == |
| | 7 | |
| | 8 | From the user's point of view, a plugin is either a standalone .py file or an .egg package. Trac looks for plugins in the global shared plugins directory (see [TracIni#GlobalConfiguration Global Configuration]) and in the `plugins` directory of the local TracEnvironment. Components defined in globally-installed plugins should be explicitly enabled in the [[TracIni#components-section| [components] ]] section of the trac.ini file. |
| | 9 | |
| | 10 | == Requirements for Trac eggs == |
| | 11 | |
| | 12 | To use egg-based plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.6) installed. |
| 20 | | Plugins can also consist of a single `.py` file dropped into either the environment or the shared plugins directory. |
| 21 | | |
| 22 | | == Installing a Trac Plugin == |
| 23 | | |
| 24 | | === For a Single Project === |
| 25 | | |
| 26 | | Plugins are packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are ZIP archives with the file extension `.egg`. |
| 27 | | |
| 28 | | If you have downloaded a source distribution of a plugin, and want to build the `.egg` file, follow this instruction: |
| 29 | | * Unpack the source. It should provide a setup.py. |
| | 22 | Plugins can also consist of a single `.py` file dropped directly into either the project's or the shared `plugins` directory. |
| | 23 | |
| | 24 | == Installing a Trac plugin == |
| | 25 | |
| | 26 | === For a single project === |
| | 27 | |
| | 28 | Plugins are typically packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are .zip archives with the file extension `.egg`. |
| | 29 | |
| | 30 | If you have downloaded a source distribution of a plugin, and want to build the `.egg` file: |
| | 31 | |
| | 32 | * Unpack the source. It should provide `setup.py`. |
| 35 | | Then you will have a *.egg file. Examine the output of running python to find where this was created. |
| 36 | | |
| 37 | | Once you have the plugin archive, you need to copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg. Then, restart the web server (this requirement was not previously mentioned in this document, but in my tests it began working only after I did so). |
| 38 | | |
| 39 | | To uninstall a plugin installed this way, remove the egg from `plugins` directory and restart web server. |
| 40 | | |
| 41 | | Note that the Python version that the egg is built with must |
| 42 | | match the Python version with which Trac is run. If for |
| 43 | | instance you are running Trac under Python 2.5, but have |
| 44 | | upgraded your standalone Python to 2.6, the eggs won't be |
| 45 | | recognized. |
| 46 | | |
| 47 | | Note also that in a multi-project setup, a pool of Python interpreter instances will be dynamically allocated to projects based on need, and since plugins occupy a place in Python's module system, the first version of any given plugin to be loaded will be used for all the projects. In other words, you cannot use different versions of a single plugin in two projects of a multi-project setup. It may be safer to install plugins for all projects (see below) and then enable them selectively on a project-by-project basis. |
| 48 | | |
| 49 | | === For All Projects === |
| | 39 | You should have a *.egg file. Examine the output of running python to find where this was created. |
| | 40 | |
| | 41 | Once you have the plugin archive, copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg. Then restart the web server. If you are running as a [wiki:TracStandalone "tracd" standalone server], restart tracd (kill and run again). |
| | 42 | |
| | 43 | To uninstall a plugin installed this way, remove the egg from the `plugins` directory and restart the web server. |
| | 44 | |
| | 45 | Note: the Python version that the egg is built with ''must'' match the Python version with which Trac is run. For example, if you're running Trac under Python 2.5, but have upgraded your standalone Python to 2.6, the eggs won't be recognized. |
| | 46 | |
| | 47 | Note also: in a multi-project setup, a pool of Python interpreter instances will be dynamically allocated to projects based on need; since plugins occupy a place in Python's module system, the first version of any given plugin to be loaded will be used for all projects. In other words, you cannot use different versions of a single plugin in two projects of a multi-project setup. It may be safer to install plugins for all projects (see below), and then enable them selectively on a project-by-project basis. |
| | 48 | |
| | 49 | === For all projects === |
| 58 | | If `easy_install` is not on your system see the Requirements section above to install it. Windows users will need to add the `Scripts` directory of their Python installation (for example, `C:\Python24\Scripts`) to their `PATH` environment variable (see [http://peak.telecommunity.com/DevCenter/EasyInstall#windows-notes easy_install Windows notes] for more information). |
| 59 | | |
| 60 | | If Trac reports permission errors after installing a zipped egg |
| 61 | | {{{ |
| 62 | | easy_install --always-unzip TracSpamFilter-0.2.1dev_r5943-py2.4.egg |
| | 58 | If `easy_install` is not on your system, see the Requirements section above to install it. Windows users will need to add the `Scripts` directory of their Python installation (for example, `C:\Python24\Scripts`) to their `PATH` environment variable (see [http://peak.telecommunity.com/DevCenter/EasyInstall#windows-notes easy_install Windows notes] for more information). |
| | 59 | |
| | 60 | If Trac reports permission errors after installing a zipped egg, and you would rather not bother providing a 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`: |
| | 61 | {{{ |
| | 62 | easy_install --always-unzip TracSpamFilter-0.4.1_r10106-py2.6.egg |
| 76 | | 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 shared plugins directory, i.e. the path specified in the `[inherit] plugins_dir` configuration option. |
| 77 | | |
| 78 | | This is done in the `[components]` section of the configuration file, for example: |
| | 76 | |
| | 77 | Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This also applies to plugins installed in the shared plugins directory, i.e. the path specified in the `[inherit] plugins_dir` configuration option. |
| | 78 | |
| | 79 | This is done in the `[components]` section of the configuration file. For example: |
| 92 | | 1. Delete executables from `/usr/bin`, `/usr/local/bin` or `C:\\Python*\Scripts`. For search what executables are there, you may refer to `[console-script]` section of `setup.py`. |
| 93 | | 1. Delete the .egg file or folder from where it is installed, usually inside `$PYTHONLIB/site-packages/`. |
| 94 | | 1. Restart |
| 95 | | |
| 96 | | If you are uncertain about the location of the egg, here is a small tip to help locate an egg (or any package) - replace `myplugin` with whatever namespace the plugin uses (as used when enabling the plugin): |
| | 94 | 1. Delete executables from `/usr/bin`, `/usr/local/bin`, or `C:\\Python*\Scripts`. To find what executables are involved, refer to the `[console-script]` section of `setup.py`. |
| | 95 | 1. Delete the .egg file or folder from where it's installed (usually inside `$PYTHONLIB/site-packages/`). |
| | 96 | 1. Restart the web server. |
| | 97 | |
| | 98 | If you are uncertain about the location of the egg, here's a small tip to help locate an egg (or any package). Just replace `myplugin` with whatever namespace the plugin uses (as used when enabling the plugin): |
| 103 | | == Setting up the Plugin Cache == |
| 104 | | |
| 105 | | 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. |
| 106 | | |
| 107 | | To do this from the Apache configuration, use the `SetEnv` directive as follows: |
| | 105 | == Setting up the plugin cache == |
| | 106 | |
| | 107 | 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. |
| | 108 | |
| | 109 | To do this from the Apache configuration, use the `SetEnv` directive: |
| 164 | | |
| 165 | | 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: |
| 166 | | * you actually added the necessary line(s) to the `[components]` section |
| 167 | | * the package/module names are correct |
| 168 | | * the value is “enabled", not e.g. “enable” |
| 169 | | |
| 170 | | === Check the permissions on the egg file === |
| 171 | | |
| 172 | | Trac must be able to read the file. |
| | 166 | If you install a plugin globally (i.e., ''not'' inside the `plugins` directory of the Trac project environment), you must explicitly enable it in [TracIni trac.ini]. Make sure that: |
| | 167 | |
| | 168 | * ...you actually added the necessary line(s) to the `[components]` section. |
| | 169 | * ...the package/module names are correct. |
| | 170 | * ...the value is "enabled", not "enable" or "Enable". |
| | 171 | * ...the section name is "components", not "component". |
| | 172 | |
| | 173 | === Check the permissions on the .egg file === |
| | 174 | |
| | 175 | Trac must be able to read the .egg file. |
| 185 | | * Only one version of the plugin can be loaded for each running Trac server (ie. each Python process). The Python namespaces and module list will be shared, and it cannot handle duplicates. Whether a plugin is `enabled` or `disabled` makes no difference. |
| 186 | | * A globally installed plugin (typically `setup.py install`) will override any version in global or project plugins directories. A plugin from the global plugins directory will be located before any project plugins directory. |
| 187 | | * If your Trac server hosts more than one project (as with `TRAC_ENV_PARENT_DIR` setups), then having two versions of a plugin in two different projects will give uncertain results. Only one of them will load, and the one loaded will be shared by both projects. Trac will load the first found - basically from the project that receives the first request. |
| 188 | | * Having more than one version listed inside Python site-packages is fine (ie. installed with `setup.py install`) - setuptools will make sure you get the version installed most recently. However, don't store more than one version inside a global or project plugins directory - neither version number nor installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins. |
| | 188 | |
| | 189 | * Only one version of the plugin can be loaded for each running Trac server (i.e., each Python process). The Python namespaces and module list will be shared, and it cannot handle duplicates. Whether a plugin is `enabled` or `disabled` makes no difference. |
| | 190 | * A globally-installed plugin (typically `setup.py install`) will override any version in the global or project plugins directories. A plugin from the global plugins directory will be located ''before'' any project plugins directory. |
| | 191 | * If your Trac server hosts more than one project (as with `TRAC_ENV_PARENT_DIR` setups), having two versions of a plugin in two different projects will give uncertain results. Only one of them will load, and the one loaded will be shared by both projects. Trac will load the first plugin found, usually from the project that receives the first request. |
| | 192 | * Having more than one version listed inside Python site-packages is fine (i.e., installed with `setup.py install`) -- setuptools will make sure you get the version installed most recently. However, don't store more than one version inside a global or project plugins directory -- neither version number nor installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins. |
| 192 | | 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. |
| | 196 | Okay, so the logs don't mention plugins, the egg is readable, the Python version is correct, ''and'' the egg has been installed globally (and is enabled in trac.ini)... and it ''still'' doesn't work or give any error messages or any other indication as to why. Hop on the [trac:IrcChannel IrcChannel] and ask away! |
| | 197 | |
| | 198 | == Web-based plugin administration == |
| | 199 | |
| | 200 | The WebAdmin plugin (part of the core since 0.11) offers limited support for plugin configuration through the web to users with `TRAC_ADMIN` permission: |
| | 201 | |
| | 202 | * en/disabling installed plugins |
| | 203 | * installing plugins by uploading them as eggs |
| | 204 | |
| | 205 | You probably want to disable the second function for security reasons: in `trac.ini`, in the `[components]` section, add the line |
| | 206 | {{{ |
| | 207 | trac.admin.web_ui.PluginAdminPanel = disabled |
| | 208 | }}} |
| | 209 | This disables the whole panel, so the first function will no longer be available either. |
![(please configure the [header_logo] section in trac.ini)](/chrome/site/cardinal.gif)
