plugins:system_eventsTable of Contents
5.2 System Events for Plugin System5.2.1 OverviewIn a standard installation of Joomla! 1.5 we have several predefined events which, when triggered, call functions in the associated plugins. For more information on plugins, look here. This topic is aimed at “global” system events, including those triggered on every page load (onAfterInitialise, onAfterRoute, onAfterDispatch, onAfterRender), those supporting search within multiple plugins (onSearch, onSearchArea) and those supporting the presentation of web services (onGetWebServices). 5.2.2 onAfterInitialise5.2.2.1 DescriptionThis event is triggered after the framework has loaded and the applicaiton initialise function has been called. 5.2.2.2 ParametersNone. 5.2.2.3 Return ValueNone. 5.2.2.4 Called in files
5.2.3 onAfterRoute5.2.3.1 DescriptionThis event is triggered after the framework has loaded and initialised and the router has route the client request. Routing is the process of examining the request environment to determine which component should receive the request. This component optional parameters are then set in the request object to be processed when the application is being dispatched. When this event triggers the router has parsed the route and pushed the request parameters into JRequest for retrieval by the application. 5.2.3.2 ParametersNone. 5.2.3.3 Return ValueNone. 5.2.3.4 Used in files
5.2.3 onAfterDispatch5.2.3.1 DescriptionThis event is triggered after the framework has dispatched the application. Dispatching is the process of pulling the option from the request object and mapping them to a component. If the component do not exist, it handles determining a default component to dispatch. When this event is triggered the output of the component is available in the document buffer. 5.2.3.2 ParametersNone. 5.2.3.3 Return ValueNone. 5.2.3.4 Used in files
5.2.3 onAfterRender5.2.3.1 DescriptionThis event is triggered after the framework has rendered the application. Rendering is the process of pushing the document buffers into the template placeholders, retrieving data from the document and pushing it into the into the JResponse buffer. When this event is triggered the output of the application is available in the response buffer. 5.2.3.2 ParametersNone. 5.2.3.3 Return ValueNone. 5.2.3.4 Used in files
5.2.4 onSearch5.2.4.1 DescriptionThis event is triggered by a variety of search related operations. It is a request for a plugin to return the result of a search request. The rows must return the following fields, which are used in a common display routine:
5.2.4.2 Parameters
5.2.4.3 Return ValueArray of stdClass objects with members as described above. 5.2.3.4 Used in files
5.2.5 onSearchAreas5.2.5.1 DescriptionThis appears to be a request for plugins to identify which “areas” they provide search facilities for. 5.2.5.2 ParametersNone. 5.2.5.3 Return ValueAn associative array of area names, indexed by the area identifier. For example, array( ‘categories’ ⇒ ‘Categories’ ). 5.2.5.4 Used in files
5.2.6 onGetWebServices5.2.6.1 DescriptionThis is an introspection request for plugins that provide web services. 5.2.6.2 ParametersNone. 5.2.6.3 Return ValueAn array of associative arrays. The outer array is indexed by the service method name and contains an array with the following elements:
5.2.6.4 Used in files
|


