1. Extend the feature of Commerce Checkout Login This module extends that pane to provide an inline registration form via AJAX. If the e-mail address, an anonymous user enters is not associated with any user account, then the checkout form will expand with a username , password textfield and sign up button for immediate registration and login.
Requirements
Drupal Commerce currently depends on Drupal 7 (>= 7.15) with module: Commerce Checkout Login
Sponsored by DrupalGeeks.org.
2. Click to see Commerce Checkout Register project page
3. Copy the link git clone http://git.drupal.org/sandbox/purushothaman.drupalgeeks/2115745.git commerce_checkout_register
Updates:
Manual reviews of other projects:
https://drupal.org/comment/8342881#comment-8342881
Other manual reviews:
https://drupal.org/comment/8347611#comment-8347611
https://drupal.org/comment/8384081#comment-8384081
Thanks,
Purushothaman
Comments
Comment #1
vijaycs85Sounds like another good module to solve login issue on a shopping flow. Thanks for working on this. Here is some review comments:
1. Looks like you are working on master (default) branch. We have to use version specific branch. Please check [#1015226]
2. Seems we have only .info file. As per [#1011698] the project application should be created once we have working application in place. So please commit your module details and change the status to 'Needs review'
Comment #2
klausiLooks like this needs work then? See https://drupal.org/node/532400
Comment #3
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi,
I have made the changes that you have pointed out
1. I have created a new branch for version specific.
2. Working application file (. Module file) is added.
Thanks
Purushothaman
Comment #4
vijaycs85Thanks for your updates @Purushothaman C... Some more reviews:
1. http://drupalcode.org/sandbox/purushothaman.drupalgeeks/2115745.git/blob... - This will be added by ci script, you can remove it.
2. Few comments from automation tool: http://pareview.sh/pareview/httpgitdrupalorgsandboxpurushothamandrupalge...
Comment #5
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi,
Comment#4 review changes are updated
Thanks
Comment #6
PA robot CreditAttribution: PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #6.0
PA robot CreditAttribution: PA robot commentedUpdated issue summary.
Comment #7
anemirovsky CreditAttribution: anemirovsky commentedhttp://pareview.sh/pareview/httpgitdrupalorgsandboxpurushothamandrupalge... is still reporting an issue with this module's branch setup:
Other than that, I've reviewed the code and it looks okay. Seems to be using the API correctly.
Comment #8
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi,
Thanks for reviewing my codes and I have fixed the branch related issues and other issues as mentioned in Comment#7.
Thanks
Comment #9
alex_sansom CreditAttribution: alex_sansom commentedHi Purushothaman Chinnadurai,
I've just installed your module and it does exactly as you've described. I found a couple of minor issues though:
All looks good to me apart from the above.
Comment #10
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi,
I have updated and moved the code changes for the listed issues on comment#9.
Comment #11
alex_sansom CreditAttribution: alex_sansom commentedYep, looks good to me.
Comment #12
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedComment #13
klausiremoving review bonus tag, you did not do all manual reviews, you just repeated the output of an automated review tool. Make sure to read through the source code of the other projects and provide your feedback.
Comment #14
xqus CreditAttribution: xqus commentedI have reviewed your module, and I have a few concerns. No offense setting this to "needs work". If you can answer my concern, feel free to set it back to "need review".
commerce_checkout_register_checkout_form_submit() register users without checking if the site administrator requires e-mail verification or even allows registrations without approval.
I think, even if you might loose functionality if the site is configured not to allow registration without admin approval that you should try to call user_register_submit() from commerce_checkout_register_checkout_form_submit() to allow the normal registration process to do it's job and send e-mail and so on.
Also, I don't see any e-mail validation at all? Does that happen somewhere else in the commerce system?
Comment #15
Calincik CreditAttribution: Calincik commentedHi everyone ! I have a question. How do I add custom fields in to registration form ? I need it to save the information from the input in the admin/people section. Any thoughts will be appreciated :)
Comment #16
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi xqus,
Thanks for reviewing my module,
Answer to the question,
- This module is basically designed for immediate registration and login on the checkout page where there won't be 2 to 3 steps of email verification required and a user doesn't like to have verification on the checkout page. The module doesn't do the normal registration.
- I had a design plan to cover/work with the site functionality, but again it takes 2 to 3 steps of registration as like of normal registration so I redesigned in such a way, when a user in the checkout page where site request the anonymous user to do immediate register and login to the site. With this feature, an anonymous user can register and login on the checkout page itself.
- An anonymous user who wants to complete the checkout will always give a valid email address and email verification will take 2 more steps which are again user doesn't like it so I thought of no email verification.
If you understand the logic of the module designed and feel agree with my answers, Please feel free to set it back to "need review"
Thanks
Purushothaman
Comment #17
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi Calincik,
Reason for not have custom fields on the registration form on the checkout page,
1 - User can update the custom fields in the user profile edit page.
2 - Having custom fields on the registration form of the checkout page, users might feel bored to update the details or may cancel the order for asking him to enter so many details. So that's the reason to have a basic registration form on the checkout page.
Thanks
Comment #18
xqus CreditAttribution: xqus commented@Purushothaman Chinnadurai I understand why the module is designed this way, and how that works best for the user/site. My question is really this:
If an admin has configured the site to require e-mail validation i don't believe your module should override this setting. At least not without waring.
If the administrator configures the site with no e-mail verification required, then your module will work as expected, even if it uses user_register_submit(), right?
If that is the case I would suggest you use that and rather instruct admins to disable email verification when enabling you module.
If that will not work for you, maybe a entry on the status report page reminding admins that user can register without e-mail verification. You can show this message depending on the site configuration.
Comment #19
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commented@xqus,
Thanks for your suggestions and I understand your question.
A few comments are,
1 - If an admin has configured the site to require email validation I don't believe your module should override this setting. At least not without warning.
2 - If the administrator configures the site with no email verification required, then your module will work as expected, even if it uses user_register_submit(), right?
Instructing the admin to make setting changes is no use if I can't able to use user_register_submit. I'll add code for admin showing the registration process on the checkout page in the status report page.
Thanks
Comment #20
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedComment #21
klausiThis sounds like a feature that should live directly in the existing commerce_checkout_login project. Module duplication and fragmentation is a huge problem on drupal.org and we prefer collaboration over competition. Please open an issue in the commerce_checkout_login issue queue to discuss what you need. You should also get in contact with the maintainer(s) to offer your help to move the project forward. If you cannot reach the maintainer(s) please follow the abandoned project process.
If that fails for whatever reason please get back to us and set this back to "needs review".
Comment #22
Purushothaman Chinnadurai - Drupal Geeks CreditAttribution: Purushothaman Chinnadurai - Drupal Geeks commentedHi klausi,
Thanks for guiding me.
As per your suggestion, I have created an issue with the maintainer of commerce checkout login (https://drupal.org/node/2175887) regarding to include the features of the commerce checkout register sandbox module (https://drupal.org/sandbox/purushothaman.drupalgeeks/2115745). But it doesn't work well.
I'm getting an issue for release of the module from some of the users (https://drupal.org/node/2194669). So I just think and made a change in the status.
Please kindly guide me. Thanks for your support.
Comment #23
klausiWhat do you mean by it does not work well? If you cannot reach the maintainer(s) please follow the abandoned project process.
EDIT: I think it would be helpful if you could create a patch against the commerce_checkout_login module.
Comment #24
PA robot CreditAttribution: PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.