Hi there,<\/p>\n
I’ve just upgraded many plugins (as listed below), and I have a question about whether or not ticket functionality has changed.<\/p>\n
BEFORE:<\/strong> AFTER:<\/strong> Now, in the old implementation of The Events Calendar PRO and WooCommerce Tickets, tickets for a recurrence series were shared. For example, let’s say I want to offer a private tutoring lesson once a day for seven days. Now, logically, I should create an event that occurs once a day for 7 days, and then add one ticket for the series with a stock of 1, so that when someone signs up for one day, nobody else can sign up for that day as well. However, if I remember correctly, the default functionality made it so that the tickets for a series were shared. i.e. when Jim signs up for Monday by purchasing that day’s ticket, the tickets are no longer available for anyone else for any other day. Jim has effectively reserved his spot for the entire recurrence series.<\/p>\n Now, this was a problem for my website because we offer different levels of classes, and if there is a recurrence series, it’s the same class being taught multiple times. i.e. “Beginner’s class” happens once a week, and nobody should want to attend the Beginner’s class more than once. My workaround was to modify the plugin by hand so that when a recurrence series was created, tickets were created for each instance of that series, not just for the parent event.<\/p>\n Is this still the case? Will I need to modify the plugin by hand again in order to get a unique stock of tickets for each recurrence instance? Or does each recurrence instance already have a unique stock for that ticket? If I do need to modify the plugin to duplicate the “parent” ticket for each recurrence instance, do you know what document of the plugin I’d need to do that in?<\/p>\n Additionally, I need to be able to set a dynamic “Sale End Date” for the tickets. Instructors for a class want to be able to estimate the class size before the class actually begins, so we don’t want to be able to sell tickets past midnight the night before the event. In earlier implementations, when you select a “Sale End Date” for a ticket, that means that that date is static. Going back to my private tutoring lessons example, let’s say that Jim wants to attend on Monday, but I don’t want my ticket to be available past 11:59 PM Sunday, so I make my Ticket Sale End Date 11:59 PM Sunday. When Monday comes, and someone wants to sign up for Tuesday’s private lesson, they can’t see the ticket, because that Sale End Date means that tickets aren’t available for ANY instance after the sale end date passes. This was another issue for us that we had to fix by hand – is this still the case? If so, do you know where I would need to make modifications?<\/p>\n Lastly, I need to be able to add the date of an event to the end of a ticket’s name. Authorize.NET doesn’t differ between two tickets for different class dates in the report we run, so we had to work around that by making each unique ticket for each recurrence instance have that instance’s date appended to it at the end. Do you know the document where tickets are saved in? If so, I could just add a line or two to modify the name of the ticket when it’s being saved as a post so it has the event’s date appended to the end of it.<\/p>\n Thank you for taking the time to read this, and I hope you’re able to help me!<\/p>\n","protected":false},"template":"","class_list":["post-1082497","topic","type-topic","status-closed","hentry"],"yoast_head":"\n
\nThe Events Calendar v3.9.1
\nThe Events Calendar PRO v3.9.1
\nEvent Rocket v2.5
\nWoocommerce v2.3.5
\nWooCommerce Authorize.NET AIM Gateway v3.4.2
\nThe Events Calendar: WooCommerce Tickets v3.9.2<\/p>\n
\nThe Events Calendar v4.0.6
\nThe Events Calendar PRO v4.0.6
\nEvent Rocket v2.5
\nWooCommerce v2.3.5
\nWooCommerce Authorize.NET AIM Gateway v3.4.2
\nEvent Tickets v4.0.5
\nEvent Tickets Plus v4.0.5<\/p>\n