Adding to price
This topic contains 16 replies, has 2 voices, and was last updated by 
-
Posts
-
Karl,
Here’s an example of using a select for the tickets. This only works for non-recurring events or when selling ‘by series’, not ‘by date’: https://gist.github.com/stephenharris/50a90b6b1a766c042d6a
It’s not a very polished solution, just a proof of concept and it works fine with the attendee questions.
However, I think the issue you’re having is that you want different questions based on the user’s selection. That would be tricky – attendee questions are just intended to be questions which are repeated for each ticket selected.
What you could do is just used standard booking fields and hide/show these based on the ticket ID selected.
Stephen Harris
Hey Stephan!
Just wanted to follow this up, telling you how i solved it in the end.
I ended up creating multiple fieldsets with input boxes and such, and hid them with css.
Than, based on what ticket is choosen, i show that amount of fieldsets.
This is by no mean an perfect solution, but atleast i got it to work the way i intended (for the end user, that is).
It now saves all the fields in the database, even though the user might only have filled a couple of them.Thanks for the support throughout this project!
Karl Lettenström