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
Event Registration - Multiple attendees | Event Espresso - Staging Server

Support

Home › Forums › Translations › Event Registration – Multiple attendees

Event Registration – Multiple attendees

Posted: August 29, 2013 at 2:50 pm

Viewing 1 reply thread


Kevin Clark

August 29, 2013 at 2:50 pm

We have pricing based off 6 attendees. Each additional attendee that is going there is a discounted price.

See here: http://screencast.com/t/fM9RwZYQI

http://screencast.com/t/2jcKYSEBU

We want it so that if the potential client selects more than one attendee – fields will show up for additional info. Example: First name / Last name.

However,we do not want there to be a standard field name for all six attendees if only 1 registers? So we need it to auto populate based on what is selected?

What is the best way around this?


Dean

  • Support Staff

    •

August 30, 2013 at 4:12 am

Hi Kevin,

There isnt any conditional logic currently.

I would suggest using javascript here. Add the 6 or correct number of name fields via the questions. Then use CSS to hide them. Use jQuery to display them depending on what ticket selection is made.
Viewing 1 reply thread

The support post ‘Event Registration – Multiple attendees’ 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.

Status: closed

Updated by Dean 11 years, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server