[Melinda Dean]

Hi Nico,
Again thanks so much for your help and swift responses. I didn’t realise how complicated a case it would be when I started integrating it, and I still have a few challenges ahead to deal with…but that’s beside the point. Thanks again! Will definitely keep the plugin in mind for future projects that aren’t quite so one-off / randomly complicated.
Cheers,
Min

[Melinda Dean]

Hey Nico, thanks for the prompt reply. For the limiting of tickets purchased, the radio button idea is just what I need. I’ll consult the themer’s guide, should be able to figure it out. Thanks!

As for the variations, I think it’s where it might get a bit trickier. The site I’m building is still local or I’d send a URL. It’s for a book launch, and the tickets come with a choice of book, which needs to be specified at point of sale. There are also two sessions, due to the early numbers that have been calculated, and it would be useful to be able to differentiate between the two (however, they need to remain as the one product, as we need people to choose between the sessions, not select to come to both).
I’ll post some screenshots instead, on how I was intending to sell the tickets through woocommerce:
http://obernewtyn.net/media/red-queen/book.png
http://obernewtyn.net/media/red-queen/type.png
http://obernewtyn.net/media/red-queen/session.png
Selling them this way makes the front end experience exactly what we want, but it leaves the process of issuing etickets and marking off attendees as they arrive entirely to us and I was hoping to be able to expedite that portion using the ticket addon.

When I started creating the tickets through an event (as opposed to creating the event as a product, just through woocommerce), after adding the plugin, I noticed that it would result in a huge list of ticket types, books and sessions. There are 18 variations in total.
http://obernewtyn.net/media/red-queen/tickets.png
This is when I thought (/noticed) that as each ticket was created, a corresponding “product” was created in woocommerce, so perhaps it would just be a matter of changing the display to catalogue/search, and changing the created product from simple to variable. When I did, what I mentioned initially happened; the “add to cart” changed to “select options”, but clicking through to the product went to the main event page with all the ticket options.

This is getting wordy…sorry. TL;DR: I’d love for a way to be able to retain the select box style used within the woocommerce variable product (using attributes, perhaps? Familiar only with the woocommerce context of attributes, though, not the event calendar context), while still use the e-ticket issuing and attendance list/check off of the ticketing plugin. Not sure if it’s possible, just outlining the ideal for our scenario.

Failing that I’m thinking that perhaps it would be better, in this instance, to revert simply to woocommerce, and find another way to manage the issuing of etickets.

Thanks for any thoughts/help on the matter. I know it’s a bit of a curly one, and if I had read more of the documentation prior to buying the plugin I may have read what I needed to find out whether it was possible or not, but as well as trying to run a web development business I’m a mother of a (relentless) 9 month old so my development time is limited.
Cheers,
Min

[Author]

Posts