I would like to allow some of my users (with help of roles) to post content in a few categories.
So I set up taxonomy and flexinode.

Let's take an example.
I created a flexinode : Car review.
I created a taxonomy vocabulary : cars that I made required and limited to my flexinode car review.
I change default Workflow to make content created under flexinode car review unpublished.

Then I allow the role "car editor" to create "car review".

Up to this point, everything is great, people, from "car editor" can create an unpublished content and with the help of workspace.module, they can review it if they want.

The big point is :
- how do I allow a role ("car review moderator" for example) to be able only to publish this content and only this taxonomy ?
- how do I create a role that can get the promote on front page ?
- optionnal : can I restrict the use of node_privacy_byrole module to display only roles that my author belongs to ?

Well the only way I found to allow users to publish content was to give them the administer content rights, but I don't like it because they are given all grants on content.

Is someone has setting up such workflows ?

Comments

tostinni’s picture

No idea ?
:(

Steve Dondley’s picture

Drupal is currently only capable granting or denying users the capability to view, update or delete nodes using node permissions.

New kinds permissions would have to be created for each of the various administrative functions you mention (promote, publish, categorize, etc.) before what you want to do would be possible.

Node-based permissions are pretty new to Drupal and the modules that take advantage of them aren't even in the core yet. It may be a while before the capabilities you seek are possible.

I'm sure someone is working on, or at least thought about, making such changes. I know I have. It would be a bit of work, though.

jasko’s picture

As a big time Pythonista/Zopista/Plonista (though notice that my community site http://fortprogress.org is run on Drupal), I can only recommend that the Drupal developers look at Zope's security model. It's truly granular and pretty much rocks socks.

Why am I running Drupal if Zope is so great? 2 reasons:

1) LAMP hosting is much more available than ZOPE hosting.
2) I needed the functionality of the submission queue. It's just what I wanted.

But that doesn't mean that Zope/Plone isn't a real technology leader. I think Drupal could be improved by taking choice pieces of Zope/Plone to heart.

tostinni’s picture

It was one of my first choice, but as I went into the detail, I feel very difficult to enter in the code, I don't know anything about Python and the massive number of files just scare me :) Also I did have troubles designing the rights permissions with plone.
So I went to Drupal and feel much more confortable with the very little code threre is to drive this CMS ;)

killes@www.drop.org’s picture

This is all possible with Drupal. You only need a few contrib modules which don't exist yet....
--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.

orangechicken’s picture

Is there a valid answer for this now? I've looked into Workflow/Actions but I can't seem to find out how to move the actions/workflow to the Roles level (instead of the individual User level) - though it seems like I'm probably missing something very easy.

How do you have a role Writer that's allowed to write unpublished content and a role Editor that publishes the content? Seems very basic.

tostinni’s picture

I don't have a complete answer for the moment, I never tested workflow/action module, so I don't know if it can solve this. (I heard that it should...)

btw, you can make something similar doing this :
- set page workflow to unpublished (admin/node/configure/types/page)
- allow some roles to create pages (writers)
- give a role "administer nodes" perm (editors)
and you get it