New features: remove “Use Attendee #1’s information for ALL attendees,” add attendees to past events, and more

In this post, we’ll highlight a few improvements that are now available in Event Espresso. We are still working on major new features like Recurring Events, but we like to sneak in some useful upgrades here and there too.

Filter by venue in the events overview screen

Do you host events such as classes & workshops at different event locations? Now you can see events for a specific venue in your events overview screen.

From your WordPress dashboard, go to Event EspressoEvents. The new dropdown menu for All Venues appears between the “Show Active/Inactive” and “All Categories” dropdown menus.

Click on All Venues and choose a venue. Then click on the Filter button.

You’ll then see events for a specific venue. Afterward, you can click Reset Filters to see all events again across your venues.

Remove “Use Attendee #1’s information for ALL attendees” through the registration form settings

Event Espresso supports group registrations where multiple attendees can register at the same time. Group registrations can be enabled for an event by checking off the Personal Information group under Questions for Additional Registrants in the lower right area of the event editor and saving changes.

Once this is enabled, then a “Use Attendee #1’s information for ALL attendees” option will appear under the first attendee’s registration questions during registration checkout.

Do you need individual names and email addresses for each attendee or registrant? Turning this option off can deter attendees from using the same contact details for each additional registration in the group.

Go to Event EspressoRegistration Form. Then click on the Reg Form Settings tab at the top of your screen. Scroll down to Copy Attendee Info Settings and update the setting for Allow copy #1 attendee info to extra attendees to No. Then save changes by clicking on the Save button.

Add attendees to events that have already past

Most event organizers set a deadline for registrations hours, days, or weeks in advance of the event so they can finish their preparations for the event. But if you accept walk-in registrations where you allow attendees to register in-person before an event starts, then it is a little more complicated because your registration period is already closed.

Does the process below for handling onsite registrations for expired events sound familiar?

1) Collect contact details like a name and email address from last-minute registrations on a list.
2) Temporarily reopen registrations after the event passes by updating the sell until date through the event editor.
3) Manually add attendees through Event Espresso.
4) Update your event to close registrations by changing the sell until date again.

You can now skip steps 2 and 4 and cut your workflow in half. If an event is expired, then it will allow you to register additional people manually through your WordPress dashboard.

Manual registrations can work well if you have a small number of walk-ins on the day of the event.

Bonus: What if you have a large number of additional registrations? Or what if your organization is growing and hosting multiple events each week?

You can still manually add registrations one by one, but it will take some time.

With our Event Espresso Importer, you can quickly import a list of attendees into an event through a CSV file. And you’ll save a lot of time over adding each registration separately.

We have some big feature enhancements coming in the future, but which of these enhancements are you looking forward to using with your events now?

Related Articles

4 thoughts on “New features: remove “Use Attendee #1’s information for ALL attendees,” add attendees to past events, and more

  1. In “Remove “Use Attendee #1’s information for ALL attendees” through the registration form settings” the following section is incorrect:

    “Go to Event Espresso → Registrations.”

    It should read: “Go to Event Espresso → Registration Form.”

Share a Reply or Comment

Your email address will not be published. Required fields are marked *

Need help with Event Espresso? Create a support post in our support forums

Do NOT follow this link or you will be banned from the site!
[gravityform id=116 title=false description=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_116' ><form method='post' enctype='multipart/form-data' id='gform_116' action='/2019/11/new-features-remove-use-attendee-1s-information-for-all-attendees-and-more/'> <div class='gform_body'><ul id='gform_fields_116' class='gform_fields top_label form_sublabel_below description_below'><li id='field_116_5' class='gfield gfield_contains_required field_sublabel_hidden_label field_description_below gfield_visibility_visible' ><label class='gfield_label gfield_label_before_complex' >What is your first name?<span class='gfield_required'>*</span></label><div class='ginput_complex ginput_container no_prefix has_first_name no_middle_name no_last_name no_suffix gf_name_has_1 ginput_container_name' id='input_116_5'> <span id='input_116_5_3_container' class='name_first' > <input type='text' name='input_5.3' id='input_116_5_3' value='' aria-label='First name' aria-required="true" aria-invalid="false" placeholder='First name'/> <label for='input_116_5_3' class='hidden_sub_label screen-reader-text'>First name</label> </span> </div></li><li id='field_116_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_1' >What is your email address so we can follow up with you?<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_116_1' type='text' value='' class='medium' placeholder='hello@example.com' aria-required="true" aria-invalid="false" /></div></li><li id='field_116_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_2' >Tell us about your concerns below<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_textarea'><textarea name='input_2' id='input_116_2' class='textarea medium' placeholder='What kind of events are you planning?' aria-required="true" aria-invalid="false" rows='10' cols='50'></textarea></div></li><li id='field_116_6' class='gfield field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement</label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_116_6'><li class='gchoice_116_6_1'> <input name='input_6.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_116_6_1' /> <label for='choice_116_6_1' id='label_116_6_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_116_3' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_3' id='input_116_3' type='hidden' class='gform_hidden' aria-invalid="false" value='' /></li><li id='field_116_4' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_4' id='input_116_4' type='hidden' class='gform_hidden' aria-invalid="false" value='https://eventespresso.com/2019/11/new-features-remove-use-attendee-1s-information-for-all-attendees-and-more/' /></li><li id='field_116_7' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_7' >Phone</label><div class='ginput_container'><input name='input_7' id='input_116_7' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description__7'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_116' class='gform_button button' value='Send my message' onclick='if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} jQuery("#gform_116").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_116' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='116' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_116' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_116' id='gform_target_page_number_116' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_116' id='gform_source_page_number_116' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 116) {if(typeof Placeholders != 'undefined'){ Placeholders.enable(); }} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [116, 1]) } ); </script>