Hi,
Sorry to ask a question that has already been asked, but I haven't managed to find a solution that works with the latest 4.7 yet, and am not sure I'm not actually missing something really obvious!!
Basically I would like for my non-admin users to be able to write a "Story" or whatever and save it without it being immediately published, or indeed publish it but not promote to front page until they choose to. This way they can work on and save articles from wherever they happen to be, and publish them only when they are happy with the final thing. However they shouldn't be able to promote / publish other people's half-written stories.
This is like giving them the "administer nodes" privilege, but only for their own stories (or other node types).
Searching the forums I have read solutions relating to the workspace node, but whilst that gives you a very useful view for this sort of thing, I can't see that it actually lets a user toggle the published or promoted flags? I can see it would be most useful in conjunction with something that did.
Is this possible with any module available for 4.7 RC? Thanks! Apologies if this is a stupid question...
Comments
I haven't used 4.7 too much,
I haven't used 4.7 too much, but the way out may be to have different roles as described here (for 4.6):
http://www.jiffle.net/node/70
Edit: I think moderation queue was removed from core for 4.7, so this may not be as simple as it sounds.
Submission Queue
See Handbook, and setup info.
Hi, Thanks for the responses
Hi,
Thanks for the responses and links - I think I haven't explained myself well though (or else I'm misunderstanding the answers :-) ). It's not that I don't want users to be able to publish their own content, but rather I want them to be able to choose whether to publish / promote to front page etc. for their own stuff as though they had node moderation permissions - but not for anyone else's stories.
Does that makes sense? Also I can't find a module actually called submission queue for 4.7 - if it's the moderating system that comes as an integral part of Drupal I can't figure out how to set the permissions to let the above happen??
Not out of the box :(
I spent the last fifteen minutes figuring this out on 4.7 RC3 and unless I haven't understood things well, you can't do this out of the box in drupal.
The publishing options for any node type (story, blog) only seem to appear on the node submission form if you give this set of users (or more accurately, the role these users belong to) the 'administer nodes' permissions. I am sure this is not what you want because it gives them blanket access to configure 'all' content types (hmmm... I thought this had been removed in 4.7).
As far as I know, the node_privacy_by_role module will be your best bet, especially if it has been updated to 4.7. You can create a role and put these users in that and any node they create will then have these options of not publishing/publishing to front page.
I don't know of any way to
I don't know of any way to do this, but I really want to push for this idea in drupal 4.8. I think of it as a draft, like in an email client. Here's some posts that have to do with the idea:
http://drupal.org/node/33499
http://lists.drupal.org/pipermail/development/2006-January/013119.html - mentions workflow
http://drupal.org/node/48731 - has a patch that you could try
http://drupal.org/project/workflow - I haven't tried this module, but it could do what you want. I'm not even sure what the status is on this.
--
Bradlis7.com | Churchofchristnet
Thanks everyone for the
Thanks everyone for the replies...
I had a look at node privacy by role, and unfortunately wasn't clever enough to work out how (if?) it could be changed to do what I wanted.
I am wondering if for 4.7 it would have to be done by hacking the node module? It's easy enough to get the options to show for the right users by doing that (move the "node options for administrators" (line 1635ish) out of the if person is an administrator section - but whatever you select as a non adminstrator isn't actually saved. Haven't worked that bit out yet :-) and I appreciate it is not a good way!
I will have a look at workflow module and see what that does. If not then I'll check out that patch that bradlis7 mentioned.
Hi again, Good news! You can
Hi again,
Good news! You can indeed do what I wanted with the workflow module.
For anyone else who wants to do the same, I downloaded the actions module and the workflow module and created 3 states - On front page, Published and Save as draft.
I put all my writers into a group (don't think this is strictly speaking necessary, but I couldn't make it work without so far!) and gave them all permutations of transition permissions between these 3 states.
Then I edited the actions choosing out of just:
Publish node
Unpublish node
Promote to front page
Remove from front page
in the obvious manner - i..e a transition from front page -> save as draft would be
Unpublish node
and
Remove from front page.
I then installed workspace to give it a sensible interface (of course non-admin users can't easily see unpublished stuff by default).
It's not quite perfect perhaps, but it works more than well enough for me! Thanks for all advice!
hey poorhouse thx for
hey poorhouse
thx for tackling this issue, youve hit the exact topic i was stuck on and was just attempting to hack the node module myself when i learned about your solution :)
the only question left - as you mentioned, a non admin user doesnt seem to be allowed to view / edit unpublished nodes ? how would i go about letting a certain role view / edit unpublished nodes ? [otherwise how would a nonadmin user republish a node he prev unpublished ?]
tia big time :)
ended up hacking up line 866
ended up hacking up line 866 in node.module from
'access' => node_access('view', $node),
to
'access' => ((node_access('view', $node)) || (array_search('staff', $user->roles))),
would rather not change node.module but i just cant figure this one out :(
Try the Workspace module
In the Workspace module, a set of links to all the nodes the user has created is made. It will display an edit button, even though the user can't view the node.
There are a few threads around seeking to remedy the view unpublished node permission problem. Here is the main issue page, http://drupal.org/node/41188, with a possible patch.
As for me, I too am contemplating a tiny tweak to the node module to make it behave as I want.
-Gman
yo Gman and thx :) i tried
yo Gman and thx :)
i tried WORKSPACE before and you are right about getting the EDIT link beside some of your content but for some reason it doesnt put that link beside all your items. dont know why and decided to look for other solutions. the one i posted above is the one i use for now.
thx for the link ill read through it. amazingly i never found it myself and i spent hours roaming the forums here :S