Aeolustw Posted October 9, 2006 Share Posted October 9, 2006 Hi,allI try to upgrade IPB v2.1.6 to IPB v2.2 Beta 2 , all Chinese words change to ??????.http://member.ipb.tw/ipb2b2/But upgrade to v2.1.7 that works fine.http://member.ipb.tw/ipb217/Thanks.p.sMySQL variables character set client utf8character set connection utf8character set database utf8character set results utf8character set server utf8character set system utf8collation connection utf8_general_cicollation database utf8_general_cicollation server utf8_general_ciand set UTF-8 also in IPB ACP Document character set Link to comment Share on other sites More sharing options...
Quillz Posted October 9, 2006 Share Posted October 9, 2006 Well, upgrading from 2.1.6 to 2.2.0 B2 wasn't recommended in the first place, as B2 is encoded and will expire later in the month. There will be an upgrade script, but I don't know how well it will actually work. Link to comment Share on other sites More sharing options...
Will L. Posted October 9, 2006 Share Posted October 9, 2006 Well, upgrading from 2.1.6 to 2.2.0 B2 wasn't recommended in the first place, as B2 is encoded and will expire later in the month. There will be an upgrade script, but I don't know how well it will actually work.indeed :whistle: Link to comment Share on other sites More sharing options...
Cool Surfer Posted October 9, 2006 Share Posted October 9, 2006 Well, upgrading from 2.1.6 to 2.2.0 B2 wasn't recommended in the first place, as B2 is encoded and will expire later in the month. There will be an upgrade script, but I don't know how well it will actually work.I am sure there will be an upgrade script, other wise no point in releasing the beta's Link to comment Share on other sites More sharing options...
gel Posted October 9, 2006 Share Posted October 9, 2006 Well, upgrading from 2.1.6 to 2.2.0 B2 wasn't recommended in the first place, as B2 is encoded and will expire later in the month. There will be an upgrade script, but I don't know how well it will actually work.the problem here is the current upgrading script in beta 2 doesn't work well with character encoding. I hope it'll be solved in the final version. Link to comment Share on other sites More sharing options...
Aeolustw Posted October 9, 2006 Share Posted October 9, 2006 the problem here is the current upgrading script in beta 2 doesn't work well with character encoding. I hope it'll be solved in the final version.ya, that's what i mean. :D Link to comment Share on other sites More sharing options...
Keven Fox Posted October 9, 2006 Share Posted October 9, 2006 Why in the world would you upgrade? Link to comment Share on other sites More sharing options...
Microo Posted October 9, 2006 Share Posted October 9, 2006 Hi,allI try to upgrade IPB v2.1.6 to IPB v2.2 Beta 2 , all Chinese words change to ??????.http://member.ipb.tw/ipb2b2/But upgrade to v2.1.7 that works fine.http://member.ipb.tw/ipb217/Thanks.p.sMySQL variables and set UTF-8 also in IPB ACP Document character setYou upgraded your LIVE FORUM?? Seems to me like you did... Well good luck fixing it mate... Link to comment Share on other sites More sharing options...
Brandon C Posted October 9, 2006 Share Posted October 9, 2006 You upgraded your LIVE FORUM?? Seems to me like you did... Well good luck fixing it mate...It seems that he has made a copy of his live board and then upgraded, not actually upgrading his live board. Link to comment Share on other sites More sharing options...
Microo Posted October 9, 2006 Share Posted October 9, 2006 It seems that he has made a copy of his live board and then upgraded, not actually upgrading his live board.Oh, Ok... It seemed to me like it was live, didn't notice my bad... Good luck fixing that up!Cheers,Brian Link to comment Share on other sites More sharing options...
Mark Posted October 9, 2006 Share Posted October 9, 2006 aeolusipb, try doing the following:Backup your cache/lang_cache folderManually add in any language vars that were not in 2.1, you will probably find them at the very top of the files in the lang_cache folderAttempt the upgrade on another copyReupload the original cache/lang_cache folderTell us what happensReport this bug in the bug tracker Link to comment Share on other sites More sharing options...
Aeolustw Posted October 11, 2006 Share Posted October 11, 2006 Thanks all.My live forum works fine, that's just a test link.Hi,Professor Paeolusipb, try doing the following: * Backup your cache/lang_cache folder * Manually add in any language vars that were not in 2.1, you will probably find them at the very top of the files in the lang_cache folder * Attempt the upgrade on another copy * Reupload the original cache/lang_cache folder * Tell us what happens * Report this bug in the bug trackerMy beta2 test forum show Tradition Chinese Language fine , like the picture bellow.http://www.aeolusa.idv.tw/ipb/index.php?ac...post&id=218The blue color frame in the picture are Tradition Chinese Language,and they show fine.But the red color frame in the picture are the data in the MySQL,and they show wrong character.I think this is not a problem and that will be ok when the final version release.Thanks anyway. Link to comment Share on other sites More sharing options...
RawkBob Posted October 11, 2006 Share Posted October 11, 2006 Oh, Ok... It seemed to me like it was live, didn't notice my bad... Good luck fixing that up!Cheers,Brian O/T - sT7, and i thought my sig was a bit on the large side... :huh: Link to comment Share on other sites More sharing options...
Jaggi Posted October 11, 2006 Share Posted October 11, 2006 not sure if its a issue but the buzz around ipb 2.2 pb2 was an upgrade script from 2.1.7 to pb2 so maybe it just doesn't support all versions of ipb yet or they overlooked summit. Link to comment Share on other sites More sharing options...
Mark Posted October 12, 2006 Share Posted October 12, 2006 aeolusipb, I would seriously submit a bug. You could try backing up the posts table then restoring it after the upgrade. Link to comment Share on other sites More sharing options...
bfarber Posted October 12, 2006 Share Posted October 12, 2006 The issue isn't with the IPB upgrade typically (I have seen similar things before) - it's typically with the act of exporting your data from mysql, and then reimporting the data. MySQL does a lot of converting when this happens I've noticed, and 99% of the time renders the data unreadable.Try setting up a new folder to test with - import your database, and then put the 2.1 files there first to see if things still show up properly before upgrading.What character sets and collations are setup on your existing server that you'd be exporting from?Make sure the character sets and collations are defined in the sql dump file for the table definitions when you import the dump (and that MySQL doesn't just take it's default, which will cause it to convert the data during import).IPB doesn't actually convert any of the post or topic data during the upgrade. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.