Log in

Forum:MediaWiki upgrade

From PathfinderWiki
Forums: Grand Lodge > MediaWiki upgrade

At Yoda8myhead's prompting, I've been looking at upgrading out MediaWiki (henceforth MW) installation. Currently, we're running 1.15, which is several years old. The newest version is 1.19. Upgrading MW itself is actually pretty simple (once you know how), but it looks like a some of the extensions we use aren't compatible with 1.19. Not the least of these is LoopFunctions extension which Morbus Iff recently suggested (the extension's author seems to have a version that works with MW1.17 in his private git repository, so I'll give that a try). There are other, less important extensions that also break, but I suspect that we could find replacements for some and others (like multiple upload) aren't deal-breakers.

Why am I telling you all this? I don't know... just to let you know what I've been up to I suppose. As the weather cools off (fingers crossed) and I can bear to sit at my computer for more than 30 minutes at a stretch, I'll continue to work on this. As I make progress, or as issues arise, I'll post updates here.

It's always nice to be kept in the loop; thanks for sharing. I fully understand the issues with heat, as well. With no AC at my apartment, I'm spending decidedly more time at the campus library. Spending time in a climate-controlled setting is a wonderful way to beat the heat.
It's been in the balmy high-60s here in the greater Seattle area, and just this week the cloud cover broke and we are getting some sun just in time for PaizoCon. So I totally empathize with the heat. I miss my mid-50s and cloudy weather. ;-P
As I write this it's 93 degrees with 50% humidity here in St. Paul. We got off easy today.

... I have never wanted to attend PaizoCon more than I do at this moment. And I've really wanted to attend PaizoCon in the past.

Fun fact, the wiki has had over 70,000 edits.

Also the updated copy of LoopFunctions I found seems to work.

It only hit 86° here today, but with the humidity it felt like 100+... we Canadians just can't cope with that.

I love pages like Special:Statistics. Also handy for when you're waiting on template changes to propagate (when job queue is 0, everything's done).

Come to England - the wettest and dullest June for over a century and July is even worse so far with torrential rain and flooding. I am wearing a jumper.

Aeakett, did you really mean 'his private git repository'? That made me laugh and set off my imagination.

Heh, "private git repository" is intentional, yes. It's a thing.

Yeah, language is funny... I wear a sweater when I'm cold, and my wife would be much more likely to wear a [jumper] than me.

In other news, I've only got a few more extensions to confirm/get working. After that, I'll have to do up a new skin. Then we should be ready to do the upgrade.

Instead of doing up a new skin, can't we just use the new default and edit MediaWiki:Common.css, etc.?

Slow progress this week as I enjoyed some the cooler temperatures. Now that it's heating back up I've been sweating over the keyboard working on the skin. More updates later this weekend.
Anything we at home can do to help speed things along? I'd love to have the upgrade done before ENnie voting starts up so we can implement a few of the new features I have had on hold until 1.19 (or whatever version we go with) goes live.
I'm really close to being ready to do the upgrade. I'm just polishing my deployment script at the moment. This weekend I plan to set up a publicly accessible test server and test/benchmark the script. Once that's done, I'll post the details here and get everybody to have a look. When we're satisfied that everything is OK we can pull the trigger on the live site. As of right now, I'm guessing that we'll have about 15-20 minutes of downtime while the upgrade runs, but I'll know better later this weekend.
Oooh! Exciting!
OK. Test site is up. Go here and give it a spin. In particular, if somebody could check the fancy new stuff that Morbus Iff introduced us to, that would be great.

As for downtime during the upgrade, it took about 5 minutes. This will vary a bit as part of the upgrade involves downloading stuff from the internet, but our connection on the server is plenty fast, so it shouldn't be a problem.

I'm guessing users didn't transfer to the temp page, as soon as I log in I get a bunch of mediawiki errors so I can't look at the clicking on your account or an edit page correctly... I like how the search is in the upper right... The tabs are a bit bigger, which are take it or leave it for me, it makes them seem more block-y in my opinion, if it were possible to make them rounder for ascetic purposes... but overall it looks good
All of the users should be set up on the test site. It actually sounds like an issue with the skin. I thought I set it up so that everybody would get the new skin, but maybe not. Could you let me know what you have your skin set to on the current site?
Test site looks good and I'm not running into any errors at all on it. The search at the top is going to take some getting used to, and the sidebar looks funny, but those are minor issues. I also don't know what I think about the tabs along the top being split on both sides of the page. I think I'd rather them all be on the left or right and not divided up like they are. Again, something we can fix later.

