It would be really nice for smooth intergration with other modules (e.g. Module Grants ,Workflow etc) to have the ability to select at which content types the UR Node Access will limit permission. The idea of all content types (enabled) or none (disabled) is not really flexible in a multi-content site. I think it's pretty logical to have the option to select which content types UR Node Access deals with grants.

Comments

alex.k’s picture

Version: 6.x-1.0-beta10 » 6.x-1.x-dev

I understand about adding per-content-type settings for what grants are possible, but that's internal to UR Node Access. Could you explain what role module_grants or workflow would play here.

charos’s picture

Smooth intergration was quite bad as an expression. What I meant to say is smooth co-existence. I'll illustrate this with what happened to me:
I've managed to setup a Workflow for a specific content type. Too summarise things , Workflow permissions don't work with unpublished content. That's what Module Grants module does (create content publication workflows that include unpublished content by controlling the granting in a more logical way). Although I don't want to relate this content type with UR (it's a content that even guest will see e.g. articles) but I need the UR Node Access to function for the profiles (Content Profile). So currently I either have to discard Workflow or UR Node Access -unless I implement the "OR" function for module_grants of UR Node Access to the Module Grants. I guess the latest will be the solution (I've got to get a developer to do that cause I cannot code) so from all this little adventure of mine , I came here to make this suggestion which seems very logical I think: have the ability to set which content type the module_grants apply to. I guess I will sort this problem of mine sooner or later. That is to indicate that this is not a "hey my site don't work so please change the code" type of post. I just think it would be useful for many users to get that flexibility generally. I don't know if it's a lot of work such thing , but if it's not , it might be worth looking into it!

alex.k’s picture

Sounds good, thanks. Will try to add this feature, just not sure when. It will amount to a checkbox on the content type configuration form, similar to how Content Profile does it. Then certain content types would be eligible to be posted to associates, and others would not, even if the user has enough permissions.

I'm just thinking, perhaps at the same time it makes sense to have all three checkboxes for view, edit, delete permissions? So that for each content type these can be set up independently. Right now it's done using permissions, so all content types work the same way for a given user role.

charos’s picture

Having all three checkboxes for view, edit, delete permissions is a choice of flexibility vs. k.i.s.s. (keep it simple stupid!). Personally I would prefer it, but it might be frustrating for other admins to do this for every single content type it's added. But it would give an excellent flexibility so thumbs up here!

mrf’s picture

Status: Active » Fixed

This is now available in ur node access.

Status: Fixed » Closed (fixed)

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