Bug – Ticket stock reduces to zero

[Joe Marsh]

Hi

I’ve come across an odd bug since the 4.1 update – the first time I edit each event since the update, the stock for that event resets to zero. Any edits since then don’t effect the stock count from what I can tell after changing the stock back to the correct amount.

Thanks

Joe

[George]

Hey @joe,

I’m really sorry to hear about this!

This is a bizarre bug we have found and are working hard on a fix for this. Stay tuned to this thread—I will be posting an update here as soon as possible with news about the bug and about the fix.

Thank you,
George

[George]

Hey @joe,

I’ve been doing some digging here, and while we do have a definitive bug here, I myself am not recreating these issues.

Can you share some extra information around the behavior of things here? It will help us continue the investigation.

1. You say, “F the first time I edit each event since the update, the stock for that event resets to zero.” Can you elaborate on these steps a bit? Did you edit the description of the event or something, for example, then click “Update” for the event, and then after the update the stock was reset to zero?

2. Is the event that has this issue an event you created before updating to 4.1?

3. If you create a brand new testing event (with just free tickets, for example, just for testing), do you have the same issue?

Thank you!
George

[Joe Marsh]

Hi George

Fortunately I’m in the process of updating all the events on the site anyway so have the opportunity to go through all of them and make sure this doesn’t affect anything.

It only applies to events created before the update – any created afterwards are fine.

Basically, if I make any edits at all (I’ve also had it happen from not making any edits but just hitting update) to events made before the plugin update, when I hit update on the event, the current sales stay the same, but the stock is reduced to zero. I then go back in to edit the ticket and put the stock back to what it was, hit update, and from there on in, any future changes don’t affect it.

As I said, not a massive issue for me as I noticed it pretty soon and it only happens once on each event, but from what I can tell it seems to be something to with the transition of old events on the new version.

Hope that helps!

Joe

[George]

Thank you for this information Joe, it’s helpful and we’ve made significant on this bug even since this morning.

I appreciate your input here and your patience with our process; stay tuned to this thread, I will post when there’s more information about the bugfix!

Sincerely,
George

[Geoff]

Hey Joe,

Just wanted to follow up and let you know that we released version 4.1.1 last night and it included a fix for this issue. Please update to the latest version if you haven’t already and do let us know if you continue to see any issues from there. 🙂

Cheers and thanks for your patience while we worked on this!

Geoff

[George]

☝️ That’s excellent, thank you for posting this Geoff (sorry for my delayed posting, Joe, I was out of office a bit today for a personal matter).

Do keep us posted on things. I hope that 4.1.1 update helps!
George

[Joe Marsh]

Hi Geoff/George

Thanks for following this up – as from what I could tell the bug only applied to events created before the 4.1 update, and because in between 4.1 and 4.1.1 I went through each individual event and updated it, I don’t have a way of testing this, however as it hasn’t recurred on any other events all is good from my end!

Thanks again

[George]

Thanks for your patience here, @joe! Glad to hear that there’s some progress. If issues arise again, of course, don’t hesitate to open a new thread. 🙂

Cheers,
George

[Author]

Posts