[16:07:21] today's question, because I spent too much time looking into it and came away empty handed, even if I'm sure the answer is obvious to everyone else: why do I need to set wgConf up *after* loading (wfLoadExtension) the various extensions? why would it not make sense to set it up first and then when extensions are loaded in, they have it accessible? [16:07:50] I'm very reluctant to write up the 'here's how I set things up and what broke/got fixed in my local setup' doc without this basic understanding. which I am clearly missing. [16:36:02] apergos: are you asking about when/where core creates $wgConf, or about where you define it yourself in LocalSettings.php? [16:36:17] or wmf-config? [16:39:39] I'm talking about instructions for an extension that say 'set up wgConf and add all your stuffs to it after wfLoadExtension('blah')' [16:41:10] so in one's localsettings or wherever else (in production, it would be in CommonSettings I suppose, and in fact before extensions are loaded I think [16:41:17] ) [16:47:06] Krinkle: [16:50:14] https://www.mediawiki.org/w/index.php?search=insource%3A%2FwgConf%2F+-intitle%3A%2F%5C%2F%2F&title=Special:Search&profile=advanced&fulltext=1&ns102=1 [16:50:16] ah so one of those 5 [16:50:40] presumably CentralAuth, the statistical outlier :) [16:51:54] apergos: I'm likely wrong given how special CentralAuth is, but my first guess is that the documentation is wrong. I suspect it was blindly updated from a time where it said "require_once CentralAuth.php" and was changed to wfLoadExtension() without revisiting the information it conveys. [16:52:13] Back then, the php entrypoint of an extension would define your globals default values. [16:52:20] so doing it before hand would be a no-op. [16:52:30] that's the missing piece right there tyvm [16:52:57] I loooked n vain for something like that, didn't find it, read through a bunch of other not-too-related-stuff but oh well, and finally bailed [16:53:31] Nowadays we have ExtensionRegistry and that defers the loadig of extension.json until after LocalSettings.php is done, and it then additionally takes care only to define what you didn't define already. So it's kind of a retroactive default. [16:53:35] and I deliberately didn't frame it as being about a specific extension because this is more about how the general mechanism works [16:53:52] Yep, and you were right. [16:54:10] as defaults should be, don't override stuff the user has already taken care to define [16:54:12] good good [16:54:13] and it also wasn't (at the time) specific to $wgConf, it applied to any local settings [16:54:19] right [16:55:37] thanks for that info, it was badly needed [16:55:54] apergos: specifically, it will have been about where you call extractAllGlobals(). Defining $wgConf itself is just an array so that's safe any time. [16:56:06] but yeah you can probably remove that warning now [16:56:46] I'll ignore it for now; what I want to do is rearrange my local files the way I htink they ought to go, verify that eveything is still good, then write that upas 'here's an example' [16:57:00] and I'll make a note about doc changes and such to be done later. [16:57:06] (I shan't forget.) [16:57:26] this is how docs get updated, right? the next new person tries to follow them, something is weird, they fix them? :P) [17:07:06] Yep! [17:08:07] certainly beats each person time-traveling to 2006 to ask Brion how it works [17:26:57] hey don't knock time travel until you've tried it