[00:16:20] dev question: does anyone know if there is a trick to getting an i18n file to load when running code through a MaintenanceJob? I see that global messages are loaded (from MessagesEn.php) but don’t seem to have access to an i18n.php file I’ve declared in the $wgExtensionMessagesFiles array [00:19:09] jordan_: do you mean a maintenance script? [00:19:19] and what version of MW are you using? [01:46:10] Hi. What tables are altered when a user is created, assuming that they've never logged in before? [01:50:02] are you looking for an exhaustive list? or…? [01:50:11] AFAIK the only thing in core would be the user table [01:50:18] naturally the 'user' table, and 'logging' for the log entry [01:50:32] that might depend on how they're created, MatmaRex [01:50:33] the number of users in 'site_stats' table is probably incremented [01:50:43] createAndPromote.php vs. on-wiki creation etc. [01:50:47] oh, yeah [01:51:16] I have a few accounts which were created that I want to delete permanently, but I don't want to mess up the database structure. [01:51:16] 'watchlist', because users watch their userpages by default since a few versions ago. [01:51:24] So I want to make sure I delete them cleanly. [01:51:36] umm [01:51:38] delete permanently? [01:51:41] why do you want to do that? [01:51:48] I want to record that they were ever created. [01:51:53] s/to/no [01:52:04] why? [01:52:39] Because it creates clutter. [01:52:52] Having all these accounts that have not and will never be logged in to. [01:52:55] 'user_properties' too, because every user gets a hidden 'watchlisttoken' preference, for historical reasons [01:53:42] orion: https://www.mediawiki.org/wiki/Extension:UserMerge allows you to delete users under some conditions. [02:02:08] MatmaRex: Thanks. [02:02:21] Is it possible to disable discussion pages? [02:03:59] orion: not really. you can protect them from editing (https://www.mediawiki.org/wiki/Manual:$wgNamespaceProtection) and probably hide the most visible links with some CSS. [02:05:14] oh, there's actually a way linked on that page. [02:05:21] we have better docs than i thought :) [02:28:43] Thanks all. [04:01:21] hi, is there a way how to find out a number of deleted revisions by a user without the deletedhistory right? [04:03:53] not to my knowledge [04:05:21] so how to tools like this: https://tools.wmflabs.org/supercount/ work? [04:05:29] *how do [04:47:52] Hi Niharika and tonythomas, either of you there? :) [04:49:24] josephine_l: I am ! Hello ! [04:50:19] Hey there tonythomas! :) Uh, could I ask when the mid-term evaluation is? My mentor asked me to fill that into my proposal timetable but I can't seem to find a fixed date [04:50:35] josephine_l: let me check in the schedule of Outreachy 11. One sec [04:50:51] Thanks! [04:51:11] I hope you would've too been looking at https://wiki.gnome.org/Outreachy/2015/DecemberMarch [04:51:17] yeah - no mid-term evaluation tehre [04:52:33] Yeah :/ I can just guess and insert it in the actual middle point of the internship period... but I figured I should ask first [04:55:38] josephine_l: dont worry. You can just reply to that comment by your mentor that it is not yet defined for this round of Outreachy. I will ping few of the other devs or in #outreachy ( in Gimpnet ) and get you back in some time :) [04:55:50] Thanks tonythomas! Much appreciated. [04:55:58] josephine_l: welcome :) [06:32:38] tonythomas: josephine_l: I can't find a concrete date either but the Payments Schedule (https://wiki.gnome.org/Outreachy/2015/DecemberMarch#Payments_Schedule) provides a good estimate. [06:33:10] You can consider January 25 as the mid-term evaluation deadline. [06:33:19] Thanks Niharika! [06:33:45] You're welcome! [10:16:17] paladox: Hi, general hint: If someone just throws in a link to Gerrit without any code-area context, you expect everybody to click in order to find out what it's about and if it's interesting to them. Or people will simply not click the link and save some time. [10:16:38] (plus asking for a review only 24h after submitting feels a bit impatient to me, just saying) [10:16:48] andre_: Sorry. [10:18:01] paladox: no sorry needed, just a hint about making communication more effective. Try to imagine that you're the reader and not the sender of the message. Would you click the link if you're already busy with other stuff? :) [10:19:05] andre__: So i should expalin in brief what the link a added is for for example if ci change i should say something like it fixes the composer test or something similar. [10:20:42] paladox: well, something that allows readers to judge whether the link is interesting to them or not, without having to first click the link to find out [10:20:45] "context", so to say :) [10:21:00] andre__: Ok will. [10:21:14] Throwing in a link without context is basically like pinging someone without saying what you want. http://blogs.gnome.org/markmc/2014/02/20/naked-pings/ comes to my mind [10:21:54] It saves everybody's time and one round of communication or clicks when directly providing some context. And it makes it more likely that your request will be successful, and that's what you're interested in :) [10:24:11] andre__: Ok i will add detail explaning what the link is for. [10:47:32] Could someone review https://gerrit.wikimedia.org/r/#/c/213825/ please. It is the last of confirmedit files to be converted to extension.json. [13:56:12] How do i format multiline code? [13:56:19] I want to post a bash script in a wiki [14:00:28] https://meta.wikimedia.org/wiki/Help:Editing [14:07:13] So, we officially adopted HTML5? When? See [[:en:Wikipedia:HTML5]] [14:07:38] Also, why Mediawiki still use the br tag with the XHTML syntax instead of HTML5? [14:08:50] probably because of tidy [14:09:29] https://www.mediawiki.org/wiki/Manual:$wgUseTidy [14:16:27] MatmaRex: thanks, but time pass, and projects like [[WP:CHECKWIKI]] are trying to clean things up: how can we justify that going against the DOCTYPE for 'some' syntax is ok? [14:17:42] waky: i don't understand what you mean. [14:18:03] (by the way, no one cares about the doctype, especially not the browsers) [14:18:33] waky: and
is valid HTML5, as far as i know. [14:18:35] MatmaRex: see https://tools.wmflabs.org/checkwiki/cgi-bin/checkwiki.cgi?project=enwiki&view=only&id=2 [14:18:51] it's kind of mixed up without a proper explanation [14:19:47] waky: neither "
", "" or "" are correct syntax (although they probably all work like you expect). both "
" and "
" are. personally i prefer "
" because it's shorter and neater, and both work exactly the same. [14:21:10] MatmaRex: so, should we say the usual "don't worry about how Mediawiki render the source code of the page"? [14:21:45] probably? i'm again not sure what you mean [14:21:46] I like
too, can't we just suggest to use only that one? [14:22:18] we should, if you ask me [14:22:26] we definitely can [14:23:18] MatmaRex: unfortunately, bots that run automatic fixes are still using
:( [14:38:19] There's nothing wrong
. [14:38:54] For bots especially, since it only has to be typed once, it's kind of nice that they use XHTML format, in my opinion. [14:39:44] Aryeh was in favor of
, as I recall. And XHTML basically lost. [14:42:24] Katie: http://www.w3.org/TR/html5/text-level-semantics.html#the-br-element [14:45:16] Sure. [14:45:43] I also still write

. It makes more sense. [14:45:57] Though that has a wikitext equivalent (----). [14:48:14] Katie: I suppose we can forget about these little incongruences untill the W3C Validator starts firing errors :D [14:56:07] does anyone use mediawiki with access restriction? [14:56:29] I need to define certain pages as only accessible by a group of people [14:56:52] !cms [14:56:53] Wikis are designed for openness, to be readable and editable by all. If you want a forum, a blog, a web authoring toolkit or corporate content management system, perhaps don't use wiki software. There is a nice overview of free tools available at including the possibility to try each system. For ways to restrict access in MediaWiki, see !access. [14:57:08] !access [14:57:08] For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [14:57:21] cluelessperson: Restricting only certain pages is unfortunately tricky in MediaWiki. [14:58:15] Katie, I think the best route would be to add a group tag to pages, and if a user is part of that group, allow reading [14:58:20] not a difficult principle [15:00:45] cluelessperson: There's a wiki page explaining the 30ish entry points each page has. [15:02:28] https://www.mediawiki.org/wiki/Security_issues_with_authorization_extensions [15:03:26] Katie, I think implementing this would give mediawiki a huge boost in corporate usage [15:03:51] Sure. [15:04:10] cluelessperson: Now if only those corporate users were willing to fund the development. :-) [15:04:38] Katie, They would be. [15:04:56] The big alternative "confluence" is stupid [15:05:32] Boooo, Atlassian. [15:05:42] If they're willing to contribute development, we can find someone to review their patches. [15:06:10] Though it's a large enough change that doing some pre-planning is probably prudent. [15:06:24] Like drafting a design document, for example. [15:08:19] Katie, I think the problem is that you don't want to work for free, and customers don't like to pay for something they don't see. [15:31:20] Maybe. [16:11:00] okay, where'd you lot hide it. Just tell me where I can find Vector's stylesheet and nobody gets hurt [16:12:58] Ulfr: Did you look in skins/vector/? [16:13:35] Trela: You betcha! No CSS files to be had. [16:14:15] Funny, I see a bunch in there. screen.less, special.less, special.variables.less, variables.less [16:14:21] ... [16:14:30] since when did .less = css?! [16:15:12] LESS is a CSS preprocessor. https://en.wikipedia.org/wiki/Less_%28stylesheet_language%29 [16:15:54] I'm getting too old for this. Since when did CSS need preprocessing?! [16:16:13] So you can do things like just edit one or two things in variable.less and have globally applied style changes. [16:16:23] * Ulfr is being entirely facetious by the bye. Coming in here and asking nicely got repetitive [16:16:32] But.. but.. [16:16:39] the whole point of CSS is that you can do that anyway! [16:17:12] Well too baaaaaaaaaaad. :P It was made easier! [16:17:31] Good lord. I just wanted pretty buttons [16:18:16] Then you should edit the MediaWiki:Vector.css page on your wiki so you do not have to modify files on disk. [16:19:50] Pfft, I know how to do that. I'm working with a little script in a widget in jQuery and classes weren't applying. figured it was a simple tag to get me some spiffy buttons [16:20:03] now I find out that even THAT needs extra processing [17:21:44] * Ulfr wonders if it's too early to start drinking [17:22:03] is there any way I can allow the upload of a specific file type without permitting it to be displayed as a thumbnail? [17:42:29] If the file type doesn't have a media handler, then it won't be displayed [17:43:41] a kind of hacky way of ensuring that is to do unset( $wgMediaHandlers['image/foo'] ); in LocalSettings.php [17:43:48] replacing image/foo with the right mimetype [17:54:20] bawolff: well right now I just have a broken SVG handler [17:54:40] but apparently users are insisting we host random people's scripted SVG images, which just seems like asking for trouble [17:55:03] Scripted svgs are dangerous even without the rendering step [17:55:19] I'm aware. I won the battle about displaying them, I just have to host them =/ [17:55:26] thus the desire to start drinking at 2pm [17:55:31] hosting them is actually the dangerous part [17:55:57] I know. [17:56:15] Anyways, if you do this, I reccomend putting your images on a separate domain [17:56:42] I did too! but I do have documentation stating that this is stupid, so at least I won't get sued when the site gets blacklisted -.- [17:57:23] Ulfr: Also instead of the unset thing I suggested earlier, setting $wgSVGConverter to something invalid is a better way to disable the svg rendering (As that will keep the metadata support, but disable showing images) [19:08:21] bawolff: Ha, I accidentally a smart then [19:45:37] MediaWiki 1.6 (!) https://www.mediawiki.org/wiki/Topic:Sr7iymi25k1n8iw6 [19:48:13] hey. If I get https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.3.patch.gz, I should be able to patch -p1 that to a 1.25.2 release tree, right? [19:48:31] Yup [19:48:37] or do I have to patch that to a 1.21(.0) tree? [19:48:39] okay [19:48:54] because I get rejected hunks in mediawiki-1.25.3.patch... [19:50:21] more specifically, in vendor/autoload.php and vendor/autoload_real.php [19:52:33] oh. that looks like auto-generated code, the patch tries to replace ComposerAutoloaderInitd8f33a349068fe343158b503c13acbbe with ComposerAutoloaderInite2ef576e4023c6f0949f5e8e1cdf8649 [19:53:04] ...but my code has ComposerAutoloaderInit9b10cc5cf6896d6e4a31983fc3498786 instead, which obviously does not match the patch :) [19:55:06] ah, the mailing list already knows this. okay :) https://lists.wikimedia.org/pipermail/mediawiki-l/2015-October/044867.html [19:59:30] but it would be nice to get a definite answer if one can ignore the failed hunks, or if the patch is broken [19:59:47] * rohieb writes to the mediawiki-l [20:02:28] rohieb: Well i'd call failed hunks to be the definiton of broken [20:02:55] yes, but I mean "broken" as in "breaks the code when applied" :) [20:03:20] if you leave the conflicts in a file, it could break a lot [20:03:43] I think its probably important [20:04:38] although if its just changing the function name, and all references are unchanged, it might not matter [20:04:47] If you've not touched the vendor folder yourself, it might be easier to just take one from the full tarball, and replace it [20:05:01] I suspect that if its going to break, its going to break catastrophically not subtly [20:16:42] yeah, gonna take the files from the release tarball [20:50:45] bawolff: Do you know how i can fix https://gerrit.wikimedia.org/r/#/c/247917/1 task at https://phabricator.wikimedia.org/T63877 or someone here. [20:50:51] please [20:51:41] [20:59:21] Thanks. [20:59:21] https://phabricator.wikimedia.org/T63878 [21:01:09] RFC meeting starting now in #wikimedia-office, talking about hygienic template arguments [21:01:34] is kaldari around? [21:03:31] jorm: he's in -dev [21:04:39] danke! [21:07:27] paladox: I have no idea. It looks pretty broken [21:07:48] bawolff: Oh ok.