A tip when upgrading from 1.6.1 to 1.7
By kiang
When upgrading with the steps found in document, the data would be broken and most entries became ??? for characters in Chinese. After some testing, I found I could fix this problem by simply deleting this file before upgrading:
engine/schema/upgrades/2009100701.sql
Everything seems to be fine now. :)
Elgg Technical Support
Get support from other Elgg users
- Brett@brett.profitt
Brett - 0 likes
You must log in to post replies.This has been discussed at length in this thread. The problem seems to only exist for users who have altered their core files by changing the encoding PHP uses to talk to MySQL. If you are having problems and haven't changed the core, could you post some info in the other thread or on the ticket linked form it? Thanks