I use Override Node Options (http://drupal.org/project/override_node_options) to control access to my publishing options. So on some pieces of content, an authenticated user may not have the ability to edit any publishing options. However, I created a custom pub option labeled "Featured" and can't remove the edit permission from this pub option and so it is just sitting there all alone. See attached image.

If the Custom Publishing Options module could work with the Override Node Options module, that would be great. But at a minimum, I need the ability to set edit permissions on a custom pub option.

CommentFileSizeAuthor
#16 incorrect_permission_function_name-1167620-16.patch664 bytesszantog
#8 incorrect_permission_function_name-1167620-8.patch664 bytesAnonymous (not verified)
featured_custom_pub_option.jpg30.86 KBdkingofpa

Comments

arcaneadam’s picture

arcaneadam commented
Status: Active » Closed (fixed)

Added this feature into the latest version: 6.x-1.3.

NathanM’s picture

NathanM commented

Is it possible to access these permissions without granting administer nodes access to those users?

arcaneadam’s picture

arcaneadam commented

Yes. Each option has it's own permission availability. Alternatively, you can use the administer nodes permission to give access to any/all of them.

NathanM’s picture

NathanM commented

I understand it is supposed to be that way, but I can't get the publishing options field to show up for authenticated users unless I enable the administer nodes permission. If I just allow edit permissions in the Custom Publishing Options permissions table, it doesn't show up on the edit form for authenticated users.

NathanM’s picture

NathanM commented

Wait, it seems to be working now. Not sure what changed here. Maybe I had to rebuild permissions. This is great, now, by the way.

NathanM’s picture

NathanM commented

Is this integrated into the 7.x version yet? I have upgraded my installation to Drupal 7.8, but can't seem to set permissions for custom publishing options.

NathanM’s picture

NathanM commented
Version: 6.x-1.1 » 7.x-1.x-dev
Status: Closed (fixed) » Active

Changing status on this to reflect D7.

Anonymous’s picture

Anonymous (not verified) commented
Category: feature » bug
Status: Active » Needs review
StatusFileSize
new incorrect_permission_function_name-1167620-8.patch664 bytes

The permissions function in the D7 version was named incorrectly (had an 's' on the end).
The attached patch fixes this to make permissions work properly.

mnordstrom’s picture

mnordstrom commented

EDIT: Nothing anymore. :)

hixster’s picture

hixster commented

Using 6x-1.4 and can't see my custom publishing options. My role doesn't have administer nodes permissions - I have the toggle permission switched on for the role. The whole publishing pane is missing?

hixster’s picture

hixster commented

**bump** anyone?

NathanM’s picture

NathanM commented

Also not seeing this anymore in 1.4 for 6.x.

NathanM’s picture

NathanM commented

Finally figured out how to apply a patch and got the 7.x version working perfectly with "Override Node Options". Thanks a lot. Hope this gets committed to the dev version soon.

NathanM’s picture

NathanM commented

6.x also works fine, so ignore comment #12.

kevinquillen’s picture

kevinquillen commented

Will review soon.

szantog’s picture

szantog commented
StatusFileSize
new incorrect_permission_function_name-1167620-16.patch664 bytes

Rerolled #8 against the latest dev. Commit please, this is trivial.
Ps. I don't know, why can't apply #8, it seems, that is exactly same as this.

kevinquillen’s picture

kevinquillen commented

I will add this immediate change right now- but I really think it should be expanded to include:

  • hook_access checks
  • expanded permissions for Viewing (users can/can't view content of type ____)

The second would help from creating a lot of Views I believe, to display different published content, and facilitate Entity access control (when it gets to that point). Just a thought.

kevinquillen’s picture

kevinquillen commented

Committed to dev. Will get it in a release tomorrow, I am going to try and knock out the other trivial issues first before that.

http://drupalcode.org/project/custom_pub.git/commit/757a712

kevinquillen’s picture

kevinquillen commented

Now the permission(s) appear and can be assigned to roles, but there is something weird that doesn't make sense with this implementation.

It looks like the status options only appear if you have administer content access- and if you have that, then you have all CPO options at your disposal. If you have added access modules to control access specifically to publishing options per role, then the UI makes more sense. But if you don't, it's a little weird to show permissions for CPO without it because they have 0 effect and can be confusing as to their purpose.

I think a few things should happen here:

  1. Update the README and/or hook_help to provide best ways of using CPO on its own, or CPO and Override Node Options used together.

The other thing I am working on now... but doesn't directly impact CPO. I'll see if I can get that up today.

kevinquillen’s picture

kevinquillen commented
Status: Needs review » Fixed

This will be in the next release and should work when using CPO on its own, or CPO with Override Node Options.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.