[00:04:26] Dhaval_: probably [00:04:42] Dhaval_: i think it ignores text other than numbers [00:04:58] MatmaRex, thanks. I have found it and have worked it out [00:05:07] if it doesn't work right, you can do {{formatnum:{{#time:Y}}}}-{{formatnum:{{#time:m}}}}-{{formatnum:{{#time:d}}}}, i guess [00:05:10] ah, okay, nice :) [00:06:25] MatmaRex: {{formatnum:{{#time: Y/m/d }}|R}} yields 2017/03/02 as I wanted [00:06:28] Thanks once again [00:06:37] yay [02:00:54] Stupid question: What do I set to make debug=true for load.php? [02:03:22] I have a strange situation where when I cut-paste the source from a page into a static file and load with debug=true, visual editor works but it doesn't when loaded with debug=false [02:05:06] More importantly: what would feasibly make visualeditor work when debug=true and not otherwise? [02:10:47] Figured out how to force debug=true, but still confused as to why debug=true works and I get "Module ext.cite.visualEditor has failed dependencies" when debug=false. [08:26:15] i would like to replace page titles with {{PAGEID}} using replace text extension, any idea how to do it? [09:26:19] Hey comrades! I want to replace deprecated wfMsg* functions (cf. https://www.mediawiki.org/wiki/Manual:Messages_API#Deprecated_wfMsg.2A_functions) in an extension (https://www.mediawiki.org/wiki/Extension:CrossReference), but I know nothing about how wfMsg* functions used to work in the first place. Where should I look for documentation on them? [09:38:04] ietaiyiof: I'm not sure if this is much help, but here's the docs page on wfMsgExt (the only wfMsg* function I can find in that extension) https://doc.wikimedia.org/mediawiki-core/1.26.0/php/GlobalFunctions_8php.html#aaf08892026bbde1ffbae3e2f67125617 [09:39:36] Thank you, Lcawte! This is much better than nothing, which is what I have known about wfMsgExt until now :) [10:06:36] Hello! [13:12:56] Hey everyone. May someone support me to figure out how the git review process works? In particular, I do not understand the branching concept when working as the MW tutorials ask me to do [13:18:55] So far, I've set everything up and did contribute multiple commits. However, now that I'm working with git-review I'm not sure whether I'm doing it right... [13:19:45] As far as I have understood the docs, you should branch from master, do a single commit and let the community review this commit which will lead to a merge into master [13:22:11] Of course, I don't want to wait for the review process to finish before e.g. starting with the next changes. And not every change is as major to become a new branch. Is there something like the develop branch, where I can simply put all the little changes here and there, that will be reviewed from time to time? [13:28:09] sebschlicht: Branches are cheap, it's the idea of this workflow to use a branch for each thing you change. You clone origin/master to your local master, create a new branch i.e. 'task15', checkout 'task15' and do your changes. You then commit your changes into 'task 15' and run git review. Your changes will go to gerrit and be reviewed there. When you want to start with another change, you just checkout your local master again (pull new changes from [13:28:09] origin/master ideally) and checkout to another working branch 'task320' for your new job and proceed as above. You do not need to wait until your changes in 'task15' have gone through the review process and have been merged into master, they'll be merged automatically. [13:30:05] I maybe should add as a disclaimer that I'm still a newbie too, so I can just give how I understood it, but I guess that's better than no answer ;) [13:33:32] sebschlicht: Have you checked https://www.mediawiki.org/wiki/Gerrit/Tutorial already? [13:33:53] Every proposed change in Gerrit is basically a Git branch. [13:34:17] You can also make proposed changes depend on other proposed changes [13:35:31] sebschlicht: yeah, what eddiegp says is right [13:36:11] sebschlicht: if you're working on multiple things and don't want to deal with dozens of branches locally, you can just delete them after you push your changes for review to Gerrit, and use `git review -d` to download them back if you need to amend them. [14:22:12] Could somebody give me a quick "recheck" at https://gerrit.wikimedia.org/r/#/c/340734/ ? Touches a lot of syntax, would like to know if tests run fine. [14:22:20] yes [14:22:53] Thanks Zppix [14:22:58] np [15:43:10] @eddiegp, @MatmaRex: Thank you for your responses. They were really helpful to me! Though andre__ is right when pointing to the tutorial, it was hard for me to believe that you REALLY use a branch for a single commit. That's not how I learned to use git so far :D [15:47:26] yeah, it's a different workflow. Git's branches are just too versatile, and sometimes calling everything "branches" gets confusing. (we also have long-lived release branches, e.g. there's a branch for MediaWiki 1.27 that patches sometimes get backported into) [15:48:41] i think what we do is similar to the "old-school" way of doing Git (like they still do e.g. for Linux kernel), where you'd generate a patch and send it over email, except that we use `git review` and Gerrit rather than `git format-patch` and email [16:03:19] At CI I'm getting "RuntimeException Error Output: PHP Deprecated: Comments starting with '#' are deprecated" as an error messages, but there aren't any # in the code ... (vim tells me 'pattern # not found'). The few style issues aren't any problem, but I don't know how to handle this error message. See: https://integration.wikimedia.org/ci/job/composer-php55-trusty/14966/console [16:04:13] @MatmaRex: Ah okay, that's where it comes from, nice to know. I think it's not that bad but I really like the usage of branches like git flow intends. However, may I ask you another question regarding to branches: [16:04:27] May this error also refer to comments which look like /** Comment */ (in a single line) and the error message is just not clear about meaning both #Comment and /** Comment */ ? [16:06:00] eddiegp: that doesn't look like it's about your code, it's something in the CI setup. it shouldn't cause test failures, it's just noise. you can probably ignore it. [16:07:02] Let's say I have just pushed a change for reviewing and I want to make another change that depends on the first one. How am I supposed to do this? For me, I'd have to branch away from the first branch, apply my additional changes to the second branch and push the second branch for reviewing. Is that the correct way of doing it? [16:07:21] MatmaRex: Okay, I'm going to upload a new patch set without the style issues and check if those errors are still up. [16:07:52] sebschlicht: yes, exactly. you can also make multiple commits on a single branch. [16:09:31] @MatmaRex: Ah, that's perfect :) Nah, these changes are too far from each other to be put in the same (feature) branch. Thank you very much! [16:13:59] Could somebody again "recheck" https://gerrit.wikimedia.org/r/#/c/340734/ ? Sorry for the noise. [16:20:02] MatmaRex did recheck eddiegp [16:20:47] Just saw it, thanks MatmaRex [16:23:41] Hi. [16:24:00] Is there a way to trace what the parser and any extensions are doing ? [16:25:33] I am trying to figure out how mediawiki thinks it's assembling https://en.wikisource.org/wiki/Short_Titles_Act_1896/First_Schedule/6_Ann [16:25:51] (and resolving unclosed and empty tags) [16:26:19] so I can compare it against - https://en.wikisource.org/wiki/Short_Titles_Act_1896/First_Schedule/Pre_Union [16:26:48] to figure out why a particular template has to use some very precise and esoteric syntax to work. [16:27:14] and why it's not possible to use the same transclusion method on both pages... [16:29:02] I have a wiki farm project I started in 2011, I've been downloading Mediawiki updates and extensions straight from MediaWiki. I think it's time for me to learn and set-up Git. I hoping someone has suggestions on the best place to start for a self taught dev, Thanx [16:37:35] !start | Mlpearc [16:37:35] Mlpearc: https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker [16:38:00] lol [16:38:03] ok [16:38:19] I was looking at http://rogerdudler.github.io/git-guide/ [16:38:24] Mlpearc: The link gives a lot of information about how to begin with developing. [16:39:04] I've been developing for 5 years, it's Git I need to set up [16:40:16] eddiegp: Thank you, that does look like a good p[lace to start :) [16:40:49] Mlpearc: Specific information about git/gerrit which mediawiki uses is at https://www.mediawiki.org/wiki/Gerrit/Tutorial but that's also linked on that page ;) [16:41:13] np [16:47:08] Any suggestions on theses https://git-scm.com/downloads/guis [16:48:12] I've never used "Command line" so a GUI seems to be the best way for me, :P IDK [16:49:22] I do want to use command line though, that seems easier than "download>install>PuTTY........ [16:50:25] how should i start contributing to mediawiki opensource ? [16:50:39] !start | sinnersdoom [16:50:40] sinnersdoom: https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker [16:50:58] sinnersdoom: There you'll find a lot of information on how to begin :) [16:51:54] I think I'll start with this https://desktop.github.com/ [16:54:45] eddiegp: Thanx again for your time :) [16:55:04] Mlpearc: no problem :) [16:57:04] eddiegp: My project if you'd like to have a look http://www.everythingfoodanddrink.org/wiki/Main_Page [17:16:04] Hi -- can anyone help me debug why my Mediawiki+wikibase installation gives an HTTP 500 error when I try to add an item or property? Here is my $wgDebugLogFile: http://sprunge.us/ALgc Any ideas would be appreciated! [17:17:21] [fatal] [21618be2] PHP Fatal Error: Class 'Wikimedia\Rdbms\SessionConsistentConnectionManager' not found [17:17:38] habs: looks like you don't have some of the dependencies installed via Composer [17:17:41] !composer [17:17:41] Composer is a dependency manager for PHP. MediaWiki uses it to include certain external libraries. See https://www.mediawiki.org/wiki/Composer for more details. For information on how to install MediaWiki dependencies with composer see https://www.mediawiki.org/wiki/Download_from_Git#Fetch_external_libraries [17:24:39] MatmaRex: Thanks, but when I run "/usr/pkg/bin/php composer.phar install" in my /meta/h/habs/html/athdb/extensions/Wikibase directory, I get "Nothing to install or update". How can I know what I'm missing? [17:26:00] habs: hmm, try also doing it in mediawiki root? i'm actually not sure how this is handled for extensions [18:18:00] Just found out that email addresses for people using mediawiki mailing lists have been archived at gossamer threads. While at some places they have been converted to images, but at others they are clearly readable by a bot as has been done by google. Anyone has any idea, how to get those removed? [18:23:03] MatmaRex: So I tried running composer at the MW root and it did install some extra packages, but I'm still getting the same error. Is there anything else I can do, or does the log show anything else of note? [18:27:53] habs: sorry, i've no idea. you could try asking for help on #wikidata too. :/ [18:46:54] !ops ich bin Hitler, NotASpy ist ein Juden! [18:47:05] Zu den GASKAMMERN! [18:47:20] * ASCII-Art loves gas chambers [18:47:22] lol gas [18:47:24] i fart gas [18:47:41] !ops AntiSpamMeta is a member of teh eleet cabal of jews [18:48:05] Chrissymad: are u an op? [18:48:09] or is u a fag? [18:48:24] !ops AntiSpamMeta is teh eleet cabal of JEWS! [19:11:06] Good afternoon folks, quick question. I'm doing a MediaWiki 1.28.0 install via Softaculous on my webhost so I can utilize a flowchart plugin I found however I get this error and am wondering if I need to use an older version or if it should still technically work "PHP version is less than the required 5.5.9" It gives me the option to override and use 5.5.38 [19:13:03] NetEcho: 5.5.38 is more recent than 5.5.9, so that should be fine [19:13:20] treat the point as a number separator, not a decimal point [19:13:29] Skizzerz: how the heck does that make sense? lol 5.5.9 seems like a higher version number than .38 [19:13:39] 5 = 5, 5 = 5, 38 > 9 [19:13:51] OH lol [19:14:05] that's how software versioning (including mediawiki) works [19:14:13] wow silly me I was thinking .3 revision 8 I.e .3* < .9 [19:14:51] it makes sense to developers :) [19:15:26] yea my logic would be correct if it was .3_8 or something lol but for whatever reason I was thinking stupidly lol [19:15:29] in a scheme like x.y.z, the first number is the major version; if that goes up that indicates major changes were made to the application, sometimes either a complete rewrite or at least a large backwards-compability breaking change [19:15:53] yea I should really know this.... I've been running Debian and FreeBSD servers for years lol [19:16:03] the second would be the minor version, which goes up as new features come out, etc. and the third is essentially used for bugfix releases that don't change much in the way of features, but come with additional bugfixes or security improvements [19:16:33] of course, everyone does it *slightly* differently [19:16:39] Today has been a major ball of Derp, I was trying to manually install on my host without even thinking to check Softaculous first lol [19:16:40] because we can't have nice things :P [19:17:47] yea I've noticed most projects are like that. Actually I'm working on some Minecraft support resources to make my life easier when helping users and we use the same versioning system I.e. current is 1.11.2 and next release is 1.12 [19:19:11] and Mojang is sometimes famous for releasing two x.x.* versions in the same day because they don't properly test lol [19:22:43] Skizzerz: I'm seeing most of the extension install instructions require bash commands to grab the git repos, what if you don't have shell access to your host? [19:23:36] can you upload tarballs? [19:23:53] if yes, see https://www.mediawiki.org/wiki/Special:ExtensionDistributor [19:23:54] i guess you can just clone the repo locally, and upload it with FTP or whatever [19:24:09] oh yeah, or that :D [19:24:18] ah that can work [19:24:19] (assuming you don't care about the Git history) [19:24:36] some extensions may require that you run other commands to finish setup, which may not be possible depending on your host [19:24:47] if the extension requires database changes, re-run the web installer [19:24:59] (after enabling the extension in your LocalSettings.php) [19:25:13] ah [19:25:19] the web installer will prompt you for the upgrade key found in LocalSettings, and then it will perform all the necessary db changes to set up that extension [19:25:33] yea I'm seeing these ones require extra stuff installed.. damnit I'll just do it in my own server lol [19:25:39] which? [19:26:02] I could take a look and know for sure whether or not they'll work in most typical shared hosting environments [19:26:08] I have a fair amount of experience with them :P [19:26:13] (shared hosting, that is) [19:26:52] Skizzerz: https://www.mediawiki.org/wiki/Extension:GraphViz https://www.mediawiki.org/wiki/Extension:Flowchart [19:28:09] you did see the security notice at the top of the Flowchart extension, right? [19:28:31] Eek ok back to the drawing board lol [19:28:57] Gah I need more coffee lol [19:29:47] graphviz should be fine though [19:29:49] well [19:29:55] are you on free hosting or paid hosting? [19:30:16] if free, chances are it won't work because free hosts typically disable the ability to execute subcommands [19:30:33] paid hosting [19:30:43] if paid, you shouldn't have that restriction, and if the graphviz command isn't installed you should be able to open a support ticket to get them to install it for you [19:31:00] I'm just trying to find an easy way to set up a help flowchart that we can easily maintain as a community to train new supporters lol [19:32:10] anyway, give it a try and see if it works :) [19:32:28] Thanks man, definitely gives me some direction [19:32:47] it looks like GraphViz depends on the ImageMap extension, ensure you have that installed as well [19:32:56] I don't believe the Extension Distributor download will include it [19:33:03] I should be able to see with phpinfo right? [19:33:14] no [19:33:18] phpinfo is for PHP stuff [19:33:33] although if you have access to that I can tell you at a glance whether or not graphviz even has a chance of working [19:33:41] you verify extensions via the Special:Version page on your wiki [19:34:15] (in phpinfo, check for the line disable_functions, and if there's anything listed there as the value, post it here) [19:34:46] kk one sec [19:34:56] or you can check yourself, if you see that things such as exec, passthru, and shell_exec are listed, then the GraphViz extension will not work [19:35:19] if those aren't listed (such as it being blank), then you're good to go [19:40:02] Skizzerz: disable_functions no value no value [19:40:11] ok cool [19:40:15] you'll be fine then [19:40:48] sweet, thanks for the assist man [21:32:14] is it possible to query the pageid of a deleted page? [21:34:09] so that I can run deleteArchivedRevisions.php on a specific pageid [21:34:45] Skizzerz: riddle me this, if I have a basic HTML page with javascript can I put the html code into a mediawiki page? [21:44:48] wmat: Sure, you have to know the DB key form (i.e. with underscores) and the namespace ID (0 = Mainspace, 1 = Talk, etc.) Then run this SQL: http://pastebin.com/nhuC6Q6p [21:45:32] wmat: Replace the filler text with what you're searching for. [21:47:13] wmat: Also put the page title in single quotes [22:05:12] NetEcho: sorry, I was afk for a while [22:05:25] by default, mediawiki heavily restricts what html you can have on a page [22:05:48] you can enable raw HTML mode, but doing so is a security risk if you do not trust everyone with edit access [22:06:15] it's far better if you can convert that page to wiki markup, putting any necessary javascript in your MediaWiki:Common.js page (which is only editable by administrators) [22:07:47] Skizzerz: that's using someone else's script to generate the chart. it's only going to be a handful of us fiddling with it [22:08:20] what I mean is that if you enable raw HTML mode, it enables it for the entire wiki, meaning anyone can put any arbitrary HTML, CSS, and JS on any page so long as they can edit [22:09:37] ergo, it's safer to do things the wiki way, even though it would require some porting effort [22:10:04] if you have a heavily restricted editing environment and you trust everyone with edit access, the former isn't as bad [22:10:30] did GraphViz end up not working out? [22:10:52] nope one of the other helpers pointed out a much nicer and easier way with this script [22:11:23] problem is I'm not very decent at HTML or JS so porting this into wiki format would basically require me learning all of this from scratch [22:11:23] "nicer and easier" is relative ;) [22:11:45] what's the script? [22:11:55] the extension I was going to use is ugly compared to this and only requires lines like A(text)-->B(text); [22:12:10] Skizzerz: http://paste.debian.net/917709/ [22:15:21] something tells me I'm gonna need to run to the grocery store and buy some coffee as it's going to be a long night :P [22:15:53] so the good news is that integrating that is going to be easy [22:17:02] Seriously? [22:17:06] yes [22:17:17] ok hold on a moment while I set up a test wiki [22:17:33] was just doing some dirty tests in joomla.. it works but doesn't scale well heh [22:17:57] the wiki page itself will only have the stuff beginning with
and ending with
[22:18:05]
is an allowed tag in mediawiki, so no issues in using it [22:18:55] sick :D [22:18:58] then you'll need to edit two other pages: MediaWiki:Common.css and MediaWiki:Common.js (you'll need to be an administrator to edit those pages) [22:18:59] that's perfect as the users don' [22:19:04] don't need to see the rest [22:19:22] one sec as I get you what you'd put on each page [22:19:26] Yea I'm the host of the wiki [22:19:42] and I'm glad this is going to be easy as I'd prefer to use mediawiki over a cms any day [22:25:56] Skizzerz: I have all 3 pages open [22:26:49] oh, I was a bit wrong, you don't need Common.css after all [22:27:25] alrighty [22:27:36] I'm assuming because it's linking that remotely? [22:28:50] yeah [22:28:52] NetEcho: https://hastebin.com/qesoniyalo.js [22:29:06] er [22:29:09] I have an extra paren in there [22:29:22] line 5 should look like } ); [22:29:31] instead of } ) ); [22:29:58] wow that would have been super easy to miss lol [22:30:05] anyway, put that (with the correction noted above) in your MediaWiki:Common.js page and save [22:30:06] k that is updated [22:30:18] then if you force reload / clear your browser cache, it should work [22:30:19] I'll screeny just incase I screwed up [22:32:04] Skizzerz: http://imgur.com/a/cWnBT that's what I have so far [22:32:30] now make your regular wiki page with that
[22:33:05] however with a forced reload I get http://imgur.com/a/4w66S [22:33:13] MTres19[m]: thx [22:33:29] wmat: np [22:33:30] press F12, do any errors appear in your console? [22:33:38] Skizzerz: do I need to call on a function on that page? [22:33:45] no [22:33:57] you can't even if you wanted to, js isn't allowed in mediawiki pages [22:34:11] Skizzerz: I see the source code and one line is highlighted in blue, would that be an error? [22:34:19] what browser? [22:34:25] chrome [22:34:38] go to the Console tab [22:34:38] Skizzerz: would it be easier if I link you in a pm? [22:34:43] yes [22:34:48] if it's publically accessible [22:34:49] oh yes [22:34:59] yea I just tossed it up on my test domain [22:35:10] then sure, send me a pm [22:35:31] there you go sir :) [22:35:38] and yes some big error lol [22:37:49] once this is working it looks like I have a lot of manual pages to read to learn how to properly run this wiki :D [22:38:59] oh I see the issue [22:39:27] Glad you do lol I'd probably have an easier time trying to read a foreign language over that [22:40:12] last time I really delved into this stuff was about 15 years ago lol [23:39:01] back to the drawing board [23:40:25] Skizzerz: am I missing some sort of extremely obvious and easy way to do a decision chart / tree like that that's natively supported in mediawiki? Cause I feel like this task is probably stupidly simple and I'm just missing it lol