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
Group Booking - Can we pre-populate toggling information from primary user's ? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Group Booking – Can we pre-populate toggling information from primary user's ?

Group Booking – Can we pre-populate toggling information from primary user's ?

Posted: July 26, 2013 at 7:20 pm

Viewing 6 reply threads


Jeyatheepan

July 26, 2013 at 7:20 pm

1. We use seating chart for event booking. E.g https://www.tamilaustralian.com.au/booking/events/?ee=23
2. Group Registration Max is set to 10.
3. Now, user buying 10 tickets has to enter Personal Information (First and last name, email and mobile – 10 times when he toggle each time )
4. When toggling this information should be pre-populated from 1st attendees personal information.

Can we do this ?


Anonymous

July 26, 2013 at 7:37 pm

Hi Jeyatheepan,

If you do not need the extra information for the other attendees you can stop this info being collected altogether.

If you edit the event, look on the right hand side (same area you set the Max Group Registration) you will see ‘Additional Attendee Registration info?’

If you set this to ‘No info required’ and update the event, when you return to the registration page you will have one form, with a drop down for number of tickets.

Is that what you are looking for?


Jeyatheepan

July 26, 2013 at 9:11 pm

Not quite correct. I am using seating chart and users have to select those seats individually. With Seating chart enables I tried enabling “No info required” but when I save the event it reverts back to “Additional Attendee Registration Info” ..


Seth Shoultes

  • Support Staff

    •

July 27, 2013 at 11:27 am

Hi Theepan,

I believe this is a limitation with the Seating Chart add-on. Since we require attendee information for each attendee record, that is stored in the database, the developer that created this add-on for us decided to make it mandatory for each additional attendee to enter their details.

I made an adjustment, to overcome this issue, for another Event Espresso user. I will see if I can track down the files with those changes, if you like, but please be aware these changes were made to the core plugin. So it may prevent you from updating in the future. However, I will bring this up with our developers to see if we can get this added as a core feature.


Jeyatheepan

July 27, 2013 at 4:00 pm

Hi Seth – Many Thanks. I think my guys managed to do it .. :-) However it would be good to get this as a core feature. Many Thanks


Seth Shoultes

  • Support Staff

    •

July 27, 2013 at 4:04 pm

Great! Thanks. I added it to our weekly dev meeting for discussion.


Seth Shoultes

  • Support Staff

    •

July 30, 2013 at 10:27 am

Hi Theepan,

Do you mind sharing your code with us? That way our devs can check it out and see if we can include it in a future version.
Viewing 6 reply threads

The support post ‘Group Booking – Can we pre-populate toggling information from primary user's ?’ 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.

The original Forum description...

Status: closed

Updated by Seth Shoultes 11 years, 7 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server