[01:09:15] Hi henstepl. [01:09:20] Do you understand category sort keys? [01:10:48] For a page titled like "Category:Foo bar", {{PAGENAME}} is just the "Foo bar" part I think? [01:11:05] And different versions of MediaWiki handled category sorting with namespaces differently. [01:11:16] Maybe "User talk:Hello there" is a better example. [01:12:20] Anyway, in some versions of MediaWiki, that page would sort under "U". [01:12:31] So people manually specified {{PAGENAME}} to have it sort it under "H" instead. [01:13:05] Or sorting under "C" instead of "F" in the case of "Category:Foo bar". AIUI anyway. [01:31:08] Basically, yeah. [02:07:31] tsundoku: here's a patch to make that exception more useful: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/465303 [04:15:59] When transcluding in a template, what alternative is there to {{CURRENTTIMESTAMP}} that does not require a purge? [14:55:38] tgr|away: thanks. with the patch, I get this http://ix.io/1oMD [14:55:42] still not sure what I should be doing about it [15:03:42] oh, stupid mistake on my end [15:04:05] I forgot to adjust permissions on the directories after doing some upgrades, so mediawiki didn't have write permission to delete the file [15:04:11] that is a nice patch, though. thanks. [17:34:55] tsundoku: not sure, the transaction handling in FileDeleteForm::doDelete seems robust enough [17:35:05] let's file a bug. What MediaWiki version are you using? [17:53:12] Is there an easy way to dump MediaWiki's parser, page output, and revision cache into a volcano? [17:54:31] cat includes/parser/Parser.php > /dev/null [17:55:12] Sounds good to me! [17:55:24] I am going to write a script for this since the existing script only works for databases. [19:18:54] 100% serious question time: Why does each release of MediaWiki keep making ResourceLoader worse? I am trying to fix issues for upgrading from MW 1.29 to MW 1.31 and finding that previous fully functional modules refuse to load now with "Unexpected general module" due to them having dependencies on other modules. Each module is a style only module. [19:20:10] Resource loader honestly hasnt changed all that much since 1.17... [19:20:44] is your style only module trying to depend on a non style only module? [19:21:11] It depends on other style only modules. [19:21:40] However, $module->getType() insists the module can not be styles only due to it having dependencies. [19:24:16] Ah, at some point after MW 1.29 "if ( $module->getType() !== ResourceLoaderModule::LOAD_STYLES ) {" in ResourceLoaderClientHtml.php was changed from a warning to a hard error that exits compiling that module. [19:24:24] Unfortunate for backwards compatibility. [19:26:22] We have deprecation policies for these things ;p [19:29:15] I would not have said anything if I saw it previously in the release notes. :D [19:29:59] Hopefully it is... but maybe it's not [19:32:14] I just found it in the MW 1.29 release. Looks like a potentially unintended side effect of this change: "(T92459) Loading ResourceLoader modules containing JavaScript through addModuleStyles() is deprecated and will log a warning server-side." [19:32:15] T92459: ResourceLoader should restrict addModuleStyles() to modules that only provide styles - https://phabricator.wikimedia.org/T92459 [19:32:59] Trela: dependencies for style-only modules never worked, they were just ignored. now they cause visible errors. [19:33:22] so, you can just remove the 'dependencies' from your module definitions, if they worked correctly previously. [19:33:35] They do work though. O_o [19:33:42] all style-only modules are loaded in alphabetical order, regardless of dependencies you specify [19:34:05] Oh... I(We) fixed that over here too. [19:34:10] and this has been the case ever since RL was introduced [19:35:23] I guess this will come down to previous changes on our local stack conflicting with new unexpected behavior. I will make a note of it. Thank you. [20:02:07] bawolff, ... didn't RL get *introduced* in 1.17? [20:02:11] 1.17 was before my time but still [20:03:18] it was Timo and Roan around 2011? [20:04:26] Yeah [20:04:39] my point is its stayed pretty stable all along [20:04:43] afaik [21:17:17] Anyone have an apt-get installation guide for mediawiki? [21:23:51] ? [21:23:55] apt-get install mediawiki [21:23:57] ???? [21:23:58] profit [21:32:25] I have too much info to categorize and contribute with, who knows if it can make profit one day.. [21:32:53] Install the debian package [21:32:57] run the web installer [21:33:01] That should be about all of it [21:34:11] I want it on postgresql with varnish webproxy in the front, I made some working varnish rules to cach so apache is on 8080 instead. [21:34:16] Reedy: [21:34:55] I probably wouldn't suggest postgresql to be the best choice of database [21:35:01] Support is known to be spotty [21:35:31] But install the php postgres module, make sure apache has been restarted... [22:34:05] Reedy: Can I have one "webdirectory" to see everything from one user? Trying to configure apache now:) [22:34:22] From one user? [22:34:57] Yes, so its easy to have a record of someone's editing, [22:35:08] One wikimedia user [22:35:29] to match a single directory. eg test.com/reedy [22:35:46] Not really [22:35:56] You could rewrite something to Special:Contributions/USERNAME [22:36:40] I know someone who did it for subdomains, But I dont have the cod [22:36:42] code [22:37:01] With MediaWiki? [22:37:45] yes [22:38:28] Does the page look like https://en.wikipedia.org/wiki/Special:Contributions/Reedy ? [22:39:00] https://en.wikipedia.org/Reedy [22:39:09] No, I mean the contents of it [22:40:47] Reedy: looks like I could do an apache htaccess, exactly what I needed:)