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 Exporting Events | Event Espresso - Staging Server
I’ve read all kinds of forum posts here about problems exporting event data and issues with 3.1.x. Right now we’re running 3.1.28P and when we export all events it comes out as csv that you have to rename to xls to view, and it contains no attendees (even though we have 36). We go to attendee reports, see all 36, click “export to excel”and again get an xls with the right columns but no attendees.
Does this feature work at all in 3.1.x? We need it now, waiting for 3.2 isn’t really an option. What can we do?
The issue with the export data had to do with custom questions. This has been resolved. You should be getting a correct export. My Excel 2010 does throw a warning at me when I open the file but that’s just Excel being fussy and on clicking yes it opens perfectly fine.
Have you recently upgraded Event Espresso from an older version? If so which version?
this doesn’t work at all – I get no entries. I do have custom questions, but I’m using the latest version of EE, and have upgraded to each release as they have come out.
OK, I would advise you to roll back from 3.1.28 to 3.1.27 for a short while. Whilst I havent been able to pin down the exact issue here, there was a problem with 3.1.28 regarding the attendee database (which is why we rolled the version back) so it is highly probable that this is related.
We are hoping to re-release 3.1.28 shortly, so I will make sure this is checked.
Viewing 5 reply threads
The support post ‘Exporting Events’ 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.