[Craig]

This reply is private.

[Craig]

Hi Nico,

Thanks for following up.

After downloading and manually installing the 4.2 updates on my dev machine, unfortunately, all my stock and ticket sales info from Woocommerce has been wiped out.

And the problem of the next-nav field is not better either. I’m going to try to delete all the tickets and re-import them using your new feature.

I’ll get back to you with my progress.

Thanks,
Craig

[Craig]

Hi Andras,

Can you give me a hand on this still?

I’ve isolated the problem to just the issue with the next-nav disappearing. Even if we add events in subsequent months, the next-nav still does not appear. If we are using the UI (instead of importing with a third-party plugin), then the system should definitely recognize it as added and display the next nav link.

Thanks,
Craig

[Craig]

Hi Andras,

I’m beginning to suspect this issue is due to the same problems I had before with the calendar not displaying events.

As I looked into things further today, I noticed that publishing a new event not only killed the nav-next link. It also deleted all the stock and price information I had in Woocommerce Tickets (Tickets Plus).

To get all those tickets in there, I used the Woocommerce CSV Import Suite and linked the tickets to the events using the _tribe_wooticket_for_event field.

I have no idea how Events Calendar could wipe out that information, but it does – completely – just about every time a change is made in Events.

The process was as follows:
1. Import Existing Events Using Events Calendar Importer.
2. Import Tickets Using Woocommerce CSV Import Suite.
3. Any new events are added using the Events Calendar front end UI.

This last action killed the next-nav link, and the stock and price information for the Tickets.

Thanks,
Craig

[Craig]

This reply is private.

[Craig]

Interestingly, when I added an event for July (next month), the next nav appeared again. To reiterate, though, I did have events for July in the calendar already. I’m just adding this to help with debugging.

Thanks,
Craig

[Craig]

Thanks, Andras.

I may also put in a feature request to have a mass update process that’s available, even if just through a support ticket. I had to manually update everything last night.

Of course, maybe that won’t be necessary with the new tickets plugins. But unless there’s a way to merge updates, I think people still may need to use another plugin, and there is really no way to know whether that import process will be compatible with all the different “save_post” actions in TEC.

Thanks,
Craig

[Craig]

Never mind. I was trying to upload it as an event instead of clicking on ticket.

Unfortunately, I’m not able to try it out fully as it’s crashing localhost when I try to upload Organizers.

Thanks,
Craig

[Craig]

This reply is private.

[Craig]

This reply is private.

[Craig]

This reply is private.

[Craig]

Hi Andras,

It appears the CSV importer I’m using must suffer from the problem described in this: http://stackoverflow.com/questions/12809525/getting-hold-of-metadata-when-creating-a-post-in-wordpress

Unfortunately, with the current Events Calendar importer, I can’t merge imports. So I’m forced to either delete and start over or use another plugin, which I did.

Is there any way you know to force an update that grabs the metadata before the save action?

Thanks,
Craig

[Craig]

This reply is private.

[Craig]

Hi Andras,

It could be this was originally caused by a mis-match in event price and ticket price due to a sorting error I made before importing tickets with Woocommerce Import Suite.

My process was as follows:
1. Upload Events.
2. Create tribe_wooticket_for_event connector based on Event ID.
3. Upload tickets using Woocommerce Import Suite.

(My error came in step 3, which produced the price conflict.)

I could likely wipe out products and tickets *IF* I can upload them both at once. Would you recommend trying the beta for this, as I understand it’s possible now?

I would delete everything, but it would take a lot of extra work to get the tribe_wooticket_for_event field to match again.

[Craig]

I’m afraid this didn’t work for me. Do you have any other ideas on how to achieve the same result? Maybe a temporary function to override the caching?

Thanks,
Craig

[Author]

Posts