[21:37:02] [1/2] one of my wiki editors is having trouble logging in, i'm not sure why. this is the error message they get when they try. their username is PoisonedMaple [21:37:02] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1277743635814809752/image.png?ex=66ce46fe&is=66ccf57e&hm=fef68315b2b0dd6e931049300c2ed132e60556da569daa69cac8a4c3656c1a54& [21:37:51] they've made edits in the past. i'm not sure why this is happening to them [21:46:59] They need to clear their cache. [21:47:04] And cookies. [21:47:16] Its a known bug for which we are waiting for a fix upstream from the Foundation. [22:32:48] oooh okay [22:39:35] tldr WikiMedia’s fault [22:54:34] they cleared their cache but they still can't log in [22:54:38] do they just have to wait? [23:06:03] @originalauthority would it be possible on paper to fork ManageWiki to support single wiki installs [23:08:36] Yes that woulf be createwiki with 1 wiki [23:08:57] Theres 0 chance of managewiki working without createwiki without significant modification [23:09:05] Managewiki is really badly designed [23:10:18] i mean yea- [23:11:28] Judt remove the parts that have the createwiki pages and boom! [23:12:02] i know your version is closed source but is your designed in a way that would allow it, im just curious [23:16:59] Kind of--my version still utilises 2 different extensions, one for creating a wiki and one for managing the wiki, but the createwiki is only separated so the extension is smaller, all it does is call out to methods from ConfigCentre (the managewiki bit) and have a ui for the special page [23:17:32] so your CreateWiki is just a frontend [23:17:43] the orchestration happens by MW [23:18:04] [1/2] You dont really need somethibt like managewiki for a single wiki. All mw does is save stuff to the database, have the ui etc. All of the setting of the config onto MediaWiki is done in MHFunctions. [23:18:04] [2/2] So really you could bring your own managewiki (specialpages etc) and then use a modified mh functions to achieve the same goal. [23:18:21] Yeah [23:18:31] That way my mw ext doesnt depend on cw tables [23:19:01] main thing for me is being able to edit permissions groups and settings on frontend [23:19:26] extensions have to be installed on backend anyways so don’t really matter [23:22:00] Then all you really need is somw special page that writes to a json and then load that json into meidawiki [23:24:10] is there a native mw function to load config from json stuff [23:28:44] no, you can use phps native `file_get_contents` to get the content of the json and then `array_merge` to merge it with $wgConf at runtime if you are using wgConf [23:29:53] [1/8] if not you can do some dubious stuff and just do something like [23:29:53] [2/8] ``` [23:29:53] [3/8] php [23:29:54] [4/8] foreach ( $config as $variable => $value ) { [23:29:54] [5/8] $GLOBALS[$variable] = $value [23:29:54] [6/8] } [23:29:54] [7/8] ``` [23:29:55] [8/8] although thats a bit odd but perfectly acceptable (and is what Fandom did before ucp (not sure if they still do, since they are closed source now [23:30:05] why is that not syntax highlighting [23:30:34] there was attempts to natively read from yaml files in MediaWiki in 1.38 but that went bye bye [23:30:58] but a whole world of opportunities will open up when $wgConf becomes a core service (no idea when that will happen, discussions have been ongoing since 2022 about it) [23:44:15] probably 2042 [23:44:34] so does wgConf work right now [23:57:02] yes [23:57:08] but it is marked as to-be-depreciated [23:57:16] not yet depreciated but 🔜 [23:59:18] Well its not marked as such but theres a ticket to do so [23:59:50] so they are removing it to readd it [23:59:57] ? [23:59:59] No