Issue Details (XML | Word | Printable)

Key: MDL-15768
Type: Sub-task Sub-task
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Penny Leach
Reporter: Penny Leach
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Moodle
MDL-14591

review roles usage in portfolio

Created: 22/Jul/08 09:14 PM   Updated: 03/Sep/08 12:28 AM
Return to search
Component/s: Portfolio API
Affects Version/s: 2.0
Fix Version/s: 2.0

Participants: Penny Leach
Security Level: None
Resolved date: 03/Sep/08
Affected Branches: MOODLE_20_STABLE
Fixed Branches: MOODLE_20_STABLE


 Description  « Hide
might be just as simple as require_cap in portfolio/add.php

 All   Comments   Change History   Version Control      Sort Order: Ascending order - Click to sort in descending order
Penny Leach added a comment - 23/Jul/08 05:56 PM
after discussion with MD the plan is to:
  • the calling code can check has_capability before calling portfolio_add_button
  • add a new method in the caller class to check permissions
  • name the capabilities consistently, eg mod/forum:export-post, mod/forum:export-attachment
  • figure out a way to disable (or enable) plugin instances per role.

Penny Leach added a comment - 23/Jul/08 05:57 PM
MD said:
10:53 <moodler_> hmm plugins, we did something similar for grade import/expot
(relating to fourth point above)

Penny Leach added a comment - 03/Sep/08 12:28 AM
closing this issue as resolved.

the outstanding thing about trying to figure out a way to enable or disable instances per role is trickier and not necessarily needed right now so i will open a separate bug for it.