-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Assign custom fields to purchased tickets element #42
Comments
Yep, that's the plan. Previously, you can store data on line item options (you still can, and always will), but we'll be evolving this to include the ticket (and maybe event) fields, so that you can still assign them to event/ticket types, but they're also applied to the purchased ticket. Will be in the next minor release. |
You're our favorite. 🤩 |
If you're feeling extra giving, adding in a CSV export for the purchased ticket table would be incredibly helpful. |
@sjcallender The current element export functionality doesn't work for you? |
Oh, yeah that'll work. We can't upgrade to the newer version yet because of other dependencies, so I haven't been able to test. |
Exporting to CSV works in Craft 3.3/Commerce 2.x - but you'll get much more benefit when using on Craft 3.4, as there's a lot more control over what you can do, module manipulation, etc. |
Is there an ETA on this @engram-design ? I'm in a similar position where each ticket needs to have attendee details mapped to it. I've currently got a matrix as an order field which is populated via the front end during the checkout process but that has some shortcomings, having it as a ticket field would be perfect. |
I can't guarantee an ETA, but we'd expect to be able to fit it in, in the next 1-2 months. |
Added in 1.4.0, just have a look at the tweaked docs as well. Special thanks to @samuelbirch for the PR. |
Description
With the purchased tickets now stored as elements, it be incredible to be able to edit the custom fields mapped to them.
In our case, a person can purchase multiple tickets on behalf of others. We save the attendee info in the Order options. We are planning on adding our own db table to then store the attendee info outside of orders for easy querying. Even better would be able to add that attendee info to custom fields on a purchased ticket.
The text was updated successfully, but these errors were encountered: