I am trying to figure out how to create multiple ticket types for any one event.
use case 1. say someone wants to offer VIP passes
use case 2. some discount for an event if you buy before X days.

I'm completely willing to "split" the process, basically saying that I'd have multiple products/tickets attached to a node and they'd signup for the product (and not the node), but I don't know how to re-integrate the signup list for the whole node, and i don't know whether this is a foolhardy approach.

So the question is is uc_signup good/"prepared" for this type of functionality or would this require custom development?

any hints on how to proceed would be useful
(including saying "just use the COD module")

Comments

anschauung’s picture

Comment #1

anschauung commented

I've had pretty good results using UC Price Per Role, normal Ubercart Attributes, and sometimes a combination of the two.

There's an upper limit to how complex of a registration product you can make using these tools without tearing your hair out. But, for straightforward member/nonmember and normal/bonus registration types it's pretty straightforward.

bewhy’s picture

Comment #2

bewhy commented

Great suggestion. However, I need to alter this not according to the role of the purchaser of the ticket.

Now that you mention something like it, I'm thinking this may mean I have to look into incorporating product attributes and discounts . . .

ezra-g’s picture

Comment #3

ezra-g commented

Ideally, uc_signup would be extended to connect product attributes to signup statuses.

bewhy’s picture

Comment #4

bewhy commented

Thanks Ezra-g.

I haven't played with attributes yet, and it seems from your comment that they aren't yet made to play nice.

. . . any timeframe on 'ideally' . . . haha!

Anyhoo, I just found and am going to look into using uc_subproduct to see if/how it scratches my itch. I'll report back what I find.

ezra-g’s picture

Comment #5

ezra-g commented
Title: Multiple Ticket types » Multiple Ticket types/ Attributes per signup for a product
bewhy’s picture

Comment #6

bewhy commented

In playing around with Attribute (which is kinda cool in itself), it seems that we'd have to link each signup user with an attribute/option. In my little test there wasn't a clear way to select which ticket went with what option. We'd have to set up a pane to allow the user to select which attributes they want for each ticket.

And it would be nice to hide the 'cost' and 'weight' attributes when editing an event attribute