Ticket

Ticket provides conditional access and permissions for Registrations.

Tickets can come from:

• Purchasing with Drupal Commerce
• Joining a digital queue
• Entering / scanning a code
• Invitation via custom link (email, text etc.)
• A user with permissions granting it to your Drupal account
• Functionality you add with a custom module

User-defined Ticket types set these source's requirements when granting access to registrations.

Version 3.x Development Status

Version 3.x for Drupal 10.1+ is under active development on Drupal Code.

3.x (D10.1+) Dependencies

• Registration through ticket_registration

Optional Supported Integrations (3.x)

• Commerce through ticket_commerce
• Event through ticket_event

Supported Migration Paths (3.x)

• Event Ticket through ticket_migrations
• Ticket v7.x-1.x to v2.x to v3.x

2.x (D8/D9/D10) Dependencies

No external dependencies for this version.

1.x (D7) Dependencies

• date
• entity
• multiple_entity_form
• views
• ctools (Optional - required for Ticket Registration States)
• entity reference (Optional - required for Ticket Registration States)
• rules (Optional - required for Ticket Rules)

Configuration Overview

1. Enable the Ticket module.
2. Add a Ticket type field to the content type where you will be providing tickets. Note that the Ticket type field can be added to any fieldable entity. This will typically be an event node content type, but your use case may differ.
3. Create a new content, filling in the information for the ticket type.
4. Your new content will have a Ticket tab. Click the tab to view information about the Ticket types.
5. From this tab, you can also manage the fields for your Ticket types. These fields wlll be presented to users when they register for a ticket of the given Ticket type.

Additional Resources

Watch a short video demo/overview of the module.