[00:00:30] All the wiki has fallback to English Namespaces. All Namespaces with Spanish names are non-existenr [00:00:49] That affects things like Plantilla - to Template [00:00:58] So all the templates are broken [00:01:10] It is a known issue? [00:01:46] Example: https://tuscriaturas.miraheze.org/wiki/Nnai [00:02:55] Well, right now isn't even showing. I am not in a rush. Just want to know if I Have to open the phabricator or there is already one. [01:18:07] Jakeukalane, YellowFrogger reported a similar issue on SN. Can you file a Phabricator task about this? [01:18:35] i'll try [01:18:52] okay, thank you :) [01:19:02] we can fix it up and add to it as needed [01:20:53] @Doug If you want, you could have a look into (you know what I'm referring to) tomorrow, since it might not get completed right away. [01:25:41] DarkMatterMan4500, yeah I've got some IRL things to do tonight, but will try and get to the above tomorrow. :) [01:26:53] @Doug Okay, also, as a bonus, why not remind yourself the very same thing instead of having me always remind you every so often? [01:29:19] Simply reminding yourself is kind of like setting up a schedule in a way. [01:32:21] DarkMatterMan4500, you don't have to remind me, though. I do remember. It's just a matter of prioritization :P [01:33:38] That's the point. Reminding yourself is a number one prioritization after all, just a though. 🙂 [01:33:57] 👍 [01:39:46] https://phabricator.miraheze.org/T7456 [01:39:54] don't know if I explain myself well [01:40:07] if I am not clear, ask me what is not clear for you [01:42:47] Jakeukalane, cool, thanks :) [01:43:05] thanks to you [01:44:01] np [01:47:29] I know we had this with 1.35 also, trying to figure out how it was fixed. [01:47:55] it should auto-correct itself after a couple days. [01:48:05] there is already 3 tasks about it also. [01:48:42] dmehus: ^ (also see #miraheze-sre) [01:52:15] Universal_Omega: ack, thanks, I don't know how to merge tickets together to link them under one parent ticket, so I'll let you do that [01:52:50] if it auto-corrects itself after a couple days, that sounds like a Varnish or MediaWiki cache issue maybe, no? [01:53:30] dmehus: they should be closed as duplicates of the first one, no need to have all open. And no, its CreateWiki and 100% impossible to fix without undoing two years of work to the extension is what I remember John saying last time. [02:00:22] seems it works now [02:00:30] except our css modifications [02:01:04] links are shown in a different colour. maybe I should edit the phabricator task to only reflect that? [02:01:21] maybe the other tasks doesn't have that part [06:15:05] Could anyone help me figure out why the personal URLs cannot be clicked on snapwikiwiki, please? I can only reproduce it on modern Vector. Link: https://snapwiki.miraheze.org/wiki/Main_Page?useskinversion=2 [06:15:14] @CSS/JS Support Volunteers ^ [06:16:45] @R4356th: What do you mean? It works for me. [06:17:15] Are you using Modern vector? [06:17:28] Yes. [06:18:24] Weird. [06:18:29] https://cdn.discordapp.com/attachments/435711390544560128/853518671140880414/unknown.png [06:18:36] Screenshot ^ [06:19:02] Oh I'm on mobile so it looks different. [06:19:15] Ah. [06:19:35] Was Parsoid config changed? [06:19:40] No. [06:20:19] Weird, there are Parsoid-related anomalies. [06:20:41] @R4356th: example? [06:20:57] https://github.com/snapwiki/wiki-mirror/commit/15d0df050f2f7e0a53ba3243e52bfb47458ca683 [06:21:09] Specifically: https://github.com/snapwiki/wiki-mirror/commit/15d0df050f2f7e0a53ba3243e52bfb47458ca683#diff-357428038377fc22d778b1ce9501b77002b3d1e83a7aa30f79ff2f5b0a6ca52d [06:21:40] The revision was not suppressed. [06:21:46] It should not complain. [06:22:24] I meant on-wiki example to see what it's doing. [06:22:52] On-wiki seems normal. [06:23:13] But the endpoint is definitely not okay. [06:24:14] I'm still not sure I see the issue. [06:24:28] Can you screenshot what you mean? [06:25:18] Screenshots won't help; it is a technical issue, not a visual one. Parsoid is returning error 404 for a revision that exists and has not been suppressed. [06:25:49] And I do not believe you can reproduce it on-wiki. [06:26:53] Oh. Hmm. [07:00:26] I figured the Parsoid issue out. [07:00:50] Which parsoid issue? [07:01:21] RhinosF1: a discussion before you got here. [07:01:52] Previously, Parsoid did not care about subpages and just returned the content of the parent. It now correctly returns error 404 which our wiki mirror [07:01:58] 's code was not ready to handle. [07:02:44] So I guess it's an issue on our side. [07:03:09] still wishes Parsoid was able to handle subpages [07:03:30] Ok [07:03:39] Im sure it will soon [07:04:05] They said in Feb 2020 that in 18 months they wanted Mediawiki to only have 1 parser [07:04:46] RhinosF1: Do you have links? (Also, sorry if my messages seemed weird and lacked context.) [07:05:05] And I do not understand your updated comment. [07:05:47] We had dodgy styling on meta but varnish eventually purged [07:06:17] If you proxy via test3 you'll bypass varnish so we know if that's caching anything dodgy [07:06:32] Oh, could you walk me through proxying, please? [07:06:34] @R4356th: RhinosF1 meant to proxy to test3 from your wiki with something like https://github.com/miraheze/MirahezeDebug to see if the issue persists. (I think) [07:06:56] You just add that to Chrome. [07:07:06] And re parsoid - https://phabricator.wikimedia.org/phame/post/history/189/#2758 [07:07:11] Universal_Omega: yes [07:07:25] wishes he used Chrome [07:08:27] RhinosF1: thanks for the post link! [11:53:43] Hello Gaming32! If you have any questions, feel free to ask and someone should answer soon. [11:54:12] Gaming32: how can we help? [11:54:22] Just checking things out [15:09:51] Universal_Omega, re: your reply above, not sure why CreateWiki would've been involved in that ticket? [15:22:13] dmehus: context? [15:22:46] Oh I see [15:22:55] Because it's createwiki's cache at fault [15:23:21] We can fix it by moving the cache out of w so we don't loose it during a MediaWiki update [16:48:27] RhinosF1: Yep. I have PRs open for that to puppet and mw-config to do that completely. [16:49:02] Yeah i have seen [17:06:55] dmehus: around for DM? [17:07:23] Universal_Omega, sure [17:07:32] RhinosF1, not sure. It was last night [17:08:07] dmehus: I ended up answering your question to Universal_Omega [17:11:27] RhinosF1, ah okay [17:11:39] so it was a CW cache issue [17:11:46] Yes [17:11:48] I forget what the original problem was lol [17:12:25] was that the namespace internationalization issue? [17:14:04] Yes [17:16:12] ah [17:16:57] dmehus seeing the "Get rid of the idle wiki dletion" -0 I would personly cut down the time for wikis to be deleted to 3 momnths [17:18:48] That is reffering the BlubbaBlubba RFC to remove the domicty policy [17:18:48] TheBurningPrincess, I wouldn't do that. 6 months is a reasonable timeframe that balances the issues/needs/circumstances. It would be nice if we could implement, technically, the part of Dormancy Policy that provides for accelerated wiki deletion after 30 days where the Main Page has not been changed and there's been zero edits to the wiki [17:19:20] Hm, I am more thinking "dead wiki, little content" should have less time [17:19:42] By "little content" I mean under 20-30 short pages that has been npt edited for a while [17:21:26] It's difficult to do that and implement technically because how do you have a script make that determination and it requires subjective analysis. Thus, in terms of scalability, any wiki closures and deletions need to be done in automated way as we don't have the volunteer power to manually close and delete wikis on a consistent and sustained basis, on a wiki farm that is growing [17:22:00] I wonder when they can make a scipt [17:22:08] We have a script [17:22:53] dmehus: thanks, sent PM. [17:23:05] I bet Miraheze will be full of dead or nearlly dead small wikis that never took off [17:23:17] It closes wikis where there's been no edits or logged actions in the initial 45 day inactivity period once there's been at least 60 days. Deletion is likely happened after a further 135 days following that 60 day closure [17:23:37] Ok [17:23:47] TheBurningPrincess, there's usually about 25-30% of wikis deleted, closed, or inactive at any given point in time [17:23:58] THta is a lot [17:24:02] Universal_Omega, okay, looking [17:24:15] I wonder if FANDOM has a lot of dead wikis [17:24:22] likely yes [17:24:28] Never really looked [17:24:31] not sure their Dormancy Policy equivalent [17:24:53] My wiki is only being edited as I paid writers to do so [17:25:17] I don't believe they have something as strict about closing/deleting wikis as our dormancy policy [17:25:46] chrs, yeah, it's more of a Closure Policy I think [17:27:15] Meh, glad I conivencd the FANDOM staff to remove all my old wikis [17:27:52] I was used to be on FANDOM and I was bureaucrat of this Wiki https://glitchtale.fandom.com/wiki/Glitchtale_Wiki, then it died. [17:28:16] Does not seem that dead [17:28:49] it's nothing compared to 2017-2019 days of that Wiki [17:30:41] The owner of the series opened a new wiki and some stuff happened [17:30:51] it's dead compared to 2018 [17:31:00] My wiki is only active due to paid writers from Fiverr without them it would be dead [17:36:52] Huh, why do we have a Schema namespace on Meta? [17:38:34] would appear to be [[mediawiki:Extension:EventLogging]] [17:38:34] https://meta.miraheze.org/wiki/mediawiki:Extension:EventLogging [17:38:35]

