[00:49:07] Any recommended way Reedy? [00:49:51] To do what? [05:11:02] when using parser functions, and you want to include whitespace, is there a better / more idiomatic trick than ""? I mean like this: Foo{{#if: blah | + Bar }} -> either "Foo" or "Foo + Bar". if we didn't use the nowiki trick, it would become "Foo+ Bar" (missing a space). [05:11:22] maybe I'll just create a {{noop}} [06:08:55] huh, apparently a completely blank template doesn't help, but if the template body contains then it works. the order in which things are parsed is a bit unintuitive I guess. [09:18:47] Hi there. since upgrade from 1.35 to 1.39; I lost the sidebar background color. I try to edit example.com/index.php/MediaWiki:Monobook.css by using 'div > pBody { background-color: black; }' but it not changing anything. Any idea please? [09:20:55] Just find it in dev tools, now it's responsive: body.skin--responsive .pBody [09:23:52] Ermh, no, not changing anything after added CSS and force refresh in the CSS page [09:34:01] Added !important;, no changes [09:34:43] My CSS is loaded from https://example.com/load.php?lang=fr&modules=mediawiki.action.styles%7Cskins.monobook.styles&only=styles&skin=monobook [09:37:42] judging by the various fixes I did to a bunch of MonoBook themes to make 'em play nice w/ 1.39 a while ago (https://github.com/wikimedia/mediawiki-extensions-Theme/commit/a3f1937d2a130237e7d09b6579943dcd1f929049), prefixing the selectors with body.skin--responsive *should* be all that you need (granted, I think it's such nonsense that the selectors changed and you need to explicitly specify tha) [09:50:33] I had only 'pBody { background-color: black; }' that was working well, but now, I dunno what to do [09:50:40] (ashley) [09:55:48] Damn, had to use selector body .pBody {} [09:56:06] * sputnickFreenode sight [11:53:53] We have an issue in TDF wiki where if I change my language to Czech and try to access Special:Preferences, I get Kritická výjimka typu „MWException“. This means that I'm now stuck with Czech interface. Any ideas on how I could change it back before we solve the root cause? [11:59:41] this doesn't work when accessing special pages: &uselang=en [12:04:34] well you need to enable detailed debugging info ($wgShowExceptionDetails = true; in the wiki's LocalSettings.php) so that we can figure out what kind of a MWException it is and how to make it go away for good :) [12:05:08] Great, I will send that to our hostmaster as well [12:07:46] meanwhile I can change my user script to also look for buttons that say "Označit tuto verzi pro překlad" :P [12:32:56] ashley: sysadmin found a fix: https://paste.debian.net/1271315/ [12:50:09] awesome :) [16:19:04] Hello!   Is there a readme/faq/tutorial available for upgrading from 1.2 to 1.39?   I read I needed to upgrade to 1.35 first, then other places say to upgrade to 1.27 first and a chain of upgrades to get to 1.39.    What is the real answer?  Thank you in advance. [18:13:37] Guest43: From 1.2 or 1.20? [18:29:47] https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CirrusSearch "MediaWiki 1.39+ require Elasticsearch 7.10.2" is that literally 7.10.2? [18:30:18] and would that explain why i search for multiple words doesn't work? [18:36:58] tuxick: yes, literally 7.10.2. Using another version will fail when you try to index your pages, or when searching [18:39:27] In theory, any version from the 7.10.X series should work, though [18:40:10] haha yeah well, java people live in theoretical world [18:40:59] well, installed 7.10.2, but advanced search for multiple words still fails [18:41:02] no errors though [18:41:16] maybe i should kick cirrus [19:05:41] have you followed the installation instructions (including running the scripts that populate the ES index)? [20:22:14] hi, I have some issues with categories on my wiki, the page content is generated via templates/lua module, the category is shown correctly on the page but on the category listings page, the page is not included. how come? I tried purging many times, currectly no more jobs to run [20:27:28] Libraleon: Maybe the jobs are lost before being added to the job queue. Try setting a debug log file temporarily, edit and save the page that should contain the category, run jobs and disable the log file again, and see if there's any error [20:27:30] https://www.mediawiki.org/wiki/Manual:How_to_debug#Setting_up_a_debug_log_file [20:29:45] Vulpix: it seems to run correctly when I added the category into a template, it didnt work when I called it from a lua module [20:32:03] It's basically the same. If you put the page wikitext in Special:ExpandTemplates you should see the [[Category: ... ]] syntax there [20:34:17] Vulpix: yes it's shown there [20:37:18] The only difference is that it will update links (including categories) in background jobs when the module is edited. If your jobs are run using runJobs.php, it may be using a different set of php settings or php extensions than the web server and it may fail to update other pages [20:39:32] Vulpix: I dont understand this but it seems to be working correctly now... even when I created a new page with the same template that has not been categorized correctly previously [20:40:08] Maybe it wasn't a problem and the category page was just cached... [20:41:04] hm possibly, thanks for trying to help anyway :) [20:41:22] I'm using CACHE_MEMCACHED [20:46:39] I think it may be a browser cache problem rather than memcached [23:44:56] I am on 1.12 (I thought it was 1.2)   What is the upgrade path to get it current?  I've ran in problem after problem for each version I've tried to upgrade to.   php version, tables, missing etc.    Any tips? [23:56:02] Guest43: https://mediawiki.org/wiki/Compatibility will give you an idea of underlying software versions. Most people recommend hopping LTS versions https://mediawiki.org/wiki/Version_lifecycle . From that far ago the latest supported upgrade is to get to 1.35. [23:56:12] Then from there to 1.35. [23:56:24] 1.39* [23:56:37] it gives errors to 1.35 from 1.12 in the upgrade process [23:56:55] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /var/www/html/maintenance/update.php on line 30 [23:57:19] Yes, so take slower jumps, like to 1.19. [23:58:08] ok, I can brute force upgrade the 25 versions different, but is the a recommended path/plan of upgrades? [23:58:42] I didn't see which ones were LTS besides 1.35 and 1.39 [23:59:37] Look further down in the lifecycle page [23:59:43] There's a graph