Difference between revisions of "Plugin"

From Joomla! Documentation

m
m
Line 1: Line 1:
[[Category:Development]]
+
[[Category:Bin]]
 
====== Plugins ======
 
====== Plugins ======
 
Joomla! plugins enable you to execute code in response to certain events, either Joomla! core events or custom events that are triggered from your own code.  This is a powerful way of extending the basic Joomla! functionality.  To see where plugins fit in with the overall Joomla! architecture, look at [[http://dev.joomla.org/content/view/1137/80/|Framework overview]].
 
Joomla! plugins enable you to execute code in response to certain events, either Joomla! core events or custom events that are triggered from your own code.  This is a powerful way of extending the basic Joomla! functionality.  To see where plugins fit in with the overall Joomla! architecture, look at [[http://dev.joomla.org/content/view/1137/80/|Framework overview]].

Revision as of 17:17, 9 July 2008

Plugins[edit]

Joomla! plugins enable you to execute code in response to certain events, either Joomla! core events or custom events that are triggered from your own code. This is a powerful way of extending the basic Joomla! functionality. To see where plugins fit in with the overall Joomla! architecture, look at [overview].

The Joomla! plugin architecture follows the [[1]] design pattern. The JPlugin class is derived from JObserver and provides the means to register custom plugin code with core or custom events. The JEventDispatcher class, derived from JObservable, is an event handler which calls all plugins registered for a particular event, when that event is triggered.

 * How to create your own plugin
 * How to use plugins in your own code
 * Creating an Authentication Plugin

Useful reference: [2: Embedding: Event-Based Loose-Coupled Integration]

Prior to Joomla! 1.5 plugins were known as mambots. Mambots were able to change content only and were based on certain signal words. Since then their scope has been stretched and extended to such an extent that to enhance the meaning of the new functionality the developers decided to change the name from mambots to plugins. Joomla! 1.5 includes legacy support for Joomla! 1.0 mambots.

Events[edit]

Joomla! ships with a variety of core events, organised into groups. These are described in the following topics.

 * System events
 * User events
 * Editor events
 * Content events

This is an alphabetical list of the core events in Joomla! 1.5 together with the group name to which each belongs. Each event name links to more detailed information.

 *onAfterDeleteUser (user)
 *onAfterDisplay (content)
 *onAfterDisplayTitle (content)
 *onAfterDisplayContent (content)
 *onAfterInitialise (system)
 *onAfterRoute (system)
 *onAfterDispatch (system)
 *onAfterRender (system)
 *onAfterStoreUser (user)
 *onAuthenticate (authentication)
 *onAuthenticateFailure (authentication)
 *onBeforeDeleteUser (user)
 *onBeforeDisplay (content)
 *onBeforeDisplayContent (content)
 *onBeforeStoreUser (user)
 *onCustomEditorButton (editors-xtd)
 *onDisplay (editors)
 *onGetContent (editors)
 *onGetInsertMethod (editors)
 *onGetWebServices (xmlrpc)
 *onInit (editors)
 *onLoginUser (user)
 *onLogoutUser (user)
 *onPrepareContent (content)
 *onSave (editors)
 *onSearch (search)
 *onSearchAreas (search)
 *onSetContent (editors)