Drupal
/
drupal
mirror of https://git.drupalcode.org/project/drupal.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

- Patch #1037352 by David_Rothstein: clarified usage of 'warning' parameter.

8.0.x
Dries Buytaert 2011-03-27 09:48:44 -04:00
parent 2edad6ef14
commit c997684dc3
1 changed files with 13 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
modules/system/system.api.php
View File

@ -1908,12 +1908,19 @@ function hook_system_info_alter(&$info, $file, $type) {
* have inherent security risks across a variety of potential use cases
* (for example, the "administer filters" and "bypass node access"
* permissions provided by Drupal core). When set to TRUE, a standard
* warning message defined in user_admin_permissions() will be associated
* with the permission and displayed with it on the permission
* administration page. Defaults to FALSE.
* - warning: (optional) A translated warning message to display on the
* permission administration page. This warning overrides the automatic
* warning generated by 'restrict access' being set to TRUE.
* warning message defined in user_admin_permissions() and output via
* theme_user_permission_description() will be associated with the
* permission and displayed with it on the permission administration page.
* Defaults to FALSE.
* - warning: (optional) A translated warning message to display for this
* permission on the permission administration page. This warning overrides
* the automatic warning generated by 'restrict access' being set to TRUE.
* This should rarely be used, since it is important for all permissions to
* have a clear, consistent security warning that is the same across the
* site. Use the 'description' key instead to provide any information that
* is specific to the permission you are defining.
*
* @see theme_user_permission_description()
*/
function hook_permission() {
return array(