- Issue created by @martin@manarock.co.uk
Firstly - thanks for what seems to be a great module!
After installing and proving the basic functionality, I am now trying to clarify how to modify a ticket for our use case. I am effectively a hobby developer/ drupal configurator, trying to use this to solve a problem for local store :)
1 - How to add information to a ticket, ideally during the checkout process?
In configuration, that page says 'In our use-case, ticket are only valid on a specific date. You can add a "Visit Date" field to the order item. Then the user can select the date during checkout'.
Using this logic, I want to have the user add a 'Attendee Name' value to the ticket, so we can check that tickets have not been transferred or resold. Logically, I have assumed this should go on the ticket variation, but I cant seem to make this field show up anywhere, am I adding this to the right place, and is there any guidance on getting it filled in by a user during purchase? (note, I have now tried to add a field to the product, the variation, and the ticket type - no joy!)
2 - The tickets are for access to events, in this case defined by https://www.drupal.org/project/recurring_events → . Can I assume that whilst creating a product (ticket) I should be able to add entity reference fields to capture the event, data and time from an instance of an event? Ideally I would like the sale of a ticket to register a user for an event and reduce the available capacity - would ECA be a candidate for this, or would this be better attempted programmatically ? In effect a product should be linked to a single instance of an event, and that information should be on the ticked that is emailed/printed. Would I need to add these fields to a ticket type and therefore have one ticket type for set of information that needs to be collected?
3 - how to filter on is_ticket entity trait in views?
I already have views where I can filter on product types (as in drupal commerce products). I can't seem to find a way to filter a view by 'is a ticket'. With a contextual filter of 'Default variation: Product variation', I can add the following field to a view "(Default variation: Product variation) Product variation relationship: Is ticket" - but nothing is available for the filters pane? What do I need to do to filter a product view on 'just tickets' , or will that require the entity being updated to publish some information so views can use it?
Thanks in advance!
Active
2.0
Documentation