[14:12:16] !cache [14:12:16] General information about caches can be seen at , for configuration settings see [15:02:31] MW 1.35: Curiosity question, I have a courts page from WP https://digitalmatrixgroup.com/index.php/United_States_District_Court_for_the_Northern_District_of_California dependent upon a template from WP https://digitalmatrixgroup.com/index.php/Template:United_States_9th_Circuit_district_judges Are the names of the judges updated manually when [15:02:31] elected or is this an API? [15:03:08] E.g.; when it updates on WP does the new data flow into my wiki when the page is called as it does now? [15:04:26] Right now there is a call that pulls the images, info, etc. I don't understand it but figure it is an API is the same true here? [22:17:35] Hi, anyone may be familiar with this exception while using Cargo? https://pastebin.com/gUxAj1St [22:18:30] Sry, full stack trace: https://pastebin.com/McL4SzFb [22:57:45] Anybody know off the top of their head what the setting is that forces users to email verify to edit? [22:57:57] I need to turn that off for my test install haha [22:58:51] $wgEmailConfirmToEdit [23:02:57] Great, they did it some other way then. Thanks anyway. [23:03:44] lmao [23:04:04] I hate taking over existing networks [23:04:11] Because of stuff like this right here [23:05:06] https://www.mediawiki.org/wiki/Do_not_hack_MediaWiki_core [23:05:27] Unfortunately people just copy answers of SO [23:06:21] Are you working on your upgraded version? [23:06:26] Yeah. [23:06:35] so it should be in LocalSettings.. Or an extension [23:06:42] That's my guess. [23:06:56] Although to be fair, I just worked around it by setting that variable to false at the bottom [23:07:06] So... at least I can continue for now? [23:07:26] potentially, yeah [23:07:28] I'm definitely going to be spending a lot of time fixing this giant mess [23:07:53] And getting things in a vcs :P [23:09:03] it's slightly odd [23:09:10] $wgEmailConfirmToEdit has been there since 1.6 [23:09:17] like 14 years :D [23:09:43] I bet they probably set it in some obscure file somewhere. Or some extension. [23:09:58] or some weird abstraction [23:10:22] Setting it to false at the end of settings and enabling the sysop "edit" permissions did the trick anyw [23:10:33] I just need to edit the javascript so it isn't a big deal [23:10:59] Once the upgrade is complete, I'm going to burn this down and start over anyways. [23:29:13] Unrelated question, if you specify a messagesdir in your extension.json, all you should have to do is place your (lang).json in the i18n directory and they'll get automatically loaded for your set language, right? [23:31:06] Depends on your config... But yes [23:33:03] Is it mandatory to have a qqq.json? [23:33:23] In Wikimedia CI it is, but otherwise, no [23:33:38] Hm. Must be a bad config somewhere then. [23:34:13] I have my directory set, I have an en.json, I have the extension.json specifying the message to use for the description, but I still get a {ext-desc} on the version page. [23:34:31] You might have some sort of localisation cache like Wikimedia do [23:34:55] look for something like... [23:34:58] $wgLocalisationCacheConf['storeDirectory'] = "$IP/cache/l10n"; [23:34:58] $wgLocalisationCacheConf['manualRecache'] = true; [23:37:41] Nope, nothing like that [23:39:39] What did you actually put into extension.json [23:39:50] Hang on, I'll pastebin it [23:39:51] "MessagesDirs": { "CodeReview": [ "i18n" ] }, [23:41:40] https://pastebin.com/5wYkMrYv [23:42:00] Wait, is it messagesdirS [23:42:05] With an "s" after dir? [23:42:26] Ja [23:42:49] My god. Once again, you save the day. [23:42:53] look at docs/extension.schema.v2.json [23:43:19] You can also run maintenance/validateRegistrationFile.php to do some validation [23:43:26] If the keys aren't liked, it should complain [23:43:34] Nice, good to know! [23:43:45] Won't necessarily tell you what to replace them with, but should be usually obvious enough if it's a typo like this [23:44:26] Hey, if I can at least validate it, I can figure out what I screwed up on my own [23:44:45] Just happy to know there's a tool to check for my own stupid spelling/syntax errors [23:45:17] Seriously, this had been bugging me for like a week, but I'd put it off because it wasn't priority. Thank you. [23:45:32] * Reedy adds a line to the invoice [23:45:45] lol [23:54:38] I guess the next step now is to check what core files were modified in the mobilefrontend extension :) plz kill me thx [23:57:53] hopefully no JS ones... [23:57:57] cause that'll be a shit show, frankly [23:58:16] Actually... Maybe on an old enough version of MF... it might not be (but replicating them forward could be fun)