📄 access.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]/<component_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 follows the format// $<componenttype>_<component_name>_capabilities//// For the core capabilities, the variable is $moodle_capabilities.$block_rss_client_capabilities = array( 'block/rss_client:createprivatefeeds' => array( 'captype' => 'write', 'contextlevel' => CONTEXT_BLOCK, 'legacy' => array( 'teacher' => CAP_ALLOW, 'editingteacher' => CAP_ALLOW, 'admin' => CAP_ALLOW ) ), 'block/rss_client:createsharedfeeds' => array( 'riskbitmask' => RISK_SPAM, 'captype' => 'write', 'contextlevel' => CONTEXT_BLOCK, 'legacy' => array( 'editingteacher' => CAP_ALLOW, 'admin' => CAP_ALLOW ) ), 'block/rss_client:manageownfeeds' => array( 'captype' => 'write', 'contextlevel' => CONTEXT_BLOCK, 'legacy' => array( 'teacher' => CAP_ALLOW, 'editingteacher' => CAP_ALLOW, 'admin' => CAP_ALLOW ) ), 'block/rss_client:manageanyfeeds' => array( 'riskbitmask' => RISK_SPAM, 'captype' => 'write', 'contextlevel' => CONTEXT_BLOCK, 'legacy' => array( 'admin' => CAP_ALLOW ) ));?>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -