Closed (fixed)
Project:
Override Node Options
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
16 Nov 2008 at 14:37 UTC
Updated:
30 Nov 2009 at 21:19 UTC
Good to see this module has a new maintainer. This module would be quite more useful if a new access permission is included: "View unpublished nodes".
For more information please have look at #273595: Move permission "view any unpublished content" from Content Moderation to Node.
Comments
Comment #1
timmillwoodI just create a view that displays unpublished nodes.
Comment #2
Roi Danton commentedAnd who is able to view those unpublished nodes that are listed in this view? Only the ones who have the "manage content" permission.
This request is about the possibility that users without manage content permissions can edit unpublished nodes. Therefore a new node permission is required. But contrary to my first thought it doesn't fit into this module since this "view unpublished nodes" permission has to be set globally and not per node.
Comment #3
cas99 commentedThe user who created the unpublished node should be able to see it - otherwise they have no way to go back to view, edit, delete or finally publish it (unless they want to remember some obscure node URL)
I don't think it requires an extra permission - it should be automatic. If you have any unpublished nodes then you should be able to view them (and do whatever else to them that your permissions allow, including edit or delete them).
Comment #4
timmillwoodI still think the best option is to create a view showing the unpublished posts.
This is what I do for all my sites.
Comment #5
Roi Danton commentedThe original purpose is to allow a collaboration with other editors (without the "manage content" permission) which should be able to edit those unpublished nodes. Therefore a view wouldn't be enough since they still can't edit those nodes.
However I'm using the workflow module and define custom states so this request doesn't exist anymore. I just wanted to clarify the purpose of this request. :)
Comment #6
mlncn commented... which makes this feature request active! Subscribing...
Comment #7
Tom Freudenberg commentedHi u all,
today we discussed same problem and for that we had decided to use module "workflow" instead of doing this anywhere else. The "workflow" module does everything you need for viewing and reviewing node content as well as an extend ACL settings for options like "which role has access to which state while being in publishing context".
See also my issue here for a patch to "override_node_options.module" to leave Author-Info untouched if it was not given by form alter.
Tom
Comment #8
KoCo commentedI believe this is a very much needed feature.
Referring to two other modules attempting, more or less, the same thing.
http://drupal.org/project/cmf
http://drupal.org/project/publishcontent
The first doesn't allow for giving publish, etc rights based on roles. Which is a prerequisite. A certain role can have rights to decide wether or not certain node types should be published, but not automaticly for all possible node types. In my case some users can override the node options, but aren't allowed to edit, create or delete those nodes.
The latter module defines publish rights by role, but doesn't provide an overview or makes other content management rights available. It does however expand on the edit node menu. Thus in combination with views, I consider it half way there.
A view displaying all nodes like the tracking, but with all possible filters for searching, only showing the nodes that can be overridden by the user and some extra actions allowed for that user role is probably the best solution. Then all override options can be set separatly by node type and user role.
However allowing a minimized edit form for nodes, just displaying the allowed node options, for users who can only override node options, would be way cool. Then they can just surf the site and override options on the go.
If only I had all the time in the world ;-).
Comment #9
bartezz commentedWhat about this;
http://drupal.org/node/357594#comment-1195499
Comment #10
joachim commentedLooks like http://drupal.org/project/view_unpublished does what people need.
Marking this as wontfix.
Comment #11
joachim commentedHmm, actually, we could do with a link to that module on this module's page.
@timmillwood, could you take care of that please?
Comment #12
timmillwoodI was going to fix (add link to project page), but can't edit the project page.
Opened an issue. http://drupal.org/node/647048
Comment #13
joachim commentedYou should be able to because you're up there as the project owner!
I wonder if this is the same problem as #646586: Detection of the maintainership of a project broken.
Comment #14
timmillwoodComment #15
timmillwood