Recurring Ticket Sales – Removes Ticket Stock on Future Events.

[carnfield]

Hi guys, there’s a rather huge flaw to recurring events and tickets.

It’s really rather silly. If you say there’s 10 tickets for a weekly recurring event, once all 10 tickets are sold, all future events are sold out.

So, any way for each recurring event to hole their own quantities? It’s the one feature I bought Events Pro + Tickets, and it’s been really badly overlooked, it’s a Captain Obvious – so am I missing something or has there been a super blunder?

[carnfield]

Just found this post from 9 months ago:–
Kelly February 27, 2014 Permalink
Hi, chesapeakeghostwalks. Great question! 🙂

Unfortunately, WooCommerce Tickets does not currently support recurring events. We’ve tried to highlight this limitation in the Roadmap section of the WooCommerce Tickets product page, but I know that it’s often overlooked.

On the other hand, we are getting close to launching our refactored recurrence infrastructure. Once that’s complete, we’ll begin the next step of investigating how that can be effectively ported over to the tickets framework. So, it’s not going to happen right away, but it’s definitely something we’re making steady progress towards.

Sorry I don’t have better news for you, but hopefully, that clears up the mystery!
——————————–

There is absolute no point in having recurring for tickets if its not supported of tickets, and 9 months on this functionality isn’t support, then I’ll be utterly gobsmacked.

If this functionality still isn’t there, I’ll be requesting a refund for both plugins and grate my teeth and go back to Event Espresso.

There is no warnings about issues with recurring, and I’m utterly shocked this hasn’t been implemented in 9 months.

[Josh]

Hello carnfield,

Thanks for reaching out to us!

I’m sorry for the confusion on the recurring events support for the WooCommere Tickets plugin. We do have a note about the lack of support for recurring events on the plugin page within the “Roadmap” section of that page. However, I do see how this can be overlooked when making the purchase.

That being said, we are actively  rewriting the plugin to have support for recurring events. I don’t have a specific ETA for this feature but it is the top priority for an upcoming release of the plugin.

Again, I’m sorry for the confusion and inconvenience. Let me know if there is anything else that I can do to help.

Thanks!

[carnfield]

Hi there;

I’m pretty certain there’s incredibly easy ways around this, there is already dates posted into the database, so adding a quantity for each date should really be a 1-2 hour fix.

I think its incredibly lackadaisical of your team to have not jumped on this sooner, given the fact that it should have been one of the original must-do parts on the planning, should have been flagged up during development, has to have been flagged up on testing.

I know for a fact that 9 months ago it was flagged, so please spare me the inconvenience when you’d had a good 9 months to release the plugin.

9 months alone is quite some time for development. You guys said pretty much the same thing back then.

Let me just remind you of what your staff said NINE MONTHS Ago:-
“On the other hand, we are getting close to launching our refactored recurrence infrastructure. ”

What’s the likelyhood of you guys spending a few hours fixing this “bug” in the next few days / week? If it’s never going to happen then I’ll have to request a refund and go back to event espresso (something I really don’t want to have to do).

Regardless of some of the feedback your product is cleaner, more user friendly and easier to design around, and I really would like to continue using it. Waving a 9 month old carrot in front of people just angers them.

[Josh]

Hello carnfield,

Thanks for following up with us.

I can understand the frustration that comes from a plugin not performing in a way that you expect it should. I also understand the frustration when it seems like it is taking so long to complete a feature that seems like it should be an easy fix.

However, I can assure you that the solution for this issue isn’t a quick 2 hour fix. Every feature is an investment of time in regards to strategy, development, quality control and countless other factors. In regards to the development phase, solutions have to be approached in a way that doesn’t affect the performance of the plugin for existing users. You mentioned that our plugin is “cleaner, more user friendly and easier to design around” than alternatives that you have used. We believe that this is due to taking feedback from our users and implementing new features while giving them the time and focus they deserve.

When approaching release cycles, there are hundreds of issues and features that are up for consideration. We have to prioritize these based on the overall severity of the issue as well as the demand from the community for specific features or functionality. For example, coming into this current release, there was a huge demand for us to focus on performance. So, version 3.7 was dedicated to bettering the overall performance of our plugin.

That being said, we do have a developer focusing on this feature and at this moment it is currently scoped for the next release. This means that barring any unforeseen issues in the development process, the feature should be shipped with the next release. If anything changes in that plan, we will definitely notify you here on this post.

If you would like a refund, you can request one via an email to pro [at] tri.be. Please be sure to include your original receipt as well as a link to this forum post in your request.

Let me know if there is anything else that I can help with.

Thanks!

[carnfield]

Actually I can assure you that:

You’ve already been told by someone who’s paid to have both Event Calendar Pro AND Woo Tickets Fixed how to fix it.

Also you’ve taken 3 payments for Event Calendar Pro and Woo Tickets:-

9 Oct 2014 Debit Card Transaction – £41.64
9 Oct 2014 Debit Card Transaction – £41.64
9 Oct 2014 Debit Card Transaction – £41.64

So you can refund all, and I’ve only had 2 bloody payment emails from you so I can’t send you that back, the triple payments from 2 purchases has made my mind up.

THanks.

[Rob]

Hey carnfield! Rob from Modern Tribe here – I head up the support team, and Josh brought this thread to my attention when I returned from vacation this morning. Naturally I wanted to prioritize a follow-up since it’s clear you’re frustrated.

You make a few great points here, and we really appreciate you taking the time to provide this feedback. I know what it’s like to use a plugin and find a limitation that diminishes its overall value – it sucks, and is made even worse when it’s a plugin you paid money for. It’s clear we failed to properly set your expectations here from the offset…as Josh noted, the lack of recurrence support across the entire tickets framework is something we try to be pretty transparent about on the product pages. (We actually even attempted to call those out more than the rest of the text by making it bold – to clearly reiterate that we don’t have recurrence support, but that it’s on the roadmap). However it sounds like the bold treatment still wasn’t enough to make this readily apparent before you purchased, and as a result left you unable to make a fully informed decision. I apologize on behalf of the whole team for that and welcome any ideas you’ve got on how we could have made that information more prominent on the product page.

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.

I’d also like to clarify: that comment about our updated recurrence structure that you mention, is actually accurate. We did launch a refactor of the recurrence framework a couple releases back and have more work on that front coming over the next month. This refactored recurrence architecture was needed as a first-step before we could get started on recurrence support for tickets…but now that it’s done, the work I mentioned above to bring this into the tickets framework is moving along nicely.

I hope that helps! It sounds like there may be some odd billing issues going on as well, which is definitely concerning. I want to help you out there but in the interest of security/privacy, I think addressing that should be done via email instead of here on the forums. If you email pro (@) tri.be we will refund the duplicate purchases for you so you’re not being tripled charged. And while it’d suck to lose you as a customer, know that if you want your original purchase refunded so you can use a plugin that better your meets your needs, that offer stands no questions asked. I want to do right by you…even if it means refunding you your $ and sending you into the arms of a competitor.

Thanks again for your feedback and helping us get better. If you have other ideas or concerns that you’d like to share, you can always email me personally: rob (@) tri.be.

[Josh]

Hello carnfield,

I’ll go ahead and close this tickets since it sounds like the remainder of this conversation will take place via email at pro (@) tri.be.

If you have any further questions, concerns or feedback please don’t hesitate in opening a new ticket.

Thanks!

[Author]

Posts