Support

December 27, 2018 at 10:01 am

Hi,

First, you can add the following to your email message templates:

https://gist.github.com/lorenzocaum/9548ac6128c98320692cd623f3481271

This will give them a link to a page where they can click “edit info” links that appear next to each ticket.

If these are existing registrations, you’ll need to create new contacts. You create new contacts and update the additional attendee name(s) by going to Event Espresso > Registrations, then click on the additional registration (labeled 2 of 2) you want to change, then click on the “Create Contact” button. The “Create Contact” button will be in the Contact Details box.

Going forward for new registrations, if they do not know the names of all attending, they’ll need to input unique placeholders for each additional attendee. Then when they’re ready to update the names they can use the link that’s included in their registration email.

January 2, 2019 at 6:32 am

Hi there,

You can use a snippet like this:

https://github.com/eventespresso/ee-code-snippet-library/blob/master/checkout/tw_ee_force_unique_emails_for_registrations.php

Place that code within a custom functions plugin on your site, we have some documentation on creating one here:

https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/

With that in place EE will block registrations if they have the same email address as the ‘primary registrant’.

January 2, 2019 at 11:23 am

Ok so what I see here is forcing someone to use multiple email addresses to register BUT if someone does not know who else will be attending at the time and they don’t have 30 or even 10 email addresses this won’t work for most people.

If they know they’ll be changing the names/emails etc, why would they not just use dummy content and then update it later?

You have the option in EE to ask questions for only the primary registrant or all registrants, if you ask the questions for all registrants, they need answering (if they are set to required).

Are you requesting the ‘personal information’ question group for all registrants?

Why can’t each ticket purchase create a unique ID instead?

You’ll need to provide more details on this as it’s not clear what you are looking for. Every ticket selected within EE creates a registration and every registration has its own ID, so it already has a unique identifier, but that doesn’t seem to be what you are looking for.

In relation to you question, what is a unique ID, how would it be set and what exactly would it be used for?

January 3, 2019 at 4:30 am

In the scenario you are solving for unique id’s on each ticket by forcing a different email address for each ticket purchased…correct?

Unique ID? No, but I suspect you are referring to something different than I which is why I asked above for you to clarify on what you mean by ‘unique ID’.

Each registration has its own row in the database and therefore has its own ID for that row, they also have a unique ‘REG_ID’ field separate from the row’s ID.

If I am buying 10 tickets to an event and do not know who will be getting those tickets at the time I purchase I won’t have 10 unique emails to provide the system. So if I use my own information 10 times I will get 10 confirmation emails – correct?

No. EE won’t send a duplicate of the same email 10 times, if you use the same email, you’ll get a single registration related email.

Each of those emails to the same single email address will have a unique code for the ticket – correct?

There will be a single email.

Each ‘ticket’ (printable ticket?) will have a unique ID though.

So if that is the case and I use the link in the email that you provided me in another ticket to change the registrant to Rob Thomas at his personal email address that would work – correct?

Can you provide more details please?

How are you wanting it to work?

Where I stumble is creating something unique at the time of initial purchase. The unique ID is in that email that was sent. Even though I got 10 emails there are 10 unique ID’s – is that correct?

What are you using this for? You may be able to use the REG_ID field I mentioned above, but I need more info on what you are trying to do.

—

If that is not correct I need to solve so I can purchase 10 tickets and be able to assign them to unique people, with unique email addresses prior to the event.

If a user selects 10 tickets and additional registrants require the personal information question group (meaning first name, last name and email will be required) but they don’t know the full details for each individual registrant at the time, they can use ‘their’ details should they wish, then use a link from the email to edit them later should they need to.

Is that what you are looking for?

January 4, 2019 at 4:46 am

How can a purchaser access their tickets and reassign them to new people with unique email addresses?

They need to use placeholder text during the initial registration, then use the link Josh provided in the email to edit the registration details later.

