Skip to content

Commit

Permalink
[#523] Remove erroneous section on plugin ordering
Browse files Browse the repository at this point in the history
  • Loading branch information
tobes committed Apr 22, 2013
1 parent 86ed2f7 commit 56588ef
Showing 1 changed file with 0 additions and 22 deletions.
22 changes: 0 additions & 22 deletions doc/extensions.rst
Expand Up @@ -414,28 +414,6 @@ At this point you should be able to write your own plugins and extensions
together with their tests.


Ordering of Extensions
----------------------

.. caution ::
The order in which extensions are initially loaded is **different** to the order that their plugins are run.
The order in which extensions are initially loaded is as follows:

1. System plugins (in setup.py under ``ckan.system_plugins``).

2. In order of the plugins specified in the config file: ``plugins =``.

3. If more than one module has a plugin with the same name specified in the config, then all those are loaded, in the order the modules appear in ``sys.path``.

The order that a plugins are run in, for example the order that IRoutes extensions have their ``before_map`` method run, is alphabetical by the plugin class.

e.g. here is the order for these four extensions: ``<Plugin DguInventoryPlugin>``, ``<Plugin FormApiPlugin>``, ``<Plugin StatsPlugin>``, ``<Plugin WalesThemePlugin>``

(This alphabetical ordering is done by ``pyutilib.component.core:ExtensionPoint.extensions()``)


Plugin API Documentation
------------------------

Expand Down

0 comments on commit 56588ef

Please sign in to comment.