Closed (fixed)
Project:
Signup Integration for Ubercart
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Jun 2009 at 19:14 UTC
Updated:
5 Aug 2009 at 15:40 UTC
Looks like we've been working on similar projects. I've attached the SignupCart module which I was close to submitting when I discovered the work here.
SignupCart is fully functional and includes full admin settings, integration with Signup Status, and employs the UC Cart Links module in a unique way that solved a few of the problems I faced in development. I've commented the code heavily, and it comes with a README.txt that's up to date for the most part.
I'm submitting this here so we can evaluate whether our two projects ought to be combined.
| Comment | File | Size | Author |
|---|---|---|---|
| signupcart.tar_.gz | 6.55 KB | mlsamuelson |
Comments
Comment #1
ezra-g commentedI took a look at this and mlsamuelson and I discussed his module briefly in IRC, and I expect to review it more thoroughly over the next two weeks.
Comment #2
socialnicheguru commentedwill this handle rsvp integration also?
Chris
Comment #3
socialnicheguru commentedcan I use this for anonymous signups? is there a config that would let me?
I have lots of anonymous people signing up for events.
i would like to capture their information.
If you use signup then uc_node_checkout is not needed, right?
Can I access signup information for a user in a view?
Thanks,
Chris
Comment #4
mlsamuelson commented@activelyOUT
SignupCart does not provide rsvp integration.
Anonymous signups are problematic since Ubercart likes users to have accounts. It's been a while since I worked through those details, but if I recall correctly, I think Ubercart creates a user account (or requires the user to) if the user is anonymous. In the README.txt it describes turning off signups for anonymous users to avoid problematic workflow, but that may have just been for my requirements. It works both ways, actually. Try it and find out what works for you.
Signup is views enabled, and actually, once this is set up, you can view the signups via tabs on the node. I'd recommend looking into the Signup settings, and giving it all a try.
Comment #5
socialnicheguru commentedThanks.
I also wanted to touch base on the idea of mutlple signups. If i goto an event and I signup, can I only signup one at a time?
also is stock integrated with signup total? which will be obeyed if they are not the same value?
Thanks,
C
Comment #6
socialnicheguru commentedHi,
ok so I was having a hard time with this.
The cart is only activated for events that have a price associated with it otherwise it just goes to signup and skips the cart.
Can you confirm this?
I am using uc_free_order
Is there a way to have it go through the cart even if there is no cost?
Use case:
I want to use node_checkout to gather information about users. So I need all events to go through checkout.
i will also need to have anonymous users to sign in.
Thanks,
Chris
Comment #7
ezra-g commented@activelyOUT -- The development plan for this module includes capturing information about multiple users. We hope to have more progress next week, so please stay tuned.
Comment #8
jrglasgow commentedUbercart behaves like this:
If the user has no account it requires an e-mail address. Ubercart then creates and account for the user based on that e-mail address and associated the order with the new user, and notifies the new user of their account.
Comment #9
socialnicheguru commentedThe cart is only activated for events that have a price associated with it otherwise it just goes to signup and skips the cart.
Can you confirm this?
Comment #10
ezra-g commented@mlsamuelson: I wanted to fill you in on some of the plan for uc_signup development that I'm hoping to implement next week. Another database table will be added for storing the order ID and the signup ID, as well as whether it is a placeholder or temporary signup. That way, we can keep track of placeholder signups without using the uc_signup form_data array or overlapping with signup_status' functionality. This will also allow purchasers to fill in account and user profile information when purchasing multiple signups, since we know how many signups they purchased and how many have been set as permanent.
Comment #11
ezra-g commentedSince uc_signup is up to an alpha release and takes a fundamentally different approach to dealing with placeholder signups, I'm marking this as fixed. I'm pleased to see so much interest in this functionality and I'd love to collaborate on specific issues in the future!
Thanks,
Ezra
Comment #12
mlsamuelson commentedSounds like a plan, Ezra.
Due to project timelines on my current project involving SignupCart, I'm going to be running forward with it (though I don't know that I'll do a contrib release, since I don't want it to detract from attention uc_signup would otherwise get). At a future date (probably the next major Drupal update of the project in question) I'll be checking into whether we can switch over to uc_signup, so we can share efforts.
mlsamuelson