|
tyler
|
June 24, 2020 at 2:38 pm
Our client contacted us today because someone registered for their site, but the confirmation was sent to a previous attendee.
I’ll post additional details privately, but from what I can see by looking at the DB, it appears that EE has begun reusing the ATT_ID and so there are multiple people with the same ATT_ID
|
|
tyler
|
June 24, 2020 at 2:39 pm
This reply has been marked as private.
|
|
tyler
|
June 26, 2020 at 9:55 am
Circling back here as the client is concerned about registrations being mixed up due to this issue. Please let us know. Thanks!
|
|
Tony
|
June 29, 2020 at 6:46 am
Hi tyler,
This is strange because the ATT_ID value is the ID of the espresso_attendee custom post type in the wp_posts table, EE simply can not start reusing them as the row ID is an auto-incrementing ID so adding a new row will always have a new ID.
The client upgraded from EE3 to EE4 several months ago and I’m wondering if that plays a part it what’s going on here.
Because of the above, this again seems unlikely as the espresso_attendee row is inserted into wp_posts and then the ID saves to wp_esp_attendee_meta table you are viewing.
Have the database tables ever been reset/altered? The only way I can think of this happening is if the WP tables were rest, but wp_esp_attendee_meta was not.
Can you send me a copy of the database itself?
|
|
tyler
|
June 29, 2020 at 7:41 am
Hey Tony, thanks for the note back. The database has never been altered. Happy to send a copy along, just let me know where to send it!
|
|
tyler
|
June 29, 2020 at 7:52 am
This reply has been marked as private.
|
|
tyler
|
July 1, 2020 at 7:16 am
Have you had a moment to review the db?
|
|
tyler
|
July 6, 2020 at 8:55 am
Could you please let us know what you see?
|
|
Tony
|
July 6, 2020 at 9:40 am
Hi Tyler,
My apologies for the delay, there’s a lot of info to go through in your DB.
EE isn’t ‘reusing’ ID’s but somewhere along the way, something is returning the ‘wrong’ ID. Is there any caching enabled on the site/server?
There’s definitely something strange going on with the site as it appears every attendee has a duplicate entry and then fairly recently entries started referencing ID’s that don’t match their attendee meta.
I’ve requested some feedback from out developers to see if hey can think of a cause for this.
|
|
tyler
|
July 6, 2020 at 9:43 am
Hi Tony,
The site is hosted at WPEngine and has been hosted there since its inception back in the EE3 days (6 years or so). Caching has previously been disabled for EE pages. Again though, they just saw this start happening and as far as I know nothing has changed other than the update to EE4 a couple months back.
|
|
tyler
|
July 7, 2020 at 10:35 am
Hi Tony,
Any word from the developers? Thanks!
|
|
Tony
|
July 10, 2020 at 5:11 am
Hi Tyler,
We spent some time working through this and double checking the logic and the short answer is it doesn’t make sense, the logic within EE checks for a current EE_Attendee before we create one, yet you seem to have 2 of every one.
The ATT_ID used on some registrations matches and then the ATT_ID used on others simply does not, it’s not a case of reusing the ATT_ID but that the ATT_ID from one contact has been saved to another and again, that doesn’t make sense.
Is it possible to take a look at the site itself?
Or can you create a dev copy we can have a look at and do little debugging on to see what is going on?
|
|
tyler
|
July 10, 2020 at 10:49 am
Hi Tony, absolutely. I’ll set up a dev copy. What’s the best way to send the credentials?
|
|
tyler
|
July 10, 2020 at 4:17 pm
This reply has been marked as private.
|
|
tyler
|
July 14, 2020 at 8:40 am
Please let me know if you were able to log into the dev site!
|
|
Tony
|
July 15, 2020 at 3:00 pm
Hi,
Yes we have access to the dev site and are investigating.
This isn’t something we can rush as we need to find the cause first, otherwise you’ll likely be back in the same situation shortly after.
|
|
tyler
|
July 22, 2020 at 10:47 am
Thanks, Tony. When do you think you’ll be able to give us an update on your findings?
|
|
Tony
|
July 22, 2020 at 12:26 pm
The tough part for this is having spent some time looking over your site, there isn’t anything standing out for a cause.
Nothing is hooking into the requests and as far as I can tell there isn’t anything on the site itself that would cause this, which then leaves caching on the live site but I was hoping for a better answer than that.
Fixing this also isn’t going to be simple as the ‘wrong’ ATT_ID is being saved with no obvious method to know which registration ID should be for which attendee.
So whilst I don’t have a solution for you just yet I just wanted to let know we are investigating and haven’t forgotten about you 🙂
|
|
tyler
|
August 17, 2020 at 10:29 am
Hi Tony, it’s been a few weeks and so I wanted to check back in on this. I know you said the team hadn’t found anything but was still looking. You had also alluded to possible caching, but, again, this client’s site has been on WPEngine utilizing EE for well over five years. All required caching blocks for EE has long ago been set up. This problem just started popping up right before I opened this topic up. Any insights you can provide would be great. Thanks!
|
|
tyler
|
September 16, 2020 at 12:29 pm
Hello, any updates/ideas on this one?
|
|
tyler
|
September 30, 2020 at 5:33 pm
Hi, the client has noticed some other weird crossovers and would like to get to the bottom of this. We haven’t heard anything back recently. I’m going to post some additional documentation privately, but the client would like to be able to have your team take a closer look – do you suggest the 30 minute or 90 minute paid token?
|
|
tyler
|
September 30, 2020 at 5:36 pm
This reply has been marked as private.
|
|
Tony
|
October 2, 2020 at 4:55 am
Hi Tyler,
Firstly, my apologies.
I think I got a little too fixated on trying to fix the problem with the details I already had here and I’ve delayed replying to this thread a few times now as, in short, I haven’t been able to find the cause so far. I have been investigating and reviewing various sections of our code but all of those have (eventually) led to a dead end and I didn’t want to reply with “all I can think of is caching, but I know you’ve said that it is disabled”.
I’m going to step back and take a fresh look at the above today.
With regards to a support token, I can’t say for sure if I can get to the bottom of this within any of those timeframes. If you’d like to purchase a single token I can at least start investigating.
|
|
tyler
|
October 2, 2020 at 9:07 am
Thanks, Tony. Appreciate the note back.
I purchased a support token and filled out the form. (Just a note here that you may want to take down the old support token page which is still available at https://eventespresso.com/support/premium-support-options/)
Everyone is hoping you’re able to get to the bottom of it. There are other examples as I’m sure you’ve seen as you’re looking through the db/records.
If you need any other access or assistance, please reach out.
The client is anxious to get these crossed data issues fixed and we’re hopeful your investigation will be fruitful.
Thanks!
|
|
tyler
|
October 2, 2020 at 9:07 am
This reply has been marked as private.
|
|
tyler
|
October 5, 2020 at 7:46 am
Hello! Just checking in to see if you’ve had time to further investigate this issue. Thanks!
|
|
tyler
|
October 6, 2020 at 7:39 am
This reply has been marked as private.
|
