Tickets no longer showing on front-end following WordPress upgrade

[John]

Hi there,

I have recently upgraded WordPress from 4.0.1 to 4.4.2, and now I’m having difficulty seeing tickets that were created prior to the upgrade on the front-end. I assumed initially it was due to plugin incompatabilities, but I’ve upgraded all of my Events Calendar-related plugins, and I’m still not seeing old tickets on the front-end. The tickets are present in the database as products still, and their postmeta seems to still be present as well. Additionally, they show on the back-end for these events, but they are not appearing on the single events.

My plugin setup (before and after the upgrade):

BEFORE:
The Events Calendar v3.9.1
The Events Calendar PRO v3.9.1
Event Rocket v2.5
Woocommerce v2.3.5
WooCommerce Authorize.NET AIM Gateway v3.4.2
The Events Calendar: WooCommerce Tickets v3.9.2

AFTER:
The Events Calendar v4.0.6
The Events Calendar PRO v4.0.6
Event Rocket v2.5
WooCommerce v2.3.5
WooCommerce Authorize.NET AIM Gateway v3.4.2
Event Tickets v4.0.5
Event Tickets Plus v4.0.5

The process I took for upgrading the plugins (after having already upgraded to WordPress version 4.4.2) is as follows:

1. Disable The Events Calendar: WooCommerce Tickets
2. Disable and Delete Events Calendar PRO
3. Disable The Events Calendar
4. Upgrade and Activate The Events Calendar
5. Upgrade and Activate Events Calendar PRO
6. Install and Activate Event Tickets
7. Install and Activate Event Tickets Plus
8. Configure License Keys

(It may be worth noting that this is all happening in my development environment)

What may be causing this issue? I don’t believe it would be a plugin conflict – if the only change between a stable, ticket-showing state and an unstable, non-ticket-showing state is that wordpress has been upgraded, it must be an incompatability with the newest version of wordpress, which translates to a need for a bugfix on my end, or an upgrade to the newest versions of relevant plugins, which didn’t alleviate the issue.

Don’t be confused, though – tickets are working when they’re created post-upgrade. Additionally, it’s not that the tickets aren’t being recognized at all – the admin interface will still list old, pre-upgrade tickets as products, and will still list those same tickets under the “Tickets” section on their related event. The tickets’ end sale date has not passed, and the events I’m looking at in a recurrence instance where this issue is arising have not passed, either. (It may be worth noting that the parent event has passed, though…)

Hope you can help me!

• This topic was modified 10 years, 2 months ago by John. Reason: Forgot to add version numbers to "BEFORE" section (had to revert database in order to figure them out)
• This topic was modified 10 years, 2 months ago by Geoff B..

[Geoff B.]

Good evening John and welcome back!

Thank you for reaching out to us.

We are sorry to hear about the tickets not showing in the front end after your latest WordPress upgrade.
I would love to help you with this topic.

As a first troubleshooting step, could you please provide us with your system information in a private reply ? (following the instructions found in the link)

That being said, I have a couple of suggestions/questions to get started towards resolution of this issue:

• Event Rocket is unfortunately no longer supported since version 4.0 of our the Events Calendar plugin. I would recommend deactivating it.
• Did you follow the complete procedure described in the following link to upgrade to Event Tickets Plus ? https://theeventscalendar.com/knowledgebase/moving-to-event-tickets-plus/
• Would it be possible to provide us with an URL for investigation purposes ?

I am looking forward to hearing back from you.

Best regards,

Geoff B.

 

[John]

Hi Geoff,

Strangely enough, it seems like it’s only that recurrence instance that is broken. I pretty distinctly remember using that event as my test case at some point, so I don’t know why it suddenly doesn’t work, but when I made a new test case in my 4.0.1 environment, then transferred the database containing that test case to my 4.4.2 environment, the ticket performed as expected. I’m not sure why this may have been the case, and that means that the broken event is still a broken event, but I’m not too torn up about that because it’s broken on both 4.0.1 and 4.4.2, so it must not have been working for quite some time, contrary to my memory.

Thanks for your help all the same! I appreciate your time, and I’m sorry I couldn’t offer a more comprehensive response – I don’t really understand why that event would be behaving that way, but I’m certainly not complaining if it’s an isolated incident. 🙂

[Geoff B.]

Good evening John,

I’m glad to hear the issue was actually limited to that specific instance.

I’m right there with you. The important part is that it’s an isolated incident 🙂

We are glad to help! After all, this is what we are here for !

Please come back any time you have questions or issues.

Cheers,
Geoff B.

[Author]

Posts