mirror of
https://github.com/moodle/moodle.git
synced 2025-01-19 14:27:22 +01:00
58 lines
1.5 KiB
PHP
58 lines
1.5 KiB
PHP
<?php
|
|
//
|
|
// Capability definitions for the rss_client block.
|
|
//
|
|
// The capabilities are loaded into the database table when the block is
|
|
// installed or updated. Whenever the capability definitions are updated,
|
|
// the module version number should be bumped up.
|
|
//
|
|
// The system has four possible values for a capability:
|
|
// CAP_ALLOW, CAP_PREVENT, CAP_PROHIBIT, and inherit (not set).
|
|
//
|
|
//
|
|
// CAPABILITY NAMING CONVENTION
|
|
//
|
|
// It is important that capability names are unique. The naming convention
|
|
// for capabilities that are specific to modules and blocks is as follows:
|
|
// [mod/block]/<plugin_name>:<capabilityname>
|
|
//
|
|
// component_name should be the same as the directory name of the mod or block.
|
|
//
|
|
// Core moodle capabilities are defined thus:
|
|
// moodle/<capabilityclass>:<capabilityname>
|
|
//
|
|
// Examples: mod/forum:viewpost
|
|
// block/recent_activity:view
|
|
// moodle/site:deleteuser
|
|
//
|
|
// The variable name for the capability definitions array is $capabilities
|
|
|
|
|
|
$capabilities = array(
|
|
|
|
'block/rss_client:manageownfeeds' => array(
|
|
|
|
'captype' => 'write',
|
|
'contextlevel' => CONTEXT_BLOCK,
|
|
'legacy' => array(
|
|
'teacher' => CAP_ALLOW,
|
|
'editingteacher' => CAP_ALLOW,
|
|
'manager' => CAP_ALLOW
|
|
)
|
|
),
|
|
|
|
'block/rss_client:manageanyfeeds' => array(
|
|
|
|
'riskbitmask' => RISK_SPAM,
|
|
|
|
'captype' => 'write',
|
|
'contextlevel' => CONTEXT_BLOCK,
|
|
'legacy' => array(
|
|
'manager' => CAP_ALLOW
|
|
)
|
|
)
|
|
|
|
);
|
|
|
|
|