Development:New permissions evaluation in 2.0: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 28: | Line 28: | ||
=See also= | =See also= | ||
* [[Development:Enrolment rewrite and role tweaks proposal]] | * [[Development:Enrolment rewrite and role tweaks proposal]] | ||
* [[Development:New permission overriding UI]] | |||
[[Category:Roles]] | [[Category:Roles]] | ||
Revision as of 22:03, 23 February 2010
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
Template:Infobox Project Template:Moodle 2.0
Goals
The main goals are:
- replace current confusing permission evaluation
- improve performance
- enable improvements in permission overriding UI
Permission evaluation algorithm
- find all roles with given capability used in definition or override
- evaluate permissions in given context for each role separately (going from bottom to top in context tree, first found wins unless there is a CAP_PROHIBIT on any level)
- user has capability if he/she has at least one role which evaluated to CAP_ALLOW and at the same time no role which was evaluated to CAP_PROHIBIT
Performance improvements
has_capability() and get_users_by_capability() uses fixed number of queries. The result could be returned as sql query instead of database records.
Backwards compatibility
The only potential problem is CAP_PREVENT in overrides when user has several conflicting roles. Originally this was highlighted as a special feature, unfortunately it was in fact the major source of confusion.
