[drupal-devel] [feature] new permission: create new books

merlinofchaos drupal-devel at drupal.org
Thu Aug 11 00:01:11 UTC 2005

Issue status update for 
Post a follow up: 

 Project:      Drupal
 Version:      cvs
 Component:    book.module
 Category:     feature requests
 Priority:     normal
 Assigned to:  moshe weitzman
 Reported by:  moshe weitzman
 Updated by:   merlinofchaos
 Status:       patch (code needs work)

Should this permission be 'create new books' or simply 'administer
books' or should they be separated out? I ask because if someone's
going to work on this, it seems like a good idea to simply back away
from administer node privileges entirely.

The question that remains, to me, is whether or not there is any real
gain by having create new books as its own permission.


Previous comments:

Wed, 02 Jun 2004 23:39:34 +0000 : moshe weitzman

Attachment: http://drupal.org/files/issues/drbook.patch (1.39 KB)

in order to create a new book, the user currently must have 'administer
nodes' permission. this is a bit too broad. this patch introduces a
'create books' permission and improves the help text a bit.


Tue, 10 Aug 2004 01:54:25 +0000 : moshe weitzman

this patch is old now, with new menu system. functionality still needed.


Fri, 01 Oct 2004 15:10:15 +0000 : moshe weitzman

Updated patch. It is far less risky to grant 'create new book' as
opposed to 'administer nodes'.


Sun, 03 Oct 2004 16:11:29 +0000 : nedjo

+1, this makes sense as a distinct permission.  Should the permission
test however be if (user_access('create books') ||
user_access('administer nodes')) {, instead of if
(user_access('administer nodes')) {, on the assumption that 'administer
nodes' includes creating books?


Sun, 13 Mar 2005 21:04:11 +0000 : killes at www.drop.org

Makes sense to me, but the patch is outdated.


Wed, 10 Aug 2005 23:46:53 +0000 : killes at www.drop.org

maybe somebody wants to look at it again.

More information about the drupal-devel mailing list