Support

January 26, 2016 at 5:01 am

Hi Irene,

1) What is the difference between a primary registrant and additional registrants?

The Primary registrant is the first attendee details entered into the registration form (by default the top registration form).

So if you select 3 tickets and request personal information for both the primary registrant and additional registrants, the user that enters their details at the top is considered the primary registrant.

Within EE the primary registrant is considered the user that will handle the payments, they will receive all payment related emails.

2) Here’s my situation: I run couples retreats. So the fee is per couple. And one person registers for them as a couple. But there are 2 people attending and typically each has a separate email addresses. Is there a way that I can get both of them signed into mail chimp so that when I send a informational group email to all people attending this retreat, each partner in a couple receives that informational email?

That should happen by default, each registrant that uses a unique email should be subscribed to the MailChimp list selected within the event editor.

However by default both of those users will receive an opt in email from MailChimp once they have registered onto your event that they must open and click to subscribe to your list. You can disable this through Event Espresso -> MailChimp -> Skip double opt-in emails. (MailChimp prefer you do not skip those emails)

Is the above not working on your site?

January 27, 2016 at 4:16 am

Ah ok, I think I understand how you have this set up.

Do you have a custom question group assigned to the Primary registrant to request the additional details for their partner? (if so that won’t work with Mailchimp)

Are the registration always for couples? No single person registrations at all?

In my situation the payment is per couple (not per attendee). I think I have it set up that the primary registrant not only handles the payment, but also gives the details (registers?)

This is normal within EE. Currently the primary registrant will always be an actual attendee so they register onto the event and handle the payment for the whole group.

Can you link me to an event so I can see the setup? You’ll likely need to change the way you request the details so that 2 tickets are purchased then both of the registrations details will be sent to MailChimp…. right now you have a single registration with additional details. EE can not send the additional details to MailChimp in that way, it needs to be an additional registration.

If I can see the event I can confirm how you have this working and what to change.

Also thank you for the feedback, we all appreciate it 🙂

January 28, 2016 at 6:26 am

Yeah so with the way you have it setup, you will always have a single registrant and that registrant will have custom questions assigned to its registration. I can see how your making it work but with that setup you can’t then send both registrants to MailChimp (because you actually only have one).

In order for it to work with MailChimp in the way you need you’ll need to move around the questions some.

I recommend setting up a test event so you can play around with this setup and work out what is going on there rather than on your main event.

The ‘Personal Information’ should request only the unique details needed from both registrants, like First Name, Last name & Email address. Then you can use the Address Question group that is also built into Event Espresso as a system group and request the address information for both Primary and Additional registrants, so you Event editor question groups would look like this – http://take.ms/XQFL4

Now you’ll need to setup the ticket editor to force users to select 2 tickets rather than 1, you can do this within the ticket editor – http://take.ms/qfupD

Se the Min and Max quantity for the ticket to 2. Meaning the user can select no more or less than 2 tickets (because it’s a single couples ticket) which on the front end looks like this – http://take.ms/OGNvb

(Note the price set on the ticket is per ticket, so for a couples ticket you’ll need to set the ticket price to 1/2 of the full value, as there will always be 2 tickets)

Does that all make sense so far?

At this point when your users register onto the event as a couple they are required to select 2 tickets, and both tickets will request First Name, Last Name, Email and Address details from both people.

On your site you have an ‘Additional’ section with questions for both people, this looks like 2 question groups ‘Additional 1’ and ‘Additional 2’. You can set this up as a single group just ‘Additional’ and request that group for both Primary and Additional. EE will then ask the questions in that group to both registrants.

One part that will remain is the ‘Information about us’ and ‘Terms of Service Agreement’. I would recommend leaving both those groups only assigned to the Primary Registrant.

So basically what we are doing the above is rather than creating a single registration and adding in the second persons details into that registration, we are splitting the registration into 2 registrations (as a group) and requesting the details needed for each registrant individually, any that apply to both or as a group can stay only attached to the Primary Registration.

Does that help? Please let me know if you have any further questions on any point (or all of it 🙂 )

February 1, 2016 at 2:58 am

I am wondering how the additional registrant will get the info into EE?

When the user selects their tickets and continue with the registration they will show as another registrant – http://take.ms/HeKf8
(I’ve shortened the questions in the screenshot to fit both into view)

Will each partner in the couple need to be present when the registration happens? Will the primary registrant complete the information for the additional registrant?

I’m not sure I understand what you are asking here?

The additional registrants details will be required during registration but can be provided by the user placing the registration.

February 2, 2016 at 3:32 am

You’re most welcome, Irene.

I had a quick look over your new registration page setup and it should work much better now. That setup should work fine with MailChimp and will also work better to keep track of your registration limits etc.

Nice job 🙂

February 2, 2016 at 3:56 am

Yes that’s the best way. You can also manually change the registration status within the admin, so you don’t need to actually pay.

However if you want to test the full user experience go with the above to do it properly.

You can also either set the event to be password protected or publish privately. Password Protected just meas you need to enter a password, private posts are only visiable to logged in users – http://take.ms/BX15r

February 4, 2016 at 7:56 am

HI Irene,

That basic settings link is for EE3, its slightly different with EE4.

Your thank you page should contain [ESPRESSO_THANK_YOU] not [ESPRESSO_PAYMENTS] (that’s an EE3 shortcode)

Can you edit your thank you page and double check that it is publicly published – http://take.ms/BX15r

February 4, 2016 at 8:40 am

Whats the URL for your thank you page please?

February 5, 2016 at 4:13 am

I don’t see any reason why I can’t leave this http://www.couplesinstepretreats.com/event-thanks/ as the new thanks page. Do you agree?

There is no reason why you can’t use that page.

From this page http://www.couplesinstepretreats.com/thank-you/ I removed the [ESPRESSO_THANK_YOU] short code. Above you note that there is a 301 redirect from http://www.couplesinstepretreats.com/thank-you/ to the home page. So seems to me that I can now just go ahead and delete that page. Do you agree?

Yes you can delete that page if you want.

However there is still this message: “A potential issue has been detected with one or more of your Event Espresso pages. Go to Event Espresso Critical Pages Settings to view your Event Espresso pages.” I expected it be gone. What gives with that?

I checked into another EE page:

http://www.couplesinstepretreats.com/transactions/

And that also looks like it has a redirect setup, you need to contact whoever setup the redirects and see why they are redirecting these pages as they need to be visible. The transactions page is needed for IPN’s (such as PayPal) to function correctly.

The notice will be showing because the transactions page can not load, you could again create a new page for this however this could just continue to happen as redirects are added. The 4 critical pages listed on the EE Crticial Pages tab must be publicly accessible and not redirect to the home page.

February 8, 2016 at 8:05 am

Hi Irene,

That indicates that there may still be a problem with one of the critical pages that help with registrations on your site. You can check in a few steps.

Go ahead and dismiss it by clicking on the x in the corner. Then go to Plugins –> Event Espresso and deactivate Event Espresso. Afterwards, immediately reactivate it through your Plugins screen.

Next, go to Event Espresso –> General Settings –> Critical Pages. You should see a status of green for the shortcode and visibility for each page.

Here is an example:

http://cl.ly/2P2a2p1e1S2a

—
Lorenzo

February 10, 2016 at 4:01 am

Hi Irene,

I’m glad its all working for you now. If you have any further problems at all please do let us know.

Have a great day 🙂