[00:09:17] Is there any way I can get multiple pages that way? Ideally ResourceLoader would bundle them so I only have to make a single request. I was thinking ?title=Page1.css|Page2.css similar to how api.php works but that fails [08:44:52] I am not certain that Edd0408 editing phabricator is in good faith [10:05:35] Is it a known issue that a list to the right of an image doesn't indent properly? [10:05:46] (sorry if I missed a reply two days ago) [10:05:54] this looks like, [[File:blah.png|left]] \n #text \n ## text etc [10:05:59] the second level li appears at the same indent as the first, but only when right of the floating image [10:46:22] any tips on migrating mediawiki database from postgre to sqlite? nothing seems to work for me... [11:10:30] grzesiek11: what are you trying? [11:13:38] i tried using sequel - it generated an empty database [11:14:42] i also tried exporting as plain SQL, making changes as some posts suggested (eg. removing SET) and importing - but it gave me loads of syntax errors [13:42:08] Hi there, I've got a freshly installed wiki (I think I changed the timezone on it afterwards, but ages ago now before the pages exhibited this even existed) that's not automagically purging pages when it ought to [13:42:30] Redlinks are not changing even a day later [13:42:56] !jobs [13:42:56] The Wikimedia Foundation has open positions listed at https://wikimediafoundation.org/wiki/Work_with_us#Wikimedia_Careers - consider applying and helping improve MediaWiki! [13:42:59] ffs [13:43:00] !jobqueue [13:43:01] The Job Queue is a way for mediawiki to run large update jobs in the background. See http://www.mediawiki.org/wiki/Manual:Job_queue [13:46:01] Reedy: yeah but it's a fresh install [13:46:05] So I can't have screwed it up [13:46:23] The time change was done after the main page edit, before anything else [14:59:32] Hello, I would like to display a page with all pages sorted by category, do you know how can I do that? the {{Special:Allpages|sort?category}} special:Allpages doesn't allow this [14:59:47] Thank you by advance [15:13:13] testetstest: A page can have several categories, and categories can have a sortkey. Can you elaborate? [15:15:05] I want to be able to see all pages but sorted by category and not by name. In my usecase, a page has only only category. It is like a subtree, for example cybersecurity which contains cryptography, firewall etc [15:15:35] I mean, not all pages but a link to all pages sorted by categories. [15:15:58] a link for each pages and gather by category. [15:20:45] Vulpix, any idea? [15:21:58] You basically want to see the category page, listing all pages that are in that category [15:54:57] Hello and big thanks for the awesome quality software with well implemented extendability and the awesome pro-bono support [15:56:28] I'm looking for something to do stats/analytics for Mediawiki, but not having luck with brief searching. I do have the Apache logs, but they are not very useful (unmodified), because of the redirection used to make pretty URLs [15:59:49] i.e. the apache logs do not have the pretty URL's, but instead just milliontillion hits to /w/somescript.php iirc when the pretty urls are /wiki/Article_name [17:14:20] how do you migrate mediawiki database from postgresql to mysql? [17:42:38] Hey all, I'm finalizing a job runner service script and systemd service files, which all seem to be working. For testing purposes, however, is there any issue with having the service running for a given wiki while also having its $wgJobRunRate still a non-zero value? [17:43:39] FWIW I have 5 wikis that will each get their own systemd service instance, e.g. `systemctl enable mediawiki-job-runner@wiki1` for each of wiki1, wiki2, etc. [17:44:12] grzesiek11: There's not really any defined migration process. Depending on what's on your wiki, you can do an XML export and re-import [17:44:27] justinl: Shouldn't do, no [17:44:50] wgJobRunRate is usually just set to 0 to improve perf of web requests etc [17:45:41] Cool, thanks. I'm definitely getting a better handle on this job queue stuff, checking and watching output from showJobs and runJobs commands, just trying to write the safest and most robust services I can, and running them on a dedicated server that has all of the wiki configs on it as well, just like how the actual wiki web servers do. [17:45:47] Gotcha, cool. [17:46:42] FWIW my wikis' job run rates are 0.1 for the two biggest ones and 0.5 for the other 3, since they're all relatively high traffic, so not overwhelmed. Just can take a while when 1000s of requests appear in a wikis' queue. [19:00:45] It looks like https://www.mediawiki.org/wiki/Extension:Matomo could be what I'm looking for (analytics) [19:01:25] It is available an analytics suite available as self-hosted and cloud (for a fee) [19:20:16] jukebohi: it's a nice piece of software. Setting up any analytics that require sending js to the client has a handful of pitfalls that you need to be aware of. 1) If GDPR or other privacy laws apply to your wiki, you need to be careful to adhere to them. Analytics is generally not considered necessary for site functionality so explicit user consent is generally required in order to track them. 2) Many ad blockers and browser privacy settings will [19:20:16] just outright prevent it from working [19:46:29] Thank you for the informatoin Skizzerz [19:49:52] So I would need something like https://www.mediawiki.org/wiki/Extension:CookieWarning ? [19:56:41] I may not yet be fulling understanding how php composer and the mediawiki vendor autoloader stuff works, but I noticed that separate from the `load_composer_autoloader` parameter that can be added to an extension's `extension.json`, adding `--no-autoloader` just prevents the `vendor/autoload.php` and `vendor/composer/autoload*php` and a few other [19:56:42] file don't get installed. Is this a possible way to avoid certain extensions-that-must-not-be-named from autoloading? [19:57:29] FWIW there are a few other extensions we have that do set that variable in extensions.json: AbuseFilter, AntiSpoof, Maps, Widgets [19:59:31] load_composer_autoloader mostly exists to load any vendor files inside a skin or extension itself [19:59:44] ie if for whatever reason they're not in the main vendor folder [20:01:07] Ok, I'm just digging through code trying to figure out what causes an extension to autoload and figure out if there's a clean way of preventing that. I don't get why an extension would do that when it's simple enough to just require() it. [20:01:53] There's been some dicussions about this in other tasks [20:02:07] It seems that some of the extensions from developers in those camps... Like to enable and load themselves [20:02:26] Like when you composer require a MW extension [20:05:25] Theoretically, if I could minorly edit an extension via perl/sed/whatever prior to running composer against composer.json+composer.local.json to not autoload, yet it would still get loaded normally in my LocalSettings.php, is there anything really bad that could happen? Like are the extensions that do this autoloading doing other things that [20:05:25] preventing the autoload could break? [20:06:00] What's the problem you're actually trying to solve? [20:06:55] Preventing SemanticMediaWiki from autoloading so it's default namespace values 102/103 (forget the names) doesn't conflict with a custom namespace/talk space that we define in one of our wikis that doesn't use SMW. [20:07:03] Trying to do the wiki family thing. [20:07:24] Is SMW installed via composer? [20:07:27] Yes [20:07:46] Along with the extensions listed above. [20:08:41] I don't think the other extensions mateter [20:08:43] matter [20:08:53] just being thorough [20:08:53] https://gist.github.com/justinclloyd/3c759295901d313e1f2e573d53158b33 [20:09:09] antispoof and abusefilter don't (AFAIK) have any fancy self loading code [20:09:35] yeah they're not a concern since the smw namespace thing is really my only issue [20:10:23] that composer.local.json is used by my 4 smw wikis, my 3 non-smw wikis each have a different such file with fewer requirements [20:10:53] the smw autoload issue then prevents me from having a single copy of mediawiki to use in a wiki family [20:13:49] Is enableSemantics in your localsettings? [20:13:55] yes [20:14:08] That's your problem [20:14:13] per-wiki, each wiki has its own, the non-smw in question doesn't have it [20:14:32] :/ [20:14:42] sorry for the confusion, each wiki has its own dedicated LocalSettings.php with exactly what that wiki needs [20:14:57] I meant that the enableSemantics is in the ones that need it [20:15:03] That's fine.. But that's the only way I can see that wfLoadExtension is being called for SMW [20:15:09] https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/a564e4cb14d9f724af5f2272990cdbffff0a7eb7/src/GlobalFunctions.php#L240 [20:15:23] composer itself is seemingly not calling it [20:16:40] hmm, well...this was 2-3 years ago that I ran into this and I haven't actually tried now to see if the loading still happens, maybe I had a bad config back then or something. [20:16:58] just so you're aware [20:17:14] "autoloading" doesn't (or shouldn't) in MW land mean code gets run automatically [20:17:15] Good to know, I figured it very possible I just might be missing something. [20:17:31] It just means MW knows where the class is (and can tell PHP) if it's needed [20:17:44] so it's like a mapping of class name to PHP file [20:18:40] A few years ago when I encountered this problem, each wiki had it's own static LocalSettings.php, both in live and dev, and there were discrepancies. Only in the past ~6 months have I unified them all into a single Salt/Jinja template that creates exactly the right thing for each dev and live mediawiki directory, so maybe I just had a bad config [20:18:40] back then and it might not be a problem for me now. [20:18:53] Guess I should go actually try it in the dev version of the affected wiki. [20:19:09] OOI.. On the affected wikis... Does SMW get listed on Special:Version? [20:20:10] I don't know, that's what I was trying to say, I haven't tried it recently, just going off past knowledge, so I need to go actually add it to the dev version of the previously affected wiki and see if it's still an issue for me. [20:21:49] So it's possible it's actually no longer an issue. [20:43:17] It seems that subsequent runs of update.php are running migrateActors.php again :(