Laura Scott wrote:

On Sep 14, 2007, at 10:36 AM, Stefan Seefeld wrote:

...

Hello,

I'm experiencing a problem (probably) related to permissions:

When a user attempts to create a new node (this applies to multiple node types), he can't see some of the options displayed at the end (publishing options, authoring information). I do see these options when I'm logged in as admin. What could cause this ? What permissions should I check ?

Those are administer nodes permissions. Not something you want to give just any user. What do you want to achieve? There may be other more secure approaches.

Huh. Earlier today I attempted to explain to some user how to write and edit content (pages, say), save it, but only publish it later once the page is ready. Do I need to be an admin to publish / unpublish nodes ?

Thanks, Stefan

Metzler, David wrote:

They don't need to be a full admin, but they do need administer nodes privileges. I typically give this for site editors.

OK. Are there any potentially dangerous side-effects in giving this sort of previledge to all authorized users (as Laura seemed to allude to) ?

(I'm talking about a small site for about 30 users and I want everybody to be able to edit and save unpublished work, and then come back to publish it later.

Thanks a lot, Stefan

On Sep 14, 2007, at 1:54 PM, Earnie Boyd wrote:

Quoting Stefan Seefeld seefeld@sympatico.ca:

...

Metzler, David wrote:

...

They don't need to be a full admin, but they do need administer nodes privileges. I typically give this for site editors.

OK. Are there any potentially dangerous side-effects in giving this sort of previledge to all authorized users (as Laura seemed to allude to) ?

Yes. If you want to control the users to a particular node type you can't. Also allows the users to CRUD node types and puts administrative items in the menu.

You *can* give users permissions to edit their own nodes, though I'm not sure if they can see their own unpublished nodes. Getting their node published, though, is another wrinkle without administer nodes permissions. Perhaps a combination of a cck field and actions module?

Laura

Quoting "Metzler, David" metzlerd@evergreen.edu:

They don't need to be a full admin, but they do need administer nodes privileges. I typically give this for site editors.

But you want to create a separate role for that check box and assign the users to that role.

Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/

Quoting Stefan Seefeld seefeld@sympatico.ca:

Huh. Earlier today I attempted to explain to some user how to write and edit content (pages, say), save it, but only publish it later once the page is ready. Do I need to be an admin to publish / unpublish nodes ?

Yes. But I can understand why you would want to allow the authenticated user to do this. I took a guess that someone else might have had the desire to do this. I went searching the list of modules for the word publish and found this http://drupal.org/project/override_node_options that might help.

Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/

A combination of workflow and workflow access would achieve this.

Create a two workflow states: draft and published

For draft, only allow the author and site admins to see and edit the node.

For published, allow authenticated users to see the node.

This eliminates the need for giving users admin node rights (something not to be done lightly), and lets you assign crud rights on a content-type by content-type basis.

Cheers,

Bill

Stefan Seefeld wrote:

Laura Scott wrote:

...

On Sep 14, 2007, at 10:36 AM, Stefan Seefeld wrote:

...

Hello,

I'm experiencing a problem (probably) related to permissions:

When a user attempts to create a new node (this applies to multiple node types), he can't see some of the options displayed at the end (publishing options, authoring information). I do see these options when I'm logged in as admin. What could cause this ? What permissions should I check ?

Those are administer nodes permissions. Not something you want to give just any user. What do you want to achieve? There may be other more secure approaches.

Huh. Earlier today I attempted to explain to some user how to write and edit content (pages, say), save it, but only publish it later once the page is ready. Do I need to be an admin to publish / unpublish nodes ?

Thanks, Stefan

Earnie Boyd wrote:

Quoting Bill Fitzgerald bill@funnymonkey.com:

...

Create a two workflow states: draft and published

For draft, only allow the author and site admins to see and edit the node.

For published, allow authenticated users to see the node.

Would you care to elaborate more on this? How are the workflow states created?

Sure. Via the workflow module -- http://drupal.org/project/workflow

Workflow ships with the workflow access module, which lets you assign rights (by role, and by node author) to view, edit, and delete nodes in specific workflow states.

So, install the workflow and workflow access modules.

Create your new node type (I recommend using CCK for this). In the access control page, assign your authenticated user role the rights to create, but not the rights to edit their own posts (rights assigned here trump the rights assigned in workflow access).

Then, in the workflow admin settings, create two new workflow states: draft and published. For the draft state, only allow the author to view, edit, or delete nodes. For the published state, open it up and allow authenticated users to view posts.

The best way to sort through this is to install the modules and play around a bit -- workflow offers you some pretty amazing options, but you need to put in some time getting your head around what it offers.

Cheers,

Bill

So