mod/exercise/db/access.php

   1 <?php
   2 //
   3 // Capability definitions for the exercise module.
   4 //
   5 // The capabilities are loaded into the database table when the module is
   6 // installed or updated. Whenever the capability definitions are updated,
   7 // the module version number should be bumped up.
   8 //
   9 // The system has four possible values for a capability:
  10 // CAP_ALLOW, CAP_PREVENT, CAP_PROHIBIT, and inherit (not set).
  11 //
  12 //
  13 // CAPABILITY NAMING CONVENTION
  14 //
  15 // It is important that capability names are unique. The naming convention
  16 // for capabilities that are specific to modules and blocks is as follows:
  17 //   [mod/block]/<component_name>:<capabilityname>
  18 //
  19 // component_name should be the same as the directory name of the mod or block.
  20 //
  21 // Core moodle capabilities are defined thus:
  22 //    moodle/<capabilityclass>:<capabilityname>
  23 //
  24 // Examples: mod/forum:viewpost
  25 //           block/recent_activity:view
  26 //           moodle/site:deleteuser
  27 //
  28 // The variable name for the capability definitions array follows the format
  29 //   $<componenttype>_<component_name>_capabilities
  30 //
  31 // For the core capabilities, the variable is $moodle_capabilities.
  32
  33
  34 $mod_exercise_capabilities = array(
  35
  36     'mod/exercise:assess' => array(
  37
  38         'captype' => 'write',
  39         'contextlevel' => CONTEXT_MODULE,
  40         'legacy' => array(
  41             'teacher' => CAP_ALLOW,
  42             'editingteacher' => CAP_ALLOW,
  43             'admin' => CAP_ALLOW
  44         )
  45     )
  46
  47 );
  48
  49 ?>