I noticed that I had a blog post that could not be edited by the author. Then I had the memory of writing the blog as first user and then setting the authors name manually. Well this shows the entry as being created and listed by the author but the ownership stays with the first user. The entry can be seen but not edited by the recipient author because the permissions are still with the first user.

It would be nice if a designated user could create content and give complete ownership to another user. So an "editor" with ownership permissions could create a story outline (node) and deliver ownership to the "reporter" that will write the story.

CommentFileSizeAuthor
#1 ownership.module1.54 KBzaim-1

Comments

zaim-1’s picture

StatusFileSize
new1.54 KB

I wanted this feature as well. I wanted it urgently so I've written a module to do it. I just implemented a hook_nodeapi() that adds a "New user name or ID" field in node submission/edit forms, and during node inserts/updates, will change it's uid field to the given new user's.

jonbob’s picture

Mguel’s picture

Version: » 5.2

I would need this but for drupal 5.2

I created many nodes for different users (I'm admin). In the ownership field I set the different meant ownerships, but afterwards I realized that that info is only the "displayed" ownership, since they can't edit that node nevertheless they have permissions to edit their own modules. In the contrary if they create a node afterwards they are able to edit it, but not the one I created for them...

Thants why I would use the ownership.module so I can change ownership to the nodes I created for different users.

cheers

jamin0’s picture

This does not work. Changing the uid to in the node table still does not give edit privileges to the new user.

damien tournoud’s picture

Status: Active » Fixed

@jamin0: please verify that the node is using an Input format that the author can use.

This is an old enough ticket for a non-issue, marking as fixed.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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