Changes between Version 1 and Version 2 of TracPlugins


Ignore:
Timestamp:
Jan 30, 2006, 11:09:12 PM (19 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracPlugins

    v1 v2  
    11= Trac Plugins =
     2[[TracGuideToc]]
    23
    34Since version 0.9, Trac supports plugins that extend the built-in functionality. The plugin functionality is based on the [http://projects.edgewall.com/trac/wiki/TracDev/ComponentArchitecture component architecture].
    … …  
    56== Requirements ==
    67
    7 To use plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.5 or 0.6) installed.
     8To use plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.6) installed.
    89
    910To install `setuptools`, download the bootstrap module [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py] and execute it as follows:
    … …  
    3435
    3536Alternatively, you can just drop the `.egg` file in the Python `site-packages` directory.
     37
     38Unlike 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:
     39{{{
     40[components]
     41webadmin.* = enabled
     42}}}
     43
     44The 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 find out by looking at the source (look for a top-level directory that contains a file named `__init__.py`.)
    3645
    3746== Setting up the Plugin Cache ==
    … …  
    6675
    6776----
    68 See also TracGuide, [wiki:TracDev/ComponentArchitecture component architecture]
     77See also TracGuide, [http://projects.edgewall.com/trac/wiki/PluginList plugin list], [http://projects.edgewall.com/trac/wiki/TracDev/ComponentArchitecture component architecture]