Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-17216

Capabilities for the database module are not atomic and ambigous, blocking designing desired module instances

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • None
    • 1.8.7, 1.9.3
    • MOODLE_18_STABLE, MOODLE_19_STABLE

      mod/data:writeentries capability

      It seems that this permission controls only creation (writing new records), although the name could imply also editing (writing to existing records).

      mod/data:manageentries capability

      It is not clear what actual capabilites are included here. I am guessing Edit and Delete. Manage is vague as a word, and the docs say nothing more concrete. There is a whole range of "manage" permissions.

      For example, with those capabilities, it is not possible to produce a database where records may be added and deleted only by teachers or administrators but can be edited by all students since manageentries is a combination of permissions.

      It be useful to rename the ambigous permissions and have more atomic capabilities. For example, instead of writeentries and manageentries:

      mod/data:createentries
      mod/data:editownentries
      mod/data:editanyentry
      mod/data:deleteownentries
      mod/data:deleteanyentry

            moodle.com Moodle HQ
            robek Robert Brenstein
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.