Update MediaWiki at getfirebug.com to the latest version

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: IT-Managed Tools
RESOLVED FIXED
5 years ago
2 years ago

People

(Reporter: sebo, Assigned: w0ts0n)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/172] [unplanned - urgent], URL)

(Reporter)

Description

5 years ago
This is a split of Bug 874621 to cover updating the MediaWiki installation of getfirebug.com.
The Firebug Working Group needs this update in order to enable new features, add extensions (see bug 631022) and get the latest (security) fixes.

Sebastian

Updated

5 years ago
Blocks: 631022

Comment 1

5 years ago
We discussed this a bit internally and have a few ideas to get this moving. The first and perhaps simplest would be to get this set up on a VM on the community vlan. This would allow you to have root access and you could control access to the VM and coordinate any maintenance amongst your team. This infrastructure was not available when we initially moved your site in-house and onto the generic cluster but has since been developed specifically to provide robust and supported hardware to community projects without all of the other IT overhead.

The other option is to continue to host this site on the Generic cluster. In this case we will need to discuss a restructuring of the layout of the current code base to bring it in line with the more standard way we deploy web properties. This will enable us to use some of our standard tooling to assist in keeping the MediaWiki portion of the site up to date within a reasonable time-frame.

If you decide to go the community vlan route you might ping xionox for advice as he seems to be a primary community coordinator for many things.

Either way let me know how you would like to move forward or if you have any questions, I will do my best to answer them.

Regards
Status: UNCONFIRMED → NEW
Component: Server Operations: Web Operations → WebOps: IT-Managed Tools
Ever confirmed: true
Product: mozilla.org → Infrastructure & Operations

Updated

4 years ago
Flags: needinfo?(sebastianzartner)
(Reporter)

Comment 2

4 years ago
Since we're a small team and don't have much resources it would be better if Mozilla could continue maintaining the wiki on the generic cluster.
If that allows us to get updates and changes faster in the future, that would be fantastic.

Let us know, if there's something you need from us related to the code base restructuring.
Also it would be great if you told us when the update requires to change or reset specific settings, the layout, something in the database, etc., so we can discuss that. Important for us is of course that we don't lose any wiki pages and that bug 631022 can finally be tackled after this change.

Sebastian
Flags: needinfo?(sebastianzartner)

Updated

4 years ago
Whiteboard: [unplanned - troubleshooting]

Updated

4 years ago
Whiteboard: [unplanned - troubleshooting] → [unplanned - urgent]
(Reporter)

Comment 3

4 years ago
Any updates on this front?
Since the current version is already 1.22.2, I made the summary more general now.

