Plugin: Difference between revisions
From Joomla! Documentation
m Referenced "Recommended Reading" reference |
m Split off events to Plugin events |
||
| Line 15: | Line 15: | ||
==Events== | ==Events== | ||
{{:Plugin events}} | |||
<noinclude>[[Category:Landing Pages]][[Category:Glossary]][[Category:Development]][[Category:Plugins]]</noinclude> | <noinclude>[[Category:Landing Pages]][[Category:Glossary]][[Category:Development]][[Category:Plugins]]</noinclude> | ||
Revision as of 13:41, 14 July 2011
<translate> A plugin is a kind of Joomla! extension. Plugins provide functions which are associated with trigger events. Joomla provides a set of core plugin events, but any extension can fire (custom) events. When a particular event occurs, all plugin functions of the type associated with the event are executed in sequence. This is a powerful way of extending the functionality of Joomla. It also offers extension developers a way to allow other extensions to respond to their actions, making extensions extensible.</translate>
<translate> The Joomla! plugin architecture follows the Observer design pattern. The JPlugin class provides the means to register custom plugin code with core or custom events. The JEventDispatcher class is an event handler which calls all plugins registered for a particular event, when that event is triggered. In Joomla 4.x this has been moved to the \Joomla\Event\Dispatcher class in Joomla, and additionally follows the Mediator design pattern</translate>
<translate> See also: Component, Module, Template</translate>
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 Framework overview.
The Joomla! plugin architecture follows the Observer 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.
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.
Useful reference: Gallery 2: Embedding: Event-Based Loose-Coupled Integration
Recommended Reading
Developers
{{Portal:Plugin_Development/Intro/<translate> en</translate>}}
<translate> Using Plugins</translate>
{{Portal:Plugin_Development/Using_Plugins/<translate> en</translate>}}
<translate> Reading list</translate>
{{Portal:Plugin_Development/Reading list/<translate> en</translate>}}
<translate> Tutorials</translate>
{{Portal:Plugin_Development/Tutorials/<translate> en</translate>}}
<translate> Plugin Development Articles Needed</translate>
{{Portal:Plugin_Development/Projects/<translate> en</translate>}}
For more developer information, see Plugin Development.
Events
<translate> Joomla! ships with a variety of core events, organised into groups. These are described in the following topics.</translate>
<translate>
Api Authentication
</translate>
<translate>
Authentication
</translate>
<translate>
Behaviour
</translate>
- onTableObjectCreate
- onTableBeforeReset
- onTableAfterReset
- onTableBeforeBind
- onTableAfterBind
- onTableBeforeLoad
- onTableAfterLoad
- onTableCheck
- onTableBeforeBind
- onTableAfterBind
- onTableBeforeStore
- onTableAfterStore
- onTableBeforeDelete
- onTableAfterDelete
- onTableBeforeCheckout
- onTableAfterCheckout
- onTableBeforeCheckin
- onTableAfterCheckin
- onTableBeforeHit
- onTableAfterHit
- onTableBeforeReorder
- onTableAfterReorder
- onTableBeforeMove
- onTableAfterMove
- onTableBeforePublish
- onTableAfterPublish
- onTableSetNewTags
<translate>
Captcha
</translate>
<translate>
Content
</translate>
- onContentPrepare
- onContentAfterTitle (
<translate> and higher</translate>) - onContentBeforeDisplay
- onContentAfterDisplay
- onContentBeforeSave
- onContentAfterSave
- onContentPrepareForm
- onContentPrepareData
- onContentBeforeDelete
- onContentAfterDelete
- onContentChangeState
- onContentSearch
- onContentSearchAreas
- onUserBeforeDataValidation (N.B. Whilst this event starts with user it's misleading - it applies to all actions and is renamed to a better name of onContentValidateData in
)
<translate>
Editors
</translate>
<translate>
Editors-xtd
</translate>
<translate>
Extensions
</translate>
- onExtensionAfterInstall
- onExtensionAfterUninstall
- onExtensionAfterUpdate
- onExtensionBeforeSave
- onExtensionAfterSave
- onExtensionAfterDelete
<translate>
Fields
</translate>
<translate>
Filesystem
</translate>
<translate>
Finder
</translate>
- onFinderCategoryChangeState
- onFinderChangeState
- onFinderAfterDelete
- onFinderAfterDelete
- onFinderBeforeSave
- onFinderAfterSave
- onFinderResult

- onPrepareFinderContent
<translate>
Installer
</translate>
<translate>
Media Action
</translate>
<translate>
Privacy
</translate>
<translate>
Quick Icons
</translate>
<translate>
Sampledata
</translate>
- onSampledataGetOverview
- onAjaxSampledataApplyStep1
- onAjaxSampledataApplyStep2
- onAjaxSampledataApplyStep3
<translate>
Schemaorg
</translate>
<translate>
System
</translate>
- onAfterInitialise
- onAfterRoute
- onAfterDispatch
- onAfterRender
- onBeforeRender
- onBeforeCompileHead
- onAfterSessionStart
<translate>
User
</translate>
- onUserAuthorisation
- onUserAuthorisationFailure
- onUserBeforeSave
- onUserAfterSave
- onUserBeforeDelete
- onUserAfterDelete
- onUserLogin
- onUserLoginFailure
- onUserAfterLogin
- onUserLogout
- onUserBeforeSaveGroup
- onUserAfterSaveGroup
- onUserBeforeDeleteGroup
- onUserAfterDeleteGroup
- onUserAfterRemind
<translate>
Web Services
</translate>
<translate>
Workflow
</translate>
<translate> === Other Core Component Events === </translate>
<translate>
Actionlog Component
</translate>
<translate>
Cache Component
</translate>
<translate>
Checkin Component
</translate>
<translate>
Config Component
</translate>
<translate>
Contact Component
</translate>
<translate>
Installer Component
</translate>
<translate>
Menu Component
</translate>
<translate>
Module
</translate>