I'd give the latest SVN HEAD a try. I had a similar encoding issue before, and HEAD has it fixed.
On Jan 26, 2009, at 4:58 PM, Chris Meller wrote: > I'm not sure what the problem with the encoding could be now, it's > not really my area of expertise. > > Rumor has it on IRC that the WordPress importer works with the > latest SVN HEAD now, so you may want to give that a try. You can > grab a zipped copy at http://habariproject.org/dist/ if you're > interested. > > On Mon, Jan 26, 2009 at 4:29 PM, HenrikWL <[email protected]> > wrote: > > > > On 26 Jan, 18:56, Chris Meller <[email protected]> wrote: > > Did you change the encoding before you imported or after? Try > wiping out > > everything, changing the database encoding, reinstalling Habari, > and then > > reimporting from WordPress. > > Ok, I tried from scratch. Dropped all the habari tables, set the > database to utf8_general_ci by default, reinstalled Habari and > reimported. Same thing. Everything truncates at the first special > character. > > Both the WP and the Habari tables are in the same database, I don't > know if that has got something to do with it? I can only have 1 > database on my webhost, so I'm kinda stuck with doing it this way. The > WP tables are all utf8_general_ci by the way. > > > I don't know why that's throwing an error, but you can always > rename the > > pingback directory to something else and it should get deactivated > the next > > time you load a page. It's in /system/plugins. > > The problem resolved when I reinstalled (naturally). > > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users -~----------~----~----~----~------~----~------~--~---
