new permission: create new books

+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?

Makes sense to me, but the patch is outdated.

maybe somebody wants to look at it again.

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.

The entire issue of permissions for book module needs to be re-examined. See also http://drupal.org/node/21559.

In the meantime, I believe that 'administer books' and 'create new books' should be kept distinct.

Administer books, for example, implies permissions to delete other user's book pages. I can think of many situations where one might want a user to be able to create new books, but not mess up other peoples' books.

Djun

To be honest, I don't like the whole "administer XYZ" permission format in the first place. What the heck does "administer" mean, anyway? Create? Edit Own? Edit Others? Delete Own? Delete Others? That's five different possible operations. Which of them does "Administer" cover? I honestly have no idea. :-)

Finer-grain permissions for those five operations would from a UI perspective be much much better, simply because they are easier to understand. (That goes for books and for everything else.)

Is there an updated verssion of this create a book patch? I am creating a writers site and need them to be able to create their own books. Thanks.