|
|
|
File Attachments:
|
1.
core-inserts.pdf (160 kB)
|
|
Issue Links:
|
Dependency
|
|
|
|
This issue will be resolved by:
|
|
MDL-16096
missing library in accesslib function "role_unassign"
|
|
|
|
|
Relates
|
|
This issue has a non-specific relationship to:
|
|
MDL-13998
Missing events_trigger in moodle 1.9 release
|
|
|
|
|
|
This issue has been marked as being related by:
|
|
|
MDL-16203 Fire events when a module is added to or deleted from a course, or updated
|
|
|
|
|
|
|
|
Sub-Tasks:
|
All
|
Open
|
|
| Sub-Task Progress: |
|
|
|
No sub-tasks match this view.
|
|
|
|
For keeping an external database of a third-party (learning environment)-software consistent to Moodle's database via an acitivity-module - this module hast to be informed about certain events out of the core. The events and the information we would like to see are:
1.1 update of a user's profile (either by an admin of the user himself)
information we need: user's name and surname, loginname, encrypted password, id of user-table and the idnumber
but we suggest to keep all information that have changed or the whole form (perhaps other later modules could use this information, too)
1.2 deleting a user's profile
information: user-id of the user-table
2.1 update of a course
information needed: id, category-id, fullname, summary
but again we suggest to keep everything changed or the whole form
2.2 deleting a course
information needed: the deleted course (at least it's id)
3.1 update of a category
information needed: id, name
3.2 deleting a category
information needed: id of the deleted category and the upper category the courses are switched to (at leased it's id)
4.1 creating an new group in a course
information needed: id, name, description, course-id, grouping-id (and -name or NULL if no grouping)
again our suggestion to keep the whole form (if later modules need to have more information than our's)
4.2 updae of a group
information needed is the same as above (better: the whole form)
4.3 add a user to a group
information needed: user (at least it's id) and group (at least it's id)
4.4 remove a user from a a group
information needed is the same as abov
4.5 deleting a group
information needed: group-id
|
|
Description
|
For keeping an external database of a third-party (learning environment)-software consistent to Moodle's database via an acitivity-module - this module hast to be informed about certain events out of the core. The events and the information we would like to see are:
1.1 update of a user's profile (either by an admin of the user himself)
information we need: user's name and surname, loginname, encrypted password, id of user-table and the idnumber
but we suggest to keep all information that have changed or the whole form (perhaps other later modules could use this information, too)
1.2 deleting a user's profile
information: user-id of the user-table
2.1 update of a course
information needed: id, category-id, fullname, summary
but again we suggest to keep everything changed or the whole form
2.2 deleting a course
information needed: the deleted course (at least it's id)
3.1 update of a category
information needed: id, name
3.2 deleting a category
information needed: id of the deleted category and the upper category the courses are switched to (at leased it's id)
4.1 creating an new group in a course
information needed: id, name, description, course-id, grouping-id (and -name or NULL if no grouping)
again our suggestion to keep the whole form (if later modules need to have more information than our's)
4.2 updae of a group
information needed is the same as above (better: the whole form)
4.3 add a user to a group
information needed: user (at least it's id) and group (at least it's id)
4.4 remove a user from a a group
information needed is the same as abov
4.5 deleting a group
information needed: group-id |
Show » |
toyomoyo committed 9 files to 'Moodle CVS' - 09/Jul/07 02:43 PM
MDL-9983, adding triggers for certain events, no handler implemented
|
|
|
toyomoyo committed 4 files to 'Moodle CVS' - 10/Jul/07 10:33 AM
fix for MDL-9983, trigger certain events out of the core to modules
|
|
|
toyomoyo committed 1 file to 'Moodle CVS' - 11/Jul/07 05:05 PM
committed 16 files to 'Moodle CVS' on branch 'MOODLE_19_STABLE' - 07/Jul/08 01:55 AM
MDL-9983, MDL-13998, MDL-15552 core events related cleanup and potential sql injection problem fixed; please note the changes are not backwards compatible, 3rd party code will need to be updated - sorry for the trouble
|
|
|
committed 15 files to 'Moodle CVS' - 07/Jul/08 01:57 AM
committed 2 files to 'Moodle CVS' on branch 'MOODLE_19_STABLE' - 07/Jul/08 03:26 AM
MDL-9983 role assignment related triggers
|
|
|
committed 2 files to 'Moodle CVS' - 07/Jul/08 03:30 AM
MDL-9983 role assignment related triggers; merged from MOODLE_19_STABLE
|
|
|
committed 4 files to 'Moodle CVS' on branch 'MOODLE_19_STABLE' - 07/Jul/08 06:54 AM
MDL-9983 role_unassign should not touch group members table directly - we need events
|
|
|
committed 4 files to 'Moodle CVS' - 07/Jul/08 06:54 AM
MDL-9983 role_unassign should not touch group members table directly - we need events; merged from MOODLE_19_STABLE
|
|
|
|