|
silveroak
|
July 15, 2015 at 7:36 pm
I read https://eventespresso.com/topic/is-it-possible-to-not-require-email-address-for-additional-attendees/ which shows a code segment that allows to hide email from additional attendee field. My question is where do I put this code segment?
|
|
Tony
|
July 16, 2015 at 3:40 am
Hi Abhishek,
That code is for EE3, I can see on your account you have EE4.
EE4 handles registration data differently, if you do the above and hide the email address within the personal info details, then provide dummy data for the additional registrant emails EE4 will create multiple ‘contacts’ from that data (which will get more complicated to manage).
However EE4 allows you to request information from additional attendees without requiring the Personal Info group (EE3 didn’t allow this which is why that work around was used)
So you can create an additional question group and 2 additional questions, (First Name, Last Name) and then require just that question group for your additional attendees, would that work?
*Note in this example the registration would still be under the ‘Primary registratants’ contact info, but the additional info would be saved within the registration itself.
|
|
silveroak
|
July 16, 2015 at 2:01 pm
Hi Tony,
We are currently using the approach you have suggested. The issue we are encountering is that all messages, thank you page, and admin screen lists primary registrant on all registrations. This is causing confusion among customers and staff. Currently the only way to easily view additional attendee name is to export registration data in csv. Not the best solution.
Can we modify code segment that is I refer to in my post to default primary registration email on all attendee email and keep it hidden. Please elaborate on your comment that “EE4 will create multiple ‘contacts’ from that data (which will get more complicated to manage).”
Thanks
|
|
Tony
|
July 17, 2015 at 2:40 pm
Please elaborate on your comment that “EE4 will create multiple ‘contacts’ from that data (which will get more complicated to manage).”
When you create a registration within EE4 it uses the Personal Information fields to create a ‘Contact’ within EE4. Your registrations are then assigned to that contact.
For example go to Event Espresso -> Registrations -> Contact list (tab)
You’ll see a list of all the ‘contacts’ created within EE.
Now click on one of those and you’ll see a list of all registrations assigned to that contact – http://take.ms/YOn0I
Those are created for registrations made using different details, which yours will be (but will all be using the same email address for each group registration – the primary registrants)
I may have been a little presumptuous when I said it’ll make it more complicated to manage. One of the main issues here will be the primary registrant will receive multiple emails as they will receive each of ‘Registrants’ emails sent (because you’ll be using their emails for those contacts)
Basically EE4 currently expects all of the additional registrants to have the same details as the Primary (and will therefore deal with the multiple email issue within core) or for them to have their own email address so that the user receives their own email (the Primary registrant handles the payment info).
|
|
silveroak
|
July 18, 2015 at 6:12 pm
Hi Tony,
We are okay with primary registrants receiving more than 1 emails. Given that would you able to guide us on this.
Thanks
Abhishek
|
|
silveroak
|
July 24, 2015 at 8:19 am
Any update on this?
|
|
Tony
|
July 27, 2015 at 11:48 am
Apologies for the delay in getting back to you over this.
The code provided in the other thread was added by another user rather than ourselves. You would need the help of a developer to add this into Event Espresso as this is not something we can provide support for, although I did take look at the code and put up a quick example of how this can be achieved:
jQuery( document ).ready(function( $ ) {
$('.ee-reg-qstn-email').on('keyup change paste', function(e){
$('.ee-reg-qstn-email').val($(this).val())
});
$('.spco-attendee-panel-dv:not(:first)').each( function() {
$(this).find('.ee-reg-qstn-email').hide();
});
});
Do you have a developer on your team able to add this to EE?
|
