[07:06:53] @cosmicalpha should we raise parsoid cache duration? [07:07:22] It's only 24 hours compared to 7 days for standard parser [07:07:35] And I'd argue parsoid is more expensive to regenerate [07:09:48] Potentially [07:10:29] @cosmicalpha I assume we've now got more than enough disk to accommodate it [07:10:53] Oh yeah we have 4TB of DB space (1TB per DB) [07:11:42] It should be less anyway as parsoid splits less [07:11:49] I'll open that PR later then [18:18:50] Miraheze\ManageWiki\Helpers\ManageWikiRequirements::process(): Argument #1 ($actions) must be of type array, null given, called in /srv/mediawiki/1.40/extensions/ManageWiki/includes/Helpers/ManageWikiExtensions.php on line 158 [18:18:51] https://github.com/miraheze/mw-config/blob/master/ManageWikiExtensions.php#L417 [18:18:57] does anyone see what the problem here is? [18:19:05] cc @originalauthority since you added it [18:36:16] I don't see the issue, hmmm [19:13:14] Hi all, I opened to day an account on Miraheze to migrate a Mediawiki site but I have some questions regarding the migration process [19:13:22] Is this the right channel to ask for that sort of thing? [19:16:06] Ye here is fine [19:17:35] So we’ve got a Mediawiki site with images, custom JS and custom CSS, edited LocalSettings.php and database modifications from several extensions [19:18:07] However in Miraheze it asks for the XML dump only, so I’m wondering how we could go about migrating the whole thing [19:18:13] If the extensions are within our portfolio, that's easy [19:19:02] I haven’t checked yet, there’s nothing too exotic, but if it’s not the case is there some way we could do it without uninstalling them? [19:19:09] We can import images [19:19:31] We can review any extensions not within our portfolio but that can take time [19:20:33] How about DB, LocalSettings.php? [19:20:48] Settings we can help you migrate [19:20:57] Lots of it can be done from ManageWiki [19:20:59] By you [19:21:14] Ok then, I’ll start by checking the extensions then [19:21:28] We don't normally import the database if we can work with xml + images [19:22:02] If there's specific data you'd like to keep that isn't in an xml or image dump then we can look at what's possible [19:22:32] Are registered users also in the XML? [19:22:50] Users will be able to recreate their accounts and still keep edits assigned [19:23:08] That’s great to hear [19:23:15] We don't use normal mediawiki login [19:23:34] If you have usernames + emails, we could create them in advance though, that should be possible [19:23:41] So they just need to reset password [19:26:43] Thanks, I'll start to check the extensions and take it from there then (by removing the ones unsupported if we can) [19:31:24] Let me know if there's any questions [19:32:02] And if you do disconnect, please feel free to drop me an email via [mycurrentnickname]@wikitide.org [19:32:17] [mycurrentnickname] = RhinosF1 [19:35:39] Thanks a lot [19:35:42] I’ve checked our extensions and there’s one that’s quite important that isn’t supported by Miraheze: I’ve checked our extensions and there’s one that’s quite important that isn’t supported by Miraheze [19:36:18] https://www.mediawiki.org/wiki/Extension:MP3MediaHandler [19:38:58] I can see that TimedMediaHandler supports MP3, so it’s not a total deal breaker [19:40:53] However one we heavily use is ReplaceText which isn’t supported either [19:41:14] How can I ask for these two extensions to be reviewed? [19:43:02] there were issues w/ replacetext, it was on Miraheze before [19:43:36] ReplaceText isn't possible for technical reasons, something with compression, that is being used I think it was, the alternative would be https://www.mediawiki.org/wiki/Extension:MassEditRegex (though it does require you know a bit of regex to use) [19:44:15] Regexes are fine, no problem [19:44:22] If there’s an alternative that should be ok [19:44:36] Correct, ReplaceText isn't compatible with RevisionCompression, which became necessary as we're a non-profit on a limited budget. [19:45:28] MassEditRegex isn't completely 1:1 feature wise, but should cover several use cases you may have. 🙂 [19:50:26] As has been said, replacetext is a no [19:50:58] As for the other, a review is possible, it doesn't look overly complex but TimedMediaHandler should work fine [19:51:10] You can request a review on [[Phabricator]] [19:51:13] I’m happy to use TimedMediaHandler if it supports MP3s [19:51:38] MP3MediaHandler seems to be abandoned [19:51:47] It doesn't seem well developed [19:51:49] (Last update is 2016) [19:52:21] Tbh, I can’t remember why we went with MP3MediaHandler in the first place [19:52:26] Some extensions don't need updates often [19:52:38] safe to assume people moved on timedmedia [19:52:46] Yeah, I guess it just used the bare minimum we needed [19:52:54] But it's a big risk especially with the seemingly huge migrations upstream seem to come up with every release at the moment [19:52:57] Yeah, I guess it just covered the bare minimum we needed