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 best way to do this? still new to ee... | Event Espresso - Staging Server
We have an event that we are currently taking registrations for. Now we want to allow people to purchase additional event options and declare specific dietary and other needs based on their participation level.
it seems like the best way to do this is to create new events with question groups for the ‘packets’ of info i’m trying to gather and then invite registrants to sign up for these new ‘events’.
my question is… is there a way to link it to the main event database so their answers to these new questions are linked to their original registration id / downloadable in the attendee exports or will i have to do magic behind the scenes to combine the exports for each ‘event’?
There isn’t a way to link event data like that, so you would either need to use “magic” or an alternative system.
One way to do it would be via questions and the Price Modifier add on (available via the Pre Release section in your account page).
The questions can help gather the extra info needed, and the Price Modifier (which also uses questions) can be used to modify the ticket price.
Two caveats of this is that Price Modifier requires Multiple Event Registration to be used, and Price Modifier can not accept values of 0.
Another consideration, is that we do not have conditional questions, so you would either need to put a note on the question group that these only need to be answered if XYZ is bought, or apply a custom JavaScript solution to hide the questions as needed.
The support post ‘best way to do this? still new to ee…’ 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.