[Barry]

Nice one. I haven’t seen your email but possibly one of my fellow team members did and dealt with it directly … but let me know if you’re still waiting for support on this front 🙂

[Barry]

Either email them (to [email protected], marking the email for my attention and linking back to this thread) or post a link here if you are able to FTP them to your site or use an image sharing service.

OK, we’re currently on 2.0.11 for The Events Calendar and Events Calendar PRO, so do consider updating as there have probably been quite a few changes and bugfixes since 1.2.

[Barry]

That’s strange.

Is deleting the problematic event, locally and on Eventbrite, then recreating it an option?

[Barry]

How odd – but great you found a fix.

I can still involve one of our devs but realistically if this is not a problem going forward (ie, when you create new events) it does rather suggest a historical issue, whether caused by a conflict with some other code or something else, and I don’t know that we would be particularly better placed to fix that retroactively than you are.

My feeling is that updating them manually, though I fully appreciate that could be something of a chore, is probably the most expeditious way to solve this for you and your client.

[Barry]

Hi Leslie.

Could you share a screenshot of the event settings (particularly, the date/time area in the event editor)?

Can you also confirm which version of The Events Calendar/Events Calendar PRO you are using by visiting the list of plugins accessible from the dashboard?

Thanks!

[Barry]

Hey Thomas.

This boils down to the same problem as covered in this thread – which is that WooTickets does not really support recurring events: effectively, the same pool of tickets is shared amongst all of the recurring events.

Also, due to the way recurring events work under the hood – they all share a common ID – I don’t think figuring out the information you need is going to be readily achievable, unfortunately. The same advice I provided to you in the above thread is still valid going forward, at least with the current generation of WooTickets:

The best advice I can offer right now is to break your sequence of recurring events out into separate events or else avoid using WooTickets with recurring events.

I know that won’t really help you out with your current problem, but it would be well worth bearing in mind from this point on to avoid any further confusion.

[Barry]

just to quickly add to this: export of wooTicket data to XLS would be a huge plus here

Sure. It might be that, if this is added to a future release, something a tad more generic (but still Excel-compatible) like CSV is used, but I’ve got this logged and the team can consider it when they do their forward planning.

I think it is extremely important for the buyer to have the date and time of the event in the PDF ticket. This shouldn’t be very difficult to implement?

I’ve logged this issue and it seems like a great idea – so I’d expect we’ll see it in the next release.

[Barry]

Thanks – we’ll look out for that 🙂

[Barry]

Hi Andrew: just checking in here – did you send across those credentials (if so I haven’t seen them as yet) and do you still require further support on this one?

[Barry]

Hmm, well – I suspect something has impacted upon the affected events that wouldn’t normally occur and has, for want of a better expression, “corrupted” them. But that’s just a guess.

What I’m going to do here is refer this to a member of the dev team and see if they can shed any further light on this/think of a way to fix the existing events.

[Barry]

Hi Amilkar – I’m going to assume you don’t need any further support here and will close this thread in a day or two.

If you do need further assistance please post back before then!

[Barry]

Liz: if you create a new (test) event, does the same problem occur?

[Barry]

Hmm, ok. Here’s the thing – the “Schedule” text should only show if the event is recurring, at least with the standard templates. If you bear with me I’ll test a few scenarios out based on those screenshots.

[Barry]

Hi jayc, no I’m afraid I can’t indicate when 3.0 will be released, but we hope it will be soon 🙂

Are you absolutely sure this is the same problem experienced by Luke? If not, simply to avoid confusion, please feel free to go ahead and create a new thread.

Luke: do you require further support here/is this in relation to custom code or a problem with the “native” output of The Events Calendar?

[Barry]

That’s right. WooTickets does not currently support recurring events at this time, and so a side effect is that creating a ticket for one event in a sequence means that same ticket (or set of tickets) will be used for all.

If that’s likely to cause problems I’m afraid the best advice I can offer right now is to break your sequence of recurring events out into separate events or else avoid using WooTickets with recurring events.

I appreciate that isn’t ideal, and this may be revisited in a future version.

[Author]

Posts