https://meta.miraheze.org/wiki/MediaWiki:Extension:EventLogging?action=edit&redlink=1 [17:39:51] Hmm... [17:55:08] quick question. I understand you can't serve the wiki from the root of the domain (example.org/Main_Page), but the custom domains page seems to suggest that if you own example.org then you have to use a subdomain (wiki.example.org/wiki/Main_Page). am I reading this incorrectly? can't you just use example.org/wiki/Main Page? [18:00:40] that could probably work if the /w directory is available [18:08:23] i'm not worried about the directory, but the subdomain (which I don't wanna use). [18:09:19] I don't think the subdomain should be necessary, and several of our wikis do not [18:10:22] *several of our wikis do not use it (allthetropes.org, idleon.info, etc.) [18:11:21] twentyonex: you can use the root domain [18:11:43] Some providers don't like CNAMEs there but you can use our dns [18:20:02] ok, ty RhinosF1. can I request the directory to be /w/ rather than /wiki/? [18:20:28] twentyonex: you can use /w/index.php?title=Blah [18:20:32] But otherwise no [18:20:40] Because of how MediaWiki works [18:21:15] aha, /wiki/ it is then [18:23:29] hello. the css issue was solved in our end [18:23:44] another problem we have are boxes arround templates that weren't there before [18:23:58] see the under bar / box [18:23:58] https://cdn.discordapp.com/attachments/435711390544560128/853701243918876732/barra.png [21:15:42] Hello Guest903! If you have any questions, feel free to ask and someone should answer soon. [21:24:30] Hello robla_! If you have any questions, feel free to ask and someone should answer soon. [23:50:54] I have resigned from SRE effective immediately- have sent an email to sre who can handle the off boarding [23:51:16] You can contact Reception|away / RhinosF1 / Universal_Omega for support. [23:52:22] 00:52:11 Ohh and Southparkfan