I'd like to propose a logical structure to these modules, which would also aid in creating relationships between Node & User, thus allowing users to create groups, add members to their groups, and together with group's members - populate their group with content.

Please see the attached illustration.

  • I create Content Type->Groups, add User Reference field.
  • User creates Content Type->Groups->Group1, and adds Users through User Reference, setting their Roles as Admin, Contributor or Member (Admins - manage group members, Contributors - contribute content, Members - view content, comment).
  • I create a Content Type->Blog, add Node Reference field.
  • User creates Content Type->Blog->BlogPost1, and adds Group1 through Node Reference(i.e. adds a blog post to his group). User can only Node Reference the Group which they are User Referenced to as an Admin or Contributor (i.e. user can post it under their group only).

The original discussion can be found here http://drupal.org/node/1231248. This structure is similar to here.

I'd love to hear all feedback, including JohnnyX!

CommentFileSizeAuthor
reference mod.png185.41 KBtimofey

Comments

danielb’s picture

danielb commented

User creates Content Type->Groups->Group1, and adds Users through User Reference, setting their Roles as Admin, Contributor or Member (Admins - manage group members, Contributors - contribute content, Members - view content, comment).

This module is not designed to assign user roles - so that makes zero sense to me - you can of course create different fields for different purposes and assign access accordingly. You can label these fields as 'admin', or 'member' etc... to suggest to your users what their purpose is.

User can only Node Reference the Group which they are User Referenced

This module does not control what can be referenced - the references module already gives you full control over this using Views (which I wrote a lot of the code for, btw). You can add contextual filters on user reference fields for the current user to make such restrictions.

Confusing diagram is confusing.

danielb’s picture

danielb commented

See also
#1261782: Only reference own nodes?
#1261790: Respect access permissions of nodes
Except instead of basing the contextual filter on authors you would base it on user reference values.

danielb’s picture

danielb commented
Category: feature » support
Status: Active » Fixed

So yeah, I believe your feature request comes from a lack of understanding, both in what can already be done, and what is within the scope of the projects in question.
If this is unsatisfactory for your needs, then you will have to write a module that brings together the functionality from the various modules in a way that is suitable for you.

timofey’s picture

timofey commented

Since I brought up the idea, I came across the relation module, which aims to build the relationships I was thinking of. So that would solve the problem.

danielb’s picture

danielb commented

Yeah I'm looking to modules like that for the future too, I think we will all get much more of what we want with a concentrated effort to do references/relations, and leave a lot more room for features and add-on solutions.

Status: Fixed » Closed (fixed)

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

Anonymous’s picture

(not verified) commented
Issue summary: View changes

correction