If they use the same firs name, last name and email address for each individual registration, all of the registrations will be assigned to the primary registrants contact, meaning to then edit the details late you (the admin) needs to create a new contact for that registration (which Josh mentioned above).

January 9, 2019 at 5:24 am

So you want the user to be able to use the same email for 10 registrations, they receive 10 emails with the exact same details (even if the name is different, its effectively the exact same email) and possibly a link to edit the details for all of the details in each email (meaning the link is the same for each email).

I’m not sure why Event Espresso would do that? That’s duplicating the email 10 times rather than a summary of 10 registrations within a single email.

—

In order for EE to send an additional email from a group registration, the email address must be unique to the others in the group, otherwise, it’s a duplicate email so EE doesn’t send it.

Not only that, but if they use the same details for each registration, each of those registrations will be assigned to the same ‘contact’ within EE and the contact is where EE pulls the Name and Email address from for each of the registrations. This complicates your setup as now you have a 1 to many relationship between your primary contact and the registrations in your group, then if you want to change the details of one of those registration you need to break it out into a new contact so that the specific registration you are editing uses that contact, thats not something you can do on the front end.

—

So to confirm, with a group of 10 registrations you want the user to be able to use the same details for all registrations and then receive 10 emails all with the exact same details.

Then you want the user to be able to edit each individual registration so they can change the Name and Email address on any/all of the registrations and then I’m assuming you would want them to be able to trigger the email again for that specific registration so that it now goes to the ‘correct’ user?

If so, the only way to do that without custom development is to use dummy context in those fields when registering.

January 9, 2019 at 8:14 am

They’d find out the names and email addresses of the people attending before purchasing and use those during the registration.

EE isn’t intended to hold tickets until the primary attendee finds all of the details required for them to update later, the user would need those before purchasing. A workaround for the expected behaviour is to use the methods mentioned above.

January 9, 2019 at 10:05 am

what would it cost to custom design this?

Event Espresso staff are not available for custom design/development projects. What you can do is get a quote from one of the experts at Codeable.io. They’re positioned to build a custom solution to your specifications.

January 11, 2019 at 9:30 am

Quite likely the issue is the shortcode you’re using, or the message context you’re using, only shows one ticket, not all of the tickets.

So for example, if you’re using the Ticket Notice message type (or other message type) to send the links to tickets, you can check to see if it has the [TXN_TICKETS_URL] shortcode in it. That’s the shortcode that will output all the tickets for the transaction.

January 14, 2019 at 9:38 am

You could share access, but it sounds like you’re not using the Primary Registrant message context. So we could log in, and see that you’re not using the Primary Registrant context for the Ticket Notice message type, and that would verify what I’m thinking. Are you not using the Primary Registrant Context for the Ticket Notice message type? If not, then you can activate it then going forward, the primary registrant will get all the tickets in the transaction.

January 15, 2019 at 11:44 am

Hi,

The reason it’s not matching is because the screenshot is of the Settings page, and that’s not where you activate the Primary Registrant context. You can get to the the Primary Registrant context on the Default Message Templates tab. Once you’re on the Default Message Templates page, you can scroll down (and if needed, go to page 2) to edit the Ticket Notice message type.

January 16, 2019 at 6:53 am

Do you see how the “Primary Registrant” text has the color grey? That means that the Primary Registrant context is deactivated. You can activate that context by clicking on the text “Primary Registrant” (it’s a link), then input the [PRIMARY_REGISTRANT_EMAIL] into the To: field. Then you click the Save button.

What that will do is send a ticket notice email to the Primary registrant, and that email will include a link to see all tickets.

January 16, 2019 at 3:16 pm

Yes you can.

You click on the icon on the registrations admin page. You’ll send those to the Primary registrant (marked as 1 of 2) to ensure the Primary Registrant template was used for the email. Then to check what was sent, you go to Event Espresso > Messages > Activity.

January 17, 2019 at 8:08 am

1) Make sure the Primary Registrant context for the Registration Approved message type is activated
2) You go to Event Espresso > Registrations and click the icon for the row of the Primary Registrant