[Aleksey]

Hi!

Yesterday we published the automatic customer registration feature. Customers can now be registered on checkout. The documentation is here: http://lemonstandapp...r_registration/

Thank you

[Jez-Timms]

Brilliant feature - I think though for us plain old designers, some code samples of the best practice to implement these hidden fields correctly and the actual data fields in the billing partial would be of benefit.

[Aleksey]

Hi, Jez! Yes, I just added the code examples. I prepared them, but forgot to paste to the article. Thank you for letting me know.

[pmeissner]

Just a few quick questions. What if you wanted to implement this behavior.

During the guest checkout you have a button that says... "would you like to create an account?"

1. If they click it the form unhides (i'll use mootools) the password fields. And then they will be registered during checkout.
2. If they don't click the button no account is created.

In other words, creating an account during checkout is optional and based on them them setting a password.

Another (not creating a password) approach would be to have a select input for the guest to click. If they click it, an account is generated and a password change request is sent to their email. If the guest doesn't select the input no account is created.

[Aleksey]

Hi!

1. If they click it the form unhides (i'll use mootools) the password fields. And then they will be registered during checkout.
2. If they don't click the button no account is created.

You can manage the register_customer hidden field value with JavaScript. Set its value to 0 by default. If the customer clicks the button "would you like to create an account?" - change the field value to 1. You will need to assign some ID to the hidden field element and then use this ID:

$('register_customer').value = 1;

Thank you!

[pmeissner]

Great. Thanks Aleksey.