[mellowvision]

thanks for responding, I have carefully reviewed the themer’s guide before starting this thread. If you look, it does not refer to the the-events-calendar/views/tickets/email.php anywhere. The problem was finding the actual file, since I expected it to be within the wootickets plugin, not in the-events-calendar. I’ve searched fairly carefully, and haven’t found documentation that discusses the location of the email ticket template. Anyway, glad to know where it is now, so thanks for that.

[mellowvision]

Hi Kelly, thanks for the reply. At this point we’ve dedicated too much time to configuring TEC, and are committed to using it for this site launch. The site is for a small community art studio, so the development budget is really limited. The recurrence is really just one issue that is a hinderance to us, but we knew that going into this and chose to use TEC + woo + wooTickets as it’s Woo’s recommended combination of plugins for selling event tickets with woo. And I don’t mean to down play how nice a lot of TEC pro is. It has a lot of great features, and a lot of it is really easy to use. The people who will eventually be responsible for adding events and maintaining the calendar have been very happy with the plugins so far, our frustration has been mostly that we seem to come up against roadblocks we weren’t expecting, such as the attendee list not working, and ticketing not working as we thought it would from reading the presale materials and forum postings. We’re not seeking a refund, hopefully just some help. I apologize in advance for the long reply.

In my example we are using this combination of plugins to manage art classes and registration for a community art studio. We need a parent to be able to register their two kids for 2 different classes, and purchase tickets for 4 or 6 consecutive tuesdays. We are using recurrence for the events because they happen every week, but it forces the user to purchase 4 or 5 individual tickets, across several pages of calendar, to buy all the class tickets. In previous threads I have seen MT folks saying that they were actively working on recurrence for the 3.0 release, and while we can create recurring events, the tickets plugin does not recognize this relationship. We have 12 seats once a week for 6 weeks. We need the parent to be able to buy a 6 week block, register the attendee(s) and give us some additional info. When they purchase this, that needs to trigger the inventory to recognize there is 1 seat less on all 6 weeks, and add the attendee to all of the attendee lists. – even if we could just register an attendee for a a 6 week block, without a ticket, that would be useful, but as is is you can not.

We also need to capture registration information beyond the billing info. So we have had to add additional fields to the checkout page, for the parents to add the student name, age, emergency contact numbers, check that they agree to the release, etc. Unfortunately, this information is then tied to the SALE, not to the event attendees list, it’s a fractured system. and if the parent is registering 2 kids for different events they’re buying at the same time, it’s impossible to determine which kid is in which event. WooTickets ought to add a layer before the billing page, which prompts the purchaser to register for each event they’ve purchased tickets for. This way, they can only make a payment after registering their children and giving consent. Anyway, this is also less than ideal, because we are also using woo to sell art supplies for the students, so having the checkout page contain ticket-related fields (emergency contact, etc) is really confusing to the user. If I’m buying a paint brush, I don’t need to be prompted for a student’s name, or any other details. Registration info needs to be tied to each event.

We also need the reverse to happen smoothly. If a parent purchases a 6 week block of tickets, and then seeks a refund, it takes a LOT of work to manually go through the system and cancel each ticket, and add a ticket to the inventory to make it available again.

Here’s a list of the things we’re actively seeking solutions/fixes/workarounds (that won’t conflict with future updates) for, hopefully you can help us with a few of them.

– attendees list does not appear to grow when I purchase a ticket

– recurrence is not recognized at all by tickets.

– there’s no way to buy a ticket to every recurrence of an event without viewing every event page and adding each to cart.

– cancelled/refunded tickets do not properly correct the number of tickets sold.

– there is no “total amount of tickets” variable, which would make it easier to sell 4 tickets at a discount, on the same event page with single tickets for the normal price, without the use of coupons. Both the discounted tickets, and the individually priced tickets should still pull from the same pool of tickets. I’d like to be able to add 12 tickets, available at either price depending on how many are purchased. The variable pricing plugin for woo does not look like it’s going to work with tickets.

– there is no way to manage registrations for an event that require additional information. or to purchase tickets to an event for 2 different attendies

– there is no way to add an upsell product to a ticket the way I can to a product. (add art supplies for $15.)

[mellowvision]

that’s a shame, I had read several forum posts in the past, implying that recurring events and tickets were being prioritized. This was part of the reason I chose to purchase these plugins.

[Author]

Posts