As for the extensions Morbus Iff asked for, I've looked at the templates they were used in and all appear to be working exactly as they're supposed to. I suggest, however, that we put some sort of alert on the main page letting folks know that we've updated our version of MW and to either post on the forum or alert us through FB or twitter if there are any issues they notice.

I just noticed, however, that the CUP text isn't displaying on the new skin. Is this something we're ok with folks going to the Disclaimer page for, or do we want it on every page?
Can we turn the links along the bottom of the page, as well as the "this page was last updated on XXX" text a color that shows up better against our background? The blue and gray is getting lost in there.
Good catches... I'm noticing a bunch of layout things that I didn't notice before including article badges not showing up and the pending account request bug being missing.

I'm going to start a list of stuff below that needs to be fixed so that I can keep track of it more easily... feel free to add to it.

Clicking on several categories at the bottom of a page did not work for me: it takes you to an empty page. Ditto clicking on the 'Categories' link on the front page.

Apart from the look of the site, has anything else changed that we can discover?

Thanks for doing this Aeakett.

Shouldn't really be anything new... my goal was to get everything back to the way it was.
And... I broke it. Stand by.
And... we're back. Hopefully I won't do that again.
Here are the messages I'm getting.... I haven't played with the skin on here, so I guess I have whatever the default is.

Call to undefined method SkinasdfBook::tooltipAndAccesskey Backtrace:

  1. 0 [internal function]: Skin->__call('tooltipAndAcces...', Array)
  2. 1 /usr/share/mediawiki/skins/asdfBook.php(141): SkinasdfBook->tooltipAndAccesskey('ca-nstab-main')
  3. 2 /usr/share/mediawiki/includes/SkinTemplate.php(494): asdfBookTemplate->execute()
  4. 3 /usr/share/mediawiki/includes/OutputPage.php(1982): SkinTemplate->outputPage()
  5. 4 /usr/share/mediawiki/includes/Wiki.php(406): OutputPage->output()
  6. 5 /usr/share/mediawiki/includes/Wiki.php(594): MediaWiki->finalCleanup()
  7. 6 /usr/share/mediawiki/includes/Wiki.php(503): MediaWiki->main()
  8. 7 /var/lib/mediawiki/index.php(58): MediaWiki->run()
  9. 8 {main}

Original exception: exception 'MWException' with message 'Call to undefined method SkinasdfBook::tooltipAndAccesskey' in /usr/share/mediawiki/includes/Skin.php:1550 Stack trace:

  1. 0 [internal function]: Skin->__call('tooltipAndAcces...', Array)
  2. 1 /usr/share/mediawiki/skins/asdfBook.php(141): SkinasdfBook->tooltipAndAccesskey('ca-nstab-main')
  3. 2 /usr/share/mediawiki/includes/SkinTemplate.php(494): asdfBookTemplate->execute()
  4. 3 /usr/share/mediawiki/includes/OutputPage.php(1982): SkinTemplate->outputPage()
  5. 4 /usr/share/mediawiki/includes/Wiki.php(406): OutputPage->output()
  6. 5 /usr/share/mediawiki/includes/Wiki.php(594): MediaWiki->finalCleanup()
  7. 6 /usr/share/mediawiki/includes/Wiki.php(503): MediaWiki->main()
  8. 7 /var/lib/mediawiki/index.php(58): MediaWiki->run()
  9. 8 {main}

