|
Nick Putman
|
November 6, 2012 at 12:25 am
Hi,
On some of my attendee records I am seeing some strangeness. I am getting two fields for first name, last name and email address. Here is a screenshot of the attendee record from the admin that shows what I mean:
This is a registration for Eliza Johnson and yet my name and email address are showing up as well. The only thing I can think of is that this is related to previous test bookings I made and then deleted from my MySQL attendee table. That somehow the previous record with the same ID is interfering with the new record. But as I deleted all of the data for the test attendees I am little perplexed.
Could someone help me fix this,
Thanks,
Nick
|
|
Dean
|
November 6, 2012 at 12:53 am
Hello Nick,
Did you upgrade to 3.1.28?
If so there was an issue with it and we reverted back to 3.1.27 and would advise you to do so until the resolved 3.1.28 comes out.
If not then we will need WordPress access to have a look at the database (via a plugin called Adminer) to see whats going on.
|
|
Nick Putman
|
November 6, 2012 at 12:57 am
Hi Dean,
No, I’m on Version 3.1.27.1.P
What details do you need to get WordPress access? Username and password? Presumably I don’t post the details on this forum? Do I set up a new account for you or do you use my admin account?
Nick
|
|
Dean
|
November 6, 2012 at 1:01 am
Yep username and password. Either for the admin account or you can set up a new user but it will need admin level rights.
Please send them via https://eventespresso.com/contact/
Choose the “I am sending login info as requested” option and fill out the form
NOTE: login details need to be Admin level.
|
|
Nick Putman
|
November 6, 2012 at 1:06 am
OK, Thanks. I have sent the necessary information via the contact form
|
|
Dean
|
November 6, 2012 at 1:39 am
Thanks Nick, got the details and had a look. I had to activate Twentyeleven as your theme and adminer conflicted.
I can see nothing out of the ordinary in the database tables, I can’t even see where its pulling your data from.
My only advice currently would to be deactivate all Event Espresso plugins, drop the Event Espresso tables, reactivate the plugins and reset up the plugin and test. Not ideal as you will lose all the setting etc, but I am thinking it will flush the database enough to clear out whatever is lingering from the test install.
|
|
Nick Putman
|
November 6, 2012 at 10:40 am
Hi Dean,
I have double checked the attendee records of the bookings I have already received and can see that on some bookings the second email address is for other attendees, which is rather concerning, as this means that attendees email addresses are getting shared with each other via email.
As my event is up and running and I have bookings, I can’t drop the EE tables, so I am hoping that there is another solution.
Nick
|
|
Nick Putman
|
November 6, 2012 at 10:47 am
I have double checked the tables for attendees and everything looks OK on wp_events_attendee, but on wp_events_attendee_meta I see this:  I wonder if this is what is causing the problem? i.e. multiple id instances in the attendee_id column?
Also, here is a screenshot of a record that I tried to update manually in the admin section:
Though the correct information is showing in the MySQL table, in the admin section there are two instances of First Name, Last Name and Email and all of them are blank.
-
This reply was modified 12 years, 1 month ago by
 Nick Putman.
|
|
Nick Putman
|
November 6, 2012 at 11:32 am
I have now worked out that the issue was caused by the wp_events_answer table. I needed to delete the old records from this table, and now the correct information is showing up.
Could someone let me know what the wp_events_attendee_meta table is for. Should there only be one record per attendee ID? I think I should be deleting some entries on this table too.
Thanks,
Nick
|
|
Dean
|
November 7, 2012 at 1:35 am
Hi Nick,
Glad you managed to find the issue. The EVENTS_ATTENDEE_META_TABLE is for determining is an attendee is the primary attendee or not. It is due to be deprecated in 3.2.
It shouldn’t contain duplicates like yours does.
|
