I'm in the process of upgrading the Wiki from MediaWiki 1.15.1 to 1.15.5.
EDIT: Finished with the upgrade. See next post for details of the PHP warnings/anomalies I've fixed.
If anyone finds problems/runs into errors (PHP warnings/errors are most commonly seen at the very top of the page, partially hidden), please post in this thread and I'll do my best to track them down + fix them. I do have full backups (of MySQL and the MediaWiki 1.15.1 installation) in case we do need to roll back.
Upgraded to MediaWiki 1.15.5
-
koitsu
- Posts: 4201
- Joined: Sun Sep 19, 2004 9:28 pm
- Location: A world gone mad
Upgraded to MediaWiki 1.15.5
Last edited by koitsu on Fri Jun 17, 2011 6:21 am, edited 2 times in total.
-
koitsu
- Posts: 4201
- Joined: Sun Sep 19, 2004 9:28 pm
- Location: A world gone mad
Finished with the upgrade. The error that was being seen is described here:
https://bugzilla.wikimedia.org/show_bug.cgi?id=20296
https://bugzilla.wikimedia.org/show_bug.cgi?id=21412
I verified that's the correct fix by looking at the referenced code review, and the trunk version of mediawiki and reading the commit annotations for getMagic():
http://www.mediawiki.org/wiki/Special:C ... Wiki/55429
http://svn.wikimedia.org/viewvc/mediawi ... 8&r2=55429
We really should see about upgrading to MediaWiki 1.16.x to try and relieve a lot of these problems. I might have to schedule some "nesdev wiki downtime" to do that though.
https://bugzilla.wikimedia.org/show_bug.cgi?id=20296
https://bugzilla.wikimedia.org/show_bug.cgi?id=21412
I verified that's the correct fix by looking at the referenced code review, and the trunk version of mediawiki and reading the commit annotations for getMagic():
http://www.mediawiki.org/wiki/Special:C ... Wiki/55429
http://svn.wikimedia.org/viewvc/mediawi ... 8&r2=55429
We really should see about upgrading to MediaWiki 1.16.x to try and relieve a lot of these problems. I might have to schedule some "nesdev wiki downtime" to do that though.
-
Banshaku
- Posts: 2417
- Joined: Tue Jun 24, 2008 8:38 pm
- Location: Japan
-
koitsu
- Posts: 4201
- Joined: Sun Sep 19, 2004 9:28 pm
- Location: A world gone mad
What prompted me to do the upgrade was that I I kept finding bugs that prevented "user permission error" strings/reasons from being shown. The fix was stupid, but after reading over some of the docs, I thought... why the heck not just upgrade the thing to the latest 1.15.x build rather than keep hand-hacking stuff?Banshaku wrote:Thank you for the update. I didn't really focus on it since it seemed to "just work".
Yeah, that probably the best choice. I hope there will be a 1.15.x to 1.17.x upgrade document / release notes that covers it. Sometimes software programmers do things like demand that you upgrade a step at a time, e.g. 1.15.x to 1.16.x to 1.17.x. I hope that doesn't become the case here.Banshaku wrote:I receive mails about the update and they are talking about 1.17 already but it's not a final yet. Maybe we should wait for this version?
-
tepples
- Posts: 22994
- Joined: Sun Sep 19, 2004 11:12 pm
- Location: NE Indiana, USA (NTSC)
As I understand the upgrade instructions on MediaWiki.org, it's best just to upgrade from what you have to the latest version. First, lock the old version's database in LocalSettings. Then unzip the new version and any installed extensions to a new folder and either A. run update.php in PHP CLI (for web+SSH hosting) or B. visit /w/mw-config/index.php in a web browser. Finally, apply your LocalSettings customizations to the new version, and once it works, rename the folders.koitsu wrote:I hope there will be a 1.15.x to 1.17.x upgrade document / release notes that covers it.
Source