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 Charset error when exporting to excel/csv | Event Espresso - Staging Server
When I export an attendee list to excel, all scandinavian characters gets replaced by strange signs:
In stead of “æ”: Kjærs v 33
In stead of “ø”: 3117 Tønsberg
In stead of “å”: KrÃ¥kÃ¥sveien 4
On the webpage they all look okay.
If i open the excel file in Notepad and copy/paste the entire thing into excel, the characters look fine. But this is a client site, and I can’t settle on a solution like that. (Also, the copy/paste-method adds a blank line between each attendee.)
I have seen a couple of forum threads on this, but haven’t found any solution to it. Do you have any suggestions on where I could start to solve this, or any plans on fixing this in a future release?
System info:
* WordPress 3.6.1
* Event Espresso 3.1.35.P
* Both WP and EE just updated, but the problem has always been present
It is basically saying use the file > open system, and select UTF encoding.
There might be a setting to automatically set the UTF8 but in my quick search I didn’t find anything.
Alternatively you could try a different spreadsheet package such as Open Office, I haven’t tested it recently but it used to have better CSV file handling.
Viewing 1 reply thread
The support post ‘Charset error when exporting to excel/csv’ 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.