Topic on Project:Support desk

Problem to update MW 1.3 (very Old) until an 1.32

4
84.166.17.147 (talkcontribs)

Hello

we have an MediaWiki 1.3 (works with LATIN1!) on an Server with PHP5.3 (!!) and an older mySQL. Now we want to update. We Copy MW 1.3 to an Server with actual mySQL and PHP5.6. (Final-Server PHP 7.2)

I figured we'd have to update to 1.4 first, then 1.5.

Ok ... Server is too new ...

Manually Change Class Namespace-Entrys to MWNamespace. Change DB-Entrys with TYPE= to ENGINE=

1) Update to 1.4 (via console: php update.php) => Works (ok we CAN'T see an webpage-output ... 100+ deprecated errors ...)

2) Update to 1.5 ... First: php upgrade1_5.php ... no errors ... but it kills the db (Umlauts ÄÖÜß; same on filesystems etc.). I think he recognize the wrong charsets in db und change LATIN1 as UTF8 to UTF8 (the "new" names are typical for this error)


How do I get it clean from 1.4 to 1.32? When do we have to switch to the PHP7.2 server in the update process?


I have an problem to understand whats the different between AdminSettings.php and LocalSettings.php (i think this is the reason for my updateproblem...). I've understand that i must fill the AdminSettings with DB-Infos ... more? $wgUseLatin1 = true to adminsettings for upgrade1_5.php? I don't to this in my last "Update-Run" ...


Thank you

Ciencia Al Poder (talkcontribs)

Apparently, it's not possible to upgrade from 1.4 to a recent version. You need to upgrade to 1.5 first. This is explained in Manual:Upgrading#How do I upgrade from a really old version? In one step, or in several steps?

I'd upgrade first to 1.4 and 1.5 on the old server (I guess MediaWiki 1.5 supported php5.3 well), then transfer database to the new server and upgrade to a recent version.

Once you upgrade to 1.5, you should check if pages with non-ASCII characters look well. If they do, when transferring database to the new system (or maybe even required for 1.5 to work), you can try to convert the database from latin1 to utf8 exporting the dump, running inconv and then reimporting it, as explained here: http://www.alphadevx.com/a/420-Converting-a-MySQL-database-from-latin1-to-utf8

For information about how AdminSettings.php worked back then, you can check Manual:AdminSettings.php.

84.166.22.144 (talkcontribs)

Heythe main-problem is converting to UTF8 - doesn't work.I've updated first to 1.4 (ansi), then to 1.5 (first: upgrade1_5.php, then normal update; both via cli). Upgrade1_5.php kills Umlauts in Filenames ....The bigger Problem: i do this "blind" ... i have only an php 5.6-Server - no 5.3 any more. But i don't have any deprecated-errors @ updateprozess. (view the result via browser don't work - of course ... deprecated-errors). Problem in updatescripts are the Namespace -> rename to MWNamespace und SQL Type= change Engine=.In the manuels stand that i have set $wgUseLatin1 = true ... upgrade1_5 knows then: i must upgrade ansi to utf. AND i think here is something wrong. upgrade1_5 thinks it is utf8 and change tables to utf8 - without conversion -> destroy umlauts ... At my next attempt I will put $wgUseLatin1 = true into the adminsettings. Apparently the localsettings.php are not read by the upgrade1_5.php ...

Ciencia Al Poder (talkcontribs)
Reply to "Problem to update MW 1.3 (very Old) until an 1.32"