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
Export to Excel problem | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Export to Excel problem

Export to Excel problem

Posted: August 4, 2013 at 6:15 am

Viewing 3 reply threads


zappohll

August 4, 2013 at 6:15 am

I’m having two issues when exporting booking information to an excel spreadsheet.
1) It appears that partway along the table, the headings get duplicated, so that the columns do not line up under the correct heading.

2) Zipcodes are not appearing as the correct datatype, so leading zeros get truncated. For example, the zipcode “07712” gets changed to “7712” in the excel spreadsheet.

I posted an example test spreadsheet here….see section highlighted in yellow.

http://torat-el.org/wp-content/uploads/2013/07/TestTicketSpreadsheet.xlsx

Thank you!!


Jonathan Wilson

  • Support Staff

August 5, 2013 at 11:49 am

Hi,

I am looking at the file you have attached, but I don’t see any duplications. Which columns are being duplicated?


zappohll

August 5, 2013 at 12:42 pm

Please look at column Y.

Thanks!


Dean

  • Support Staff

August 6, 2013 at 1:15 am

Hi,

This is a known issue, we have a ticket outstanding to fix it. If it needs to be fixed urgently, there is a temporary fix available on thie forum thread http://staging.eventespresso.com/topic/excel-error-duplicate-fields/

Viewing 3 reply threads

The support post ‘Export to Excel problem’ 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.

Event Espresso - Staging Server