Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Same User, 4 Registrations, Only 1 Transaction | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Same User, 4 Registrations, Only 1 Transaction

Same User, 4 Registrations, Only 1 Transaction

Posted: September 3, 2013 at 2:10 pm

Viewing 4 reply threads


Brian Siddle

September 3, 2013 at 2:10 pm

Sorry, this is a bit of a confusing one and I’m not sure what else to do but get more ideas.

I have an event that originally didn’t have the shopping cart feature turned (it has since been implemented to make multi-registration life easier). We had a user that didn’t see the “add attendee” button and registered 4 separate times, 1 person each time for the same event within the span of 6 minutes. Nothing strange here yet other then they did more work then they needed to.

When we look at the attendee list this person is accounted for only once and for 1 ticket. At first I thought it was because subsequent registrations were under different names. Then I looked at the transaction confirmation emails I received. There are 4 separate Transaction ID’s through our payment system that we received confirmation emails from. He registered each time under the same email and name. Each one has a different transaction ID as mentioned BUT the same Customer ID. Which wouldn’t make sense if he registered 4 separate times?

So this is where I am at. I did a data export of every last attendee as well to make sure his name is under a separate event and the other 3 Transaction ID’s are no where to be found and the event that was registered to only has him once.

Does this make any sense or trigger thoughts on possible issues. Sorry to bother but I was hoping someone may have an idea on the cause of the glitch.


Anonymous

September 3, 2013 at 3:35 pm

Hi Brian,

Can I ask which version of Event Espresso you are running?

The issue you are having is caused when users click the back button to re-register other attendees. Basically their session is still active so each new registration overwrites the previous one (that is why the Customer ID is the same).

The latest version of Event Espresso displays a warning to the user when this could happen to help prevent it, older versions don’t have this.


Brian Siddle

September 3, 2013 at 3:51 pm

Running 3.1.35-ALPHA
It makes sense to me and it was a thought I had early on. So will an update with my current version fix that or is it possible the person did not see the message or ignored it?


Anonymous

September 3, 2013 at 4:11 pm

It would appear that version has the warning already.

We do see users ignoring the message and continuing on so it is very possible/likely.


Brian Siddle

September 3, 2013 at 4:16 pm

Thank you for your time!
Viewing 4 reply threads

The support post ‘Same User, 4 Registrations, Only 1 Transaction’ 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.

The original Forum description...

Status: closed

Updated by Brian Siddle 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server