The number of permissions this module adds is a bit overwhelming and hard to manage -- bit of a mixed blessing.

Integration with http://drupal.org/project/node_permissions_grid might help, though my concern there is that it would make the table for the permissions there REALLY wide, and possibly hard to use too!

Thoughts?

Comments

joachim’s picture

NPG would have to turn action_prefixes() into an info type hook, so ONO can supply the extra action strings.

timmillwood’s picture

This module originally had one permission per field, which then worked across all content types site wide.

I added per content type permissions to give more flexibility, although it has made the permissions page a bit of a mess.

node_permissions_grid might help.

Another option i was thinking was to have all permissions on a override node options settings page, but that gets a bit messy.

joachim’s picture

Slight problem...
NPG works with permissions of the form ACTION CONTENT-TYPE SUFFIX, like 'edit own / page / node' or 'create / forum / post'.
With something like 'override blog revision option' we have ACTION CONTENT-TYPE ACTION SUFFIX.
It's not easily doable; would need the regexes reworking somehow to find CONTENT-TYPE inside ACTION (and *then* not look for it afterwards.)
Given my reservations about how wide it would make the NPG page, I think I might drop this particular tack.

The other option like you say is an ONO page. How about a tab for each content type?

opdavies’s picture

Issue summary: View changes

node_permissions_grid is now marked as obsolete, and has been superseded by permission_grid. There's only a D7 version of permission_grid though.

opdavies’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
jenlampton’s picture

Status: Active » Closed (works as designed)

I'm going to close this issue since it looks like the demand has disappeared, but please reopen if I'm wrong.