Same stock for recurring events

[Luc]

Dear support team,

I’m facing an issue in which a stock of tickets for recurring events is shared among all instances of the recurring event. It’s the issue described in this thread: https://theeventscalendar.com/support/forums/topic/recurring-ticket-sales-removes-tickets-on-future-events/.

However, in that thread you write multiple times you are working on it and at the end of the story you somewhere mention it is in the next release. However, I purchased te plugin this week and face the same issue. Is it a setting I am missing or is it still an open issue, which I really hope not?

Thanks for addressing this topic. Have a nice weekend.

Best,
Luc

[George]

Hey Luc,

I’m really sorry about your running into these issues again – as a developer on our products line myself, I can address your concerns about this functionality. First, however, I’d like to highlight Rob’s comments from that ticket you linked to:

As Josh noted, this is actually something that we’re working on currently – the development work is literally going on as I type this 🙂 While I don’t want to commit to any specific release, you should know that we do see the value in this and realize that it’s a hugely requested feature among the community. If we weren’t to act on it we’d be letting our customers down and failing to stay competitive. Once the work is done and passed QA – so we know it’s solid code that we can stand behind that our users will be stoked about – we’ll ship it. While certain users may claim to have found a way to “hack the code” and make this work, it is worth reiterating that it’s not an easy tweak…definitely not something doable within just 2 hours. The recurrence code runs pretty deep throughout the PRO codebase and there are a lot of factors that have to be considered. Rather than implement a “hacky” solution just to get something out the door, we prefer to do it right – even if that means delaying the finished product a bit. I’m optimistic that if you stick around (which we hope you do!) that you’ll find it to your liking.

Rob was spot-on about the recurrence code being very deep-seated in our codebase, and since we changed so much of the codebase in our 3.10.x releases, the recurrence improvements you’re looking for here were, unfortunately, pushed back until a later date.

I’m really sorry to bear that bad news – recurring events still do not fully support tickets at this time.

The best solution is to make a recurring event, and then as a specific within that series approaches, just “Split” it out of the series (there’s a link to do this in the Admin toolbar when you view a recurring event’s edit screen in the admin of your site).

Then, once it’s “split”, you can add tickets for that one event, and it should function normally and well.

Please let us know if this helps, and any further followup questions / feedback / complaints / suggestions you might have! 🙂

Thanks,
George

[Luc]

Thanks. It helps, but of course isn’t ideal. We’ll just have to wait. 🙂

[George]

Thanks for being cool about it Luc, sorry to disappoint. Stay tuned for future products updates though, this is a set of features we’re really keen on implementing (and are actively writing code to do so! 🙂 )

Cheers,
George

[Author]

Posts