There is something that has me kinda worried, I read the upgrade instructions, it all went well, few little hiccups but nothing that couldn't be fixed, so far*.

My question is about this piece of text

"Upgrading a non UTF-8 site:
UTF-8 encoding has been introduced into XOOPS 2.30 as default charset. However, there might be some problems with converting existent websites from non UTF-8 charset to UTF-8.
Before there is a good enough solution for this conversion, following settings are recommended when you upgrade an existent website if you are not an experienced user:
- Select "Do not change" option in "Database character set and collation" step during upgrade process
- Modify /languages/yourlanguage/global.php to use existent _CHARSET value if it has been changed to UTF-8 in your new global.php file as"

So, I did follow this exactly I did not change the option just like it says, so tell me is there going to be some kind of fix as suggested or is this going to be a problem for future upgrades?

Or did I misunderstand it and totally stuff?things up for future upgrades?

I then see other posts about this subject with varying answers that would seem to suggest I did stuff up, I just don't get it! There seems to be the very odd strange character here and there but definitely nothing too major

My Database details the main first page in PHPMYAdmin

MySQL charset: UTF-8 Unicode (utf8)

MySQL connection collation: utf8_Unicode_ci

then I see in the tables

Collation: latin1_swedish_ci <<< should this be some kind of utf-8 or is it fine the way it is?

Can someone just tell me will there be a problem please?

Other details

XOOPS Version - XOOPS 2.3.0
PHP Version - 5.2.4
MySQL Version - 5.0.51a-community

Cheers.....Darin ;o)

No one has any idea about this?

Cheers

i dont think there will be a problem if you are not using another language than english! there is however an sql command that can convert that to utf!I dont really remember which one it is, perhaps you can export your db, and import it again in utf encoding. Do some tests though before you do that to a test db.

ok cool thanks, I will have a look around, that gives me a place to start ;o)

If anybody has any more information it would be appreciated as well.

I will look at those options when importing tables, I might make another test site.

Cheers....Darin ;o)

Anders is working on some instructions - as soon as he is done with testing, we'll publish a short guide to UTF conversion, as it seems like there is a need for it.

In the meantime, please share your test results, and any tips you might gather from it.

Thanks Mamba and Anders ;o)

Hello

here you are

Basically, since you can see

Quote:
it says your data are not encoded in UTF8. That's normal since you chose the Do not Change option during the upgrade.

So go to language/english/global.php, and change the line
//%%%%% LANGUAGE SPECIFIC SETTINGS %%%%%
define('_CHARSET', 'UFT-8');

to //%%%%% LANGUAGE SPECIFIC SETTINGS %%%%%
define('_CHARSET', 'ISO-8859-1');

make the same for language/yourlanguage/global.php

that's all, should be ok now, but let us know

Thanks Marco I have done what you said and the immediate change I can see is the copyright symbol in the footer of my theme it was a "Diamond shape with a ? in the middle" now "XOOPS 2.0 © 2001-2007" it has that lovely Copyright symbol. I have to get to bed but that's a great start lol. I will check other text in the morning.

By the way the Profile module rocks, I downloaded the one from SVN 2.3.1 seems great so far, members like the new fields I have created, makes the Profile more site specific.

Thanks to all you guys!

Cheers....Darin ;o)

ok, it seems you're on the right road now

have fun and a good night

Quote:

I have the exact same problem with the copyright symbol in my theme. Will try Marco's solution.

Thanks guys