[00:02:16] [1/3] Hmm. If I specify the Data namespace explicitly, it does exist and come with json by default, but it still doesn't have all the boilerplate pre-filled unlike my local testing environment, so somehow JsonConfig and Chart are not taking over this namespace. [00:02:16] [2/3] https://cdn.discordapp.com/attachments/1006789349498699827/1469483363273281659/image.png?ex=6987d287&is=69868107&hm=a70365eb4d3469bb604f2ef4a718bd85a584e559f18e96a6b39a254169b5d676& [00:02:16] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1469483363730718820/image.png?ex=6987d287&is=69868107&hm=d2c59c50ca4e7ac1ce03e10b05dce2d4a9796fe5e0983215274dadd757a18be4& [00:25:48] [1/4] ^ this is the warning I'm talking about [00:25:48] [2/4] ``` [00:25:49] [3/4] PHP Warning: JsonConfig: Invalid $wgJsonConfigs['Tabular.JsonConfig']: Namespace 486 is already set to handle model 'json' [Called from JsonConfig\JCSingleton::parseConfiguration in /srv/mediawiki/1.45/extensions/JsonConfig/includes/JCSingleton.php at line 138] in /srv/mediawiki/1.45/includes/debug/MWDebug.php on line 485 [00:25:49] [4/4] ``` [00:25:56] namespace 468 is "Data" I believe [01:01:08] [1/4] Hmm that's odd. My original hypothesis is that: [01:01:08] [2/4] Before NS 468 is added to ManageWiki: JsonConfig tries to create NS 468 from its config but the NS gets removed by ManageWiki, resulting in nothing showing up in Special:NamespaceInfo. [01:01:08] [3/4] After NS 468 is added to ManageWiki: the NS does exist but JsonConfig is for some reason failing to take over this NS. [01:01:09] [4/4] From the warning you have shown, it seems that NS 468 already exists before I added it to ManageWiki? [01:01:31] 486 [01:06:15] Oh yeah I'm blind lol [01:16:29] @posix_memalign when testing locally do you set https://github.com/miraheze/mw-config/blob/d0d89066c05f8ee9884365319d5030bb23b5683a/GlobalSettings.php#L637 ? [01:17:00] isLocal = false prevents NS creation it seems looking at code. We have the same setup as the WMF though there. [01:45:09] In my local testing environment I had `'isLocal' => true`. [01:45:27] hmm odd [01:46:11] I figured that we don't want to host charts in commons like the WMF so isLocal => true is the sane choice here. [01:48:20] Yeah. I can look more at this tomorrow if you want. [02:03:18] [1/2] If I mark isLocal as true for both JsonConfig and Chart I get this exception, which is very odd considering the point of isLocal is to disable querying json data stored on commons. [02:03:18] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1469513825693859961/message.txt?ex=6987eee6&is=69869d66&hm=6180f5a039811298f50d93e1d466819966870f16825ef2abfb323341b0a0db7d& [02:34:10] The error is due to `$wgTrackGlobalJsonLinks` which goes away after I disabled it. [02:34:47] [1/2] Yeeeessss! I think having the Data namespace managed by ManageWiki somehow prevents JsonConfig from taking it over. [02:34:47] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1469521747995787390/image.png?ex=6987f647&is=6986a4c7&hm=1e3298cb4e73cb46ac72d96c80b65c68e3db3bbdd96876de663bdbc4d13a8ad7& [02:40:50] Still wrestling with `The page title you have specified does not match any of the patterns configured for the JSONConfig extension for this wiki.` when creating `Data:Chart.chart`, but at least there's some progress.