From: Daniel Friesen dan_the_man@telus.net
People complain about issues cause they don't follow instructions...
(Much good advice about how to do incremental upgrades clipped...)
Remember Wikipedia? Wikimedia runs off MediaWiki and is being constantly upgraded. If the upgrade process wasn't handled right then you'd see Wikipedia broken all the time.
I believe the OP suggested export/import because they had fallen way behind, and lacked confidence in an upgrade process that is generally designed for Wikipedia's needs of strictly sequential incremental upgrades.
I am in the same situation, running 1.3. Short of upgrading to 1.4, then 1.5, then 1.6... I don't believe this posting really addresses strategies for someone who is way behind to "catch up." The further you are behind, the more likely something will break, no matter how carefully one follows the instructions for upgrading from 1.13.1 to 1.13.2.
Anyone have any good strategies going from 1.3 to current? I'm planning on making a complete copy, accessed from a new URL, and trying the upgrade on that. But I'm doubtful that such an upgrade will be fruitful.
:::: Number of developed nations besides the US lacking universal health insurance coverage: 0 :::: Rank of US among countries that spend the most as a percentage of GDP on health care: 1 :::: -- Harper's Index :::: Jan Steinman http://www.Bytesmiths.com/Item/99-6313-12
Jan Steinman wrote:
I believe the OP suggested export/import because they had fallen way behind, and lacked confidence in an upgrade process that is generally designed for Wikipedia's needs of strictly sequential incremental upgrades.
I am in the same situation, running 1.3. Short of upgrading to 1.4, then 1.5, then 1.6... I don't believe this posting really addresses strategies for someone who is way behind to "catch up." The further you are behind, the more likely something will break, no matter how carefully one follows the instructions for upgrading from 1.13.1 to 1.13.2.
Anyone have any good strategies going from 1.3 to current? I'm planning on making a complete copy, accessed from a new URL, and trying the upgrade on that. But I'm doubtful that such an upgrade will be fruitful.
Theoretically, the update script should be able to move you to current without problems. When bugs are discovered on it, they're fixed on the next release. The problem is that you update once per release. If something breaks with a current release, as many people have been doing it, it's more likely someone hit it, remembers that piece of code, etc. and can give you a better answer.
And if people avoid those updates, they're even less tested. ;)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jan Steinman wrote:
Anyone have any good strategies going from 1.3 to current? I'm planning on making a complete copy, accessed from a new URL, and trying the upgrade on that. But I'm doubtful that such an upgrade will be fruitful.
1) Back up your database
2) Grab the current code and put it in place of your old code
3) Follow the upgrade instructions.
The updater should update the database automatically from any MediaWiki installation version 1.2 or later. The one serious exception to this is that installations from prior to 1.5 which used Latin-1 encoding instead of UTF-8 may require a separate character set conversion first. (To add a little to the confusion, this issue is dependent on the $wgUseLatin1 config variable in your LocalSettings.php, _not_ the "character set" setting on MySQL.)
Otherwise, there are no *known* problems that should prevent you from upgrading directly from 1.3 to 1.13, as long as your PHP, MySQL etc are current.
If you actually do encounter an error while following the standard upgrade procedure, we want to find out about it so we can fix it! Please save the *exact output* from the updater *at the time you first ran it*, which should show any error conditions encountered during the update.
And don't forget to back everything up first. ;)
- -- brion vibber (brion @ wikimedia.org)
Hello,
I want to come back to the (safe) upgrading problem.
To upgrade a Wiki Brion Vibber wrote :
Back up your database
Grab the current code and put it in place of your old code
Follow the upgrade instructions.
In fact, I am unable to pass the first point :
Back up your database
I have not access directly to the database (which is on the access provider site and I cannot use mysqldump commands) I can only manage the database through phpMyadmin which is definitely not reliable.
This is the reason why we need the following procedure to upgrade.
1. Save the information stored in the database using a specific Mediawiki tool.
2. Grab the current code and put it in place of your old code.
3. Import the information previously stored in the database using a specific Mediawiki tool.
-------------------------------------------------------------------- As an example of the way phpMyadmin is working :
I just tried to export and import a small MySql database using phpMyadmin with XML format.
I got the following error message:
Error There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem
ERROR: Unknown Punctuation String @ 1 STR: <? SQL: <?xml version="1.0" encoding="utf-8" ?> <!-- - - phpMyAdmin XML Dump - version 2.11.3 - http://www.phpmyadmin.net - - Host: framesproject.sql.free.fr - Generation Time: Nov 08, 2008 at 04:18 PM - Server version: 5.0.67 - PHP Version: 5.2.5 -->
<!-- - Database: 'framesproject' -->
--------- this seems to mean that phpMyadmin is NOT able to read back the XML it has written. And by experience I know that using the SQL format is hazardous.
Best regards
Francois Colonna
Frames Project wrote:
Hello,
I want to come back to the (safe) upgrading problem.
To upgrade a Wiki Brion Vibber wrote :
Back up your database
Grab the current code and put it in place of your old code
Follow the upgrade instructions.
In fact, I am unable to pass the first point :
Back up your database
I have not access directly to the database (which is on the access provider site and I cannot use mysqldump commands) I can only manage the database through phpMyadmin which is definitely not reliable.
HAve you tried any of the many php shells out there?
Have you tried exporting it in anything other than the XML option?
Le dimanche 09 novembre 2008 à 08:05 +1000, K. Peachey a écrit :
Have you tried exporting it in anything other than the XML option?
Yes of course (it is said in my message) it was a disaster : phpMyadmin is unable to read back a file dumped using its export command.
The only reliable solution is to use mysqldump which is impossible for me : I cannot access directly to the database.
Best F.C.
Try the following program http://www.mysqldumper.de/en/
Works like a charm
At 07:10 PM 11/9/2008, you wrote:
Le dimanche 09 novembre 2008 à 08:05 +1000, K. Peachey a écrit :
Have you tried exporting it in anything other than the XML option?
Yes of course (it is said in my message) it was a disaster : phpMyadmin is unable to read back a file dumped using its export command.
The only reliable solution is to use mysqldump which is impossible for me : I cannot access directly to the database.
Best F.C.
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Henny (Lee Hae Kang) ----------------------------- http://www.henny-savenije.pe.kr Portal to all my sites http://www.hendrick-hamel.henny-savenije.pe.kr (in English) Feel free to discover Korea with Hendrick Hamel (1653-1666) http://www.hendrick-hamel.henny-savenije.pe.kr/indexk2.htm In Korean http://www.hendrick-hamel.henny-savenije.pe.kr/Dutch In Dutch http://www.vos.henny-savenije.pe.kr Frits Vos Article about Witsen and Eibokken and his first Korean-Dutch dictionary http://www.cartography.henny-savenije.pe.kr (in English) Korea through Western Cartographic eyes http://www.hwasong.henny-savenije.pe.kr Hwasong the fortress in Suwon http://www.oldKorea.henny-savenije.pe.kr Old Korea in pictures http://www.british.henny-savenije.pe.kr A British encounter in Pusan (1797) http://www.genealogy.henny-savenije.pe.kr/ Genealogy http://www.henny-savenije.pe.kr/phorum Bulletin board for Korean studies
Le samedi 08 novembre 2008 à 18:56 +0100, Platonides a écrit :
Frames Project wrote:
Hello,
I want to come back to the (safe) upgrading problem.
To upgrade a Wiki Brion Vibber wrote :
Back up your database
Grab the current code and put it in place of your old code
Follow the upgrade instructions.
In fact, I am unable to pass the first point :
Back up your database
I have not access directly to the database (which is on the access provider site and I cannot use mysqldump commands) I can only manage the database through phpMyadmin which is definitely not reliable.
HAve you tried any of the many php shells out there?
Sorry I do not understand your question: which shell ? to do what ?
Best F.C.
Hi,
Am Sun, 09 Nov 2008 11:06:25 +0100 schrieb Frames Project frames@lct.jussieu.fr:
[..]
HAve you tried any of the many php shells out there?
Sorry I do not understand your question: which shell ? to do what ?
I guess he was talking about something like this: http://phpshell.sourceforge.net/
A shell emulator written in PHP. You upload it to your web space and after installation you can run shell commands in it e.g. mysqldump -u $USER --password=$PASSWORD $DATABASE -c | /bin/gzip -9 > ~/backup/wiki-$DATABASE-$(date '+%Y%m%d').sql.gz
HTH, Matthias
Le dimanche 09 novembre 2008 à 11:17 +0100, Matthias Korn a écrit :
Hi,
Am Sun, 09 Nov 2008 11:06:25 +0100 schrieb Frames Project frames@lct.jussieu.fr:
[..]
HAve you tried any of the many php shells out there?
Sorry I do not understand your question: which shell ? to do what ?
I guess he was talking about something like this: http://phpshell.sourceforge.net/
A shell emulator written in PHP. You upload it to your web space and after installation you can run shell commands in it e.g. mysqldump -u $USER --password=$PASSWORD $DATABASE -c | /bin/gzip -9 > ~/backup/wiki-$DATABASE-$(date '+%Y%m%d').sql.gz
HTH, Matthias
Thank you for this information.
My problem is : I cannot install mysqldump on the Internet Provider machines I have no root access.
I suppose I am not the only one in that case, I wonder how other people do.
Best F.C.
Am Sun, 09 Nov 2008 17:28:33 +0100 schrieb Frames Project frames@lct.jussieu.fr:
[..]
I guess he was talking about something like this: http://phpshell.sourceforge.net/
A shell emulator written in PHP. You upload it to your web space and after installation you can run shell commands in it e.g. mysqldump -u $USER --password=$PASSWORD $DATABASE -c | /bin/gzip -9
~/backup/wiki-$DATABASE-$(date '+%Y%m%d').sql.gz
HTH, Matthias
Thank you for this information.
My problem is : I cannot install mysqldump on the Internet Provider machines I have no root access.
I suppose I am not the only one in that case, I wonder how other people do.
They use PHP Shell. Have you tried it? You don't need root access. You upload und install it like any other PHP-enabled software (e.g. MediaWiki).
HTH, Matthias
Hi,
Am Sun, 9 Nov 2008 17:43:02 +0100 schrieb Matthias Korn matsch@rockinchina.com:
Am Sun, 09 Nov 2008 17:28:33 +0100 schrieb Frames Project frames@lct.jussieu.fr:
[..]
I guess he was talking about something like this: http://phpshell.sourceforge.net/
A shell emulator written in PHP. You upload it to your web space and after installation you can run shell commands in it e.g. mysqldump -u $USER --password=$PASSWORD $DATABASE -c | /bin/gzip -9
~/backup/wiki-$DATABASE-$(date '+%Y%m%d').sql.gz
HTH, Matthias
Thank you for this information.
My problem is : I cannot install mysqldump on the Internet Provider machines I have no root access.
I suppose I am not the only one in that case, I wonder how other people do.
They use PHP Shell. Have you tried it? You don't need root access. You upload und install it like any other PHP-enabled software (e.g. MediaWiki).
MySQLDumper seems to be of the same type. Just upload and install.
What exactly is your problem?
HTH, Matthias
Le dimanche 09 novembre 2008 à 17:43 +0100, Matthias Korn a écrit :
Am Sun, 09 Nov 2008 17:28:33 +0100 schrieb Frames Project frames@lct.jussieu.fr:
My problem is : I cannot install mysqldump on the Internet Provider machines I have no root access.
I suppose I am not the only one in that case, I wonder how other people do.
They use PHP Shell. Have you tried it? You don't need root access. You upload und install it like any other PHP-enabled software (e.g. MediaWiki).
HTH, Matthias
Well, my Mediawiki is copied on an external Provider disk space via ftp. The MySql database has been installed, on requirement, by the Provider together with phpMyadmin. That's all what I am allowed to use. I have no possibility to install Php Shell or MySQLDumper (I tried, but some data are lacking and it went on error).
What I suggest is to do everything from the Mediawiki code with an internal upgrade command not external.
Best F. Colonna
Jan Steinman wrote:
I believe the OP suggested export/import because they had fallen way behind, and lacked confidence in an upgrade process that is generally designed for Wikipedia's needs of strictly sequential incremental upgrades.
I am in the same situation, running 1.3. Short of upgrading to 1.4, then 1.5, then 1.6... I don't believe this posting really addresses strategies for someone who is way behind to "catch up." The further you are behind, the more likely something will break, no matter how carefully one follows the instructions for upgrading from 1.13.1 to 1.13.2.
Anyone have any good strategies going from 1.3 to current? I'm planning on making a complete copy, accessed from a new URL, and trying the upgrade on that. But I'm doubtful that such an upgrade will be fruitful.
I put the answer to this question in the upgrade FAQ, and since then I've answered it about another 5 times on mediawiki-l.
http://www.mediawiki.org/wiki/Manual:FAQ#Upgrading
I don't know how many more times I'm going to have to say it.
Upgrades for 1.3 to 1.13 were tested automatically prior to the release of 1.13 using an automated upgrade test:
http://svn.wikimedia.org/viewvc/mediawiki/trunk/release-tools/upgradeTest.py?view=markup
There are no open bug reports regarding upgrading from 1.3 to 1.13. The vast majority of reports indicate that it works just fine.
Upgrading may take a long time. Back up your wiki in case the upgrade script is aborted halfway through and leaves your wiki in an intermediate state.
The upgrade script is inherently incremental. The updaters.inc file has a large list of database operations which have been steadily accumulating since the first MediaWiki release. They are run in the order in which they were added. Occasionally obsolete or redundant upgrades are removed. So running each upgrader in turn is effectively equivalent to running the most recent one.
Some of the old upgraders had bugs. We fixed them in later major releases. If you run the old upgraders, you risk encountering unfixed bugs in them.
Old upgraders are not supported and we will ignore bug reports against them. If you encounter a bug when upgrading directly from 1.3 to 1.13, we will fix it. If you encounter a bug when upgrading from 1.3 to 1.4, we will ignore you.
-- Tim Starling
Jan Steinman wrote:
From: Daniel Friesen dan_the_man@telus.net
People complain about issues cause they don't follow instructions...
(Much good advice about how to do incremental upgrades clipped...)
Remember Wikipedia? Wikimedia runs off MediaWiki and is being constantly upgraded. If the upgrade process wasn't handled right then you'd see Wikipedia broken all the time.
I believe the OP suggested export/import because they had fallen way behind, and lacked confidence in an upgrade process that is generally designed for Wikipedia's needs of strictly sequential incremental upgrades.
One more thing: the upgrader is NOT used by Wikimedia and is not designed for it. We've never run the upgrader on Wikimedia while I've been around. The upgrader is designed for small wikis and is aimed at a general non-technical user audience.
To upgrade Wikimedia wikis, we run the SQL patch files directly, or write special replication-friendly scripts. We aim for at most a few minutes of read-only time even for a huge wiki like the English Wikipedia, and that goal sometimes requires quite a bit of planning and effort to achieve.
-- Tim Starling
mediawiki-l@lists.wikimedia.org