As exposed in #3246055: Refactor ticket display page and PDF generation → , we might want to consider a way for users to configure what's on the QR Code, right now it is hardcoded to the uuid of the ticket and that might be enough for most use cases but some others might want to include other stuff as they see fit, such as seat numbers, ticket holder information or other metadata information.
The original proposal could be a display mode "qr_code_data" that renders the information into a JSON encoded string. Probably the best way would be to gather the fields individually and render them in sequence.
Alternatives to this approach are warmly welcomed.
Decide and implement :)
Fixed
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
How can I use this hook to pass the name and phone number of the owner of the ticket, and fields from the product variation, say the label, into the QR code?
Thank you.
I later understood better and was able to use the hook to load the ticket in the browser. I guess this is about all what the hook is meant for? And then whatever other information one wants to make available will be added to the ticket page that loads on the browser?