I would make a backup of your database if possible beforehand, but generally, the web updater should be sufficient for your needs if your wiki isn't extremely large.
The update mostly refresh your database tables to match the latest mediawiki version's ability to access and update them, and the jump in version you are doing is somewhat considerable, so I would definitely back up your database before the upgrade. Unless your wiki is on par with something like Wikipedia, the web updater should be fine with something far smaller. If you have an custom extensions or any of your extensions do not work in the newest versions of mediawiki (I would check this beforehand by going to the pages for those extensions on mediawiki.org), you may wish to comment them out of your localsettings.php file, otherwise the web updater will prematurely abort, which is generally harmless, as it will prevent extensions that have incompatible database schema changes from negatively impacting the updated database tables. Aside from that, provided a backup is available just in case, I see no harm in running the web updater on a small to medium sized wiki without any major customizations to the database. On Mon, Jun 24, 2013 at 11:58 AM, Mickey Feldman <[email protected]> wrote: > I'm getting ready to upgrade our (hosted) corporate wiki from 1.161.1 to > 1.21.1. > > I have done an upgrade using the web interface on a local copy of our wiki > - this worked fine. The docs suggest that with a "large" wiki this could > fail due to timeouts, that the command line upgrade script is preferred, > and that if you don't have command line access you should change hosting > providers to one that allows command line access. > > Changing hosts is not always an option, but it seems to me that you ought > to be able to upgrade the DB on a local machine, using the command line > script if necessary, then import that new DB structure (and data) on your > host. Has anyone tried this, and is there some reason it does not/would not > work? > > Also, I have found that although I don't have command line access, I can > run php scripts as cron jobs. Is there any reason the upgrade script could > not be run this way? For example, is there any point at which the upgrade > script requires/requests user input? > > I have not yet tried to upgrade our hosted wiki, and I think it's likely > that the web interface will work fine, I just want to be aware of all > possible safety nets in case problems do arise. > > > Thanks > > -- > Mickey Feldman > > Vigil Health Solutions Inc. > 2102- 4464 Markham Street > Victoria, BC Canada > V8Z 7X8 > 250.383.6900 > > > ______________________________**_________________ > MediaWiki-l mailing list > [email protected].**org <[email protected]> > https://lists.wikimedia.org/**mailman/listinfo/mediawiki-l<https://lists.wikimedia.org/mailman/listinfo/mediawiki-l> > _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