Exception caught inside exception handler: exception 'MWException' with message 'Call to undefined method SkinasdfBook::tooltipAndAccesskey' in /usr/share/mediawiki/includes/Skin.php:1550 Stack trace:

  1. 0 [internal function]: Skin->__call('tooltipAndAcces...', Array)
  2. 1 /usr/share/mediawiki/skins/asdfBook.php(141): SkinasdfBook->tooltipAndAccesskey('ca-nstab-main')
  3. 2 /usr/share/mediawiki/includes/SkinTemplate.php(494): asdfBookTemplate->execute()
  4. 3 /usr/share/mediawiki/includes/OutputPage.php(1982): SkinTemplate->outputPage()
  5. 4 /usr/share/mediawiki/includes/Exception.php(182): OutputPage->output()
  6. 5 /usr/share/mediawiki/includes/Exception.php(209): MWException->reportHTML()
  7. 6 /usr/share/mediawiki/includes/Exception.php(490): MWException->report()
  8. 7 /usr/share/mediawiki/includes/Exception.php(569): MWExceptionHandler::report(Object(MWException))
  9. 8 /usr/share/mediawiki/includes/Wiki.php(506): MWExceptionHandler::handle(Object(MWException))
  10. 9 /var/lib/mediawiki/index.php(58): MediaWiki->run()
  11. 10 {main
Yup... that's a skin issue. I've tried again to slam everything into place. I used a bigger hammer this time, so hopefully it works now.
I remember deleting asdfbook when I was doing some namespace cleanup a while back. It seemed to have been an early version of pathbook, and wasn't being used as far as I could tell. Maybe that's the problem?
Yup, that fixed it!
The banner on the bottom "This website uses trademarks ..." is no displaying correctly. On short pages it is overlapped by our Ennies nomination pic.
Yes... that's fixed now along with the donate button overlapping the "Toolbox" pod on user pages.

That pretty much leaves the account request problem. I think I might have that solved but I want to do a fresh spin through my upgrade script to make sure. At some point tonight the link I provided earlier will cease to work when I spin down the current test site and recreate it to test the upgrade script. Once I've done that I'll post a new link for everyone to look at again.

OK. New test site is here (I've edited the previous link I provided too... just in case anybody accidentally uses it). Unfortunately, the account creation notification thing isn't working. I'm going to keep on it.

Fo now, keep hammering away and let me know about broken stuff.

I'm not seeing the pending account request notice on all pages like on this version, but I do see one pending when I check out Recent Changes on the test site. That should be sufficient for us, since anyone with admin privileges is likely to refer to that page a number of times on each visit to the site.
So... huh. OK, that seems like it would be good enough to me too.

That officially clears out the "stuff to fix" list. I'd like to wait another day or so just to make sure nothing else crops up. After that, I'd say we're ready to do the upgrade... FINALLY!

Is there a way for the tabs at the top to be a little shorter? Right now there's a lot of dead space at the top of the page that is pushing somethings past the fold. I don't think we need quite such large margins on that text.
First of all, thank you Aeakett for all your hard work. Secondly, is there a list we can create (or link to if it already exists) that shows us what changes the new version of MediaWiki will bring? Or is it mainly back end stuff?
We're going from 1.15 to 1.19, so there are a lot of steps in between that this page doesn't cover, but you can see the main MediaWiki release notes for 1.19 here.
Sorry all, between a leaky window and an emergency tech support call, I didn't get anything done tonight. To Yoda8myhead's comment about the overly tall tabs, I have to day I agree. I worked on it for almost an hour at lunch but didn't too far... the markup and css are pretty dense. We can always work on it after the upgrade though.

If there are no objections, I think we're ready to do the upgrade. Tomorrow night is a definite maybe depending on how my window situation plays out... I'll give an update on my plans tomorrow when I get home from work.

Thanks for all your work on this, Andrew. I know it hasn't been a small project, and I appreciate the time you've put into it.
So the goo news is that my window didn't leak during today's 5-hour rain shower. The bad news is that I had to do a follow-up on last night's tech support call.

That said, tomorrow is the day. I'm thinking 8:30 PM EDT. I'll update the site notice appropriately. As for all the thanks, you're all welcome I suppose, but they really aren't necessary. I often disappear for weeks at a time, so things like this are my way of contributing.

Upgrade complete. It looks like everything went as planned. If anybody notices any issues, please let me know.
It looks like div parameters aren't working. For example, the <div align="center"> in {{Yearbox}} isn't centering the box...
... or in the {{Stub}} template.
I've fixed the offending templates. It looks like the syntax of table styles has changed since our old version of the software. If anyone sees any others, just let me know.
Thanks, Yoda!

Thanks both

The centering thing is strange. From what I could tell it only affected Webkit browsers (Chrome and Safari)... it looked just fine in Firefox and Opera (I meant to look at it in IE at work today but forget). So there's something a little off in the markup of the new skin that is causing the problem.

At any rate Yoda8myhead seems to really be coming along in his CSS Ninja training, so it's mostly a moot point. Good work Mark.

Also, a nija edit, with the new version, when accessing the site with a mobil device, the sidebar isn't pushed way down like it was with the old one (before the navigation and toolbox were pushed 5 screens down on my phone)
When I approved the last two accounts, in addition to adding text to the new Chroniclers' talk pages, also created blank user pages for them. Is there a MediaWiki page we can edit to put real boilerplate userpage text in new user pages? Alternatively, is the autocreation of user pages something we can switch off?
How long should we leave up the sitenotice? I'd like to clean up the site as much as possible, but I also don't want to take down something that is typically left up for a set amount of time when done on similar projects.
Re: Site Notice. I was thinking that we leave it up for a week or so. We're long past that so I'll edit them shortly.

Re: Auto-creation of user pages. There's a setting in the LocalSettings.php on the server that will allow us to turn off the auto-creation. I recall that that's the way I had it set up originally, but it seems that the syntax may have changed in the new version of the extension... I'll have a look.

I actually like the auto-welcome message and the idea of user page auto-creation, I'd just like to be able to define what gets put there. Something akin to the welcome page, but saying "This user hasn't set up a user page yet. If this is your user page, feel free to customize it to your liking. It's a great way to get accustomed to wiki editing for those new to the process and a personalized user page will help other Chroniclers get to know you." I was making a template somewhere in my sandbox, adapting something from Wookieepedia. Anyway, shutting it off until that template's ready is probably the best idea.
Site notice is done. As for the auto-creation, I have it turned off but it doesn't seem to be doing its job. I'll have a poke around in the code, but no guarantees. As for what gets put on the new user page, my impression is that it will be the user's provided bio. There is also a conifg setting (on the server) to add extra text. I imagine that this could include wiki code.
First of all, thanks again to everyone who's helped with the mediawiki upgrade. On a completely different topic, I've recently been using the Safari browser more for wiki editing. One of the little extensions the browser uses is called "Reader", which displays a page with most of the formatting simplified, and just the text and images displayed. The font used in Reader is "Georgia" and reading one of the longer wiki articles in this font makes me want to curl up on the couch and just keep reading for hours; I love it! I know this is a long-shot, and others may disagree, but is there a way of changing the wiki's base font, and could it be changed to Georgia? If it is, could we considering changing it to that font of fonts? Is this a horrible idea? Could we just test it out? Am I just experiencing a boyhood crush? Should I just leave good-enough alone? It's like buttah, I tell you, buttah!
Even if we didn't change the style sheet for the entire site, you could always set custom default fonts on your personal style sheet. But we don't want you reading the wiki for hours and hours; we want you to edit it for that amount of time or longer. ;-)
Just noticed something else. All tables seem to have a default white background now. Is this something we have to change on a per-case basis, or is there something we can do "behind the scenes" to address this? For an example, check out the huge Monster index.
It's something you can set on a case-by-case basis, but likely something we want to define as part of a common CSS class.
No doubt about it, Georgia is pretty. I prefer Palatino myself, but it's best not to get me started down the path of typeface geekery.

Changing the main face for the entire site probably has design implications, but if you want to use it just add the following to User:Brandingopportunity/vector.css:

  html, body {
     font-family: Georgia;

As for the table colours, we can set those site-wide in MediaWiki:Common.css if somebody would like to make a suggestion.

Thank you Aeakett

not a big deal, but I just noticed that on user ages therer is no longer a tab for 'contributions' to see what pages that editor has done.... I know it has helped fighting spam in the past, so I thought I'd bring it up
You can see any user's contributions by manually entering the url /wiki/Special:Contributions/USERNAME. It's fairly easy to just replace the "User:" in the url with "Special:Contributions/"

stuff to fix

  • CUP text not showing
  • account request notice not showing
  • badges not showing
  • Cpt kirstov's skin issue
  • make out-of-article text at bottom of the page a colour we can see
  • Categories displaying empty page when clicked
  • show/hide not showing on info-boxes