Userreference Access

OK, the problem is definitely in this function. I'll get back to it in a little bit, but it may make enough sense for you to correct where an OR isn't doing what I think it should. I'm dyslexic and I swear that's why I can't do a damn thing with ANDs and ORs.

UPDATE for Drupal 6: If you provide a submit handler for a drupal_set_form form, you no longer have to add the system handler explicitly too.

The array() silliness at the end is gone, instead #submit itself is a simple, non-associative array.

In Drupal 6, whether the form is handled by the settings page helpful form wrapper or not, all you have to do is tack on another function to call.

Simply looking at this function is one of the most useful things you can do to understand node access control in Drupal. From the 5.3 version of node.module

I created a module (attached, in case you're curious) that's a user reference widget. When placed on a node type, it will hide itself and fill itself in from the URL with the person the request is being made of. When a node with the field on it is submitted, it emails the person.

What I need is a way to allow the user in the user reference field the same rights to the node as the author of the node. So for all access control, they should be treated the same.

Do you think that's something you can / want to do?

Thanks,

Michelle

Deep background: