Re-open feature request to allow admins to edit ticket "Additional Information"

[Daniel]

There are a few calls to allow admins to edit the “Additional Information” collected during ticket purchase however, the feature request appears to be locked pending additional clarification. I think that the clarification is present but there can be no further up votes for the feature as it appears to be locked.

Suggestion is at https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/16518778-edit-attendee-meta-information-in-admin-backend

The need is to allow admins to edit the “Additional Information” that is collected before tickets are added to the cart.

The scenario is:

1. User sets ticket quantity
2. Users enters ticket information (All or partial)
3. User adds to cart, pays
4. User emails/contacts admin says “Help me out, change the details on the ticket”
5. Admins visits backend of site to make amendment to customers ticket
6. Locates ticket in list
7. Expands details of ticket
8. Presses ‘edit’ to adjust value
9. Changes value
10. Clicks ‘update’ to replace value in database

Please see mockup screenshot.
Thanks.

[Daniel]

Alternatively – could we cross link from the list in the screenshot to the tickets editing page /tickets/NN/ is that in orders-edit-meta.php?

[Daniel]

Apologies for not getting all my questions together but, we urgently need to edit a ticket – where in the database is the information held? Thanks.

[Cliff]

Daniel, thanks for the heads up on that UserVoice item. I’ll have our team get that opened up again soon.

Regarding where such data is stored, one way to find out (in the spirit of “teach a man to fish”) is by opening PHPMyAdmin, navigating to your full database (not any specific table), and then doing a Search across all database tables for the exact item you want to change, the more unique the better to avoid possible false-positive results (e.g. wanting to change the Business Name attendee meta field’s value from “Sue’s Shoes” to “Bob’s Boot Barn”) –> search for “s shoes” or something…

(Of course, we always recommend restorable database and file backups before modifying anything on your site.)

To answer your question, though, the Attendee Meta Information is stored in the postmeta table, with its value stored as a serialized array. Example: https://cl.ly/2O1j021G2b0p

From that screenshot, the string “test here. let’s see what emails get sent.” is 42 characters, which is why “s:42” precedes it. So if you change that Attendee Meta’s value to “Bob’s Boot Barn” (s:15) you’d have to change

s:42:"test here. let's see what emails get sent."

to

s:15:"Bob's Boot Barn"

That being said, you shouldn’t change serialized arrays directly in the database due to the high likelihood of making an error!

For learning, though, tools like http://unserialize.onlinephpfunctions.com/ and http://serialize.onlinephpfunctions.com/ may come in handy (third-party, not guaranteed or supported by us).

[Daniel]

Thanks for taking the time to supply the details – this will allow us to make the changes that we need to today. I’ll be up voting the feature too!

[Cliff]

Proceed with caution (we can’t help if you break something directly in your db) and have a great weekend.

[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