'. t('The Taxonomy Access Control module allows users to specify how each category can be used by various roles.') .'
'; - $message .= ''. t('Permissions can be set differently to each USER ROLES. Be aware that setting Taxonony Access permissions works ONLY WITHIN ONE USER ROLE.
(For users with multiple user roles, see section "GOOD TO KNOW" below.)') .'
'. t('On the category permissions page for each role, each category displays a list of the terms within it, each with five types of permission: View, Update, Delete, Create and List:') .'
'; - $message .= ''. t('VIEW, UPDATE, and DELETE control the node access system. LIST and CREATE control if a user can view and select a given term. (Note: In previous versions of Taxonomy Access Control, there was no LIST permission; its functionality was controlled by the VIEW permission.)') .'
'; - $message .= ''. t('VIEW, UPDATE and DELETE have three options for each term: Allow, Ignore, and Deny. Indicate which rights each role should have for each term.') .'
'; - $message .= ''. t('CREATE and LIST have only two options for each term: YES (selected) or NO (deselected). Indicate what each role should be allowed to do with each term.') .'
'; - $message .= ''. t('IMPORTANT NOTE:
The DENY directives are processed after the ALLOW directives. (DENY overrides ALLOW.) So, if a multicategory node is in Categories "A" and "B" and a user has ALLOW permissions for VIEW in Category "A" and DENY permissions for VIEW in Category "B", then the user will NOT be permitted to VIEW the node. (DENY overrides ALLOW.)
Access is denied by default. So, if a multicategory node is in Categories "C" and "D" and a user has IGNORE permissions for VIEW in both Category "C" and "D", then the user will NOT be permitted to VIEW the node.
(If you are familiar with Apache mod_access, this permission system works similar to directive: ORDER ALLOW, DENY)') .'
'. t('Allow/Ignore/Deny All or Select/Deselect All:
Beside each vocabulary title there are dropdowns containing the options that can be set for individual terms. Selecting one of these options using the dropdown effectively selects that option for ALL of the individual terms inside that vocabulary when the options are saved.
Selecting "--" does not make any automatic changes to the permission of the terms in that vocabulary; only manual changes that you make will be saved.
NOTE: This does not change the "Default" option (described below).') .'
'. t('Default:
This option, just underneath the vocabulary title, sets the permission that will automatically be given to the role, for any new terms that are added within the vocabulary. This includes terms that are added via free tagging.') .'
'. t('GOOD TO KNOW:') .'
'; - $message .= ''. t('Users with multiple user roles: Allow/Ignore/Deny options are interpreted only within one user role. When a user belongs to multiple user roles, then user gets access if ANY of his user roles has the access granted.
In this case, permissions for the given user are calculated, so that the permissions of ALL of his user roles are "OR-ed" together. Meaning that Allow will take precedence over Deny. This is different from how node access permissions (for multi-category nodes) are handled within ONE USER ROLE, as noted above.') .'
'. t('
Input formats: Node editing/deleting is blocked, even when user has UPDATE/DELETE permission to the node, when user is not allowed to use a filter format that the node was saved at.') .'
'; + $message = ''; + $message .= '' + . '
'. t('The Taxonomy Access Control module allows users to specify how each category can be used by various roles.') .'
' + . ''. t('Permissions can be set differently for each user role. Be aware that setting Taxonomy Access permissions works only within one user role.') . '
' + . '' . t('(For users with multiple user roles, see section Good to know below.)') .'
'. t('On the category permissions page for each role, administrators can configure five types of permission for each term: View, Update, Delete, Create and List:') .'
' + . _taxonomy_access_grant_help_table() + . ''. t('View, Update, and Delete control the node access system. List and Create control the terms themselves. (Note: In previous versions of Taxonomy Access Control, there was no List permission its functionality was controlled by the View permission.)') .'
'. t('View, Update, and Delete have three options for each term: Allow (A), Ignore (I), and Deny (D). Indicate which rights each role should have for each term. If a node is tagged with multiple terms:') .'
' + . "'. t('Create and List have only two options for each term: Yes (selected) or No (deselected). Indicate what each role should be allowed to do with each term.') .'
' + . "" . t('The Deny directives are processed after the Allow directives. (Deny overrides Allow.) So, if a multicategory node is in Categories "A" and "B" and a user has Allow permissions for View in Category "A" and Deny permissions for View in Category "B", then the user will NOT be permitted to View the node.') . '
' + . '' . t('Access is denied by default. So, if a multicategory node is in Categories "C" and "D" and a user has Ignore permissions for View in both Category "C" and "D", then the user will not be permitted to view the node.') . '
' + . '' . t('(If you are familiar with Apache mod_access, this permission system works similar to directive: ORDER ALLOW, DENY)') .'
' + . "'. t('This option, just underneath the vocabulary title, sets the permission that will automatically be given to the role, for any new terms that are added within the vocabulary. This includes terms that are added via free tagging.') .'
'. t('Users with multiple user roles: Allow/Ignore/Deny options are interpreted only within one user role. When a user belongs to multiple user roles, then the user gets access if any of his/her user roles have the access granted.') . '
' + . '' . t('In this case, permissions for the given user are calculated so that the permissions of ALL of his user roles are "OR-ed" together, which means that Allow in one role will take precedence over Deny in the other. This is different from how node access permissions (for multi-category nodes) are handled within one user role, as noted above.') .'
' + . ''. t('Input formats: Node editing/deleting is blocked, even when the user has Update or Delete permission to the node, when the user is not allowed to use a filter format that the node was saved at.') .'
' + . 'Vocabulary Settings: Each vocabulary displays a list of the terms within it, each with five types of permission: View, Update, Delete, Create and List.
For a detailed description of these permissions and how to use them, see Taxonomy Access Control help. If you are new to Taxonomy Access Control, it is very important that you read the help page.
', array('@taxonomy_access_help' => url('admin/help/taxonomy_access'))); - return $output; - } - else { - return ''.t('In this area you will define the permissions that each user role has for each category. Each category can have View, Update, Delete, Create and List permissions set for each user role.', array('@role' => url('admin/user/roles'))).'
'; - } - }*/ + break; } } diff -urp taxonomy_access/taxonomy_access_admin.inc taxonomy_access_new/taxonomy_access_admin.inc --- taxonomy_access/taxonomy_access_admin.inc 2010-03-01 19:59:32.000000000 -0600 +++ taxonomy_access_new/taxonomy_access_admin.inc 2010-03-03 11:35:39.000000000 -0600 @@ -130,6 +130,10 @@ function taxonomy_access_admin_form($for $grants[$row['tid']] = $row; } + $form['instructions'] = array( + '#value' => _taxonomy_access_admin_instructions_html(), + '#weight' => '20', + ); $form['rid'] = array('#type' => 'value', '#value' => $rid); $form['grants'] = $form['selected_terms'] = $form['selected_defaults'] = array('#tree' => TRUE); @@ -217,9 +221,9 @@ function theme_taxonomy_access_admin_for array( 'data' => t('List')), ); $sub_header = array( - ' '. t('A') .'', - ' '. t('I') .'', - ' '. t('D') .'', + ' '. t('A') .'', + ' '. t('I') .'', + ' '. t('D') .'', ' ', ); $sub_header = array_merge(array(' '), $sub_header, $sub_header, $sub_header); @@ -286,6 +290,8 @@ function theme_taxonomy_access_admin_for $row = array(); } + + $output = ''; $output .= theme('table', $header, $rows); $output .= drupal_render($form); @@ -474,3 +480,107 @@ function taxonomy_access_defaults_update // issue #167977 - klance _taxonomy_access_node_access_update($affected_nodes); } + +function _taxonomy_access_admin_instructions_html() { + $instructions = ''; + $instructions .= '' + . "" + . t('Options for View, Update, and Delete are Allow (A), Ignore (I), and Deny (D).') + . "
\n\n" + . "" + . t('Remember: This role will inherit permissions from the authenticated user role. Be sure to configure +the authenticated user properly.', + array("@url" => url("admin/user/taxonomy_access/edit/2")) + ) + . "
\n\n" + ; + } + $instructions .= '' + . ""
+ . t('For more information and for troubleshooting guidelines, see the help page and the !readme.',
+ array(
+ '@help' => url('admin/help/taxonomy_access'),
+ '!readme' => "README.txt"
+ ))
+ . "
" + . t('Grants this role the ability to view nodes with the term. (Users must also have this permission to see nodes with the term listed in Views.)') + . "
" + . "" + . t('The role must have access content permission on the permissions administration form.', + array( + '@path' => url('admin/user/permissions#module-node'), + )), + ); + + $rows[] = array( + array('header' => true, 'data' => t("Update") . ", " . t("Delete")), + "
" + . t("Grants this role the ability to edit or delete nodes with the term, respectively.") + . "
" + . "" + . t('The role must not have edit any [type] content or delete any [type] content permission on the permissions administration form if you wish to control them here.', + array( + '@path' => url('admin/user/permissions#module-node'), + )) + ."
", + ); + + $rows[] = array( + array('header' => true, 'data' => t("Create")), + "" + . t("Grants this role the ability to add the term to a node when creating or updating it.") + . "
" + . "" + . t('This does not give the role the ability to create nodes by itself; the role must have create [type] content permission on the permissions administration form in order to create new nodes.', + array( + '@path' => url('admin/user/permissions#module-node'), + )) + ."
", + ); + + $rows[] = array( + array('header' => true, 'data' => t("List")), + "" + . t("Whether this role can see the term listed on node pages and in lists, and whether the user can view the %taxonomy-term-page page for the term.", + array( + '%taxonomy-term-page' => "taxonomy/term/x" + )) + . "
" + . "" . t("This does not control whether the role can see the nodes listed in Views, only the term.") . "
", + ); + + return theme('table', $header, $rows, array('class' => 'grant_help')); +} \ No newline at end of file