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 Additional Questions after Registration | Event Espresso - Staging Server
One difficulty we are having … We would like to limit the number of questions people are asked when they register for our event and allow them to answer additional questions (such as which sessions they would like to attend) at a later date.
Is this possible? … or do we need to ask all the questions when they purchase their registration?
This really depends on how you want the data stored and how your users are being dealt with on your site.
For example, you could just not have the questions (except the basic core ones) on the registration form and then email them for question answers.
You could do the same as above but have the questions marked as Admin only so the user never sees them, but you can input the answers into the attendee record from the admin dashboard.
With the questions being answered to begin with, the onus is on the admin to update or edit the responses.
Thank you for the info. We’d really like to minimise the admin work and have the users enter their details and options. I guess what I’m looking for is the option to setup the info in the database and then only ask a subset of questions at registration allowing for user sign-in at a later date to fill in the remaining details.
Sounds like the only option is to ask all the questions up front so that the fields are set in the database for every registrant. Can you please confirm that this is the case and there are no other options?
The support post ‘Additional Questions after Registration’ 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.