An extension to make collaboration on JSON files possible with MediaWiki. Homepage
Details
Nov 7 2025
Change #1203165 merged by jenkins-bot:
[mediawiki/extensions/LockDownEnglishPages@REL1_44] Swap the sneakily deprecated (circa MW 1.37) userCan hook to the non-deprecated getUserPermissionsErrors hook; require MW 1.39+
Change #1203165 had a related patch set uploaded (by Umherirrender; author: Jack Phoenix):
[mediawiki/extensions/LockDownEnglishPages@REL1_44] Swap the sneakily deprecated (circa MW 1.37) userCan hook to the non-deprecated getUserPermissionsErrors hook; require MW 1.39+
Jul 29 2025
May 29 2025
Change #1151802 merged by jenkins-bot:
[mediawiki/extensions/LockDownEnglishPages@master] Swap the sneakily deprecated (circa MW 1.37) userCan hook to the non-deprecated getUserPermissionsErrors hook; require MW 1.39+
May 28 2025
Change #1151802 had a related patch set uploaded (by Jack Phoenix; author: Jack Phoenix):
[mediawiki/extensions/LockDownEnglishPages@master] Swap the sneakily deprecated (circa MW 1.37) userCan hook to the non-deprecated getUserPermissionsErrors hook; require MW 1.39+
Jan 9 2025
the history of the CongressLookup extensions has in fact been removed from public view
@Dinoguy1000 - thanks for providing the CongressLookup extension as an example. It would appear that the history of the CongressLookup extensions has in fact been removed from public view. It's disappointing that y'all are making the project history unavailable; it's a bit demotivating as a contributor.
Dec 30 2024
It's not archived. It just has to be added back to translatewiki.net and that's it.
Dec 8 2024
Could you point me to an example of an extension that's been archived? How easy is it to unarchive?
Six months since the last comment, and over two and a half years since @RobLa's last comment, unstalling.
May 30 2024
Explicit ping to @RobLa (to make clearer who's addressed by that question)
May 18 2024
I'm going to be bold and decline this task. Feel free to reopen if incorrect.
May 16 2024
@Ottomata: Removing task assignee as this open task has been assigned for more than two years - see the email sent to all task assignees on 2024-04-15.
Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome! :)
If this task has been resolved in the meantime, or should not be worked on by anybody ("declined"), please update its task status via "Add Action… 🡒 Change Status".
Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator. Thanks!
Oct 26 2023
Jul 12 2023
Jun 29 2023
Apr 11 2023
Change 907488 merged by jenkins-bot:
[translatewiki@master] Archive several extensions
Apr 10 2023
Change 907488 had a related patch set uploaded (by Amire80; author: Amire80):
[translatewiki@master] Archive several extensions
Apr 8 2023
Dec 3 2022
Jun 22 2022
Done. Sorry for the delay!
Mentioned in SAL (#wikimedia-releng) [2022-06-22T17:35:18Z] <taavi> gerrit: create group extension-JsonData with robla in it, make it an owner of mediawiki/extensions/JsonData per request in T303147
Jun 16 2022
"If there is a consensus of trusted developers on the Phabricator task, any of the Gerrit administrators can resolve the request." That would be someone listed in https://ldap.toolforge.org/group/gerritadmin
Jun 15 2022
Apr 13 2022
Apr 8 2022
+1, obviously
Mar 30 2022
+1 from me
Mar 24 2022
WMF is trying to stop using on wiki schemas for EventLogging. From our perspective, we can and should remove any support in EventLogging for on wiki JSONSchemas. However there may be 3rd party wikis that use on wiki JSONSchemas via EventLogging, so I'm not sure if we can just do this.
Mar 22 2022
Mar 17 2022
Mar 7 2022
@RobLa, does this extension provide anything that JsonConfig doesn’t / does it anything better than JsonConfig? Nothing against your code, but maintaining two extensions for essentially the same purpose looks a waste of efforts. (Please note that the checklist says to delete only the GitHub mirror; the Gerrit and Phabricator copies should only be archived, so the whole commit history would be retained; if you just don’t want to see your code irrecoverably disappear, you don’t have to worry.)
