MAJOR ISSUE: ATTENDEE DATA NOT SAVED IF 10 OR MORE TICKETS ADDED

[FRANK]

HI Geoff B,

Thanks again for the continued updates.

Just a quick questions and as much for my piece of mind as anything.

The solution, whichever one, from the 4 you implement, will it have any impact on all the attendee meta data already saved in the database at all?

I know at present there is no functionality for the admin to update attendee meta. However, I can access this via phpmyadmin to make any changes.

Is there likely to be any issue with me updating attendee meta this way?

When accessing the records via phpmyadmin I notice there are 2 entries for each set of attendee information provided. One corresponds with the order number and the next one has an order number incremented by one.

Is this what I should expect to encounter?

Any advice or words of caution on amending data that way welcome.

I also came across a bit of code in another post which I can no longer find but I still have the link to the code. It was to allow attendee meta to be updated from admin, titled ET metahawk. Any ideas about this snippet/plugin?

Thanks,

Frank

[Geoff B.]

Good evening Frank,

I’d love to answer your follow-up questions.

The solution, whichever one, from the 4 you implement, will it have any impact on all the attendee meta data already saved in the database at all?

There will be absolutely no impact on the attendee meta data already saved in the database.
What will change is how the data gets there. But everything else will stay the same.

Is there likely to be any issue with me updating attendee meta this way?

That’s a great question. Updating data directly in phpMyAdmin usually goes great.
There should not be any issue with data updated that way.

That being said, I would advise a database backup every time you do. Just in case.

When accessing the records via phpmyadmin I notice there are 2 entries for each set of attendee information provided. One corresponds with the order number and the next one has an order number incremented by one.

Is this what I should expect to encounter?

The best thing here would be a screenshot. But in all likelyhood one of these as a “published” status whereas the other should have a “inherit” status and is probably a revision.

I also came across a bit of code in another post which I can no longer find but I still have the link to the code. It was to allow attendee meta to be updated from admin, titled ET metahawk. Any ideas about this snippet/plugin?

I believe you are referring to: https://gist.github.com/GeoffEW/0767b38ffcccfbf90817a542253de1d6

It’s an experimental snippet so once again, please backup before using. But some of our users are using it successfully instead of going the phpMyAdmin route.

Best regards,

Geoff B.

[Geoff]

Hey there, Frank! Just a heads up that we released Event Tickets and Event Tickets Plus 4.2.6 moments ago and it included a fix for this issue. Please do update when you have the chance and definitely let us know if you continue to have any issues at all.

Thanks so much for reporting this and for your patience while we worked on a fix. 🙂

Cheers!
Geoff

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts