Updating to 3.8 beta error

[Floris]

I see you use mysqli, did you set the mysqli charset?

// ****** MySQLI OPTIONS *****
// When using MySQL 4.1+, MySQLi should be used to connect to the database.
// If you need to set the default connection charset because your database
// is using a charset other than latin1, you can set the charset here.
// If you don't set the charset to be the same as your database, you
// may receive collation errors. Ignore this setting unless you
// are sure you need to use it.
// $config['Mysqli']['charset'] = 'utf8';

[Floris]

@ Wayne, I remember Marco had a charset script, I do not know if this works on 3.8, but perhaps it's worth 'trying' that? I searched the staff forum but couldn't find it.

[texterted]

What should I change to what? general to unicode or vice verca?
Is it just to change coalition in phpmyadmin???

Well, following Wayne's advice above, you should change the one with the least amount of mismatches. I had to change them all individually in phpmyadmin and there where quite a few!

Make sure your database is set to the same collation as its default.

Make sure you have a back-up first though as it can break the tables!

Good luck

[Wayne Luke]

@ Wayne, I remember Marco had a charset script, I do not know if this works on 3.8, but perhaps it's worth 'trying' that? I searched the staff forum but couldn't find it.

Its very primitive though and can cause its own problems.

Well there is this:

http://www.vcharset.com/

But it is third-party and unsupported by us. It only converts to UTF-8 as far as I am aware as well. Even then it can cause problems. vCharset is more sophisticated than the 2 year old staff script though.

Well, following Wayne's advice above, you should change the one with the least amount of mismatches. I had to change them all individually in phpmyadmin and there where quite a few!

Yes, it can be tedious. If there was a better supported method, I would have given it to you. Future versions of vBulletin should handle this better. We just need to wait for proper UTF-8 Support.

[joomlajon]

I have a mysqli charset, uncommented the utf-8.

When I installed vbulletin a while ago everything has been utf8_general

Now the most have changed to utf8_unicode, and I have no plugins besides the blog provided by vbulletin. It is as if the 2.0 blog and 3.8 differs from previous versions in some way???

Well, I have changed it to unicode standard, which was before general. And then changed the tabels with general to unicode. So now everything says it is unicode. But still I get the same database error from step five.

In admincp it says that I use 3.7.3 and that I should upgrade to 3.7.3 pl1, I had the 3.7.3 pl1 version installed before the upgrade.

So is it fixable or shoule I go back to earlier version?

[joomlajon]

Ok, found more inside the tables as well, now I have changed all and the upgrade is complete

Now I know if it happens again.

One question left.

I changed a couple of utf8_bin to utf8_unicode_ci as well, was that wrong???

[texterted]

One more question about collation....

Now my tables are set to latin1_german2, what will happen when I try another upgrade?

Seeing as the vbulletin upgrade will want to install it as latin1_swedish... will it again cause a mismatch or will it accept my default setting? (Seeing as blog 2.0 beta didn't!).

[texterted]

Any update on this collation question, anyone?

[Wayne Luke]

If you do not change the default collation of the database then future upgrades can use the improper collation. You need to consult the MySQL documentation to see how to change the default collation of a database.

[texterted]

What should I change to what? general to unicode or vice verca?
Is it just to change coalition in phpmyadmin???

Well, seeing as you have to change all of the affected tables one by one, I'd change the ones with the least amount.
Just check that your databases' default collation is the same. All of this is done from phpmyadmin.