We repeatedly create the same tickets over and over, with specific parameters.
i.e. multiple times/prices/specific days per event.
I know it would take a bit of work to add templated tickets, but this would be SO handy.
Is there a Github repo for pro features? Would I be able to make a pull request?
Joshua Dorenkamp
HI Joshua,
There’s no public Github repo for Pro unfortunately. However, I’m interested in what you mean by a “ticket template”. How might they be set up and used?
Stephen Harris
Totally understandable on the Pro repo. And it’s definitely worth paying for. Just looking for a way to give back to this AMAZING plugin. Thanks for all your hard work.
In our case, we are working with a theater who has preset prices per day/showing. Wednesday Matinee – $36, Wednesday Evening – $42, Friday Evening – $47 etc. We are having to input 7 different tickets for each show, and the only frustrating part is having to reference the prices and make sure the names/spaces are consistent.
Ideally, I’d like to be able to have the ticket name as a dropdown, with preset prices. The sale portion would be able to handle price changes on the fly I think. Or, set this up like adding venues on the fly. Or maybe selecting a “ticket” from the drop down just prepopulates the price/spaces fields and they can be modified on the fly.
I think a custom post type might be overkill, but a possible solution. Might be better to set this up as a serialized EO-Setting, since there are only a name/price/space value.
You know the code better than I, but a simple serialized option value seems to be the best method I can see.
Thanks!
-
This reply was modified 10 years, 7 months ago by Joshua Dorenkamp.
Joshua Dorenkamp
Oh! The days are also preset per ticket (fx – every Wed for the length of the event schedule). But this seems like it may be a huge pain to add, or a little subjective for our case
Joshua Dorenkamp
Sorry Joshua,
This thread fell off my radar. However, you might want to see this thread, which I think comes very close to what you’re after.
The only problem is that whenever the dates change, (and when they are initially selected) you’ll want to update the tickets to reflect this. (There is a eventorganiser_update_ticket()
correspondings to eventorganiser_insert_ticket()
in includes/tickets.php
).
Stephen Harris
Great! Thanks, I think that will suffice for now.
Maybe one day I’ll find the time to dive further into the code and play around some more 😉
Thanks for your help Stephen!!
Joshua Dorenkamp