This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
August 20, 2012 2:44pm
Subscribe [1]#16 / Sep 04, 2012 2:05pm
OK. I rolled back, but it looks like it’s all still a mess. Instead of the Persian, or the ???? it is now some wacky stuff like this: قربون جگرت - اپ
I am wondering if this might have been a function of not having the proper settings when doing a database backup.
Any idea how to fix this?
I’d like to get it so I can see the Persian (and apostrophes, etc., which also seem to be awry) before doing the upgrade to 2.x
Let me know!
Best,
Rezwan
#17 / Sep 05, 2012 10:46am
Hi Rezwan,
FYI, I uploaded the old database and saw that it (ee1.7) has things coded in latin_1_swedish_ci whereas the new stuff (ee2) is in utf-8_general_ci - I thought it would be the other way around.
There was no set standard in ExpressionEngine 1.x - which leads to issues like you are having. Do you still have a copy of your database before any updates?
There is no benefit to updating to 1.7.3 before the upgrade to 2.x
The key here is, if you have Unicode data in your database already, you don’t want to re-encode it during the upgrade to 2.x You only want to convert the structure, not the data.
How large is your database? Can you place a pre-update/upgrade version on a server that we can FTP into?
I’d love for us to get a look at the database in the “before” state. Be on the lookout for an email from EllisLab.
Cheers,