Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Presales question - custom data capture based on ticket type | Event Espresso - Staging Server
We have an event with three ticket types. Full, Student and Society.
I need to be able to purchase tickets for multiple people. e.g. for me and my PA.
Based on the ticket type I then need to capture additional information.
e.g. for a student I need to ask who is the supervisor but for society i do not.
is this possible?
is the software open source so we can customise if we need to?
We do not have conditional questions based on ticket type currently. It is likely possible with some customisation (maybe even just some JavaScript) but would not be something we could officially support at this time.
Conditional questions have been requested previously and I will add this post to the features requests.
The software is open source and you can customise it if you wish, a lot of the functions within Event Espresso are ‘pluggable’ and you can therefor alter the functions fairly easily.
Having said that, please bear in mind that whilst we will do our best to help with problems we can not officially support customisations, there are just to many variables to take into account so you may also need the help of a developer.
Viewing 1 reply thread
The support post ‘Presales question – custom data capture based on ticket type’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.