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 Two email columns in exported spreadsheet? Blank Records? Wrong names? Yikes! | Event Espresso - Staging Server
Some odd behavior, perhaps related to shrapnel from last version? Currently using 3.1.28.3
For every record, when the admin clicks any attendee name, a different person’s details (Sarah ….) show up in the entry fields, even though she wasn’t the name that was clicked.
When I exported to Excel to see what the file looks like, I see her email address on every record as a second email column.
Interestingly enough, her first and last name aren’t showing up on those records so I have no idea where EE is getting it from!
Not surprisingly, this doesn’t inspire great confidence by our members in us nor by our admin staff in Event Espresso.
I’m sorry to hear about this. We’ve been working very hard to quickly resolve any issues that have come up in the latest version. In order to investigate further, is it possible for you to send FTP and WordPress admin-level credentials via our contact form?
Also, if you had updated to Event Espresso 3.1.28.1 (not .2), was a backup of the database made at that time that we could take a look at?
Please select the “I am sending login info as requested” department form if it’s possible for you to send these.
Viewing 2 reply threads
The support post ‘Two email columns in exported spreadsheet? Blank Records? Wrong names? Yikes!’ 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.