Page MenuHomePhabricator

Update extensions on Brickipedia and GBC
Closed, InvalidPublic

Description

Yes, I'm aware that this is o bviously this isn't an easy task, there's ~80+ extensions at https://github.com/Brickimedia/extensions, and each needs one testing to make sure nothing breaks! The last time they were updated was...almost a year (11 months really, but still really close to a year!) Check it out:

http://en.brickimedia.org/wiki/Special:Version

As you can see, a lot of them were updated were in 2015 (mostly September, but a few November instances here and there, with one October instance), and then some in January 2016. (Don't bother about Donate, that's gonna be in a new ticket, and NewTalkGlobal is basically unmaintained now. and I haven't seen updates to ArticleRatings but we still use it, so)

Event Timeline

First off, the whole associated procedure should be documented on-wiki so that someone unfamiliar with our setup could relatively easily figure out the answer to the question, "as a Brickimedia sysadmin, how do I update an existing extension or add a new one?".

Secondly, this would probably prove to be a good opportunity to add the TitleKey extension at least, and maybe some others.

Thirdly, all social tools should be using the master version. Branched ones (REL1_NN) are untested, not guaranteed to work and outdated. With social tools, the master (=latest) version is the only really supported one when used either with the latest stable version of MediaWiki or the version that ShoutWiki uses, should these two differ for whatever reason. I've actually switched Comments and VoteNY over to use the master branch a few days ago so that I was able to deploy the recent Comments security fix and fix some functional bugs with VoteNY (but turns out that while there's nothing wrong with VoteNY per se, it did however expose a bug with MediaWiki 1.26 core...we can either hack around that or consider the 1.27 upgrade to get rid of that bug and have VoteNY fully functional).

MediaWikiAuth extension is not yet MW 1.27-compatible due to the AuthManager stuff in 1.27+, but @Legoktm is working on patching that. (This, of course, is not an issue if we're staying on 1.26 for the time being.)

ProtectSite and Quantcast extensions are maintained by me, so the master version of these extensions should be used.

Closing https://github.com/Brickimedia/brickimedia/issues/288 as this ticket superseded it. In some later version of Echo, global notifications was created as a preferences option so it's a matter of updating Echo and testing to make sure the version we're using is compatible with Refreshed and that it works.

Closing https://github.com/Brickimedia/brickimedia/issues/473 as this ticket superseded it (update the Refreshed extension).

It's been reported that http://en.brickimedia.org/wiki/Review:71011_Minifigures_Series_15 wasn't able to be accessed, this was the fatal PHP error the page was throwing from @ashley, which is directly related to the MediaWiki-extensions-Comments extension:

PHP message: PHP Fatal error: Call to a member function getPrefixedDBkey() on a non-object in /var/www/core/extensions/Comments/CommentClass.php on line 511

Also relevant comments from chat:

04:18, 1 January 2017 Jack Phoenix (Talk | contribs | block): and it would appear we're using a slightly outdated version of Comments again? should poke UltrasonicNXT about that -- social tools should be git master (against latest stable MW, which we're '''not''' running on Brickipedia...but they should still work. it's just an unsupported combo, because I don't have the resources to maintain ancient stuff.)
04:18, 1 January 2017 Jack Phoenix (Talk | contribs | block): actually ironically enough updating SocialProfile itself to git master would break stuff, since the Echo support code is written for MW 1.27+ versions of Echo >.>

Since Brickimedia has moved to ShoutWiki's server, this is now invalid.