[00:01:14] Just that there's so many pages that I think it might be quite much. [00:01:29] How many pages does AVID have? @thedemon08 [00:06:19] I don't think he'd know [00:06:45] when is this wiki going to be back up and running easily [00:07:12] not sure to be quite honest. I'm going to look into how to get things sailing a bit more smoothly [00:07:26] I'm guessing removing some unused extensions might help [00:07:44] where are those unused extensions [00:07:49] ¯\_(ツ)_/¯ [00:08:26] Assessment is the first step in this process, which is part of what Agent's doing in the background. 🙂 [00:09:23] assessment [00:10:19] [1/2] what if the extensions are used [00:10:19] [2/2] you're breaking more stuff lol [00:13:18] That's why assessment comes first - figuring out the trouble extensions and whether they are used. [00:14:07] either wiki or no wiki, what do you pick \:P [00:14:21] ok [00:14:27] [1/2] these guys aren't idiots [00:14:27] [2/2] I trust they know what they're doing [00:14:38] me too [00:14:40] In all seriousness, I'm not 100% sure if it's an extension but if it is then I'm guessing it's an unmaintained extension that might cause that [00:14:40] I for one like wiki more than no-wiki. 😄 [00:15:51] what is that Unmaintained extension [00:16:18] When extensions are created, sometimes the original creator and community lose interest in keeping the code behind that extension up to date. [00:16:59] When that happens, it's referred to as unmaintained. As the state of technology moves forward, sometimes that older code breaks and the extension stops working. Or worse, starts eating all the server resources. [00:19:13] who wrote the original code [00:20:19] please stop positing these things, they clearly do not come from a place of familiarity and are clearly incorrect [00:21:05] Well, I'm not familiar with it, either. I'm honestly just as confused as everyone is right now. [00:21:24] so, let it be and let those more familiar troubleshoot without positing confusion [00:21:27] We don't know which extension is the problem yet (or whether it is an extension to blame), so it's too early to say. That's what we're looking into [00:21:28] things like UploadWizard and Tabber [00:22:29] [[mw:Category:Unmaintained extensions]] [00:22:45] [[:mw:Category:Unmaintained extensions]] [00:22:46]

