Two different prices for one ticket

[james3]

I've had a look and can't see this issue coming up before.

Can we have different prices (e.g. adult/child) for a single ticket with a single maximum number of tickets across both prices?

Thanks

[discoverRG]

Agreed - this option would be great to have!

[samholford]

Currently, the revenue summary would have a problem with multiple ticket prices, as it sums the sold tickets and compares them to what was actually paid. The only purpose of this that I'm aware of is error tracking, but seems to be more trouble than it's worth (excuse me if I'm wrong). It stops you being able to change ticket prices after one has been sold and also causes problems if you delete coupons after it has been used. I'd like to see a move towards tickets being more independent. In addition to multiple prices, it would be nice to be able to change the price after selling and also set a unique currency. Personally, I would even have a use to be able to assign different PayPal accounts to tickets.

Perhaps a move could be made to freeing up these current limitations. In the current setup tab, a default event name, currency and PayPal account could be set, with the option to override these on a per-ticket basis. I don't think the front-end simplicity would suffer from doing this.

[discoverRG]

It would also be nice to be able to categorize the tickets so that, for example, you could display all of the tickets for Category 1 on one page, and all of the tickets for Category 2 on another page.

I'm not a PHP developer (so correct me if I'm wrong), but it seems like this should be a fairly simple thing to do - the tickets would just need a category parameter, and then they could be called within the shortcode, if desired. For example,

[camptix category="category1"]

[kovshenin]

@samholford yes, the revenue report is currently very fragile and sensitive to any pricing changes, etc. That's why we disallow changing the price after at least one ticket has been sold. We're thinking of other ways of doing this while maintaining consistency.

@discoverRG we're working towards something like that. The problem is not assigning taxonomy to tickets or querying them afterwards, but the fact that there will be more than one ticketing page, and right now that causes a lot of weirdness -- you can be redirected to a totally different ticketing page after a successful transaction. We're working towards fixing that.

[frederickandersen]

How's it going with developing this feature into the plugin? I'm really looking forward to seeing it implemented.

Thanks for a great plugin, Frederick Andersen