Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Guest Checkout #127

Closed
pilot opened this issue Jun 3, 2013 · 10 comments
Closed

[RFC] Guest Checkout #127

pilot opened this issue Jun 3, 2013 · 10 comments
Labels
Feature New feature proposals.

Comments

@pilot
Copy link
Contributor

pilot commented Jun 3, 2013

Goal to give a user choice to have a regular registration to suppose that the user come back in future or a put a quick order with a minimal required (configured) steps.

image

@umpirsky
Copy link
Contributor

umpirsky commented Jun 3, 2013

#90

@ghost
Copy link

ghost commented Jun 13, 2013

@pilot : i'm wondering if that should just be the the default behaviour. Is there any reason for it not to be?

@pilot
Copy link
Contributor Author

pilot commented Jun 13, 2013

@jrobeson any reasons, just should be by default :)

@sargath
Copy link

sargath commented Jun 13, 2013

i think that should be optional thing to enable guest checkout

@pilot
Copy link
Contributor Author

pilot commented Jun 13, 2013

yes, this feature should be enable/disable in admin panel

@ghost
Copy link

ghost commented Jun 13, 2013

with guest checkouts on products that require shipping addresses, you end up requiring the same information guest checkout or not. So a guest checkout isn't really all that guesty imo for most people.

@marcospassos
Copy link
Contributor

Where are the technical specifications of this RFC? This is just a feature suggestion, not a RFC.

@pjedrzejewski can you share how do you imagine this implementation?

@pjedrzejewski
Copy link
Member

I'd leave this for later... we all know how tricky it can become to handle that. If we want this implemented, we need a very clean solution.

@marcospassos
Copy link
Contributor

It can be done splitting the model User into User + Costumer and using NullObject's.

@stloyd
Copy link
Contributor

stloyd commented Oct 23, 2013

Closing as duplicate of #90.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature proposals.
Projects
None yet
Development

No branches or pull requests

6 participants