[00:16:21] <Celelibi>	 Hi
[00:16:40] <Celelibi>	 Is there an easy way to indent a whole block?
[00:16:46] <Celelibi>	 I mean, add a space before every line.
[02:28:33] <Cory_1975>	 I'm trying to install the UploadWizard extension
[02:28:51] <Cory_1975>	 The install instructions say to install ImageMagick
[02:29:09] <Cory_1975>	 I'm on a shared host (Namecheap) and don't know how to do that
[02:29:42] <Cory_1975>	 But a Google search says that Namecheap already installs ImageMagick 
[02:30:19] <Cory_1975>	 So I skipped that. I added the required configuration lines to LocalSettings.php
[02:30:56] <Cory_1975>	 But got an error from require_once("$IP/extensions/UploadWizard/Uploadwizard.php);
[02:31:22] <Cory_1975>	 The problem being that there's no UploadWizard directory in my extensions directory.
[02:31:44] <Cory_1975>	 Anyone know what I'm supposed to do?
[10:56:25] <Betacommand>	 !magic
[10:56:25] <wm-bot>	 For more information about creating magic words and their inner workings, see <http://www.mediawiki.org/wiki/Manual:Magic_words>. For a list of magic words, please see <http://www.mediawiki.org/wiki/Help:Magic_words>.
[12:37:18] <betz>	 Hi. I am looking for a way to type "todo's" on each page, and having a overview page where I show an overview of all todo's, grouped per page title. How should I go to achieve this?
[13:18:28] <marktraceur>	 betz: "todo"s for the page, or for something else?
[13:18:50] <marktraceur>	 betz: Honestly this doesn't sound like a MediaWiki Thing.
[13:19:57] <betz>	 marktraceur:for example, we have a 'kitchen' page, where there are some todos for work in the kitchen. And same for living room. Then the overview would show all todo's
[13:20:02] <marktraceur>	 betz: However, you could probably do it. I just don't think anyone has, because 1. there are talk pages and B) if you don't want to use a talk page for task management, there are only about 5000 other bug trackers you could use
[13:20:14] <marktraceur>	 Oh, yeah, see, that seems like a misuse of MediaWiki to me
[13:20:46] <marktraceur>	 betz: However, you could probably do it with some nasty conglomeration of templates.
[13:21:09] <betz>	 i build the same thing once in drupal, but local hackerspaces tend to use mediawiki for everyting :)
[13:21:17] <betz>	 Drupal, but why?...
[13:21:36] <marktraceur>	 betz: e.g. have [[Template:Bathroom tasks]] and transclude it into [[Bathroom]] and [[All tasks]] separately
[13:21:44] <marktraceur>	 You could also have subsections that way.
[13:21:58] <marktraceur>	 But I hate, hate, hate to suggest this because there are so many better ways to accomplish this.
[13:22:20] <betz>	 how / what would you use?
[13:22:45] <marktraceur>	 Tell the hackerspace to stop telling you to reinvent the wheel and use e.g. trac, bugzilla, phabricator, roundup, or really *any other of the 5000 free bug trackers*
[13:23:48] <marktraceur>	 Then not only will you get to-do lists, tracking of all of them, projects under which you can file "living room", "bathroom", etc., but also assignees, email alerts, tracking of status (including not just "done" and "open" but also stuff like "declined"), and even discussion.
[13:23:55] <betz>	 well, the fact that the todos are on a parent page is nice. SO you have a page with info about the kitchen, the goal, current state etc. And then on the bottom tasks for this page
[13:24:16] <betz>	 so not just a bunch of tickets
[13:24:47] <betz>	 will reinvent the wheel in drupal i guess
[13:24:53] <betz>	 thanks
[13:24:54] <marktraceur>	 You may be able to write a bridge to list the tasks on a $bugtracker instance in MediaWiki. Or to fetch the content of a MW page to be placed on some page in a bugtracker.
[13:24:58] <marktraceur>	 Wait wait wait what?
[13:25:13] <marktraceur>	 Why would you reinvent the wheel AT ALL
[13:27:48] <betz>	 marktraceur: i did it once for https://taz.io/todos
[13:29:21] <marktraceur>	 betz: Actually, I bet Wikia has some silly solution to this problem
[13:29:21] <marktraceur>	 One sec.
[13:31:27] <marktraceur>	 Ugh, nope, but maybe I forgot about something.
[13:32:34] <marktraceur>	 Sigh.
[13:32:44] <marktraceur>	 betz: Well, no software exists that's easy, I guess
[13:34:03] <betz>	 yeah, will stick to what I know best. In fact, the one on taz.io already had assignment to users, a general overview, and a overview on user page
[13:34:30] <betz>	 just need to convince people to install drupal instead of the holy mediawiki :)
[13:34:46] <betz>	 thanks for your help
[13:44:48] <Betacommand>	 any run across cases of jobs being stuck in the queue and never being run?
[13:46:46] <Lcawte>	 So question for people. I've got a tag in MediaWiki for my extension, but I want the tag's contents to appear in my specific (custom) skin above the page content/title which I figure is best to use a hook for (yes, yes, skin specific hooks are bad etc). What's the best way to get tag output to be whereever my content is? Would I just put my $wgHooks in the tag's function and pass it the output as
[13:46:49] <Lcawte>	 a variable?
[13:49:06] <Betacommand>	 Lcawte: what kind of output are you trying to add?
[13:49:30] <Lcawte>	 A block of HTML
[13:50:58] <Betacommand>	 you could try using a CSS hack, or look to make it a universal skin change
[16:26:55] <hypergrove>	 hello - is there any way to define my own translated mediawiki:messages and to then reference them in a template? I really am tiring of using #switch:{{lc:{{UILANGCODE}}}}
[16:27:56] <Betacommand>	 hypergrove: is your UI language something special>?
[16:28:34] <hypergrove>	 no - the wiki intends to support en, af, and zu right now, adding 9 more later
[16:29:16] <Betacommand>	 let me grab some docs
[16:29:24] <hypergrove>	 Betacommand, thank you!
[16:31:15] <Betacommand>	 !e Translate | hypergrove 
[16:31:15] <wm-bot>	 hypergrove: https://www.mediawiki.org/wiki/Extension:Translate_
[16:32:06] <hypergrove>	 wm-bot what does the translate extension have to do with my question? thanks
[16:32:06] <wm-bot>	 Hey hypergrove, you are welcome, but keep in mind I am just a stupid bot, it was actually Betacommand who helped you :-)
[16:32:40] <hypergrove>	 Betacommand, what does the translate extension have to do with my question? thanks
[16:32:45] <Betacommand>	 hypergrove: thats just a bot, 
[16:34:47] <hypergrove>	 Betacommand, the translate extension has something to do with defining or accessing system messages file from a template.???
[16:35:14] <Betacommand>	 hypergrove: its what commons uses, see an example at http://commons.wikimedia.org/w/index.php?title=File:Marvin_Kirchhoefer_2012_Lotus.jpg&uselang=de
[16:35:40] <Betacommand>	 the license section header automatically gets translated to german
[16:37:18] <Betacommand>	 hypergrove: actually see int: magic word
[16:39:07] <Betacommand>	 hypergrove: so you would have {{int:messsage_name}} to reference the text
[16:39:23] <hypergrove>	 so I can define a new mediawiki message?
[16:39:35] <hypergrove>	 and then reference it using {{int:msgname}}?
[16:39:56] <Betacommand>	 and then [[Mediawiki:Message_name]] and [[Mediawiki:Message_name/zu]] ect
[16:41:30] <hypergrove>	 i do not see how to define messages as a user, not as a programmer
[16:42:09] <hypergrove>	 i guess i have to define them in an i18n file
[16:42:15] <hypergrove>	 ok
[16:45:22] <Betacommand>	 hypergrove: No
[16:45:33] <Betacommand>	 hypergrove: you just set them on wiki
[16:46:58] <Betacommand>	 hypergrove: messing with i18n files should only be done on the extension level
[16:51:23] <hypergrove>	 betacommand there is no way to "just set them on wiki" for messages I wish to reference from my templates. I see no way around creating an i18n in the context of a new extension
[16:51:49] <hypergrove>	 .... an extension specific to the application the templates are for/about
[16:52:28] <Betacommand>	 hypergrove: yes there is.
[16:52:42] <Betacommand>	 hypergrove: what is the message called?
[16:54:47] <hypergrove>	 there is? ok and that would be great. Call it anything you want .... it's a new message .... let's call it "office-contacts" and the english message says "Office Contacts" .... how do I record this message in the messages subsystem without defining an i18n file?
[16:55:22] <hypergrove>	 the af version is "Kantoor handleidings"
[16:55:45] <Betacommand>	 hypergrove: is your wiki public
[16:57:34] <Betacommand>	 hypergrove: go to [[Mediawiki:office-contacts]]
[16:57:54] <hypergrove>	 ok
[16:58:05] <Betacommand>	 set with the English/default text 
[16:58:18] <Betacommand>	 then go to:
[16:58:23] <hypergrove>	 done
[16:58:35] <Betacommand>	 [[Mediawiki:office-contacts/af]]
[16:58:53] <Betacommand>	 set it with Kantoor handleidings
[16:59:08] <Guest62061>	 who is admin?
[16:59:11] <hypergrove>	 done
[16:59:27] <hypergrove>	 now i will try int:office-contacts
[17:00:37] <marktraceur>	 Guest62061: Admin on what wiki?
[17:01:32] <hypergrove>	 Betacommand, it worked great - wow didnt know that one very cool
[17:01:39] <Guest62061>	 i'm having problems with deleting my pics
[17:01:44] <Guest62061>	 can't delet them
[17:02:10] <marktraceur>	 Guest62061: On what wiki?
[17:02:16] <Guest62061>	 wiki commons
[17:02:23] <marktraceur>	 Guest62061: OK, go to #wikimedia-commons then
[17:02:30] <marktraceur>	 This is a channel about the software that runs the site.
[17:02:33] <Guest62061>	 wrong room ? sorry
[17:02:37] <marktraceur>	 No problem :)
[17:03:24] <hypergrove>	 Betacommand, for all this time I've not known the message system could be used this way!
[17:03:36] <Betacommand>	 hypergrove: like I said i18n files are for extensions only
[17:04:08] <hypergrove>	 I see it differently now - I see them useful to ALL templates
[17:04:19] <marktraceur>	 Use sparingly :)
[17:05:32] <Betacommand>	 hypergrove: it does add more overhead, and server stress so ask marktraceur said, use wisely
[17:05:44] <hypergrove>	 sparingly yes -- for interests of maintenance -- but no reason otherwise not to use messages in any event, even for monolingual wikis
[17:06:18] <hypergrove>	 adds more stress to have #switch:{{lc:{{UILANGCODE}}}} everywhere in one's template
[17:06:34] <marktraceur>	 Probably better to use Extension:Translate
[17:06:45] <marktraceur>	 "better"
[17:06:50] <marktraceur>	 !e Translate | hypergrove
[17:06:50] <wm-bot>	 hypergrove: https://www.mediawiki.org/wiki/Extension:Translate_
[17:07:00] <hypergrove>	 i don't see how that comment relates to strings output from templates
[17:07:02] <marktraceur>	 ymmv.
[17:07:18] <Betacommand>	 marktraceur: read scrollback :P
[17:07:34] <marktraceur>	 Yes, for this case, I agree, use messages
[17:07:40] <hypergrove>	 again, I don't see how extension:Translate relates to strings output by templates
[17:07:41] <marktraceur>	 But there are a lot of cases where it won't be as useful.
[17:08:21] <Betacommand>	 hypergrove: its useful for mass translation, its the scaled up version if int
[17:08:56] <b3niup>	 Is there any way to create checklists inside mediawiki articles? I mean something like http://www.mediawiki.org/wiki/Extension:Tasks_Extension
[17:09:21] <hypergrove>	 scaled up version of int --- well sure, but it relates to the general content of a page not to templates called by the page
[17:09:24] <hypergrove>	 right
[17:09:25] <hypergrove>	 ?
[17:09:34] <Betacommand>	 Both
[17:11:03] <hypergrove>	 both in the sense that the string(s) output by a template can be an input to the template, eg. {{template_x |string_1={{int:string_1}} |string-n={{int:string_n}} }} etc////
[17:15:15] <hypergrove>	 sorry, that was a question
[17:46:52] <sabretache>	 Trying to run 'runJobs.php' with the --memory-limit "max" param. get "Fatal error: Allowed memory size of 262144 bytes exhausted". php.ini memory_limit is set at 1000M. So what exactly is 'allowing' a max memory size of only 256K for this script?
[17:47:15] <sabretache>	 any ideas?
[17:47:51] <sabretache>	 it runs fine without the max memory paam
[17:47:57] <sabretache>	 param
[17:50:04] <kikero>	 Hey! I would like to create an extension that inserts an input box + submit button on a page. If submitted, it should add a section to the talk page of the article with the content of the input box.
[17:50:10] <kikero>	 What hooks should I use for that?
[18:09:41] <Superlokkus>	 I'm using the latest media wiki but I'm getting an [342ec54d] 2015-04-28 18:08:59: Fatal exception of type MWException when it tries to send a mail
[18:10:42] <Superlokkus>	 I'm using google mail as extern smtp and I tried https://phabricator.wikimedia.org/T32260 already
[18:14:07] <Superlokkus>	 Using of the built in php sendmail lent to missing mails
[18:35:14] <legoktm>	 !debug
[18:35:14] <wm-bot>	 For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging
[18:35:22] <legoktm>	 Superlokkus: ^ have you tried that?
[18:39:33] <Superlokkus>	 legoktm I've got "Notice: Uncommitted DB writes (transaction from DatabaseBase::query (LCStoreDB::get)). in /var/www/vhosts/web199.c14.webspace-verkauf.de/html/programmatikWiki/includes/db/Database.php on line 4266"
[18:40:12] <legoktm>	 that's unrelated
[18:40:37] <kikero>	 I know about http://www.mediawiki.org/wiki/Extension:InputBox, but would like to be able to enter the text into the given inputbox and have it posted to the page.
[18:42:05] <Superlokkus>	 Ah got it now with the $wgShowExceptionDetails setting, I'm sorry I was to stupid to find the exception details. PEAR is missing on my damn webhoster installation.
[18:42:19] <Superlokkus>	 legoktm Thank you very much
[18:42:26] <legoktm>	 :)
[18:42:42] <^d>	 legoktm: We really should pull in PEAR_Smtp (or something similar) with composer.
[18:42:46] <Superlokkus>	 thought I could work around this PEAR problem with swift mailer
[18:42:51] <^d>	 Our existing smtp setup is kinda cruddy
[18:43:07] <legoktm>	 ^d: composer supports pear packages, so that should be doable
[18:43:50] <^d>	 Ship it in vendor rather than relying on people to install it and deal with include paths :)
[18:44:38] <Superlokkus>	 limesurvey worked on my crappy setup btw
[18:45:39] <Superlokkus>	 says l/UserMailer.php: PEAR mail package is not installed so I guess I need my hoster to install PEAR:mail for me?!
[18:45:50] <Superlokkus>	 No workaround?
[18:47:16] <legoktm>	 ^d: https://packagist.org/packages/pear/mail
[18:49:32] <Superlokkus>	 legoktm So shall I just upload it in the include directory of my mediawiki installation?!
[18:51:07] <legoktm>	 Superlokkus: for now that should work
[18:52:43] <legoktm>	 ^d: https://phabricator.wikimedia.org/T97454?workflow=create
[18:53:18] <^d>	 woot
[18:56:02] <Superlokkus>	 damn include/mail doesnt work looks like I have to create /PEAR
[18:56:12] <Superlokkus>	 doesn't I?
[19:01:52] <Superlokkus>	 (ok looks like I has to be done by installing PEAR and then pear/mail. I hate hosters where I don't get ssh access)
[19:04:36] <kikero>	 At least, is there a way to have a template which inserts the user's signature?
[19:04:55] <kikero>	 i.e. User:Test calls {{test123}} in Talk:Test Page
[19:05:11] <kikero>	 {{test123}} returns "Hello World + <user's signature>".
[20:44:59] <xkomczax>	 Hi, today I updated to the latest Mediawiki and now the InstatntCommons is not working (it was working for me shortly after the update). Was this behaviour already observed? Is the problem in the latest Mediawki (or my instalation of latest Mediawiki) or there is some issue with the Commons?
[20:46:59] <xkomczax>	 I am observing the same behaviour at least on http://www.enviwiki.cz/wiki/Hlavn%C3%AD_strana as well...
[20:47:55] <xkomczax>	 Funny think is some (two in total) pictures are working (small svg files. But the other ones svgs are not loading)
[20:52:31] <Krenair>	 xkomczax, I think there are issues on the commons side
[20:53:06] <Krenair>	 https://phabricator.wikimedia.org/T97469
[20:55:22] <xkomczax>	 Krenair: oh, so just coincidence. Thank you for the info! :-) 
[21:43:55] <statistics_>	 hello everybody! I installed the "usage statistics" extension (mw 1.24.1) but I all get once I click on the link on my special pages site is an empty page (http://mediaewiki.org/wiki/Spezial:Benutzerstatistik) :(. do you guys have any idea how I could fix that?
[21:49:01] <statistics_>	 nobody? :(
[21:49:22] <^d>	 !blankpage
[21:49:23] <wm-bot>	 A blank page or HTTP 500 error usually indicates a fatal PHP error. For information on debugging (including viewing errors), see <https://www.mediawiki.org/wiki/Manual:How_to_debug>.
[21:56:51] <statistics_>	 thx ^d! I'll figure it out :)
[21:59:27] <statistics_>	 hmmm, seems like this line is causing an error: Xml::namespaceSelector( $namespace, 'all' ) . do you know whether this could be some kind of incompatibility between extension version and mw version?
[21:59:47] <^d>	 Possibly. What's the error?
[22:04:03] <statistics_>	 Fatal error: Call to undefined method Xml::namespaceSelector() in /home/mediaewi/public_html/w/extensions/UsageStatistics/UsageStatistics_body.php on line 369
[22:09:28] <statistics_>	 any idea?
[22:11:54] <bawolff>	 statistics_: Yes, that method was removed 
[22:11:57] <bawolff>	 !git e7ecd273d73ca031fd24
[22:11:58] <wm-bot>	 MediaWiki development is using git, a distributed source control manager, starting on March 21st, 2012; details: https://www.mediawiki.org/wiki/Git_happens Instructions for using it: https://www.mediawiki.org/wiki/Git/Workflow To get an account: https://www.mediawiki.org/wiki/Project:Labsconsole_accounts
[22:12:05] <bawolff>	 !gerrit e7ecd273d73ca031fd24
[22:12:05] <wm-bot>	 https://gerrit.wikimedia.org/r/#q,e7ecd273d73ca031fd24,n,z
[22:12:54] <statistics_>	 so there is no way I can fix that without going deep into the code?
[22:19:43] <bawolff>	 Either extensions needs to be updated, or mediawiki needs to be downgraded
[22:22:57] <statistics_>	 aaaa, I think I fixed it by including the missing method
[22:23:07] <statistics_>	 thank you very, very much — u made my day!