Plugin Support
Darian
(@d0153)
Hi @webhria,
Thanks for reaching out. I’d be happy to assist you with this.
Upon checking, this is a known bug, and we’ve received reports from some users who are still experiencing the issue even after the latest update.
Rest assured, our team is actively working on a fix, and we hope to have it available soon.
In the meantime, could you please let me know the version of the Event Tickets plugin you’re currently using? This will help me check your setup further.
Hi Darian,
The version was the most recent one. While waiting for a fix, I’ll use 5.27.5 because that one still works for me.
Thanks for your time!
Plugin Support
Darian
(@d0153)
Hi @webhria
We’ve just released a new version of Event Tickets that should address this issue. Could you please update it on your end and let us know if that resolves the problem?
As always, we recommend testing the update on your staging site first before applying it to your live environment.
Looking forward to your update.
<span style=”font-size: inherit; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;”>Hi, I’m experiencing the same issue and wanted to add another data point.</span>
We are currently running Event Tickets 5.29.4 and The Events Calendar 6.17.4. Our ticket has a defined capacity of 35 rather than Unlimited.
The interesting behavior is that checkout <strong data-start=”948″ data-end=”999″>works correctly when I am logged into WordPress, but when testing as a logged-out user in Incognito, selecting a ticket and clicking “Get Tickets” takes me to the checkout page with <strong data-start=”1134″ data-end=”1157″>“Oops, no tickets!” A customer attempting to purchase is experiencing the same issue.
We have cleared the WP Engine cache and retested in a new Incognito session.
We are also running Events Calendar Pro 7.7.2 and are seeing a notice that 7.7.12+ is required, although WordPress currently shows no Pro update available despite the license being valid.
Before we attempt a rollback or make additional changes, can you advise whether this logged-in vs logged-out behavior is consistent with the known issue, and what version/workaround you currently recommend?
Thank you!
Plugin Support
Darian
(@d0153)
Hi @kalvareztb
Thanks for your message. Unfortunately, we cannot provide any kind of support in this forum for premium users.
For us to help you better, please open a Support Ticket on our Help Desk.
You’ll hear from one of my colleagues soon!