Jump to:
| Project: | Revisioning |
| Version: | 6.x-3.14 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I can enable the "New revision in draft, pending moderation" option in the content type defaults. Doing so makes every new edit for the node go into the "draft" state. Roles with this module's "publish revisions" permission can then move the revision out of the "draft" state. This works as expected.
If I turn off the "New revision in draft, pending moderation" option, with no other permission changes, every new edit is immediately published. This works as expected.
How can I get a per node choice when editing wether or not I want to put the edits to the node into a "draft" revision or a "published" revision?
Roles with "administer nodes" get this choice, but the whole point of this module is to not have to give that permission to people.
I'm not certain if my issue is the same or related to this issue: http://drupal.org/node/848474
Thanks for any help.
Comments
#1
Hey bigdave,
As you mention yourself... all is working as originally intended.
That is not to say that your suggestion doesn't make sense. But it requires code or another module to help us out.
Have you considered throwing Workflow in the mix?
Off the top of my head it looks to me that you could have a forked workflow whereby two routes lead to a published node: one via moderation, the other direct.
Here's a tutorial, http://drupal.org/node/408052, explaining how to use Revisioning in combination with Workflow. It's not describing your exact use-case, but it may help in familiarising yourself with this module combo.
Hope this helps,
Rik
#2
Just having that "New revision in draft, pending moderation" checkbox available on the node edit form is what i'd ideally like. It's a simple choice that doesn't require setting up another module. And like I said a user with "administer nodes" gets this behavior exactly. I just don't need or want to give users that permission.
My primary use of this module is to allow someone to save an draft of the node before publishing it. Perhaps to let someone review it, but that reviewer isn't required to formally approve it. Or just to work on a revision over the course of several days without having to resort to using something outside of drupal like say Microsoft Word (shudder) to draft the document.
I do see the usefulness in a more complex scheme, and it the future it might be necessary, but for us, for now, it's not.
#3
Save as Draft ?
#4
"to see the Save as Draft checkbox you need to either grant "administer nodes" permission..."
The module talks about another module that can allow it to work without administer nodes. I'll research and post back my findings for future generations.
#5
Hello, RdeBoer! Thanks for your work, module is great.
All bigdave askes is to change the line 22 in revisioning.pages.inc
<?php
if (user_access('administer nodes')) {
?>
to
<?php
if (user_access('publish revisions') || user_access('administer nodes')) {
?>
to let people who has right to publish revisions do it right through the edit form without giving them the right to administer nodes. Seems appropriate to me, I give my vote for this feature.
#6
#2: If that checkbox is available on the node form, and the user has permission to see it, and unchecks it, the new revision is published immediately.
Does that also mean all further revisions by other users (who may not be able to see the checkbox) would also be published immediately, ie the checkbox retains its state?
Or is it a "one-shot" thing that reverts back to the default checkbox state for the content-type the next time the node is edited - as it does now if the user has "administer nodes" permission?
#5: Either way, I think this needs to be a new permission, not just the existing 'publish revisions' permission. That could have very bad side-effects on existing installations.
#7
Old post I know but I second comment #5 it needs a new permission .
#8
This latest check-in should do it: #952616: Publish permissions per content type.
Using these publication permissions authors can create revisions and then have them published by someone else OR THEMSELVES.
Available in 6.x-3.13 and 7.x-1.2.
Note also that D7 is more flexible in this respect, in that the (too powerful?) "administer nodes" permission has been split into the less far-reaching "Administer content" permission and the super permission "Bypass content access control".
#9
I don't think the solution mentioned in #8 resolves the issue. I want certain people to have control over whether they save a node revision as a draft or published. Having access to the "New revision in draft, pending moderation" checkbox seems the natural solution to this. And the method in #5 seems elegant and logical. If a user has "publish revisions" permission, why shouldn't that person have access to the checkbox?
Am I misunderstanding #952616: Publish permissions per content type? Does it give the user control over whether to save a node revision as a draft or published? If so, how?
#10
@bwinett, #9:
Hi @bwinett,
Thank you for your interest!
Have you tried the module for yourself? If so, 6.x-3.13 or 7.x-1-3? Having a play with it may clarify things.
The "New revision in draft, pending moderation" on the content type determines whether a new,initially not-yet published revision (i.e. draft) is created.
Then after this those users with the "publish revisions for content-type XXX" permission have the option to publish this revision or leave it as a draft for a little longer.
In addition users with the "administer nodes" permission in D6 or "administer content" in D7 may opt-out of the the creation of the new revision (draft) by unticking "Create new revision" on the Edit form and then either ticking or unticking the Published box.
This is ok in D7, but not recommended in D6, as in D6 the "administer nodes" permission also gives the user far-reaching permissions regarding content editing and deletion.
Rik
#11
Hi @Rik,
We're using 6.x-3.13. The meaning you give to "New revision in draft, pending moderation" is not the meaning I had inferred, nor the meaning I would hope for. In addition to determining whether a new node is saved in draft state, I was expecting that it could be used to save a new revision of a pre-existing node in draft state, leaving the earlier revision published. In fact, for a user who has "administer nodes" permission, this is how it works.
However, if a user who doesn't have "administer nodes" permission edits an existing, published node, that user doesn't see the "New revision in draft, pending moderation" checkbox. This user can't control whether to save edits in draft state or published.
We made the change in #5 above, and it works for us. But although it works, thinking about it last night I realized it's not technically correct - we want the user to have permission to save a new revision in draft state, which is not implied by the "publish revisions" permission. This might be what @Mike Dodd might have been implying in comment #7.
#12