En construction, n'hésitez pas à modifier, compléter, relier, traduire !

Définition et utilisation

à compléter et traduire depuis http://docs.elgg.org/wiki/Elgg_Events

Il existe 2 types d'événements dans Elgg : les événements events et les hooks (littéralement : "crochets") des plugins. Les events sont activés ("trigger") lorsque quelque chose est créé, mis à jour ou supprimé, ou lorsque le framework d'Elgg est chargé.

TODO : Examples would include a blog post being created or a user logging in. Each event is determined by an event name and an object type (system, user, object, relationship name, annotation, group). By registering handlers for Elgg events, your plugin can have code executed when that event occurs.

Les événements disponibles dans le coeur (core) d'Elgg

à traduire, depuis http://docs.elgg.org/wiki/What_events_are_available_in_the_Elgg_core%3F

System events

• boot, system - first event triggered. Triggered before plugins have been loaded.
• plugins_boot, system - triggered just after the plugins are loaded. Rarely used. init, system is used instead.
• init, system - plugins tend to use this event for initialization (extending views, registering callbacks, etc.)
• pagesetup, system - called just before the first content is produced. Is triggered by elgg_view().
• shutdown, system - triggered after the page has been sent to the user. Expensive operations could be done here and not make the user wait.
• log, systemlog
• upgrade, upgrade

User events

• login, user - triggered during login. Returning false prevents the user from logging in.
• logout, user - triggered during logout. Returning false should prevent the user from logging out.
• validate, user - when a user registers, the user's account is disabled. This event is triggered to allow a plugin to determine how the user should be validated (for example, through an email with a validation link).
• profileupdate, user - user has changed profile
• profileiconupdate, user - user has changed profile icon
• ban, user - return true to ban user
• unban, user - return true to unban user

Relationship events

• create, - called after the relationship has been created. Returning false deletes the relationship that was just created.
• delete, - called before the relationship is deleted. Return false to prevent it from being deleted.
• join, group - user joined a group
• leave, group - user left a group

Entity events

• create, - called for user, group, object, and site entities after creation. Return true or entity is deleted.
• update, - called after group update and return false to delete group. Called after object update and return false to delete the object. Called after site update and return false to delete site. Called after user update and returning false deletes the user. Called before entity update and returning false prevents update.
• delete, - called before entity deletion and returning false prevents deletion.
• disable, - return false to prevent disable
• enable, - return false to prevent enable

Metadata events

• create, metadata - called after the metadata has been created. Return false to delete the metadata that was just created.
• update, metadata - called after the metadata has been updated. Return false to delete the metadata. (That doesn't sound like a good idea)
• delete, metadata - called before metadata is deleted. Return false to prevent deletion.

Annotation events

• annotate, - called before the annotation has been created. Return false to prevent annotation of this entity.
• create, annotation - called after the annotation has been created. Return false to delete the annotation.
• update, annotation - called after the annotation has been updated. Return false to delete the annotation. (That doesn't sound like a good idea)
• delete, annotation - called before annotation is deleted. Return false to prevent deletion.