Events API - Historial de revisió

Davosmith: /* Events wishlist */

2011-02-10T14:46:33Z

Events wishlist

← Versió més antiga		Revisió del 14:46, 10 feb 2011
Línia 291:		Línia 291:
	* assignment_submitted		* assignment_submitted
	* course completed		* course completed
			* course module completion state changed (completed / not completed)

	Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.		Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.

2010-11-05T12:13:58Z

Events wishlist

← Versió més antiga		Revisió del 12:13, 5 nov 2010
Línia 290:		Línia 290:
	* grade_update		* grade_update
	* assignment_submitted		* assignment_submitted
			* course completed

	Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.		Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.

2010-09-09T14:01:47Z

Added 'assignment_submitted' to events wishlist

← Versió més antiga		Revisió del 14:01, 9 set 2010
Línia 289:		Línia 289:
	* module_removed		* module_removed
	* grade_update		* grade_update
			* assignment_submitted

	Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.		Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.

2010-08-31T17:06:15Z

Events wishlist

← Versió més antiga		Revisió del 17:06, 31 ago 2010
Línia 288:		Línia 288:
	* module_installed		* module_installed
	* module_removed		* module_removed
			* grade_update

	Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.		Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.

2010-08-26T20:21:51Z

Events wishlist

← Versió més antiga		Revisió del 20:21, 26 ago 2010
Línia 288:		Línia 288:
	* module_installed		* module_installed
	* module_removed		* module_removed

			Provide event trigger hooks for the modules, similar to what is done for the cron service which checks the LOCAL directory for a cron file. It is already possible to define an event trigger but the core/module code must be modified to actually make use of it.

	== See also ==		== See also ==

2010-08-19T22:15:50Z

Users

← Versió més antiga		Revisió del 22:15, 19 ago 2010
Línia 187:		Línia 187:
	* user_created		* user_created
	** full new record from 'user' table		** full new record from 'user' table
			* user_deleted
			** record from 'user' table before marked as deleted
	* user_updated		* user_updated
	** full new record from 'user' table		** full new record from 'user' table

2010-05-19T11:36:02Z

Events wishlist

← Versió més antiga		Revisió del 11:36, 19 maig 2010
Línia 283:		Línia 283:
	List of events which it would be nice to have. Please add to this list if what you want is not shown here.		List of events which it would be nice to have. Please add to this list if what you want is not shown here.

	* user_role_assign
	* user_role_unassign
	* mform_print_form -- this for all types of form e.g. admin settings, user profile, module updating, + some sort of standard way of discriminiating between them e.g. if ($form->name == 'user_profile') {}. This would be better triggered at the end of the form generation process so that new bits can be inserted at any point, or existing bits could be removed.		* mform_print_form -- this for all types of form e.g. admin settings, user profile, module updating, + some sort of standard way of discriminiating between them e.g. if ($form->name == 'user_profile') {}. This would be better triggered at the end of the form generation process so that new bits can be inserted at any point, or existing bits could be removed.
	* module_installed		* module_installed

2010-05-19T11:35:30Z

Events which exist

← Versió més antiga		Revisió del 11:35, 19 maig 2010
Línia 189:		Línia 189:
	* user_updated		* user_updated
	** full new record from 'user' table		** full new record from 'user' table

			===Roles===
			* role_assigned (full new record from 'role_assignments' table)
			* role_unassigned (record from 'role_assignments', course context only)

	===Courses===		===Courses===

2010-05-04T11:42:04Z

Handling an event

← Versió més antiga		Revisió del 11:42, 4 maig 2010
Línia 56:		Línia 56:
	The handler function accepts one parameter (the event data object) and should return a boolean. Returning false indicates that there was an error and the event will be left in the event queue.		The handler function accepts one parameter (the event data object) and should return a boolean. Returning false indicates that there was an error and the event will be left in the event queue.

	~~{code}~~		function message_send_handler($eventdata) {
	function message_send_handler($eventdata) {		// handle event
	// handle event		// ...
	return true;		return true;
	}		}
	~~{code~~}

	==Database structure==		==Database structure==

2010-05-04T11:40:11Z

Handling an event

← Versió més antiga		Revisió del 11:40, 4 maig 2010
Línia 54:		Línia 54:
	Any code can hook into any events this way.		Any code can hook into any events this way.

			The handler function accepts one parameter (the event data object) and should return a boolean. Returning false indicates that there was an error and the event will be left in the event queue.

			{code}
			function message_send_handler($eventdata) {
			// handle event
			return true;
			}
			{code}

	==Database structure==		==Database structure==