Posted: December 21, 2015 at 8:23 am
|
Hi, I need to know what the expected functionality would be when a registrant changes their email address via the ‘Click here to edit All Attendee Information’ link at the foot of the confirmation page. As far as I can see, the emails don’t go out again to the new address. Also, when I click on the ‘resend email’ link below the registrant details line, I get the following:
Thanks Geoff |
Hi Geoff, An email does not go out automatically when the details are updated. Are these steps accurate? 1) Complete a registration through the front-end of the site 2) Edit registration details 3) Return to WP dashboard and go to the registration details screen 4) Click to resend the registration details and messaging appears in the WP dashboard. What version of Event Espresso are you seeing this issue on? https://eventespresso.com/wiki/ee4-changelog/ — |
|
|
Hi Lorenzo, Thank you for your reply. Sorry, I should have included the version. It’s EE4 (latest – 4.8.27.p), WP 4.4–en_GB, X-Theme 4.2.2 (Child theme). I think the error message “This is a system page for displaying transaction information after a purchase.” is perhaps to do with the fact that the tickets are free. I’ve confirmed that if I follow your steps it does resend the event information. However, I suppose my client is wondering how they will know if a customer changes their details and therefore requires the email to be resent. Also, given that the error above is what happens when the registrant tries to click the button to resend their details, it looks bad to the end-user. Thanks Geoff |
|
Also – just to be clear, the link giving the error is the ‘resend email’ link under the registrant summary list on the confirmation screen. The link itself points to the following: /thank-you/?token=1-f3498fbc7d5ef4889f9bdca2bc14e449&resend_reg_confirmation=true |
Hi Geoff, The error when you click the resend email link should not be happening. Instead, it should just send an email and display a message that says “The message for this registration has been re-sent”. Is there a way we can investigate this further, perhaps a test event on your site that you can link to here? |
|
|
Hi Josh – sorry for the late reply on this. You could have a look at this event. http://scld.staging.wpengine.com/events/test-event-1-2/ Thanks Geoff |
|
Also – just select a standard ticket and then invoice as the payment type. Thank you once again. |
Hi Geoff, That event is sold out, can you upp the values on the Datetime/Tickets so we can run a registration please? |
|
|
Hi Tony, Once again – sorry for the late reply. That event should have places again. My clients were testing that day. Thanks Geoff |
Hi Geoff, This is actually not an issue with changing the details. Without changing the details if you take the same steps you’ll see the same problem, that link should trigger an ajax request to resend the messages it seems it’s not and is reloading the page with the parameters provided by the link which is why you get the error as the thank-you page doesn’t know what those parameters are. The reason for this is WPEngine block the Heatbeat API, the Javascript that loads on that page to catch when that link is clicked is currently dependent on heatbeat loading. I’ve created a ticket for our developers to investigate this and see how we can allow that link to work even if heatbeat is disabled. You’ll notice on the thank you page, currently you see ‘loading transaction and payment information…’ that never changes. That too relies on heatbeat. So to fix this on your site we have a snippet of code here: https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/#heartbeat You may want to contact WPEngine and have them enable heatbeat properly, but the function shown there should allows this to work for EE if you add it to your themes functions.php file or within a Site Specific Plugin. |
|
|
Thank you once again Tony for the fantastic support. That code snippet did the trick. I’m actually moving this site (and all my other sites) over to SiteGround, and I’ll ask them if they also block Heartbeat API by default. Best regards, Geoff |
The support post ‘Registration change of details’ 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.