Fixes in 3.5.1

[reddishpink]

Hey Guys
Thanks for updating Event Calendar Pro!! Awesome.
I saw this update: Changed how recurring events are stored, to give a unique post ID to each recurrence

Will that now allow us to sell tickets for each occurrence?
I just tried with Wootickets and the new version of Event Cal Pro and Im still seeing the inventory is the same for all reoccurences. Meaning I buy a ticket on one day and the stock decreases from all days. Or am I doing something wrong?

Thanks

[Casey D]

Hello reddishpink!

Converting the way recurring events are stored was a big update for us in 3.5.

https://theeventscalendar.com/march-release-responsive-and-recurrance/

The other big note in this release has to do with recurring events. We’ve fully rearchitected how recurring events work. You won’t notice a huge difference in this release, but the updates will allow us to do some really cool things in the future including custom recurrence and finally getting recurring events to work with our ticketing plugins.

 

Unfortunately, recurring ticketing with WooCommerce is not yet supported, as discussed in the Roadmap section here:

https://theeventscalendar.com/shop/wordpress-wootickets/

So while there is no solution right now, we’ve heard quite a bit of demand for this feature and hope to release a solution at some point in the future.

We take a great interest in what features our users would like to see. You can vote for this feature and others at our UserVoice forum.

http://tribe.uservoice.com/

I hope this clarifies things 🙂

Cheers!

Casey

[reddishpink]

Hi that’s great. Any idea when the next release of wootickets that will support re-occurring events might be? Two – Three months or more like a year?

We have to launch a site soon with this capability and Id love to use your tool. Otherwise we have to look elsewhere.

Thanks

[Casey D]

Sorry reddishpink, I can’t offer any help with a tangible timeline. The best I can offer is that we are working on a solution, but it would be a disservice for me to give you a predictable time frame.

We were excited to release 3.5, as it made this and many other features possible in the future. With so many ideas in the pipeline though, it’s difficult to know when each will be ready for release.

The nature of software development makes it difficult to predict the future. We hold quality, simplicity and backwards-compatibility to a high standard, and bugs, feature requests and industry trends are obstacles to predicting the rate of development. Especially when projecting for any length into the future, sometimes even we find ourselves unsure of what a few months forward might bring.

So we remain diligent in our active development, so that when we ship, we are confident it is the quality our customers expect.

What we have now is our current feature set, until we release another update.

Does that make sense? Sorry for the opaque answer! It is the best answer I can offer at this time.

Thanks for your support so far! Cheers!

– Casey Driscoll

[Author]

Posts