[17:44:13] @originalauthority when you did https://github.com/miraheze/mw-config/commit/18d3158c8a81cf45da4caad49e7a0708dad76b28 did you also use toggleExtension --disable to disable it on all wikis? [17:44:26] yes [17:44:53] hmm, so that wouldn't likely be the cause of the drafts issue [17:45:07] @cosmicalpha suggests it's because an extension is present in s_extensions that isn't in MWE.php anymore [17:45:55] Yeah if even one is still in DB that isn't in MWE.php it would cause the error. [17:45:59] but I don't see any recently removed extensions [17:46:08] https://discord.com/channels/407504499280707585/808001911868489748/1199120198175838298 [17:46:40] (and it deffo worked because it took forever) [17:46:48] oh, I thought it had to be lowercase `editnotify` [17:46:59] like the variable name in MWE [17:47:06] maybe it took forever because the servers were so slow back then [17:47:07] It does yeah [17:47:18] I vividly recall it outputting to the screen [17:47:40] Even if it didn't work it would still take forever as it still does the script on it on every wiki. [17:48:13] You can look in Graylog for something mentioning s_extensions and something might show up. [17:50:32] Hmm, now even trying to run toggleExtension --disable on that wiki returns the same error [17:51:12] Indeed that is why you have to remove before removed from ManageWikiExtensions.php or it doesn't work, you'll have to readd to remove. [17:51:47] ManageWiki can be annoying sometimes! [17:53:08] Yeah... [17:55:09] let's see if that was the issue [17:55:37] yep, that was it [17:55:42] I'll run the foreach command now and then remove again [17:56:23] case sensitive is the worst [18:10:48] [1/2] This is nothing to do with this I'm just curious on how this works and can't find anything in either MHFunctions or ManageWiki, but where does ManageWiki override default permissions? [18:10:49] [2/2] I know in MHFunctions we extract from the JSON wgGroupPermissions and load it into $wgConf, but surely that we must be unsetting the default perms somewhere? or else something being missing from wgGroupPermissions but assigned by default would still be assigned? [18:11:04] Nothing to do with this like I say, just on a quest to understand fully how this beast works 😆 [19:03:22] it puts that in wgConf using `default` which overrides the default, if it was `+wgGroupPermissions`, then `default` would append rather than overwrite but since it isn't it overwrites. [19:05:49] Ahhh I see [20:48:14] FYI, I've restricted those that can create dashboards on phabricator to trusted contributors (and admins/acl*security). We've got way too much uncontrolled spam there to allow it to remain open to all users. [21:15:14] <.labster> Spam still exists tho [21:15:41] <.labster> [1/2] Meanwhile, I love clearly written error messages, when they're correct: [21:15:41] <.labster> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1202361586837364776/Screen_Shot_2024-01-31_at_1.10.54_PM.png?ex=65cd2d7d&is=65bab87d&hm=38a2131caf6408e74b83cccbb7009ea8a0aaf5c121d1cc1f7cb05ab22ba7811f& [21:18:54] Yeah, deleting manually takes some time, there's probably a faster way to do it, but I have no idea how to best do that and disable the relevant accounts at the same time. [22:25:36] Dashboards have been purged, taking a break before cleaning out spam panels [22:30:30] we should update https://phabricator.miraheze.org/W1 to say Phorge instead of Phabricator (if a phab admin could do that) [22:31:34] done