[00:25:38] that [00:25:53] which one of those might be causing that problem [00:26:23] thats what agent doing [00:26:56] Avid.wiki is back on, but i can't edit to loss of session data [00:30:02] That means something's wrong. [00:30:19] Can't edit, log out, or log in if you clear cookies. [00:30:26] Just wait patiently. [00:30:41] well, i'm already log in [00:31:00] something's been wrong since yesterday [00:31:14] Repeatedly noting the situation doesn't help with the situation [00:31:29] They are already looking into it [00:31:42] FarmerShire's talking isn't exactly helping either. [00:32:03] I was talking about them. [00:32:16] Oh, OK. [00:33:05] Please, just wait patiently until the SRE identifies and fixes the issue [00:33:39] Data is likely not going to be lost, and this is more or less just a downtime [00:35:27] Alright. [00:36:09] Let them fix it and do not make baseless guesses [00:50:21] invalid CSRF Token on AVId.wiki [00:50:44] just wait [00:50:48] [1/2] > Repeatedly noting the situation doesn't help with the situation [00:50:48] [2/2] > They are already looking into it [00:51:14] good news is that accessing to the website is back up and running [00:51:35] also this https://discord.com/channels/1088870295412146347/1130665399386656838/1140444805416104026 [00:51:45] [1/2] > Repeatedly noting the situation doesn't help with the situation [00:51:45] [2/2] > They are already looking into it [00:52:14] thanks [00:52:40] no, I invalidated CosmicAlpha's user sessions [00:52:46] oh [00:52:51] To log everyone out, you need to edit LocalSettings.php [00:53:03] Have I not told you guys to stop speculating... [00:53:14] ok sory [00:53:14] Well good news, things load now [00:53:21] mw2 was the issue it seems, not poor mw1 [00:53:33] Interesting find. [00:55:02] wait so not php? [00:55:23] not not PHP, that's part of the function of the mw servers [00:55:47] i meant php wasn't the problem [00:55:51] Assessment is still underway, let's let 'em keep at it. [00:56:04] This hasn't ruled out PHP, exactly. [00:56:41] As has been reiterated a few times though, speculation isn't a good idea while they're still looking into things. [00:56:56] Mw2 [00:58:10] i was asking [00:58:34] Asking doesn't mean that you aren't speculating. [00:58:46] You guessed, so you were speculating already [00:59:31] . [01:00:03] "not" something is a guess. [01:00:05] php8 wasnt working for mw1 [01:00:20] Doesn't mean it is working now [01:00:28] So it's a guess. [01:00:37] Can you please, just stop. [01:04:08] I think everything's fixed [01:04:08] [1/2] Gonna ask all involved in this particular topic to take a break for a little bit. [01:04:08] [2/2] Nothing to be gained at this point. [01:06:55] okay for that I'm not sure [01:08:15] I don't see this when I visit avid. just fyi. [01:11:30] Can’t even log out to try logging back in lol. [01:12:19] Also, found some Miraheze leftovers [01:15:45] pretty sure one of your admins changed that message to say that [01:20:33] Well I found the message, but I can’t edit because of this token issue 😆 [01:21:17] token issue [02:01:08] I'm going to kindly ask that you stop repeating technical words/phrases. This isn't helpful to the community and doesn't improve the conversation being had. [02:07:47] ok [11:11:47] DCM is still inaccessible due to 502s [13:02:34] that's an extension problem, not wikiforge's [13:02:57] whats that [13:05:25] portableinfobox [13:07:12] i see [13:49:09] That's why you should use Lua module infoboxes instead of PI [13:49:28] Scribunto is officially maintained [13:50:07] So it won't be down in major MW releases unless there's a giant security issue [13:50:43] And if issues hit that, it affects all Wikimedia wikis, so they will scramble every person to fix that [13:51:40] PI after all is just a port of the Fandom extension where Fandom isn't even running the latest version of MediaWiki most of the time [13:51:54] [1/2] and that's why you should use wikitables [13:51:55] [2/2] guaranteed no problems forever [13:52:03] lol [13:52:26] Nein, that only has equal risk with modules [13:56:47] nee [13:57:49] nee, lua boxes hard to import and weird parameters [14:03:43] Wikitables aren't supposed to be used for templates for starters. Using wikitables with #if parameters are counterintuitive (have to evade the pipe and equal signs when designing them) and are extremely ugly and hard to format. [14:05:04] [1/2] then why are {{=}} and {{!}} magic words [14:05:04] [2/2] and lua with all the invokes is uglier [14:05:55] Oh btw, only one invoke is needed for all infobox templates on one single master template [14:06:04] So if you have multiple involes [14:06:13] You're actually doing it wrong. [14:06:52] [1/2] the lua code is messy [14:06:52] [2/2] really this is just subjective [14:07:33] Lua code is complex, but well far from messy. [14:07:45] you have to learn lua [14:07:55] [1/3] wikitext is [14:07:55] [2/3] ... [14:07:56] [3/3] wikitext [14:08:08] Since when does someone have to learn Lua when they just import the entire thing over..? [14:08:25] when someone wants to modify something [14:08:28] Wikitable infoboxes can't perfectly have a master template due to the parsing [14:09:10] Nope. The infobox template needs not be modified at all, it's designed to take customization on it's usage end. [14:09:14] and also there's problems when importing all the time [14:09:20] ok fine [14:10:24] That's only coz you didn't import everything. At least things don't break once you imported everything, and wikitable infoboxes will break at random times due to unknowing restrictions fro syntax. [14:10:41] Also the "module not found" error is pretty self explanatory [14:11:11] It is precisely not found i.e. not imported. [14:11:13] sometimes it's not [14:11:17] PI Infoboxes are fixed btw [14:11:37] Good to know. [14:11:37] to each their own but I like PI because of how easy it is to use [14:11:52] With too many restrictions. [14:12:06] It's easy but terrible for aesthetics [14:12:34] If you don't need something too terribly complex then you're fine [14:12:36] And more complex template code to apply special things onto the template [14:12:42] of course, if you're a power user then that's different [14:13:33] A single color/style change based on a parameter is already annoying and counterintuitive enough [14:14:06] [1/2] not complex? [14:14:06] [2/2] ᵥᵥ ᵢ ₖ ᵢ ₜ ₐ ₆ ₗ ₑ ₛ . [14:14:11] I applied Wikipedia infobox CSS onto my PortableInfoboxes so I'm good \:P [14:14:24] That's arguably worse. [14:14:31] how? [14:14:41] it's literally a table [14:14:56] /table {| |} [14:14:58] Oh right. Forgot Wikipedia infoboxes always have parameters to affect the colour of the infoboxes. That doesn't help on PI. [14:15:48] You should really look at how complex the infobox template on Wikipedia used to be before it became a module. [14:18:28] [1/2] if you don't have to change lua code then you don't need to change wikitext code either [14:18:28] [2/2] logical [14:19:21] Nope. The wikitext version has quite a few subpages, and they would sometimes (or even always) have issues with your wikitext. [14:19:32] same for lua [14:19:48] No. Lua doesn't break other things. [14:20:10] what "have issues with your wikitext"? [14:20:15] Wikitext breaks other wikitext [14:20:21] Lua doesn't [14:20:28] does [14:20:35] it's still a template [14:20:48] Nope. If there's an error in the Lua template, it gives an error [14:20:56] except the wikitext isn't broken [14:21:01] If there's an error in the wikitext template, it breaks other wikitexr. [14:22:41] if everything with closing/unclosing tags is bad then program your website with css [14:22:44] [1/2] Worse, it's tedious to add parameters on the wikitext template, you have to manually change the parameter names [14:22:44] [2/2] Lua modules run on loops so its kust one number. [14:23:10] Funny that Lua templates don't have that issue. [14:23:29] Coz there aren't {{#if:}}s lying everywhere. [14:23:38] what infobox will use a thousand rows [14:23:54] invoke [14:24:08] Which only appears once unlike #if. [14:24:27] and lua code has brackets [14:24:48] and what if there's a broken wikitext template before the infobox [14:25:04] Oh yeah. As if changing one number has more chances of breaking a bracket than replacing hundreds of numbers. [14:25:29] [1/2] > and what if there is broken wikitext before the template [14:25:29] [2/2] Doesn't break it. [14:25:37] whag "replace numbers" [14:27:20] Adding parameters. If you use consecutive numbers, of course it never exceed the limit, but that's the worst practice of all. Leaving big gaps between row(n) is the norm for allowing adding things in between when designing specialised infoboxes. [14:29:22] [1/2] what "doesn't break it" [14:29:23] [2/2] it obviously breaks [14:29:48] what? [14:29:50] Have fun manually adding label(n), labelstyle(n), data(n), datastyle(n), class(n), rowclass(n) onto the master template. [14:30:03] oh [14:30:17] well there's no problem with that [14:30:20] While I just only have to edit one number. [14:30:43] The count on the for loop in the lua module. [14:31:22] Sigh. Learn more about the topic before arguing with others. [14:32:03] [1/2] i said it's subjective here [14:32:03] [2/2] and you didn't stop [14:32:17] There are many objective points on the issue [14:32:23] And you just ignored it and called it subjective. [14:33:03] it's subjective [14:34:41] Also: whoever "beginner" decides to start editing advanced parts like modules before even familiarizing themselves with the basics of that is clearly 未學行先學走 [14:35:06] Everything involving templates and modules aren't intended to be starter level. [14:35:09] can't read [14:35:19] Translator exists. Wiktionary exists. [14:35:33] [1/2] and actually there's no need for `data1` `data2` ... parameters [14:35:33]