Plugin: Difference between revisions
From Joomla! Documentation
m Split off events to Plugin events |
m Merged into Template:Plugin |
||
| Line 1: | Line 1: | ||
<onlyinclude>{{Plugin}}</onlyinclude> | <onlyinclude>{{Plugin}}</onlyinclude> | ||
Useful reference: [http://codex.gallery2.org/index.php/Gallery2:Embedding:Event-Based_Loose-Coupled_Integration Gallery 2: Embedding: Event-Based Loose-Coupled Integration] | Useful reference: [http://codex.gallery2.org/index.php/Gallery2:Embedding:Event-Based_Loose-Coupled_Integration Gallery 2: Embedding: Event-Based Loose-Coupled Integration] | ||
| Line 13: | Line 7: | ||
===Developers=== | ===Developers=== | ||
{{RecReading|Plugin|dev|audience}} | {{RecReading|Plugin|dev|audience}} | ||
==Events== | ==Events== | ||
{{:Plugin 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 20:13, 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>
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>