I'm cleaning up all extensions flagged on MediaWiki.org as using removed hooks by filing issues if there is an active issue tracker. If what you want is to declare the extension broken and uninstall it (and archive it on the MediaWiki.org side too), then that works for me.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 1 2024
Nov 5 2023
Should someone mark https://github.com/miraheze/customheader as archived on GitHub (and thus mark https://www.mediawiki.org/wiki/Extension:CustomHeader as archived on MediaWiki.org, which I'll handle) then?
Oct 24 2023
Someone should make sure to clear the months-old backlog at Requests for Adoption before possibly deleting wikis someone may still want.
(The correct venue being https://meta.miraheze.org/wiki/Stewards%27_noticeboard, or you can configure ManageWiki to allow the crat group to be removed locally)
Oct 23 2023
Oct 22 2023
Oct 12 2023
Note that a new version has now been released to remove the deprecated code.
Sep 26 2023
Sep 23 2023
Yet you seem to have done https://github.com/miraheze/CustomHeader/commit/88b863248a7a25dfede5807f4fafbadcbe08c89d last week. If the extension is abandoned, then what was the point of that?
Sep 22 2023
Sep 21 2023
A backup might exist somewhere on archive.org. See https://archive.org/search?query=Miraheze
Sep 16 2023
Sep 11 2023
Miraheze is currently understaffed. You should expect response times on the order of a week or two, not a few days.
Sep 5 2023
Sep 4 2023
Miraheze is suffering from a severe shortage of volunteers so things take longer than usual to get processed. Someone will get to this in a few weeks.
Aug 4 2023
In T11080#223229, MacFan4000 wrote:Please understand that it may take awhile to complete tasks due to severe understaffing. I am effectively the only person working on these tasks, and to keep up completely on my own is a lot of work, and I unfortunately can't get things done super quickly. SRE requests simply cannot be actioned quickly at the moment. I apologize for this, and just want to say that your patience and understanding is appreciated.
Aug 2 2023
Jul 28 2023
In T11080#223229, @MacFan4000 wrote:Please understand that it may take awhile to complete tasks due to severe understaffing. I am effectively the only person working on these tasks, and to keep up completely on my own is a lot of work, and I unfortunately can't get things done super quickly. SRE requests simply cannot be actioned quickly at the moment. I apologize for this, and just want to say that your patience and understanding is appreciated.
Miraheze won't give you managewiki-restricted rights yourself. You can request Semantic MediaWiki be enabled over on Miraheze Meta, although note that Miraheze is severely short-staffed right now so it will probably be a while before anyone responds.
Jun 15 2023
The upgrade not happening does not change the fact that this extension is being archived and should be undeployed at some point.
May 23 2023
Apr 25 2023
Neither of the extensions meet the definition I would use for completely unmaintained, though:
Mar 27 2023
Mar 18 2023
Jan 10 2023
Sep 6 2022
See step 2 of https://meta.miraheze.org/wiki/Custom_domains#Steps
Jan 19 2022
It looks like it's actually gzip-compressed XML, and I was using an editor that automatically uncompressed the file without clearly communicating to me that it was doing so. Sorry for confusing everyone.
Jan 7 2022
The actual problem seems to be that the custom blog page creation system doesn't subst {{REVISIONUSER}} (that is, https://qualitipedia.miraheze.org/w/index.php?title=Qualitipedia:CBP/2&action=edit should say [[Category:Articles by user {{<includeonly>subst:</includeonly>REVISIONUSER}}]] instead of [[Category:Articles by user {{REVISIONUSER}}]]. Once you do that new blogs created using that system should at least not error.
Jan 6 2022
Actually, it looks like https://archive.org/download/turtlewiki-datadump/index.php is a XML dump (despite the file extension), and https://archive.org/download/turtlewiki-datadump/index_(1).php is an image dump (actually a tar.gz file, despite the extension). The file Reception123 linked to has to do with archive.org and has no content relevant to the wiki.
Note that making that edit was much harder than expected: trying to do it manually via the edit page produced a bogus edit conflict; so I tried to do it via the API, which didn't work. I then tried to delete the page, which also didn't work. I was eventually able to un-corrupt the page by using Special:MergeHistory to move all the edits to another page and then back again.
Dec 28 2021
Deleting also errors. Also note that at one point I deleted and then selectively undeleted the page, which may have confused checkStorage.
Dec 23 2021
Jan 7 2021
Also note that translatewiki.net supports several different formats for exporting messages, not just MediaWiki's JSON.
Dec 7 2020
Oct 30 2020
@Universal_Omega This works in vanilla MediaWiki (and thus on Wikipedia). ManageWiki's handling of namespaces breaks it. This task is not invalid.
Oct 16 2020
Oct 8 2020
Oct 7 2020
I've fixed that Lua error (https://tuscriaturas.miraheze.org/w/index.php?title=Plantilla:Infobox_settlement/doc&diff=19028&oldid=14767). Note that it only affected the documentation, and didn't prevent the rest of the template from working.
Sep 18 2020
Sep 11 2020
In T6166#120563, @Universal_Omega wrote:In T6166#120562, @Pppery wrote:Are you sure? This extension looks unmaintained to me, with the last commit that isn't a bot or formulaic change being in 2013 (!)
It has 1.35 support branch
This action was performed automatically (https://phabricator.wikimedia.org/T257892), so should be ignored.
was not flagged as unmaintained
Yes, there is a large backlog of extensions which should be tagged unmaintained on MediaWiki.org but aren't. https://www.mediawiki.org/w/index.php?title=Extension:Numbertext&diff=4098554&oldid=3625842
and updated 5 days ago on master (non bot).
Umherirrender made an identical change to over 100 extensions. It is not reasonable to assume from that all 100 of those extensions are being meaningfully maintained because of that one formulaic change.
Are you sure? This extension looks unmaintained to me, with the last commit that isn't a bot or formulaic change being in 2013 (!)
Sep 1 2020
I'm not at all familiar with Miraheze's standards for extensions, so I don't actually have an opinion on whether it should be approved or not. I do care, though, that if it is approved it's approval is not based on false premises.
This extension has not suffered from a lack of commits because there is nothing needing changing, if that is what you are trying to say, as it has 8 open tasks on Wikimedia Phabricator, one of which is ominously named "Discuss future of the Arrays extension".
In T6123#119685, @Universal_Omega wrote:The arrays extension has previously been marked as unmaintained, however there have been changes to the repository in the past 3 days. As such the extension is no longer unmaintained, and I will now review the extension.
Aug 22 2020
Benjamin Hardie created Module:Documentation/config with the wrong content. I've fixed the problem. (and sorry for the redlink in the edit summary, that was actually copied from https://template.miraheze.org/wiki/Module:Documentation/config.
Jun 7 2020
That doesn't look like "a lot has changed" to me; there's a ton of translatewiki and libraryupgrader commits (both of which are bots whose changes aren't significant), and most of the rest of the commits are routine removal of deprecated code applied across all of Gerrit.
Jun 2 2020
May 3 2020
You've run into https://phabricator.wikimedia.org/T125857 (Flow boards don't respond to template updates unless they are edited). I've fixed the problem by making a dummy edit to the board header and then reverting that edit, and it does now appear to include a link a a wikitext archive.
I don't see how this prevents you from doing anything; you could create the templates that this script would create manually.