This may be out of scope for this module, so feel free to won't fix it. There was someone on IRC working on making it possible for a user to adopt a node by entering a password. Unfortunately, I can't for the life of me remember who it was. I saw this module come up in the tracker with one of the issues and thought it might fit in here.

My use case is that I am planning on having a business directory. I will be initially entering businesses myself. I'd like to notify the business that they have been added and give them a password whereby they can assume ownership of the node to make any changes they desire. I'd rather not have to have them email me back and me manually go in and change the author, so having this automated by password would be really nice.

Extra points if the module could create a password for the node for me so I don't have to think of one each time. :)

Thanks,

Michelle

Comments

Christefano-oldaccount’s picture

Christefano-oldaccount commented

I'm all +1 over this. Great idea!

functions’s picture

functions commented

This sounds great! Any word?

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Active » Closed (won't fix)

No answer in well over a year. I'm assuming the maintainer isn't interested.

Michelle

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Closed (won't fix) » Active

New maintainer, new hope. Re-activating and crossing my fingers. :)

Michelle

VenDG’s picture

VenDG commented

subscribing

sabrawy’s picture

sabrawy commented

+sub im trying to understand the idea

if you mean a password of the user
what will happened if password match 2 users or more.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Version: 5.x-1.0 » 6.x-1.0

No, password per node. Basically an access code. So I add a listing for ABC Business and send them an email with a password of hfkdjshjkd and a link. They create a user account, go to the link, type in the code, and the node gets assigned to them.

It's been nearly 4 years since I asked for this and I could still use it but I've given up hope. Eventually I'll just write something myself.

Michelle

sabrawy’s picture

sabrawy commented

sorry but i need to understand more why using password to do it , i think the node ID is enough for me.

what i have understood you need a node id filter to just adopt the node for a new user.
i'm developing a condition filter for node adoption for now i almost done with assigned terms for the node filter, and the content type. maybe in future im going to add node id filter.

for more information about the new enhancements that i'm developing please see this node
http://drupal.org/node/1000644

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

The password is so XYZ Company can't go in and take over ABC Company's listing.

I didn't realize you were taking this module over. If you do and this doesn't fit in, feel free to won't fix it. I've learned a lot more about writing Drupal modules since I filed this issue and can just write something custom.

Michelle

sabrawy’s picture

sabrawy commented

why won't fixed? i'm not asking some one for features i'm doing it.

in this case i will post it as a new module under another name.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

What I am asking for here is pushing the scope of this module. Since I don't need most of what this module does, if I write something, I will just write something custom. Which means it's only going to be added to this module if whoever maintains the module wants to write it. If that's not going to happen, this can be won't fix'd. If you would like to write it, that's great. All I'm saying is that I filed this feature request nearly 4 years ago and I don't think it's going to happen.

If you are writing features for this module, just file a webmaster's issue to take it over. There's no need to make a new module when this one looks to be abandoned anyway.

Michelle

caligan’s picture

caligan commented
Version: 6.x-1.0 » 7.x-1.x-dev

Sounds handy to me - I'll think about how to do it. Maybe pulling in http://drupal.org/project/genpass (or using it as a jumping-off point) as a dependency, though it has no 7.x yet.

What are the particulars of the way your use-case differs from, say, creating a user login, assigning the node or nodes to it, and then emailing the password to the would-be owner? Is it that you want to be sure the nodes stay assigned to their original owner if the new one never shows up to claim them, or--?

caligan’s picture

caligan commented
Status: Active » Closed (won't fix)

I'm opting out of adding this, since the module concept is really just designating who gets control of a particular removed/blocked author's nodes. The feature requested can be handled natively by creating a user account for which to send the login information, and assigning the new content to that user as author. Use cases where that approach doesn't work are (in my opinion) a bit specific for this module.