Enhance permission system
| Project: | Quiz |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
- Add additional privileges, such as:
o “Access quizzes” (used if you want to limit quiz taking to registered users)
o “Administer quizzes” (used to make changes to a quiz after the fact)
o “Revise questions moderated” and “Revise questions unmoderated,” for submitting question revisions to a moderation queue, or directly to the question, respectively (note: I had an idea of how to avoid the ambiguity situation of someone having both of these options checked… Change the names to: “Suggest question revisions” (submit to a moderation queue) and “Administer questions” (used to review queue and make actual changes to the questions), and have a checkbox or similar that says “Overwrite current question” to differentiate between the two… Because an administrator could still use the interface to merely suggest question revisions, if for example they weren’t completely confident in some area and wanted them to be reviewed by other administrators).
#1
Some work was done on this front, but we might want to take another pass at it. webchick's comment from http://drupal.org/node/85983:
Are there any other issues with permissions that need to be addressed?
#2
Attached is a small patch that allows the "administer quizzes" permission to be assigned to different roles.
#3
I created a new issue (http://drupal.org/node/90686) for the missing "administer quizzes" permission that the above patch fixes. Re-opening this issue as it is a broader feature that needs to be addressed.
#4
Also see http://drupal.org/node/92182 as an issue with further thoughts to this one.
#5
The first two permissions have been implemented. The latter two permissions only make sense if there is some moderation queue. Even then, there are permissions in place for that with Drupal's revision system. Either edit to make a new revision or edit in place. See, http://drupal.org/node/26997
Marking this as fixed.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.