Sebastian
Summary: Update MediaWiki at getfirebug.com to 1.21.1 → Update MediaWiki at getfirebug.com to the latest version
Whiteboard: [unplanned - urgent] → [kanban:https://kanbanize.com/ctrl_board/4/110] [unplanned - urgent]

Updated

3 years ago
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/110] [unplanned - urgent] → [kanban:https://webops.kanbanize.com/ctrl_board/2/172] [unplanned - urgent]
(Assignee)

Comment 4

2 years ago
Howdy,

This is a very old bug.. and now some very old software. Happy to get this moving again (if it's needed), but since this is so old I want to tread with caution. :sebo are you happy to discuss this over IRC? 

I'm going to need to:

* backup DB
* backup files
* update to newer version
* check everything isn't broken. 


If things are broken it would be good to have someone on IRC to chat with who knows the system so we can either fix it or revert back.
Assignee: server-ops-webops → rwatson
Flags: needinfo?(sebastianzartner)
(Reporter)

Comment 5

2 years ago
(In reply to Ryan Watson [:w0ts0n] from comment #4)
> :sebo are you happy to discuss this over IRC? 

Meanwhile I'm not working for the Firebug Working Group anymore, so I'm redirecting the request to Honza.

Sebastian
Flags: needinfo?(sebastianzartner) → needinfo?(odvarko)
(In reply to Ryan Watson [:w0ts0n] from comment #4)
> Howdy,
> 
> This is a very old bug.. and now some very old software. Happy to get this
> moving again (if it's needed), but since this is so old I want to tread with
> caution. :sebo are you happy to discuss this over IRC? 
> 
> I'm going to need to:
> 
> * backup DB
> * backup files
> * update to newer version
> * check everything isn't broken. 
> 
> 
> If things are broken it would be good to have someone on IRC to chat with
> who knows the system so we can either fix it or revert back.

It would be great to update it, but I don't have any knowledge of the system so, I am afraid I can't help if it's broken.

Honza
Flags: needinfo?(odvarko)
(Assignee)

Comment 7

2 years ago
I've had some time to work on this during our IT change freeze and have managed to get the stage site to a reasonable state:
https://getfirebug.allizom.org/wiki/index.php/Main_Page 

It currently has the most recent checkout applied:
Last Changed Rev: 149712
Last Changed Date: 2015-12-04 05:04:46 -0800 (Fri, 04 Dec 2015) 


If there are no objections, I'm going to go ahead and get the stage site updated first and figure out any problems there and if all is well, attempt prod.
(Reporter)

Comment 8

2 years ago
At https://getfirebug.allizom.org/wiki/index.php/Special:Version it still says version 1.16.5. The current stable version of MediaWiki is meanwhile 1.26.2 (2015-12-21).

Sebastian
(Assignee)

Comment 9

2 years ago
Yes. I'm aware of this. The above comment was just updating the bug that I got a working updated site for us to test on @: https://getfirebug.allizom.org/wiki/ so progress is being made.
(Assignee)

Comment 10

2 years ago
I ran the upgrade today on stage/dev. I had to first upgrade the database using the /maintenance/update.php
then I had to add the following lines to LocalSettings.php:
wfLoadSkin( 'CologneBlue' );
wfLoadSkin( 'Modern' );
wfLoadSkin( 'MonoBook' );
wfLoadSkin( 'Vector' );

Plugins also need to be updated after installation. 

Otherwise all looks well:
https://getfirebug.allizom.org/wiki/index.php/Special:Version

Provided the date works for everyone, I'll do the update on getfirebug.com/wiki on the 5th of January (after IT change freeze)?
Flags: needinfo?(odvarko)
(Reporter)

Comment 11

2 years ago
There are some issues where links refer to port 80, e.g. the background image is missing, or the link for creating a new page refer to https://getfirebug.allizom.org:80/. That may be related to the issue explained in bug 782683 comment 15. (Though image uploads work on the staging server.)
Also, it happened to me a few times that the theme switches to the old MonoBook MediaWiki default theme.
Besides that I only see a few CSS glitches so far.

Sebastian
(Reporter)

Comment 12

2 years ago
Ah, the editor toolbar is gone.

Though I assume adding it back is part of bug 631022.

Sebastian
So, looks like the update can happen today.

Honza
Flags: needinfo?(odvarko)
(Assignee)

Comment 14

2 years ago
The update happened. 

I/we also removed the /wiki directory from the SVN repo. It was causing some issues and I don't believe anyone but IT will be updating it.

Can you test the wiki and see if you notice any features missing? 
If we can R+ the update I can then work on: 631022 if still needed.
(Assignee)

Updated

2 years ago
Flags: needinfo?(sebastianzartner)
Flags: needinfo?(odvarko)
(Reporter)

Comment 15

2 years ago
The only issues from testing are related to CSS. When logging in I see the default MonoBook theme. And as mentioned in comment 11, some styles are different now and need some maintenance.

The problems related to the port don't happen anymore. Thanks for that!

Sebastian
Flags: needinfo?(sebastianzartner)
(Assignee)

Comment 16

2 years ago
Hey sebo,

which theme should it be? I can try and switch it back if you can get me a link?
(Reporter)

Comment 17

2 years ago
This one:
https://getfirebug.com/wiki/index.php/MediaWiki:Common.css

Note, that it only switches back to MonoBook on the login page, nowhere else, as far as I saw.

I already fixed the other small CSS issues.

Sebastian
(Assignee)

Comment 18

2 years ago
Can you reach out on IRC to guide me on how to fix this particular issue?
(Assignee)

Comment 19

2 years ago
I've downloaded and installed the newest Vector theme. 
I've then set it as the default theme.
(Reporter)

Comment 20

2 years ago
I've fixed the CSS issues now caused by switching to the Vector theme.

(In reply to Sebastian Zartner [:sebo] from comment #17)
> Note, that it only switches back to MonoBook on the login page, nowhere
> else, as far as I saw.

Ryan and I fixed that issue, too. It turned out that the preference $wgAllowSiteCSSOnRestrictedPages needed to be set.

So, let's call this fixed! \o/

Sebastian
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(odvarko)
Resolution: --- → FIXED
(Assignee)

Comment 21

2 years ago
w00t.
You need to log in before you can comment on or make changes to this bug.