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
Most recent attendee being over-written! | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Most recent attendee being over-written!

Most recent attendee being over-written!

Posted: January 9, 2013 at 5:13 pm

Viewing 4 reply threads


Shannon Bentley

January 9, 2013 at 5:13 pm

Here’s a weird glitch…I’ve been trying to test my PayPal payment processing (which still isn’t working BTW – neither the customer or the IPN is being returned to my website)…anyway…every time I go to register an attendee, they get added to the attendee list, but they REPLACE the last attendee I had signed up (ie the previous person disappears). Is this just a cookie/shopping cart glitch…or is it a real problem???


Josh

January 9, 2013 at 6:12 pm

With PayPal’s IPN and return page not working, it sounds like the URL’s getting sent to PayPal are not correct. Can you post a link to the registration page so we can take a look?

With the most recent attendee being over-written, this will happen if, and only if, the default payment status is set to incomplete and the registration limit is close to being reached. For example, if the attendee limit is set to 10, and there are a few incomplete (non-paid) registrations in the system, a paid registration will take one of the unpaid registration’s place. If you set the default payment status to pending, all registrations will count toward the limit.


Shannon Bentley

January 9, 2013 at 6:25 pm

I think it was a web browser cookie thing. If I closed all my browsers and started the whole process again, it added the new attendee instead of replacing.

You will be happy to know I actually just got the payment process working too – what a learning curve! Few things that contributed to the problem…
1) I didn’t realize that I had to have my Sandbox PayPal account e-mail address in the PayPal settings instead of the real one (duh!)
2) I can’t use the Force “HTTPS on Return URL” or I get that crazy error.
The ONLY issue I’m having now is that stupid warning that the page the user is going to is not secure.
Will this disrupt payment in any way? If they click “do not continue”?


Josh

January 9, 2013 at 6:44 pm

They will not get to registration confirmation screen if they don’t return from PayPal.

If you install a SSL certificate for the domain, then set the Force https on return option, they will not get the insecure page warning.

You can get a free SSL cert from startSSL.com, or buy one from your host or domain registrar.


Shannon Bentley

January 9, 2013 at 6:56 pm

They actually still do get back to the confirmation screen – is that weird? I’m going to install a SSL certificate though…just in case. Thanks so much for all your help – you guys are great!
Viewing 4 reply threads

The support post ‘Most recent attendee being over-written!’ 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 Shannon Bentley 12 years ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server