Database Conversion Tools [Support Thread]

[gernot]

Hi @lat9
I am trying to set up a test DB in ZC 2.1.0, and import the old 1.5.6c DB into that.
However, if I try to use a DB with ZC 2.1.0, I have to set up admin & storefront configure.php first.

I am confused now, since it appears that utf8mb4 is a requirement in the configure.php:

define('DB_CHARSET', '%%_DB_CHARSET_%%'); // 'utf8mb4' required. If using older 'utf8' or 'latin1', convert your database to utf8mb4. See conversion util in docs site.

So it appears I would need to convert the database first, other charsets are no longer supported in 2.1.0?

If so, then I suppose I will need to revert to the other plan option, of converting to utf8mb4 on 1.5.6c, and then converting again later in 2.1.0, only for the the collation update?

[gernot]

Hi @lat9
I suppose I might try to run a DB upgrade using ZC 1.5.8a, where an option of utf8 is still there, and where you mentioned there is automatic adjusting of VARCHAR columns.
I am not sure if this is viable though using the base ZC files and my 1.5.6c database, or whether I would need to customize the base ZC files first, so as to let the installer "know" about the extra tables. Which would be several more weeks of work.
All in all, this seems like too many dependencies not all in one place.

[gernot]

I have gone for the to me safer-sounding convert-now approach in ZC 1.5.6c.
The conversion, as previously noted, deleted 3 indices on my test DB, which I then recreated manually using truncated lengths of fields as applicable.

I now have a utf8mb4 DB with a fairly old collation which I plan to update in ZC 2.1.0.

[richard7315]

Hi,
I have recently upgraded our site from 1.5.7c to 2.1.0. After upgrading I used the Zen Cart Database Conversion Tool to convert from UTF8 to UTF8MB4.

A customer has informed us that they are no longer able to log into their account. I have checked our old test customer account and this did not seem to work either.

It looks as though the passwords may not have converted to the new format or were affected by the upgrade to 2.1.0. The accounts can be accessed by resetting the passwords.

If anyone can offer any advice on what may be causing this issue it would be much appreciated.
Many thanks
Rick

[lat9]

Hi,
I have recently upgraded our site from 1.5.7c to 2.1.0. After upgrading I used the Zen Cart Database Conversion Tool to convert from UTF8 to UTF8MB4.

A customer has informed us that they are no longer able to log into their account. I have checked our old test customer account and this did not seem to work either.

It looks as though the passwords may not have converted to the new format or were affected by the upgrade to 2.1.0. The accounts can be accessed by resetting the passwords.

If anyone can offer any advice on what may be causing this issue it would be much appreciated.
Many thanks
Rick

I'm remembering an issue with "special" characters (i.e. & < > " ') in admin passwords, I don't know if that's what's going on.

[swguy]

If you have access to the old database, you might verify that the old password still works, and if it does, export the customers table and try updating the customers_password field in the new database.

Do in a test environment first, of course.
This was an issue in the old database updater but I have not seen it in this current version, even after running it dozens of times. Sorry you are having this issue.

[richard7315]

Hi lat9 and swguy
Many thanks for your replies. After further investigation I have found some older test account login details. I can confirm that these passwords are working after upgrading, but they don’t contain special characters.

It appears that special characters in the customers password could be the cause of the issue. I will contact the customer to see if this is the case.
Rick