I'll describe my setup, just incase someone has a suggestion on how to better organize this.
For my art site, I have content types for artwork, artists, and places. When a user creates an account, they have the ability to create these content types and edit the ones they've created.
For each of these content fields, though, I've created a CCK user reference field. I forsee that in the early stages of this website, I'll be creating places (mostly galleries) on my own...and then creating accounts for gallery owners later...These owners can maintain their pages.
Also, when the site gets going, I'd like the ability to have more than one user edit a node type. So if a person creates an artwork, they can maintain that node as well as a user of their choosing (i.e. a gallery owner).
So basically, how can I use the value in the CCK user reference field to give a user "edit own content" access?
Comments
Just wondering if anyone has
Just wondering if anyone has a solution. I know there's Organic Groups but I'm looking for something that wouldn't fundamentally change my site. Most of my content would, at most, need no more than two or three users (something easily managable with user-reference fields). Then again, I haven't tried Organic Groups yet, so if there's not another way to allow more than one user to "own" a node, then I'll switch to OG.
Taxonomy
Did you consider using taxonomy?
You could use the modules taxorole (generates roles for taxonomy-terms) and taxonomy-access.
So, you would replace the user field with a taxonomy. For each user-taxonomy taxorole generates a role. you can then asign the
roles to the users and manage the access with taxonomy-access. Thats a little bit complicates, but should work.
Daniel Greitens
www.maximago.de
The some problem, but I'm
The some problem, but I'm not using taxonomy.
Solution
Try this patch: http://drupal.org/node/323692 for the view_own module
http://drupal.org/project/nod
http://drupal.org/project/nodeaccess_autoreference