function book_access_help in Book access 6
Same name and namespace in other branches
- 5 book_access.module \book_access_help()
Implements hook_help().
File
- ./
book_access.module, line 78 - Allows access control for book nodes on a per book basis. It is based on forum_access.module and tac_lite.module.
Code
function book_access_help($path, $arg) {
switch ($path) {
case 'admin/help#book_access':
$help = '<p>' . t('Allow access control for book nodes on a per book basis.</p>
<p><a href="@permissions">Permissions enabled</a> will override the
module access settings. For example, if you would like a role to be able
to edit all book pages, enable <q>edit any book content</q> in
<a href="@permissions">Permissions</a>.
If you would like to control edit permission on a per book basis,
disable that permission in <a href="@permissions">Permissions</a> and
configure the module accordingly.', array(
'@permissions' => url('admin/user/permissions'),
)) . '</p>' . '<p>' . t('Certain access control modules can impact functionality of this
module. Broad reaching modules such as "taxonomy access" and "content
access" can override the values set in the <em>Book access</em> settings page.
You must turn off all enabled access controls in such modules.</p>
<p>If you are using additional access control modules, be
certain that none of them are allowing access to book nodes. The simplest
way to do this is to limit the types of pages that a book may contain to
a single node type (such as <q>book page</q>) and unset any access grants
provided by other modules on that node type configuration page.') . '</p>';
break;
case 'node/%/book_access':
$help = '<p>' . t('Configure access control per book based on users or roles. Settings
affect all pages within the given book.
These settings will have no effect for roles with permission to administer nodes.') . '</p>';
break;
default:
$help = '';
}
return $help;
}