Closed
Bug 1073038
Opened 10 years ago
Closed 10 years ago
Delete older, non-supported skins from the wiki.mozilla.org environments
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cliang, Assigned: cliang)
References
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1343] )
All skins (other than Vector and monobook) should no longer be in use any more and can be deleted.
Updated•10 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Comment 1•10 years ago
|
||
I've deleted the old skins on the wiki dev environment and pushed the change out. This change should "bake" for a while before pushing to stage and prod. I needed to comment out the following from LocalSettings.php: require_once("$IP/extensions/gmo/gmo.php"); Checking with Christie, it sounds like this might be a legacy thing. (That is, the gmo.php file is only there to provide the skin and for no other reason.) Noting it in the bug if it turns out not to be the case.
Comment 2•10 years ago
|
||
(In reply to C. Liang [:cyliang] from comment #1) > I needed to comment out the following from LocalSettings.php: > > require_once("$IP/extensions/gmo/gmo.php"); > > Checking with Christie, it sounds like this might be a legacy thing. (That > is, the gmo.php file is only there to provide the skin and for no other > reason.) Noting it in the bug if it turns out not to be the case. This is actually the opposite of a legacy thing; skins are no longer auto-detected. They now have to be installed and activated just like extensions: https://www.mediawiki.org/wiki/Manual:Skin_configuration#Installing_skins With error reporting turned high, MediaWiki would actually display a warning that mentions this when there are skins present/used that are not explicitly activated: https://www.mediawiki.org/wiki/Manual:Skin_autodiscovery
Assignee | ||
Comment 3•10 years ago
|
||
Changes pushed out to the staging server.
Assignee | ||
Comment 4•10 years ago
|
||
Changes pushed out to the prod server. New Relic shows a sharp drop-off in errors and it should now be easier to pull out errors / warnings that may need to be addressed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•