How to create ticket dependencies in Dryfta registration?

Is it possible in Dryfta event management to make a ticket type dependent on the purchase of another ticket type, for example, allowing someone to purchase a post-conference or PhD-course ticket only if they have also purchased a student registration ticket?

In Dryfta, it is not possible to directly make one ticket type dependent on the purchase of another ticket type. However, you can implement functionality where ticket types are displayed or offered based on answers selected in the registration form. For example, you can use conditional form fields to display specific ticket options only when certain criteria are met (such as selecting 'student' as the registration type). 

Furthermore, Dryfta has introduced a feature allowing you to create rules under ticket settings that enforce purchasing dependencies between tickets — that is, you can configure rules to allow or disallow purchasing certain tickets together. 

To use this, go to the Ticket setup, click on Settings, and create rules to control ticket purchase dependencies. This is the recommended way to enforce that a PhD course or post-conference event ticket can only be purchased if the student registration ticket is also selected. 

Please note that conditional questions in the registration form can be set to show or hide tickets accordingly, but the dependency enforcement is handled through ticket purchase rules. If you need to make a ticket mandatory or ensure certain checkboxes are selected at checkout (e.g., the 'student registration early bird' checkbox), this can be managed through the ticket purchase rules and form configurations. 

If you are encountering issues with dependent questions not appearing for rule setup, ensure that child fields are included in the ticket rules as well. 

For any advanced or custom dependency logic not covered by current features, you may need to contact Dryfta support or check if new feature releases include this functionality.