I have tried many different ways to achieve this but without success. I hope I can get some help for the following workflow:
1. User clicks on create new node link, e.g. node/add/sometype
2. User fills up the fields and click Save
3. System checks if user is currently logged in, if yes, save the node
3a. If user is not logged in, redirect to login page; user logs in, save the node
3b. If user doesn't have account, click on register to create account, then the node is saved
The bottom line is, I want to let users to be able to create new node without prompting them to register/login first. By getting them to go through the node creation process first, is more likely to increase the chances of them register/login (since they have spent time fill up the fields, they might as well go through the registration too)
If anyone has sussessfully implemented the above, please be kind to share.
Comments
Comment #1
wondertum commentedSubscribing.
Comment #2
benone commented+1
Comment #3
Remon commentedsubscribe
Comment #4
mitchell commentedThis seems like a common issue, so we need a documentation page as well. See this for now, #786436-3: publish node after confirmation by mail.
Comment #6
chus69 commentedlooking for the same solution
Comment #7
mitchell commentedComment #8
mitchell commentedWaiting for review of my comment in #3 and #786436-3: publish node after confirmation by mail? (I tend to mark support requests as fixed quickly because there are so many to contend with, but feedback would be great in verifying a solution for this.)
Comment #9
davedg629 commentedSubscribe.
Would love to find an answer to this. I'm going to play around with the rules module and see if I can figure something out.
If anyone has an answer or a link to an answer that would be awesome. It is important that the user is able to fill out the entire node form, hit save, and then be prompted to login or register. This is the functionality that many websites are looking for to entice users to sign up.
Thanks maintainer(s)!
Comment #10
zualas commentedThe Inline_registration module has severe limitations:
- It does not play well with multistep forms, will always be displayed on the first one
- It doesn't support the custom features that other modules can provide, e.g. Logintoboggan
- If the user wants to login instead of registering, all his form data will be lost
So hopefully this can be solved somehow by Rules...
Comment #11
jasom commentedAny progres?
I want to add to #9, that user should be able to define his password and throught login toboggan received validation email.
Comment #13
syturvy commentedSubscribing
Comment #14
g.paluch commentedSubscribing
Comment #15
jasom commentedI have started using this module https://drupal.org/project/anon_nodecreate
Comment #16
itangalo commentedIt is possible to use Rules to automatically create a user account and assign it as author to the node being saved, but it is as far as I know possible to halt the saving of the node, have the user create an account manually, and then have the node saved and set with the new account as author.
This questions seems to crop up over and over again. I've suggested a few different approaches over here: http://drupal.org/node/1110970#comment-4283154
As the comment says, the tricky part is that if the node is saved, it has user 0 (anonymous users) as author -- and then it becomes really difficult to know which node should be owned by the new user.
A compromise would be to automatically create a new account, and redirect the user to her new account edit page once the node is created -- to set user name, password and e-mail address.
Comment #17
itangalo commentedI'm changing this to 'wont fix', since it involves features that Rules doesn't have. (It could be reopened again as a feature request, but I think it's better to have a new issue for that.)
By the way: I just posted a stub for a mad approach to solving this problem for real, over at the discussion linked to above.
Comment #18
WtheM commentedI am looking for same solution.
My idea is, inspired by tests and observations, to simply create special Field Module for "User E-mail" which will be added in node creation form. This solves the problem with multistep forms as you can place this Field at any position. So after node creation, Drupal creates account for the user with the given E-mail and sends a confirmation link (same user creation with email confirmation) to this email. After confirming the email, user will be redirected to a page where he can set up own password.
Comment #19
zualas commentedThis can be accomplished with Rules. I have written a rough instruction here at http://drupal.org/node/1281466. If it is too vague, Drupal Commerce in Drupal 7 has the exact same rule that you can copy.