Changes between Version 5 and Version 6 of TracPlugins


Ignore:
Timestamp:
04/19/23 14:06:21 (20 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracPlugins

    v5 v6  
    1 = Trac plugins =
    2 [[TracGuideToc]]
    3 
    4 Trac is extensible with [trac:PluginList plugins]. Plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture], with peculiarities described in the [trac: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.
    13 
    14 To install `setuptools`, download the bootstrap module [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py] and execute it as follows:
    15 
    16 {{{
    17 $ python ez_setup.py
    18 }}}
    19 
    20 If the `ez_setup.py` script fails to install the setuptools release, you can download it from [http://www.python.org/pypi/setuptools PyPI] and install it manually.
    21 
    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`.
    33  * Run:
    34 
    35 {{{
     1[[PageOutline(2-5,Contents,pullout)]]
     2
     3= Trac plugins
     4
     5Trac is extensible with [trac:PluginList plugins]. Plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture], described in the [trac:TracDev/PluginDevelopment plugin development] page.
     6
     7== Plugin discovery
     8
     9A plugin is either a single .py file or a package (.egg or .whl). Trac looks for plugins in Python's `site-packages` directory, the [TracIni#GlobalConfiguration global shared] `plugins` directory and the [TracEnvironment project environment] `plugins` directory. Plugins installed to the project environment `plugins` directory are enabled, unless explicitly disabled in the `[components]` section of the `trac.ini` file.  Plugins installed elsewhere must be explicitly enabled in the [TracIni#components-section "[components]"] section of the `trac.ini` file.
     10
     11== Installing a Trac plugin
     12
     13The instructions below are applicable to a plugins installed as packages. 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.
     14
     15=== For a single project
     16
     17Packages built for a single project must use the egg format, as the wheel format (described below) is not supported by the setuptools loading mechanism. Build the `egg` file from the plugin source:
     18
     19* Checkout or download and unpack the source.
     20* Change to the directory containing `setup.py` and run:
     21 {{{#!sh
    3622$ python setup.py bdist_egg
    3723}}}
    38 
    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 ===
    50 
    51 ==== With an .egg file ====
    52 
    53 Some plugins (such as [trac:SpamFilter SpamFilter]) are downloadable as an `.egg` file that can be installed with the `easy_install` program:
    54 {{{
    55 easy_install TracSpamFilter
    56 }}}
    57 
    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
    63 }}}
    64 You should end up with a directory having the same name as the zipped egg (complete with `.egg` extension) and containing its uncompressed contents.
    65 
    66 Trac also searches for plugins installed in the shared plugins directory, see TracIni#GlobalConfiguration. This is a convenient way to share the installation of plugins across several, but not all, environments.
    67 
    68 ==== From source ====
    69 
    70 `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:
    71 {{{
    72 easy_install http://svn.edgewall.com/repos/trac/plugins/0.12/spam-filter-captcha
    73 }}}
    74 
    75 ==== Enabling the plugin ====
    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:
    80 {{{
     24 The egg file will be created in the `dist` subdirectory.
     25* Copy the egg file to the `plugins` directory of the [TracEnvironment project environment].
     26
     27Make sure the web server has sufficient permissions to read the plugin egg and restart the web server. If you are running as a [TracStandalone "tracd" standalone server], restart tracd (i.e. kill the process and run again).
     28
     29Trac also searches for plugins installed in the [TracIni#GlobalConfiguration global shared] plugins directory. This is a convenient way to share the installation of plugins across several, but not all, environments.
     30
     31'''Note''': The minor version number of the Python used to build the egg ''must'' match the minor version number of the Python running Trac. For example, if you are running Trac with Python 2.6, but build the egg with Python 2.7, the egg won't be recognized.
     32
     33'''Note''': In a multi-project setup, a pool of Python interpreters 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 plugin in different projects of a multi-project setup. Install plugins for all projects (see below) and enable them as needed for each project.
     34
     35==== Uninstalling #UninstallEgg
     36
     37Remove the egg from the `plugins` directory and restart the web server.
     38
     39=== For all projects
     40
     41==== Using pip
     42
     43The modern Python package manager, `pip`, is included in Python 2.7.9 and later. In earlier versions of Python it can be installed through the package manager of your OS (e.g. `apt-get install python-pip`) or using [https://pip.pypa.io/en/latest/installing.html#install-pip get_pip.py].
     44
     45Using `pip`, the plugin will be installed
     46in the [https://pythonwheels.com/ wheel format], which is the modern standard for Python and a
     47replacement for the egg format.
     48
     49==== From PyPI
     50
     51Some plugins, such as [https://trac-hacks.org/wiki/TagsPlugin TracTags], can be installed directly from [https://pypi.org PyPI] using `pip`:
     52{{{#!sh
     53$ pip install TracTags
     54}}}
     55
     56The version can be specified, which can be useful if you don't want to install the latest:
     57{{{#!sh
     58$ pip install TracTags==0.10
     59}}}
     60
     61==== From source
     62
     63You can install directly from a source repository:
     64{{{#!sh
     65$ pip install svn+https://trac-hacks.org/svn/tagsplugin/trunk
     66}}}
     67
     68Replace the `svn+` prefix with `git+` if installing
     69from a Git repository.
     70
     71Or from the path or URL of a tar.gz or zip archive:
     72{{{#!sh
     73$ pip install https://trac-hacks.org/browser/tagsplugin/trunk?format=zip
     74}}}
     75
     76Or checkout the source and provide `pip` a path to the source directory:
     77{{{#!sh
     78$ svn co https://trac-hacks.org/svn/tagsplugin/trunk tractags
     79$ pip install tractags
     80}}}
     81
     82==== Enabling the plugin
     83
     84Unlike plugins installed per environment, you have to explicitly enable globally installed plugins. This also applies to plugins installed in the shared plugins directory.
     85
     86This is done in the `[components]` section of the configuration file `trac.ini`. For example:
     87{{{#!ini
    8188[components]
    82 tracspamfilter.* = enabled
    83 }}}
    84 
    85 The name of the option is the Python package of the plugin. This should be specified in the documentation of the plugin, but can also be easily discovered by looking at the source (look for a top-level directory that contains a file named `__init__.py`).
    86 
    87 Note: After installing the plugin, you must restart your web server.
    88 
    89 ==== Uninstalling ====
    90 
    91 `easy_install` or `python setup.py` does not have an uninstall feature. Hower, it is usually quite trivial to remove a globally-installed egg and reference:
    92 
    93  1. Do `easy_install -m [plugin name]` to remove references from `$PYTHONLIB/site-packages/easy-install.pth` when the plugin installed by setuptools.
    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):
    99 {{{
    100 >>> import myplugin
    101 >>> print myplugin.__file__
    102 /opt/local/python24/lib/site-packages/myplugin-0.4.2-py2.4.egg/myplugin/__init__.pyc
    103 }}}
    104 
    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.
     89tractags.* = enabled
     90}}}
     91
     92The name of the option is the plugin package name. This should be specified in the documentation of the plugin, but can also be discovered by looking at the source: it is usually the top-level directory name containing a file named `__init__.py`.
     93
     94Plugins can also be enabled from the [#Web-basedpluginadministration administration] page.
     95
     96After installing the plugin, you must restart your web server.
     97
     98==== Upgrading the environment
     99
     100Some plugins 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:
     101
     102{{{#!sh
     103$ trac-admin /path/to/env upgrade
     104}}}
     105
     106A 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`.
     107
     108==== Redeploying static resources
     109
     110If you [TracInstall#MappingStaticResources mapped static resources] so they are served by the web server, and the plugin contains static resources (CSS, !JavaScript and image files), the resources will need to be deployed to the location on the filesystem that is served by the web server.
     111
     112Execute the `deploy` command, as is done during install and [TracUpgrade#a5.Refreshstaticresources upgrade]:
     113
     114{{{#!sh
     115$ trac-admin /path/to/env deploy /deploy/path
     116}}}
     117
     118After executing the command, you must restart your web server.
     119
     120{{{#!div style="border: 1pt dotted; margin: 1em"
     121**Note:** Some web browsers (IE, Opera) cache CSS and Javascript files, so you should instruct your users to manually erase the contents of their browser's cache. A forced refreshed (SHIFT + <F5>) should be enough.
     122{{{#!comment
     123Remove above note once #9936 is fixed.
     124}}}
     125}}}
     126
     127==== Uninstalling #UninstallWithPip
     128
     129Get a list of installed plugins:
     130{{{#!sh
     131$ pip list
     132Package    Version
     133---------- -------
     134Jinja2     2.10.1
     135MarkupSafe 1.1.1
     136pip        19.2.2
     137setuptools 41.2.0
     138Trac       1.4
     139TracTags   0.10
     140wheel      0.33.6
     141}}}
     142
     143Uninstall a plugin by specifying the package name:
     144{{{#!sh
     145$ pip uninstall TracTags
     146}}}
     147
     148== Web-based plugin administration
     149
     150The admin page offers limited support for plugin configuration to users with `TRAC_ADMIN` permission:
     151
     152* en/dis-abling installed plugins
     153* installing plugins by uploading them as eggs
     154
     155If you wish to disable the second function for security reasons, add the following to your `trac.ini` file:
     156{{{#!ini
     157[components]
     158trac.admin.web_ui.PluginAdminPanel = disabled
     159}}}
     160This disables the whole panel, so the first function will no longer be available.
     161
     162== Setting up the plugin cache
     163
     164Some plugins installed as eggs will need to be extracted by the Python egg's runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory to 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.
    108165
    109166To do this from the Apache configuration, use the `SetEnv` directive:
    110 {{{
     167{{{#!apache
    111168SetEnv PYTHON_EGG_CACHE /path/to/dir
    112169}}}
    113170
    114 This works whether you're using the [wiki:TracCgi CGI] or the [wiki:TracModPython mod_python] front-end. Put this directive next to where you set the path to the [wiki:TracEnvironment Trac environment], i.e. in the same `<Location>` block.
    115 
    116 For example (for CGI):
    117 {{{
     171This works whether you're using the [TracCgi CGI] or the [TracModPython mod_python] front-end. Put this directive next to where you set the path to the [TracEnvironment Trac environment], i.e. in the same `<Location>` block.
     172
     173For example for CGI:
     174{{{#!apache
    118175 <Location /trac>
    119176   SetEnv TRAC_ENV /path/to/projenv
    … …  
    122179}}}
    123180
    124 Or (for mod_python):
    125 {{{
     181Or for mod_python:
     182{{{#!apache
    126183 <Location /trac>
    127184   SetHandler mod_python
    … …  
    131188}}}
    132189
    133  ''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.''
    134 
    135 For [wiki:TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables.
    136 
    137  ''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.
    138 
    139 {{{
     190'''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.
     191
     192For [TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables.
     193
     194'''Note''': 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:
     195
     196{{{#!apache
    140197FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac -initial-env PYTHON_EGG_CACHE=/var/lib/trac/plugin-cache
    141198}}}
    142199
    143 === About hook scripts ===
    144 
    145 If you've set up some subversion hook scripts that call the Trac engine, such as the post-commit hook script provided in the `/contrib` directory, make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts as well.
    146 
    147 == Troubleshooting ==
    148 
    149 === Is setuptools properly installed? ===
    150 
    151 Try this from the command line:
    152 {{{
    153 $ python -c "import pkg_resources"
    154 }}}
    155 
    156 If you get '''no output''', setuptools '''is''' installed. Otherwise, you'll need to install it before plugins will work in Trac.
    157 
    158 === Did you get the correct version of the Python egg? ===
     200=== About hook scripts
     201
     202If you have Subversion hook scripts that invoke Trac, such as the post-commit hook script provided in the `/contrib` directory, make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts.
     203
     204== Writing Trac Plugins
     205
     206You can write your own Trac plugin using the following resources:
     207* [trac:TracDev Developer documentation]
     208* [https://trac-hacks.org Examples on trac-hacks.org]
     209* [trac:browser:branches/1.4-stable/sample-plugins sample-plugins]
     210
     211== Troubleshooting
     212
     213=== Did you get the correct version of the Python egg?
    159214
    160215Python eggs have the Python version encoded in their filename. For example, `MyPlugin-1.0-py2.5.egg` is an egg for Python 2.5, and will '''not''' be loaded if you're running a different Python version (such as 2.4 or 2.6).
    161216
    162 Also, verify that the egg file you downloaded is indeed a .zip archive. If you downloaded it from a Trac site, chances are you downloaded the HTML preview page instead.
    163 
    164 === Is the plugin enabled? ===
    165 
    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.
    176 
    177 === Check the log files ===
    178 
    179 Enable [wiki:TracLogging logging] and set the log level to `DEBUG`, then watch the log file for messages about loading plugins.
    180 
    181 === Verify you have proper permissions ===
    182 
    183 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.
    184 
    185 === Is the wrong version of the plugin loading? ===
    186 
    187 If you put your plugins inside plugins directories, and certainly if you have more than one project, you need to make sure that the correct version of the plugin is loading. Here are some basic rules:
    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.
    193 
    194 === If all of the above failed ===
    195 
    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 interface 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.
     217Also, verify that the egg file you downloaded is indeed a .zip archive. If you downloaded it from a Trac site, you may have downloaded the HTML preview page instead.
     218
     219=== Is the plugin enabled?
     220
     221If 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:
     222
     223 * you added the necessary line(s) to the `[components]` section.
     224 * the package/module names are correct and do not contain typos.
     225 * the value is `enabled`, not `enable` or `Enable`.
     226 * the section name is `components`, not `component`.
     227
     228=== Check the permissions
     229
     230Trac must be able to read the .py file or package (.egg or .whl).
     231
     232=== Check the log files
     233
     234See [trac:TracTroubleshooting#ChecktheLogs].
     235
     236=== Verify you have the proper permissions
     237
     238Some plugins require you have special permissions. !TracTags, for example, requires `TAGS_VIEW` permissions for the //Tags// navigation item to be added.
     239
     240=== Is the wrong version of the plugin loading?
     241
     242If you put your plugins in one of the `plugins` directories, and certainly if you have more than one project, you need to make sure that the correct version of the plugin is loading. Here are some basic rules:
     243
     244* 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.
     245* A globally installed plugin will override any version in the global or project plugins directories. A plugin from the global plugins directory will be discovered ''before'' any project plugins directory.
     246* 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 unpredicatable 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.
     247* Having more than one version listed inside Python site-packages is fine, because 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 the version number nor the 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.
     248
     249=== If all of the above failed
     250
     251See TracSupport.
    210252
    211253----
    212 See also TracGuide, [trac:PluginList plugin list], [trac:TracDev/ComponentArchitecture component architecture].
     254See also TracGuide, TracIni.