Drupal book outline only for nodes of specific type

1

I have a Drupal site, which allows all logged in users to add and edit book pages. On the permissions page I have enabled they may also administer book outlines.

The problem is that they can do this for all nodes, even forum topics and pages, and blog entries. Does anyone know how I can fix this, so that people can only change this for book pages?

rightfold

Posted 2009-07-27T16:22:23.763

Reputation: 579

Perhaps link the website? Since if I google Drupal I hardly understand your question – Ivo Flipse – 2009-07-27T16:26:11.353

Sorry, my website is only on a local website. If you want to know what Drupal is, check http://www.drupal.org/

– rightfold – 2009-07-27T16:27:06.780

Shouldn't this question be rather on serverfault? – txwikinger – 2009-07-27T16:51:22.707

Answers

2

You should look into the acl modules. There are acl modules that allow you a finer granularity which allows you to say certain users can only do certain tasks with nodes of a certain type.

txwikinger

Posted 2009-07-27T16:22:23.763

Reputation: 2 467

1

Better, you can go to user management => permissions. from that, uncheck the relevant box in the authenticated users column. Instance "Administer nodes" (All Appropriate edit permissions). Similarly for your forum & blog modules.

user320784

Posted 2009-07-27T16:22:23.763

Reputation: 11

0

In User Management -> Permissions be sure to uncheck the relevant boxes in the authenticated users column, for instance "administer nodes" (and all the appropriate edit permissions) under node module and similarly for your forum and blog modules.

Dan U.

Posted 2009-07-27T16:22:23.763

Reputation: 223

Sorry, didn't help. They are unchecked already. – rightfold – 2009-07-27T16:30:45.247

Hmm, only others things offhand I can think to check are (a) to make sure all the permissions set for authenticated users are correct and (b) that the users who are able to do this editing where they shouldn't be aren't accidentally set up with any role that they shouldn't have. And that you're not inadvertently logged in as admin while replicating this behavior, but rather logged in as an authorized user. – Dan U. – 2009-07-27T16:40:13.540