|
Joshua Dickard
|
September 16, 2019 at 8:33 am
We are having issues where one person will go to register, but another totally different name shows up on their paid invoice. They are basically paying the registration fee for someone else. We have verified that both names are actually trying to register, but somehow the records are being crossed. We are using Authorize.net AIM to process payments. I have caching turned off for all event pages and I have disabled Memcached. Understandably, this is causing us a huge headache as well as causing our registrants to worry about card fraud, etc. Please help!
|
|
Josh
|
September 16, 2019 at 9:44 am
Hi,
This is the kind of thing that can happen if some (but not all) of Event Espresso’s database tables were reset or emptied. So for example if someone registered for an event last year and their registration ID was 123, then then the _esp_registration table was emptied and started over at 1, then next registration ID 123 would share details with the prior registration (where other details come from relationships with other database tables).
Are you aware of any work being done on the site where some of the tables may have been reset?
|
|
Joshua Dickard
|
September 16, 2019 at 9:58 am
No, there is no work being done that would cause that. It isn’t everyone; just a few people this has happened to.
|
|
Josh
|
September 16, 2019 at 10:04 am
It would have been work that was done. For example, are the registrations from the prior year’s conference still in the database, or were they deleted?
|
|
Joshua Dickard
|
September 16, 2019 at 10:17 am
They are still in the database.
|
|
Josh
|
September 16, 2019 at 10:33 am
Can you clarify a bit about this?
We have verified that both names are actually trying to register, but somehow the records are being crossed.
So are they actually trying to register at about the same time? If that’s the case, then it could be a caching problem, or a problem with the way PHP sessions are set up on the server. Basically Event Espresso 4 relies on the Session ID to be unique for each visitor. If the server is assigning two different visitors the same Session ID, and there are two registrations happening at the same time, one will overwrite the other.
Can you contact your web host to see if there’s any caching happening at the server level that could affect PHP sessions?
|
|
Joshua Dickard
|
September 17, 2019 at 8:43 am
I have contacted our web host and had them ensure that all caching is disabled for the account. I will keep my eye on it and see if we have any further issues. Thanks!
|
