Support

May 2, 2013 at 2:17 am

Hi,
i’ve bought event espresso shortly and now trying to setup the “standard case” for music festivals.
with standard case i mean:
– there is an event over more then one day
– there are different ticket types with different access types (tickets with access for one special day, tickets with access for all days etc.)
– the customer can buy more then 1 ticket. even not every ticket must be personalised. the attendee information is only required for payment handling.

what i’ve done until now:
every day is an single event. so i can sell seperate tickets for each day.
creating an single event with just different ticket prices doesnt fit my requirement. because i cant see any posibility to assign the ticket price to especially one or more days.
or is there better solution?

my current problems are:
1. if the customer buys more then one ticket (group reg. is activated) only one ticket will be generated. on the ticket itself he can see the quantity (and so it could printed more then one time), but they all have the same qr code.
for me thats no acceptable solution. let me explain it on 2 common cases:
– one person buys 3 tickets. the 3 persons are not visiting the festival togehter. person one is the first visitor. he checks in. later he leaves the festival and a short time later he checks in again.
person 2 checks in. person 3 is coming at last and want to check in. he cant, because the qr code has been used for 3 times.
– one person buys 3 tickets. one for himself, 2 for selling. same szenario like in case 1. first person checks in, leaves and checks in again. so the 3rd person cant check in.
2. if more then one ticket will be bought, the customer should not have to give attendee information for each ticket.
3. the customer view should looks like:
event || price || qty
day 1 || 1,00 € || 0..20
day 2 || 2,00 € || 0..20
day 3 || 3,00 € || 0..20
allday|| 6,00 € || 0..20
qty should be a dropdown list.

bullet 2 and 3 should be possible i think. i have deep php/css/html knowledge and think i can create customized solution.
bullet 1 is a bit more tricky. its not a problem to show 3 links (depending on the qty) in the email. but for me its a must that every ticket has its own and unique qr code.
i’ve said that developing knowledge is available. however i want to keep event espresso updatable. so only customization by using the custom files is a acceptable way for me.

i hope u can give me some hints for setting up / customize event espresso for my case.

thanks in advance