Module-idea: Password for creating and editing Node
Okay, for an upcoming site, i need a special feature:
A ('n anonymous) user can submit his e-mail-address. By the next cron, an email is sent to the emailaddy with a code(like a hash or something) or an url. With this he can create just ONE node and edit it later, if he wants.
I haven't found such a module yet and therefore i'm planning to write this.
What i'm asking for: Did i miss such a module? What do you think about this idea? Somebody whant to join?
best regards,
dunkelfuerst
Groups:
Login to post comments
Why not just use the email
Why not just use the email to track back the user as an input in the node create form, and once created the node send a token (hash, whatever) you were talking about to that email address? the user would use the hash to manage the node.. First operation: publish of course, that would reduce the spam (even if you set up some captcha).
This is a kind of 'lazy registration' (http://webjackalope.com/lazy-registration/) I would like to see in drupal.
Don't forget to take a look at http://drupal.org/project/session_api, it may help.
I'm not aware of other modules with this kind of functionality, but I suggest to do another search before starting.
Good luck!
Just made a little SOA of
Just made a little SOA of this, and I've found the following 'related' info:
I've found a list with related modules in g.d.o.
http://groups.drupal.org/node/21317
Also, interesting approaches will be:
http://drupal.org/project/node_expire
http://drupal.org/project/email_registration
But I would like to focus you on this:
http://agaric.com/note/registration-flow-let-people-register-or-log-whil...
Almost every existing initiative revolves around the fact that user should remain in the site (for a long time) and how to ease the registration process, while you want to create a kind of "temporary users with permissions to create a single node", right?
This could be done with some module tweaking for now, and some glue code to finish the result..
First task: if you have defined the content type, skip this, otherwise define the content type the anonymous user will be able to create.
First task: role configuration: create a role for your real registered users, as this "temporary users" will also be authenticated users. Just leave anonymous and authenticated to handle the temp. users and use a role to set the permissions of the real site users. Give permissions to anonymous user to create this content type, and permissions to authenticated users to edit and delete own nodes. Authenticated users will not be able to create a node, and each node created by an anonymous user will add a new temporary user to the user list, so in this case each user will be managing each own node.
Caveats here are the fact that users should be created with each new node, and they should able to publish/unpublish edit/delete their content. So..
Second task: users and nodes lifetime. It's clearly a requirement to have defined the way this temporary users and nodes should be purged. There are modules for that that can handle both Users lifetime and remove users's content.
So in the end (third task), the glue 'module' should include the email address in the node creation form, create a temporary user associated with the node on the content submit, and keep safe the "Publishing options" permissions and settings of each node. The rest of functionality can be achieved using existing modules.