Upgrade 2.0.13 to 2.1.4 stop on Step 6: Convert to UTF-8

[VadiKO]

Hello everybody!

I'm updating an old forum 2.0.13 to 2.1.4 and I get a conversion hang while updating.
Can you look at the log, or how to find out what is the problem of stopping the update?

Thanks! 

You cannot view this attachment.

[Deaks]

interesting place for it to hold, do you have many reported and moderated posts on your forum??

[VadiKO]

no, not much. the forum is small.

have any ideas?

[Kindred]

What mods did you have installed?

[VadiKO]

Installed packages display: reCAPTCHA for SMF and SMF 2.0.14 Update. I once installed the buttons by hand hide and spoiler

I tried to clear the contents of the log_reported_comments table, it helps, it gets to the next table log_search_subjects and stops there... I tried to clear it, it also helps... it gets to the next table - smf_members and again there is a stupor... I didn't clean smf_members anymore, this is not a solution Yes, and I understand that the next one will be smf_messages

[VadiKO]

Solved the problem, but got a new one. 

In general, I'll start from the beginning. Forum version 2.0.13 is running successfully, the forum encoding is set to:

<meta http-equiv="Content-Type" content="text/html; charset=windows-1251" />

and the language pack Russian windows-1251 is installed.
The data in the database is written in ISO-8859-1 (latin1) and if you look through phpmyadmin, you will see:
You cannot view this attachment.
line: äëÿ íåîïûòíûõ þçåðîâ is defined by the decoder as ISO-8859-1 (latin1) encoding and is decoded in windows-1251 where it receives its normal value - for inexperienced users.

If you use the conversion utility built into the forum, then by default it offers to convert the database from windows-1251 to UTF-8, but I know that I have data in the database in ISO-8859-1 (latin1), so I change windows-1251 to ISO-8859-1 and I perform the conversion. As a result, the database data looks completely unreadable:
You cannot view this attachment.
If I still leave the proposed value and convert the database from windows-1251 to UTF-8, I also get an unreadable format:
You cannot view this attachment.
phpmyadmin says the db has a mapping utf8mb4_0900_ai_ci

Actually, where to dig???

[Sir Osis of Liver]

Did you set language to english before starting upgrade?

[VadiKO]

No, I didn't update.

I restored the forum from a backup and went further Admin - Forum Maintenance - Database - Convert the database and data to UTF-8
You cannot view this attachment.

Need to change the language to English before performing the conversion?

Thanks!

[Sir Osis of Liver]

No, you need to set english as default language in 2.0.13 before upgrading to 2.1.4.  That's a known issue, thought it had been fixed but it's still being reported.  You'll need to restore the 2.0.13 files and database, set language to english, then run 2.1.4 upgrade from beginning.

[VadiKO]

Ok, I will do it.
Now I tried to convert the database on the forum version 2.0.13 by switching the language to English and got the same bad result  :

You cannot view this attachment.

[Sir Osis of Liver]

Changing the default language should not affect the database.  If the database is working when you restore the 2.0.13 install, set english as default in Admin > Languages, then run the 2.1.4 upgrade from beginning. 

[VadiKO]

No, you need to set english as default language in 2.0.13 before upgrading to 2.1.4.  That's a known issue, thought it had been fixed but it's still being reported.  You'll need to restore the 2.0.13 files and database, set language to english, then run 2.1.4 upgrade from beginning.

Did as you said, restored the files and database to version 2.0.13, set the language to English, and then ran the update to version 2.1.4 from the beginning.

The result is the same, the upgrade stops:
You cannot view this attachment.
Well, the database still converts into an unreadable form:
You cannot view this attachment.

[grega]

Check what I did:

https://www.simplemachines.org/community/index.php?topic=588397.0

[shawnb61]

A couple general notes...

When dealing with hidden errors in the upgrader like this, the best way to get it to tell you the actual underlying error is to run the upgrader via the command line.  Freezes during the upgrade step are usually caused by some DB changes that the upgrader doesn't know how to deal with, e.g., deleted columns or added columns without a default value.  Those DB changes would need to be dealt with & the upgrader re-run. 

I believe the 2.1 upgrader's UTF8 conversion is more robust than the 2.0 internal conversion.  I haven't looked at 2.0 code in a very long time, but IIRC the 2.1 upgrader is better at avoiding double-encoding.

Running the upgrader in English is always a safe bet & is easier.  You can run the upgrader (& installer) in other languages, but you need to install the 2.1 language pack first - (that's where the 2.1 language strings are...). 

tl;dr:  Try CLI.

[VadiKO]

Thanks to all.
The issue is resolved.
Converted the database using notepad++
Then I fixed the errors
And everything was updated well.