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
One Attendee's event doesn't appear in database after purchasing two events with | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › One Attendee's event doesn't appear in database after purchasing two events with

One Attendee's event doesn't appear in database after purchasing two events with

Posted: June 27, 2013 at 2:57 am

Viewing 3 reply threads


art4srl

June 27, 2013 at 2:57 am

Hi,

is the second time I have a problem like this: one user buyed 2 events with MER, making 2 different payments with PayPal (I have 2 transactions) but in the “Event overview” – “All attendees” I have only one registration, and my user (with EE Members) can see only 1 event on his page.
Also in the database I have only 1 event for this attendee.

This happened (like the other time) when I was connected to the EE Background “Event overview” – “All attendees” .

I wonder if something similar happened to someone else and how can resolve this!

Thank you, Marco

Wordpress 3.5.1
EE v. 3.1.33.3p
MER v. 1.0.4
WP User Integration v. 1.9.7.2


Jonathan Wilson

  • Support Staff

    •

June 27, 2013 at 1:49 pm

Hi Marco?

Are you using Roles and Permissions? You may want to deactivate it if you aren’t. It can prevent users from seeing each other’s events.


art4srl

July 1, 2013 at 6:18 am

Hi Jonathan,
I have Role and permission, but I don’t need it, so I just deactivated.
Searching in the forum I found something aout my problem, and it’s probably because with MER my users can buy 1 ticket and pay it via paypal, then go back with the browser to the registration page and buy the ticket for another events, and pay with paypal. This action delete the first ticket and replace it with the second (becouse the user is in the same session).

So admin (I) and users (members in “My Events” page) can see only the second ticket purchased.

I don’t know if the last udpdate Change Log – June 22, 2013
3.1.33.3
– Adds improvements to payment page so people get warned not to click the back button (which can delete their registration.

will solve this problem!

Thanks, Marco


Josh

July 1, 2013 at 11:07 am

Hi Marco,

In this case I think the update will solve the problem because it warns the member to not use the back button if they try to use back button after completing the registration.
Viewing 3 reply threads

The support post ‘One Attendee's event doesn't appear in database after purchasing two events with’ 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 Josh 11 years, 6 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server