|
Benjamin
|
April 16, 2013 at 5:55 am
Hello,
I think there are two minor bugs with the excel exports functionality in EE 3.1.32.B.2
On admin.php/?page=events :
– For every exports (every buttons) : accented and special characters in the files exported are badly encoded. Excel uses UTF-16LE+BOM as default Unicode encoding, so there should be a conversion of the output somewhere.
– When exporting all the datas with the buttons at the bottom (export all visitors, export all events), the generated file has no .xls extension.
|
|
Josh
|
April 17, 2013 at 10:21 am
Hi Benjamin,
Thanks for reporting. I’m not sure that this is a new bug in 3.1.32.B2 but if it is we can look into it. Do you happen to know if you’ve seen this happen in 3.1.31?
|
|
Benjamin
|
April 17, 2013 at 12:32 pm
Hi Josh,
Well yes I think it’s the same in the 3.1.31 version. I’m using at the moment the beta version on my dev site so I thought I’d report it in that branch first (and it’s not super important by the way).
|
|
Josh
|
April 17, 2013 at 2:32 pm
Hi Benjamin,
If this is similar to a related issue that has been reported before with the exports + excel, it may help to try using the CSVFileView application. Another Event Espresso user recommended it to us because he was having some character encoding issues when importing the reports to excel.
We are going to be refactoring the reporting tools for Event Espresso 4 and I’ll be sure to include your findings with the character encoding.
|
|
Benjamin
|
April 17, 2013 at 2:42 pm
OK thanks, good luck with Arabica, can’t wait for the 4.1 version and the occasion to go on production with it !
|
|
Josh
|
April 17, 2013 at 4:11 pm
Thanks Benjamin.
We’re pretty excited with how Arabica is shaping up and looking forward to seeing it being used outside of our testing and onto real sites.
|
