Jump to content
thirty bees forum
  • 0

CSV import with Scandinavian letters broken since TB1.4


Question

Posted (edited)

Hello,

I upgraded to TB1.4 and since then TB wont accept CSV-imports where I use scandinavian letter (åäö etc). This is quite the problem for me - anyone else expericened the same problem? Any solutions?

When looking at the CSV import page, fields with these characters arn't even being read...

Br.

Erik

Edited by 312erik123

10 answers to this question

Recommended Posts

  • 0
Posted

We'll kind of figured that it was safer to stay on a stable release for a production environment...but maybe I'll set up a test environment and do the upgrade.

Do you have good experience with the 1.5 alpha/beta?

  • 0
Posted (edited)

No issues, not a single commit is reverted in probably one year. Few new minor features and many, many fixes and code improvements, plus as I said couple of security fixes.

EDIT: Just keep in mind one quirk in this update - email transport functionality was moved to a module. Nothing is changed but you have to install the module and configure your shop to use it. After update to currentedge there are couple of db fixes aswell. 😉 

Edited by the.rampage.rado
  • 0
Posted (edited)

Hello,

This issue has kind of re-appeared, now most of, not all, scandinavian letters are changed to chinese(?) characters... On bleeding edge...Anyone else? @the.rampage.rado Do you know anything?

Br.

Erik

Edited by 312erik123
  • 0
Posted

First make sure that You use UTF-8 encoding, second there is difference between CSV formats in TB1.1 and 1.4 (I have no info about 1.2 and 1.3)

  • 0
Posted
Just now, led24ee said:

First make sure that You use UTF-8 encoding, second there is difference between CSV formats in TB1.1 and 1.4 (I have no info about 1.2 and 1.3)

The strange this is that it only changes some of the characters:

 image.png.6096040b666cdd2355fa2ae4486c1f64.png

Checked it on a prestashop site where the import works without any problems...

  • 0
Posted
6 hours ago, led24ee said:

First make sure that You use UTF-8 encoding, second there is difference between CSV formats in TB1.1 and 1.4 (I have no info about 1.2 and 1.3)

Seems as it was the UTF-8 enconding - thanks for pointing me in the right direction!

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...