Development:Enrolment usage overview: Difference between revisions
| Line 36: | Line 36: | ||
=Modules= | =Modules= | ||
== | ==Assignment== | ||
==Chat== | |||
==Choice== | |||
==Feedback== | |||
==Forum== | |||
==Glossary== | |||
==Lesson== | |||
==Quiz== | |||
==SCORM== | |||
==Survey== | |||
==Wiki== | |||
==Workshop== | |||
=See also= | =See also= | ||
Revision as of 19:35, 29 March 2010
Template:Infobox Project Template:Moodle 2.0
Goals
There is a lot of confusion related to guest access, enrolment of users, etc. This page is trying to sum up the usage of enrolments and guest access in various parts of Moodle.
Definitions
Core APIs
get_enrolled_users() get_enrolled_sql() isguest() isguestuser() is_siteadmin() has_capability() get_users_by_capability()
Core usage
Group membership
Only enrolled users may be members of groups. In 1.9 and earlier we only guess by looking at roles that have moodle/course:view which is not hidden, this may actually return incorrect results if overrides used. All group membership is removed when unenrolling form course.
Technically we need to look only at users that are returned by get_enrolled_users() when looking for new group membership candidates. Existing group membership should be filtered so that only enrolled users are displayed.
Logs and reports
In some cases we want to see only enrolled users, in others we want to see really all users. This should be decided by a new capability.
