Auto registration workflow

I tried to associate the new user experience issue with the user subsystem but got an error.

Related issue: allow for 'buy then register' e-commerce situation.
The solution should also allow for that functionality.
Reference: http://drupal.org/node/92869

Please tell me how do you recommend me to advance it - Can you give tips where are the most appropriate hooks? do you have time to implement it? Or should I create a reverse bountry? Any help will be appriciated and will benefit the whole of drupal.

Updates:

This module shoulb be a separate module, not an extension to LoginToboggan.
(reference: http://drupal.org/node/100376).

The budget is no longer limited to 200$ - I have found a sponser - please send your price offer
(reference project request: http://drupal.org/node/101151).

To clarify the previous point: This module should be a separate module, yet it should preferablly be an addon module to LoginTobbogan and integrate well with the LoginToboggan functionality.

Updates:

Viral registation workflow should be implemented as a separate module, hooking into the logintoboggan login/registration process.

When an anonymous user submits a node or comment, it is created but
in a special "pending user registration" state. When the user then
registers and successfully validates their registration, the node or
comment transitions to being treated like a submission by any other
registered user: posted, moderated, whatever.

The registration / login fields should appear in a separate tab, only for users who are not logged in (We will need multipart forms). The data should not saved in the database until the user fills the registration details.

The module should provide an API in order to allow presenting the login/registration info in additional, non-node forms such as petition filling and contact form filling.

Thanks for your feedback, daniel. The links helps alot.

Auto generating the user's login name and password should be a good idea.

I feel that user's email should still be confirmed twice - like in LoginToboggan. Later the second field can be auto-expanded when the user fills the first email address but this is not currently required.

No multi-page forms for the first version. My current need is for a Drupal 4.7 site, and multi-page is actually supported only from Drupal 5.

The form is saved when the user fills the details, exactly as it's done in a regular post. The data is saved in pending state, until the user is validated.

All profile fields makred as 'for the user registration form' should be displayed. Those fields should be webmaster-defined. This should enable webmaster to ask a user for his/her real name.

Regarding your idea to save the shopping cart contents:

The current shopping cart mechanism uses browser sessions. Sessions expires when the browser crashes, and all data is lost. It happened to me many times.

There are two alternatives to save shopping carts for unregistered users:

1. Save session details as a cookie. This can be a separate feature treated by the autosave module. However, this solution is not my favorite since it has privacy and security implications.
2. Allow the user to register. Add a "Save" button below the shopping cart, next to an email field. The "Save" button will register the user and save the cart. For users to do it, registration should be super-easy. Your suggested link is the answer.

My chosen solution: The auto-registration API should enable shopping cart writers to add a "Save" button to the shopping cart. This botton would enable the user to register/login. Then, the cart shold be saved under his/her name.

Let me know if I can help in any way.

You have already gave important feedback on the suggested features. Please continue.

There are many ways other in which you can help:
Are you ready to help testing this module?
Are you ready to define which API will be needed by the shoppping cart?
Will you help integrating the API provided by this module, with the e-commerce shopping cart?

Thanks in advance,

Amnon

Attached: UI Design Doc

Thanks, Daniel

I don't object putting it into LoginToboggan - on the contrary, I've already opened it as a logintoboggan issue - but I got a "won't fix" response, so we will have to push it alittle harder after we release the actual code.

Your UI sketch is fantastic - it says it all:

1. Indeed - There is no need for confirmation email - the email may appear in the confirmation page where the user may be given a chance to modify it if there were errors
2. Indeed, there is no need for a signup form for registered users in the right side. If the site member forgot to login and tried to enter his email - he will be prompted for his password (via Javascript or in the second, confirmation page).

Did you suggest to change the module name from 'autoreg' to 'Briefly'? Because when you change the message subject you've changed the title of the whole issue. Anyway it's a good name if we still need a separate module.

Updated spec

Returning the name to the previous form.

Would love to hear about any progress.

For the moment, I am using loginToboggan's auto-registration feature and adding the following code (or similar) to the argument handling code of each relevant view:

global $user;
if ($user->uid > 0 ) {
  $view->page_header .= "<a href='/node/add/biz'>To add a new business press here</a>. ";
}
else {
  $view->page_header .= "To add a new business please <a href='/user/login?destination=/node/add/biz'>login</a> or <a href='/user/register?destination=/node/add/biz'>register</a>. ";
}

A similar code may be added as a block above each node add form.