Posted by uberKeith on October 14, 2010 at 7:57pm
10 followers
Jump to:
| Project: | Signup Integration for Ubercart |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Issue Summary
Hello Folks,
Is there a way to skip asking for attendee's e-mail and go straight to a form of required information? I'm building an e-commerce site for a dance school, the attendees are little kids who would not have profiles on the site, and I need the parent fill out "name of child, gender, age, legal guardian information". Is this the right module and way to do this?
THANKS for any help or pointers!
Comments
#1
You are asking people to signup but not create a profile. Someone correct me if I'm wrong, but this is not supported. When you are asked for a email address, that email address is tide to an existing account or one that is created.
How would the information be stored in the database, if it is not tide to a user, in a one-to-one relationship?
This would be a great feature to have in the future. I'm changing the status to postponed.
The only way I could think this would happen now, would be to use content_multigroup.module (part of CCK-6--3). This way a parent (node) could have multiple children (cck multigroup) and each child would have a name, gender,age and legal guardian. There is still flaws in this setup
#2
This is interesting. Our need would be to allow the one user whose profile is created with the provided email address to purchase several tickets for his/her friends, but no profiles need to created for this persons friends
Any ideas on how to do this?
Thanks
#3
Again this is the same program. There is no way in doing this. How would you store this information in the database if its not tied to a user. A user with an email address.
#4
I put some more thought into this. And I think something could be created to do this. There would have to be some custom coding done.
So take the Dance School as an example. You would have a node called Dance Program and another node called Kid. Dance Program would have a Title, ie Fall 2010 Junior Class, and some other custom cck fields (instructor, start time, finish time, etc). Kid would probably have a autonodetitle, first name last name, etc. You would setup Drupal so that user can signup to Dance Program nodes. This is already possible. If someone signups 5 Dance Program, then they could create 5 kids nodes. Theses nodes would be node reference to the Dance Program, and User Reference to the purchaser automatically.
This way there would be no extra table in the database. I know there are flaws with this new system. This is just a start.
#5
Istryker, am I mistaken or there is an option to turn off "Attendee Signup Information" request on admin/store/settings/checkout/edit/panes?
Forcing users to insert dozen fake e-mails to buy multiple signups at once is unprofessional and limits the applicability of the useful Ubercart integration.
If the need for an e-mail is just technical, not factual, i. e. the site admin knows that most users won't care to have an account, let's limit the necessary e-mail to the buying person. Allow to skip request for other people's e-mail, instead record the placeholder e-mail automatically created by Ubercart.
#6
My last comment was about something that could be created/extended for this module. There is no turn off "Attendee Signup Information" yet.
#7
Thank you iStryker! This sounds really promising! I kind of follow.....but.....how are the "Kid" nodes associated with the Dance Program node, and how doe the user create them? Is that where the custom programming is involved, or could you give me a little more instruction on how to arrange this?
Thanks!
#8
@uberKeith, What I have suggested is just an idea of how I think this module could be extended. There will be alot of custom coding needed. Code that would associated a signup node (my example Dance Program) with another node type (my example Kid).
Another way to look at it is: You signup (buy) X numbers, which allows you to create X nodes of another type. All in the checkout process. For tracking, the newly created node(s) will be node reference to the signup node, and a user reference to the creator.
There might already be another module that has this functionality. The functionality of when a user buys X products, they are allowed you to create X nodes. The difference is there are more steps when you sign up vs buying.
#9
Anyway, the option to turn off e-mail request is where I mentioned: admin/store/settings/checkout/edit/panes
#10
@Als, the question is not to turn off e-mail request. Its to signup people that will not have email addresses. The problem is every user needs an email address.
#11
I think of swaping en email adress for an openid identifier. With some core changes and notifications disablers it should be possible.
#12
Subscribing. Need this exact functionality for a project we're working on. We can contribute development resources -- will review your approach next week and see if we can implement something...
#13
The issue is not how do you sign up a "user" without an email address. The issue is to allow a "user" to purchase multiple quantities of a product and fill in the attendee name for each.
Sometimes the simple solution is the best one.
My 2 cents...
#14
Istryker, but you already get that parameter (e-mail) from Ubercart:
- User is logged in: UC reminds you the associated e-mail on Checkout page
- User is not logged in: UC asks for an e-mail on Checkout page
In both cases, it makes total sense for Signup to use that e-mail:
- If I am subscribing myself, of course that will be the right address.
- If I am subscribing a dozen people, there must be a reason why they do not subscribe on their own. The module should tie all subscriptions to the user that is checking out.
#15
subscribe.
Also need this functionality. We have wrestled this issue on and off now for various scenarios and the reality is there are multiple use-cases for a single user determining the attendance for multiple attendees. Any event planner can attest to this.
Maybe this go-round results in a reasonable resolution .. tia
#16
We need this functionality for parents who want to register their many young children for events. Most users in the 2-5 year old age range have a parent who has an email address, but don't have their own email address to register. Perhaps finding a way to give a single user (parent) with an email address the option to register other users (children) who can count against the limit on total signups.
#17
This sounds like a very good idea, I would have use for this
#18
Hi,
We have implemented something that supports this, though we are still hitting a bunch of issues...
Our use case was a convention registration site, where users would sign themselves up for the main convention and a bunch of optional events, and be able to mark whether their spouse or children were coming, too.
Our approach was to create a new content type called "signup profile", and add it to a node checkout form using the Node Widget module. We had 3 different node reference widgets embedded on the page -- one for the attendee, one for the spouse, and one for kids. This created a bunch of signup profiles owned by the user.
Then, we modified uc_signup to basically show on the first page of the checkout, a checkbox for each signup profile "owned" by the current user for each signup-enabled event in the cart. We suppressed the second page where profile details were confirmed or created, and skipped straight to the cart checkout page. We ignored the qty field for each of the signup products in the cart, recalculating qty based on the number of checkboxes on the first page.
We put the signup nid, profile type, and title in the "data" field for the signup, so we can make it visible in signup views.
So far, so good. I'm not sure exactly how we'll handle the next event, to allow re-using existing signups. We don't necessarily have a good way to administratively add signups properly and get the data we need for some other views -- and this took a fair amount of custom code to do.
And of course later the client asked for one event to get handled differently -- more like the original uc_signup behavior to add other users with email addresses to an event. And we struggle with orders made on behalf of another person (having a secretary sign up multiple people for the convention, for example).
So I don't think our code is generally useful, but we have identified some key things that need to be considered to allow signups without an email account (and also #628068: Single Email address, multiple unique profiles).
#19
@18 This is an example of something I've looked to accomplish before, as well as having arrived at similar solution(s). ... problems I've seen as well. Seems a more elegant solution is to be had, somehow.
#20
Just to add to this ongoing discussion:
In our case, we just simply don't allow users to modify signups at all, and disabled the user account confirmation email.
This way we still use the user system, and users can still get in via forgot password.
However this seems like it would only work for sites built around the event itself.