Add create permissions

It is not needed to add 'deny others' permission, because that's how it already works...

I think the create permissions could be difficult... The referenced user should become create permissions for selected content types or the content type which referenced (selected content types at field settings from master node) to the "master node". Is it possible?

I don't understand what you're asking for. Do you want the create permission for selected content types, or do you want create permissions for the type of node which is referenced? Do you need this at all or is this just a random idea that you don't actually need?

I want to talk to someone that has a legitimate use-case for a 'create' permission in this module, and a good explanation of why no other module is suitable for this purpose.

sub

I gotta say I didn't follow that at all. You pretty much lost me at "I build a group with references." which is the first thing you said :/ I have no idea what that means.

How about we just have an options like

Grant 'create' to referenced user for content types:
[ ] Page
[x] Article
[ ] Story
[ ] Product

And you tick the content types you want?

something like that?

And why not going deeper:
- give possibility to tick by taxonomy
- give possiblility to add dynamically referenced users as editor/moderator/publisher to a node
- ...

kukle, those sound like ideas that might need some more elaborate discussion, if you care to explain further please start some new issues, cheers.

This is actually more awkward to do than I thought, but I think I can make it work.

I've committed a solution, give it a go see if it does the trick. It doesn't work the way the other grants do, so I can't use my usual ways to easily test it.

The posts #14 and #15 do not appear to describe an attempt to use functionality that this module actually provides? I.E. you cannot "give referenced users view access to referenced nodes" - that doesn't sound like what this module does.

The feature that was added for this issue was the 'create' permissions.

I think I understand what you're trying to do, but you have it totally backwards, unless you're not explaining it right.

1) Create a content type called 'circle'
2) Add a user_reference field on 'circle' type and set up nodeaccess_userreference to give referenced users 'view' access to the current node.
3) Create a circle node and reference the users you want to be in on the circle.
4) Create a content type called 'circle item' (this represents other pages within the circle - you can several such content types for different stuff)
5) Add a node_reference field to 'circle item' type which can reference only 'circles', and set up nodeaccess_nodereference to pass on view access when they can view a reference.
6) Create a 'circle item' and set it's node reference to be the 'circle'.
7) The users referenced in the circle should now have access to the circle item created in step 5.

Anyway, I'm marking the create feature as fixed as no doubt the issue will resurface if there is any problem with it.

Here's how I use it:

• I have a content type, called "Groups", with user_reference.

Users on my site can create a Group item, i.e. Travel, Hiking, Swimming, etc... and reference users (mods)

• I have a content type, called "Blog", with node_reference.

Users on my site can create a Blog items, i.e. 99 Reasons to Travel, How to Swim, etc... and reference the node (their group)

As a result, the Blog item only appears under the Group item, i.e. "99 Reasons to Travel" can be seen under Group "Travel".

Features lacking:

• Limit users to only provide Blogs for their Group, i.e. ability to only reference node (blog item) to the node (group item) of which I am referenced. Example - If I'm referenced in Group->Travel, I can only post Blog->99 Reasons to Travel under Group->Travel, not to any other groups.
• Assign roles/permissions to the user_reference field, per user. In other words, the creator of the Group->Travel can have the "admin" role, with an ability to add (reference) users to the group with "mod" role (less permission).

The create permissions feature was added, the issue settings are meant to reflect this, please don't change them unless the implementation was wrong.
I'm not sure your comments even make sense for *this* module, but if you want to explain in more detail why they do, then start one issue per request.

I second JohnnyX! Exactly the same issue here.

FYI, I've created a new issue on this request http://drupal.org/node/1295370

Updated description...