Page MenuHomeMiraheze

Remove Skin:Pivot
Closed, ResolvedPublic

Description

It is unmaintained and completely broken on 1.38 (nothing appears whatsoever)

Related Objects

StatusAssignedTask
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)

Event Timeline

Unknown Object (User) triaged this task as Low priority.Jun 5 2022, 05:30
Unknown Object (User) created this task.
Unknown Object (User) moved this task from Backlog to Upgrade Blockers on the MediaWiki board.
Unknown Object (User) moved this task from Backlog to Short Term on the Technology-Team (MediaWiki) board.
Unknown Object (User) removed subscribers: Excelsis, CrystalClear, Ajhalili2006, LisafBia.

300 wikis have it enabled 17 of which are using it as the default skin.

Unknown Object (User) added a comment.Jun 5 2022, 17:49

Is there a list of wikis that use it?

Unknown Object (User) raised the priority of this task from Low to Normal.Jun 5 2022, 20:17
Unknown Object (User) closed this task as Resolved.Jun 12 2022, 22:38

A patch has been submitted for this skin and confirmed as working (though not yet merged), can it please be retested for those wikis that use it?

https://github.com/Hutchy68/pivot/issues/114#issuecomment-1154267477

To be clear, I understand the maker is likely going to stop and has stopped maintaining this skin… this however gives us one more update cycle to modify the CSS for another skin to make the switch, rather than being in a panic to do it all right now and see what else doesn’t work or needs changing after the upgrade.

The patch isn't even merged.

It's not sustainable for SRE.

Sorry, I'm not a programmer, just a MH user. I saw there was a fork by a Wikimedia developer, with one file different (which has 4 lines changed in it. isLoggedIn looks to have been changed to isRegistered in each). I didn't realize it was a problem to swap out that file or use fork at the bottom of the link, so again, sorry.

We were waiting for the upgrade to 1.38 to hopefully make the switch to MH feasible, we'll wait.

It becomes hard when every extension needs forks deploying, that are all on branches that could be deleted at any point and if a change is made upstream and not pulled to the deployed branch. It's on us to notice and work out the right solution.

I personally find "It is unmaintained" simply false given that after the initial ticket for it a patch was submitted within 3 days.
I hope once it is merged into the trunk again, this ticket will re-evaluated and we can keep our favorite theme for a while still.

Unknown Object (User) added a comment.Jun 15 2022, 19:10

I personally find "It is unmaintained" simply false given that after the initial ticket for it a patch was submitted within 3 days.
I hope once it is merged into the trunk again, this ticket will re-evaluated and we can keep our favorite theme for a while still.

The patch is not by an original maintainer. It depends on them being able to merge it.

This extension has been moved to Wikimedia Phabricator, is marked as maintained (now maintained by Wikimedia folks, as was kindly offered here once it was posted about), and is now marked compatible with 1.39+ on its extension page.

I've created a new ticket to request it get re-enabled (and cross referenced this one).