[10:29:59] "You want `$wgNamespaceAliases['..." <- Okay, it actually did work. I had "USER" still written in lowercase. [10:30:04] Thank you! [11:57:55] Another question: I know it is not exactly MediWiki but some of you probably use Bluespice too.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/c75f9449e137d11dc6d32aa286f55d8c3b8c4957) [12:57:19] I've downloaded the BueSpice tarball and indeed there's no BlueSpiceExtensions folder inside the extensions folder. Looks like the guide may be outdated [13:01:06] Yes, it is. I found an old forum post which confirms that as of Bluespice 3.0. But nowhere is the information where one should manipulate the extensions now. I tried it in the LocalSettings.php with wfLoadExtension( 'Extensionname' ); and it just worked. So yeah, lots of burned time with another outdated doc. At least its running now. Thanks for looking into it anyways! [16:03:32] Is there an extension or other mechanism to display to the user the reading time of an entry? [20:17:21] https://mstdn.io/@anjum/107406505650921499 [20:17:39] Was looking for responsive skins, and learned that the old fashioned monobook theme is so. [20:18:25] Was surprised. Was looking at the various other skins, the most common one I see in the wild is Timeless. [20:18:50] Which I never really like somehow (personally) [20:20:04] Cause it doesn't scream out to me as an interface where I can immediately contribute (?) don't know if that makes sense. [20:24:21] Basically, giving serious thought to using monobook cause it's both response and looks inviting for potential contributors. Cons are that is pretty dated and people equally well will might assume it's an old abandoned wiki. [20:25:17] There's a "version 2" of Vector which is more responsive, https://en.wikipedia.org/?useskin=vector&useskinversion=2 [20:25:31] there are also other responsive skins out there, I use GreyStuff on my personal wiki [20:26:03] IMO Timeless is really geared towards editors, with various layout decisions making links and tools editors use easier to access [20:27:32] Ooo [23:07:44] can someone please help debug https://phabricator.wikimedia.org/T297046 [23:08:11] Reedy, majavah: ^ [23:09:32] https://www.mediawiki.org/wiki/Excimer ? [23:11:05] Reedy: how do i attach it to every php-fpm proccess [23:11:17] * Reedy shrugs [23:11:30] Reedy: i need a bit of help here [23:11:46] i got a server crying at me and not much clue what to do [23:16:59] Is something killing the processes (and hence the drop in memory usage)? [23:18:12] Is the PHP config actually similar for the fpm workers, and their counts/limits etc? [23:18:55] Cause we really don't know at this point if it's an MW (or extension etc) issue, or site/server/os config [23:21:26] Reedy: config wise should be exactly the same between buster and bullseye [23:21:36] every [23:21:44] everything is set in puppet [23:21:56] Doesn't mean it's set correctly etc [23:22:48] Reedy: yes the process is being killed when memory gets too high [23:22:50] Active: active (running) since Tue 2021-12-07 23:11:45 UTC; 10min ago [23:26:43] https://www.irccloud.com/pastebin/oXfYRBBj/ [23:26:57] Reedy: exact config ^ [23:27:10] not actually sent because SMTP isn't set up