[01:59:27] MediaWiki 1.44 is the last version DPL3 is going to be supported, starting with 1.45 it will be DPL4! [02:15:16] will ManageWiki automatically update/will it br backwards compatibilile [02:15:59] Backwards compatability might not be done as it will need explicit switching to the new extension. Easy to update ManageWiki though. [02:16:40] will it break for those for dont? [02:17:48] Only for non-miraheze they'll just have to replace the old extension with the new extension, for miraheze we will enable the new one for all those that have the old one. It doesnt immediately break even on 1.45 if DPL3 is kept though. [02:18:13] only categorylinks migration will likely break current DPL3 (and that'll be handled in DPL4) [02:18:24] categorylinks migration is in 1.45 [02:21:50] dun dun dun [02:22:49] categorylinks will break dpl the most since 1.35's revision changes that caused me to fork it in the first place lol [02:23:33] maybe even more so because im not sure what I'll do with the dpl view. Maybe it won't even be needed anymore... [05:50:45] Who will be managing DPL4? [05:50:55] CA? [05:53:43] Me [05:54:23] I've created DPL4 why wouldnt I manage it? Kinda confused what you mean lol [05:56:02] Well creating it... its not done yet... [05:57:06] the pre-release versions on https://github.com/Universal-Omega/DynamicPageList3/releases will become DPL4 in a new repository when they are finished. [05:57:35] I thought Wikimedia was taking over maintainership or something by the way you worded it. [05:58:04] oh no lol. Just me creating a new version of DPL3 updating code that hasn't been updated in like a decade lol [05:58:22] Why change the name then? Are major parts of it changing? [05:59:45] Well the code base is basically being stripped down and reformed. Started with the Query builder which is pretty much done now. High chance I broke something though but much easier to fix things now. Also many functionality/bug fixes are being done in DPL4 that the changes open up the gateway to do... [06:00:15] Also more secure and better performance [06:00:28] Was it DPL3 that was going to conflict with parallelized parsing? Or was the Variables? [06:01:17] PortableInfobox is my extension that is totally incompatible with parsoid [06:01:40] Variables is fixed with it. PortableInfobox is not possible to fix with it under the current state of Parsoid [06:01:52] Ah yes, when do we get a PI rework I wonder. [06:02:21] No matter how its done the way PortableInfobox uses parser functions is completely incompatible with parsoid [06:02:22] I'll give it five years, that'll be when Paranoid is finally done. [06:03:15] Its been in the work for so many years lol [06:03:50] the temptation to say some hyperbole [06:04:57] I already reworked it pretty extensively when I took the extension over lol [06:05:48] I know that it was a Wikia extension before they decided to go behind their back in the open source promise, who was updating it for public wikis after that? Was it always you or was there someone else before you? [06:06:06] There was someone else. [06:06:31] But it kept breaking and then fell unmaintained so I took it over. [06:07:18] I released the builder and stuff (the old maintainer started it in a seperate branch but it didn't work like at all so I redid and fixed large parts of it and released it) [06:07:42] The Infobox Builder? I didn't realise that was part of the extension. [06:07:51] yep [06:07:59] Mind you, after learning the syntax for PI I never used it again on Wikia. [06:08:24] its useful for some very simple infoboxes but the more advanced ones it never is... [06:09:02] I prefer doing all my infoboxes manually, mainly because the builder keeps attaching an extra number after every duplicate component which pisses me off. [06:09:25] Like no, I don't want the first tile element to be `title1`. [06:10:34] I do miss having the Wikia toolbar though on my own wiki, I don't think there are any maintained extensions that add one anymore. [09:19:13] did main page as domain root setting get changed? [09:19:33] [1/2] the main page would always be xxxxxx.miraheze.org [09:19:33] [2/2] now it directs to xxxxx.miraheze.org but later adds /wiki/Main_Page [09:39:51] That's always been the default [10:00:51] really? [10:01:05] i could've sworn it would stay as xxxx.miraheze.org if i set main page as domain root [10:05:29] Ye if you set main page as domain root [10:05:32] But it's off by default [10:05:46] Are you saying main page as domain root is no longer working? [10:08:11] [1/2] Yes [10:08:11] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1393534394454511676/ScreenRecording_07-12-2025_18-06-47_1.mov?ex=6873858a&is=6872340a&hm=8c431357f4b57730dc9962d466f343b05cb3c300444ec0bb7dc2cbf67760466d& [10:08:19] [[mh:utg:Special:ManageWiki/core]] [10:08:20]

[10:08:45] Ok [13:09:15] So what’ll the plan be in 2035 [13:09:28] Core patch? [13:28:51] PortableInfobox will break when Parsoid rolls out [13:28:56] Which is not that far off [14:02:52] The WMF have already said they will patch parsoid to fix the issue. [14:03:02] Whether they do is another story, though. [14:18:46] The plan to have it out by the next LTS seems quite ambitious because even mediawiki.org has quite a few broken places under parsoid. [14:19:32] [1/2] I wonder if they will actually be able to do this by the end of July… [14:19:32] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1393597650225332224/IMG_5360.png?ex=6873c073&is=68726ef3&hm=ce939a117a13a04c9c4ab63c5be3423283f2c7d2fd92494136863646116f8636& [14:19:58] damn a whole year to complete a rollout [14:20:13] you bet your ass they're gonna start later than july [16:24:31] They said it but not 100% counting on it [16:27:05] We honestly can't upgrade so something where that isnt supported without some sort of replacement or fix. It would break to many wikis to extensively [16:27:46] I imagine we'll delay the rollout significantly [16:27:49] Even if we have to patch core in some way that is. [16:28:00] They've said they'll retain the ability to opt out [16:28:11] At both user and wiki level [16:28:15] for now but not forever. [16:28:20] true [16:28:35] But I'd say it'll be like a couple of LTS away before they kill that [16:28:51] Yeah but still that'd only be a few years tbh. [16:28:57] and Parsoid team were supportive of ensuring opt outs were available where needed [16:29:17] Hopefully they find a way to help PortableInfobox in a few years [16:30:24] Indeed. And if we have to we can patch core tbh. I actually thought abour copying a couple core files to PI hacking them and overriding them. Once upon a time it did that with BlockLevelPass but I managed to find a way to avoid it so removed the hack... [16:31:06] Probably best to have a chat with the parsing team if we still have no way forward closer to the end of the wmf rollout [16:31:15] Indeed. [16:31:33] We have options is all I mean here. [16:32:26] But not matter what we can not roll something out that will break PortableInfobox which is used to such an extent and wikis rely on it so much that it is one of those extensions that blocks upgrades. [16:32:27] Not upgrading isn't a long term solution [16:32:54] unless you wanna maintain a fork of mediawiki [16:33:24] Well no but there are options to fix it just no options I like. Even if we have to maintain a single patch for MediaWiki that fixes it (not an entire fork) [16:33:45] If we have to we will do something like that though. As a very last resort. [16:33:52] Fair