[00:38:16] [1/3] uh... [00:38:16] [2/3] on https://battlecats.miraheze.org/w/load.php?lang=en&modules=site.styles&only=styles&skin=citizen when logged in [00:38:17] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1523488217104646196/image.png?ex=6a4c4a78&is=6a4af8f8&hm=09c1d71b025217c58971ddc6f1533e85397abedc4b187b59cca94fd956fd9101& [00:39:04] (error is just that db161 wasn't available at the time this was cached, but I don't know how to fix it) [01:00:03] If you can check the headers (cf-cache-status or x-cache), it should show where it's being cached [01:06:12] (it loads properly for me so I can't really help) [02:31:59] If it's cached by Cloudflare you can mass-purge cached resources by prefix (e.g. `.../w/load.php`) [03:11:45] What kind of settings? For ones that don't exist past 1.46 I would assume they're handled the same way as before, either once we start migrating prod wikis to 1.46, or just beforehand, we remove those settings from their ManageWikis. [03:13:39] Although, if the removed settings can't be set via ManageWiki, then we just make a PR to remove them from the associated `mw-config,`, repo files that contain those settings. [04:10:35] LocalSettings.php can be versioned (e.g. https://github.com/miraheze/mw-config/blob/aa553891a05d730b09abeb6304f2db0571df2492/LocalSettings.php#L6917) [04:11:38] And for more complicated settings we can use PHP to manually check the version. [08:37:35] [1/2] https://exttest.mirabeta.org/wiki/VoteNY [08:37:35] [2/2] The extension kinda works but its template such as numberofvotespage didn't parse in the extension wiki [08:50:15] ^ `{{numberofvotespage}}` is in Special:Version so at least that part works. Same results for legacy parser and parsoid. [11:45:13] cached on cp201. cf cache only lasts for 5 minutes for this css [11:58:54] what about in managewiki though? I think it would be probably confusing if production wikis had some configuration that doesn't work, but it would also be useful for beta wikis to be able to test out the new configurations (namely scribunto shared invocation env) [12:08:45] We can make it `managewiki-restricted`? [12:19:55] [1/2] ig that works [12:19:56] [2/2] and then for stuff like vectornightmode that's getting removed, should we just mark them as 1.45 in localsettings, and remove them once all wikis are upgraded [12:28:38] Yeah I think that's reasonable. [12:42:03] [1/2] Btw I think we should get a list of extensions we want to undeploy for this MW upgrade cycle again. DataTransfer is on my personal list right now because I think it is currently broken and serves a very niche use case. I am not even sure how it got added in the first place. [12:42:04] [2/2] There's also LanguageSelector, AutoCreatePage, CleanChanges, and MagicNoCache which we've discussed already. [12:42:42] FeaturedFeeds is another one of them. Exactly 0 wikis is using its features, which require custom configurations in mw-config. [21:24:34] [1/2] https://cdn.discordapp.com/attachments/1006789349498699827/1523801859893235762/image.jpg?ex=6a4d6e92&is=6a4c1d12&hm=3f2b28d6c542a943b447a354ce5e6f7ca153c048f7b3c604c84726af69ffc8d4& [21:24:35] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1523801860518183013/image.jpg?ex=6a4d6e92&is=6a4c1d12&hm=495bd22cd60b2dc0bb57bfbf603995468eb8e815dfa8b68603782676c8188281&