[00:12:56] <willwh>	 marktraceur: well, messed with it for an hour
[00:13:02] <willwh>	 still no further forward
[00:13:35] <willwh>	 turns out I didn't have the Widgets installed when I created Widget:Iframe
[00:13:41] <willwh>	 so I deleted the page from the db
[00:13:43] <willwh>	 and recreated
[00:13:46] <aelevadoan>	 o/
[00:13:54] <willwh>	 now I have Widget:Iframe in my Widget namespace
[00:13:59] <willwh>	 and no longer duped in Main
[00:14:02] <willwh>	 but it's still broken
[00:14:07] <aelevadoan>	 I want to offer mediawiki instances on my vps 
[00:14:26] <willwh>	 plural, on a vps, with mysql on the same vps?
[00:14:28] <aelevadoan>	 I would like to know if its more advisable to set up seperate mediawiki installations
[00:14:31] <aelevadoan>	 or a farm
[00:17:35] <willwh>	 aelevadoan: that's a broad question
[00:17:45] <willwh>	 how many do you plan to host, what kind of load, etc
[00:17:59] <willwh>	 I just installed medaiwiki today, but these are not mediawiki specific questions really
[00:18:02] <aelevadoan>	 I dont know how many, I suppose several
[00:18:15] <aelevadoan>	 what do you mean with "what kind of load"?
[00:18:17] <willwh>	 well, I'd suggest at least have a seperate vps for databases
[00:18:26] <willwh>	 I mean - what kind of load on the various hosts do you expect
[00:18:28] <aelevadoan>	 For now I only have this vps
[00:18:33] <willwh>	 how can you expect someone to answer how to host stuff
[00:18:36] <willwh>	 if you don't really know
[00:18:43] <willwh>	 what you plan to host
[00:19:00] <willwh>	 a vps should be able to run multiple deploys, and a database, if it's not high load
[00:19:01] <aelevadoan>	 I have a 50gb vps host
[00:19:10] <aelevadoan>	 it will be limited load
[00:19:12] <willwh>	 disk size irrelevant mostly
[00:19:23] <aelevadoan>	 they will be small community wikis
[00:19:48] <aelevadoan>	 what I was wondering is that if they are going to be independant wikis
[00:19:52] <aelevadoan>	 if its worth doing a farm
[00:20:20] <willwh>	 like I said, I only installed mediawiki today
[00:20:22] <willwh>	 so I have no idea
[00:22:23] <DanielK_WMDE_>	 aelevadoan: if you have no reason to run different versions of mediawiki, make a farm. if you set it up right, it will save you a lot of work
[00:22:33] <DanielK_WMDE_>	 (if you set it up wrong, it will mess things up bad)
[00:22:51] <aelevadoan>	 DanielK_WMDE_: what do you mean by setting it up bad?
[00:23:48] <DanielK_WMDE_>	 Getting pathes mixed up, etc. Setting up a farm takes a bit of fiddeling. Though the Farmer extension should take care of most of it for you. If you are willing to risk running it...
[00:23:53] <aelevadoan>	 DanielK_WMDE_: I was checking a tutorial that recommended creating symlinks from the initial wiki to the second wiki
[00:24:07] <aelevadoan>	 except the LocalSettings.php, images directory and mw-config directory
[00:24:11] <DanielK_WMDE_>	 having a web interface for configuring the server always feels scary to me. too easy to hack in...
[00:24:27] <aelevadoan>	 DanielK_WMDE_: I prefer doing the fiddeling
[00:24:30] <DanielK_WMDE_>	 symlinks are not needed, rewrite rules work better imho.
[00:24:39] <aelevadoan>	 DanielK_WMDE_: which way is that?
[00:24:47] <DanielK_WMDE_>	 the magic is really in how you set up your gobal LocalSettings, and how you manage the settings for the individual wikis
[00:25:21] <aelevadoan>	 DanielK_WMDE_: do you have any link of a documentation?
[00:25:26] <DanielK_WMDE_>	 you basically write an "active" config file. php code that decides which settings to use, based on the Host header or request path.
[00:25:40] <DanielK_WMDE_>	 not offhand, but maybe the bot does
[00:25:41] <DanielK_WMDE_>	 !farm
[00:25:41] <wm-bot>	 To run multiple wikis, you can simply install MediaWiki in different folders, with different databases or in one with database prefixes. You can also have multiple wikis using a single installation: <http://www.mediawiki.org/wiki/Manual:Wiki_family> If you run a farm or want to, join the mailing list: <https://lists.wikimedia.org/mailman/listinfo/wikifarm>
[00:25:44] <DanielK_WMDE_>	 :)
[00:26:16] <DanielK_WMDE_>	 not sure how good that documentation is... maybe i'll write a howto one day. in my copious free time
[00:27:08] <aelevadoan>	 DanielK_WMDE_: I tried the scenario 1 of that documentation which is via symlinks
[00:29:37] <DanielK_WMDE_>	 you can use symlinks or rewrite rules, but you need to diferentiate between the wikis in the LocalSettings.php file in any case.
[00:29:55] <DanielK_WMDE_>	 like this: https://www.mediawiki.org/wiki/Manual:Wiki_family#Scenario_2:_Quick_set-up
[00:30:40] <DanielK_WMDE_>	 eek, the "Updating wikifarm from the commandline" is a nasty hack :/
[00:31:26] <aelevadoan>	 DanielK_WMDE_: in scenario 2 I share the same images directory for all the wikis, right?
[00:31:53] <aelevadoan>	 I wanted to see which is the easiest way for backing up each mediawiki individually, afterwards
[00:32:07] <DanielK_WMDE_>	 i didn't read in detail, i don't think the "scenarios" described are really complete or exclusive. that page is a bit of a mess :(
[00:33:22] <DanielK_WMDE_>	 aelevadoan: if you have a wiki form set up right, each wiki has a separate database and a separate image dir. you can make an xml dump using dumpBackp.php --wiki whatever.
[00:34:16] <aelevadoan>	 DanielK_WMDE_: scenario 1 and 2 on that wikipage are with the same databse
[00:34:19] <DanielK_WMDE_>	 i have no experience with a shared image dir. i'd do this by setting up a separate wiki as a common file repo, mediawiki has special support for this (that's how wikimedia commons works)
[00:34:59] <DanielK_WMDE_>	 aelevadoan: you can have separate databases or use table prefixes. separate is nicer.
[00:35:06] <aelevadoan>	 DanielK_WMDE_: what do you mean by setting up a separate wiki as a common file repo?
[00:35:06] <DanielK_WMDE_>	 has nothing to do with using symlinks or not. 
[00:35:19] <aelevadoan>	 DanielK_WMDE_: Im interested in trying that way
[00:35:25] <aelevadoan>	 seperate databases
[00:36:31] <aelevadoan>	 DanielK_WMDE_: is this scenario 3?
[00:36:41] <DanielK_WMDE_>	 https://www.mediawiki.org/wiki/Manual:Image_administration#Foreign_Repositories
[00:37:50] <DanielK_WMDE_>	 aelevadoan: the "scenarios" are useless. you have several independent choices: symlinks or rewrite rules, shared images or separate, shared database or separate, wiki by domain or by path (or even request parameter).
[00:38:19] <DanielK_WMDE_>	 in all cases, you need some sort of dispatching logic in your localsettings, as shown in "scenario 2".
[00:38:45] * DanielK_WMDE_ grumbles at crappy documentation
[00:39:12] <aelevadoan>	 you recommended rewrite rules before, right?
[00:39:25] <DanielK_WMDE_>	 aelevadoan: seems like people just wrote down what they did on the help page, in more or less detail. would be nice to describe the different choices and techniques separately.
[00:40:17] <aelevadoan>	 DanielK_WMDE_: is the rewrite rules option complicated?
[00:40:18] <DanielK_WMDE_>	 aelevadoan: yes, rewrite rules, separate databases, shared images via ForeignDBRepo (or "instant commons" if you want to use commons.wikimedia.org as your shared repo).
[00:40:42] <aelevadoan>	 I dont need shared images
[00:41:05] <aelevadoan>	 rewrite rules, separate, separate db and wiki by (sub)domain
[00:41:13] <DanielK_WMDE_>	 i don't find it complicated. there are several approaches for that two (mainly, for apache, rewrite rules or aliases). it depends on the web server you are using.
[00:41:32] <DanielK_WMDE_>	 but really... you can get away without even that
[00:41:46] <DanielK_WMDE_>	 just mapp all the domains to the same wiki installation, and have a "dispatcher" in your localsettings
[00:41:59] <DanielK_WMDE_>	 you may want rewrite rules for pretty urls, but you can farm without.
[00:42:37] <DanielK_WMDE_>	 (see https://www.mediawiki.org/wiki/Manual:Short_URL if you are interested in rewrite rules, but you can skip that for now)
[00:43:08] <aelevadoan>	 when you say map all the domains to the same wiki installation
[00:43:23] <aelevadoan>	 you mean through the virtual hosts in etc/apache2/sites-available?
[00:43:29] <DanielK_WMDE_>	 yes
[00:44:22] <DanielK_WMDE_>	 aelevadoan: i'm about to go to bed... you can find me here again in 12 hours or so :)
[00:44:32] <aelevadoan>	 DanielK_WMDE_: thanks very much
[00:44:35] <aelevadoan>	 just one more thing
[00:44:44] <aelevadoan>	 what do you mean by dispatcher?
[00:46:30] <DanielK_WMDE_>	 aelevadoan: a switch statement like the one shown in https://www.mediawiki.org/wiki/Manual:Wiki_family#Scenario_2:_Quick_set-up
[00:46:45] <aelevadoan>	 thanks
[00:46:48] <DanielK_WMDE_>	 it picks the config for a given wiki based on the host name
[00:46:51] <DanielK_WMDE_>	 have fun :)
[00:47:01] <aelevadoan>	 DanielK_WMDE_: thanks, see you son
[01:43:57] <Phoenix303_>	 Is there any problem when jenkins-bot does not run? I have submitted the bug https://gerrit.wikimedia.org/r/#/c/183406/ it ran for the first patch set but it did not for the second patch set
[01:46:41] <unicodesnowman>	 recheck :)
[01:49:56] <Phoenix303_>	  Is there any problem when jenkins-bot does not run? I have submitted the bug https://gerrit.wikimedia.org/r/#/c/183406/ it ran for the first patch set but it did not for the second patch set
[01:50:22] <Reedy>	 Sometimes it's broken
[01:50:25] <Reedy>	 It's run it now
[01:58:18] <Phoenix303_>	 What is build test failure with non-voting?
[02:06:19] <MatmaRex>	 Phoenix303: it means that it will be possible to merge the change even if that test is failing
[02:06:45] <MatmaRex>	 Phoenix303: in practice, it often means no one cares about that test. :)
[02:06:55] <Phoenix303>	 Yes MatmaRex
[02:07:04] <Phoenix303>	 okay thanks :)
[02:07:32] <Phoenix303>	 How can i get help for code review? Any suggestion?
[02:20:24] <TheRetroGamer>	 I am wondering if anyone can tell me if it's possible to layer images (put one on top of another) in wikiscript?
[02:27:18] <unicodesnowman>	 TheRetroGamer, perhaps copy this template https://en.wikipedia.org/wiki/Template:Superimpose
[02:29:30] <TheRetroGamer>	 Thanks, that might be useful.
[04:53:38] <aelevadoan>	 o/
[04:53:43] <aelevadoan>	 anyone here has a mediawiki farm?
[05:08:55] <Yaron>	 aelevadoan: I do.
[05:09:07] <aelevadoan>	 Yaron: o/
[05:09:18] <Yaron>	 o/ to you!
[05:09:19] <aelevadoan>	 Yaron: and how did you create it?
[05:09:49] <Yaron>	 It took a lot of work. But it doesn't have to, depending on what exactly you need it to look like.
[05:10:09] <Yaron>	 Mine took a lot of work because I needed it to be super-automated.
[05:10:12] <aelevadoan>	 I want seperate databases
[05:10:19] <Yaron>	 Alright.
[05:10:26] <aelevadoan>	 and seperate image directories
[05:10:31] <Yaron>	 Did see the "Wiki family" documentation?
[05:10:35] <aelevadoan>	 yes
[05:10:45] <aelevadoan>	 but Im confused
[05:10:53] <aelevadoan>	 Ive seen there are several ways of doing it
[05:10:56] <aelevadoan>	 both with symlinks
[05:10:59] <aelevadoan>	 and rewrite rules
[05:11:09] <aelevadoan>	 having several LocalSettings files
[05:11:11] <aelevadoan>	 etc.
[05:11:39] <Yaron>	 You should do the "Drupal-style" approach - that's the only good one, in my opinion.
[05:11:56] <aelevadoan>	 let me check it again and ask you for guidance
[05:11:58] <aelevadoan>	 one second
[05:19:12] <Yaron>	 Ah, going to sleep - talk later.
[06:43:32] <Nemo_bis>	 Sigh, still https://getcomposer.org/doc/00-intro.md#installation-linux-unix-osx
[07:19:28] <legoktm>	 Nemo_bis: yeah, composer's installer is pretty bad. And it's not packaged for any distros afaik except in homebrew :/
[09:47:07] <theatrex>	 Hey folks. When I submit changes to a page on my wiki, I get a screen that says this: "Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot contact the database server)"
[09:48:08] <theatrex>	 But it only happens to 1 page.
[10:16:25] <theatrex>	 Hey folks. When I submit changes to a page on my wiki, I get a screen that says this: "Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot contact the database server)"
[10:51:11] <theatrex>	 Hello?
[13:19:18] <Fiona>	 Hi theatrex.
[14:27:02] <frogsy>	 Can anyone tell me, is there a MediaWiki extension that will allow for "in-page editing", where you can edit a section of an article and then save those changes without loading a new Edit page?
[14:29:49] <Betacommand>	 frogsy: no
[14:30:23] <marktraceur>	 frogsy: There's VisualEditor, but no, not with Wikitext
[14:30:33] <marktraceur>	 And not per-section.
[14:30:41] <marktraceur>	 So basically we have failed on every level of your requirements.
[14:30:53] <marktraceur>	 I will look into buying seppuku implements.
[14:31:38] <frogsy>	 Hah. Damn.
[14:32:24] <theatrex>	 Fiona: Hello! Can you help me? :)
[14:32:30] <marktraceur>	 frogsy: It seems like the sort of thing that wouldn't be too hard, though
[14:33:09] <marktraceur>	 theatrex: Your error message says that MW can't connect to the database, so maybe check that your database configuration is correct
[14:33:43] <theatrex>	 marktraceur: Well yes it is correct. It's only 1 page that gives me that error.
[14:33:57] <Reedy>	 Delete it
[14:34:01] <marktraceur>	 frogsy: There's already an edit section link on every section, there's already an API method for getting section wikitext (I think...) and there's definitely an API method for saving pages
[14:34:06] <marktraceur>	 Reedy: Hush
[14:34:21] <marktraceur>	 theatrex: Maybe you could tell us what page it is
[14:34:45] <Reedy>	 My minds gone blank.. One of Roans uni friends did a POC type thing for this inline editing
[14:35:11] <theatrex>	 I could just copy the code out of it, delete it, then make a new page couldn't I?
[14:35:20] <frogsy>	 marktraceur: See, that's what I thought. Replace the section you want to edit with a textarea containing its wiki markup, add a button that submits its contents to the save-new-page API endpoint, then load in the new section via AJAX. But I don't know enough about MediaWiki to say it's easy without knowing all the details
[14:35:23] <marktraceur>	 theatrex: I doubt that would help
[14:35:26] <frogsy>	 I suppose there's a reason no one's done it yet?
[14:35:49] <marktraceur>	 frogsy: I'm not *totally* confident that you could parse only the section.
[14:35:56] <marktraceur>	 You would need to get the full page text
[14:36:05] <marktraceur>	 Which is fine, you can still do *that* through Ajax.
[14:36:13] <Reedy>	 Not if you have things like references that may refer to multiple parts
[14:36:21] <marktraceur>	 (also, things I learned later than I should have: "AJAX" isn't an acronym anymore)
[14:36:31] <marktraceur>	 Reedy: Exactly.
[14:36:49] <frogsy>	 Oh, it's just Ajax now?
[14:36:49] <marktraceur>	 Or behaviour switches...
[14:36:55] <marktraceur>	 frogsy: Right? Seems silly to me.
[14:36:59] <frogsy>	 Makes sense since it seems like 90% of people aren't using it with XML anymore, I guess.
[14:37:10] <marktraceur>	 Anyway, you should be able to do this in a gadget or a user-script
[14:37:12] <marktraceur>	 !userjs
[14:37:12] <wm-bot>	 There is no such key, you probably want to try: !javascript, 
[14:37:16] <marktraceur>	 !javascript
[14:37:16] <wm-bot>	 To set up custom javascript on a wiki, edit the page called [[MediaWiki:Common.js]] (NOT a file, a page on your wiki, which is included via <script>) as a sysop. If $wgAllowUserJs is true in LocalSettings.php, you may also edit the /vector.js (assuming your skin is vector) subpage of your userpage. https://www.mediawiki.org/wiki/Manual:Interface/JavaScript
[14:37:23] <marktraceur>	 Thanks wm-bot
[14:37:23] <wm-bot>	 Hey marktraceur, you are welcome!
[14:40:45] <theatrex>	 marktraceur: https://corningwiki.org/index.php/Brandon_Smith
[14:43:05] <marktraceur>	 theatrex: I see this has an infobox, did you import that template and its dependencies from enwiki?
[14:45:08] <theatrex>	 Yes. I used Wikipedia's export tool.
[14:45:33] <marktraceur>	 theatrex: And the server you're running this on...what kind of physical resources does it have? RAM, CPU, etc.
[14:45:57] <marktraceur>	 I *doubt* that it's actually that big an issue, but it seems possible.
[14:46:08] <theatrex>	 2GB RAM, Dual Core CPU, 50GB SSD
[14:46:16] <marktraceur>	 Hm, well, that seems like it'd be OK.
[14:46:17] <frogsy>	 marktraceur: Thanks for the tip. Not sure that I know enough actually implement a solution for this but I'll look into it
[14:46:27] <marktraceur>	 frogsy: 'kay. Thanks for dropping by!
[14:46:46] <marktraceur>	 theatrex: Is there more error text in the server logs, by any chance?
[14:47:12] <theatrex>	 Let me look again. There wasn't before but let me check.
[14:47:19] <marktraceur>	 *nod*
[14:48:59] <theatrex>	 Nothing in /var/log/apache/error.log
[14:50:15] <marktraceur>	 !debug
[14:50:15] <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
[14:50:19] <marktraceur>	 theatrex: ^
[14:51:26] <theatrex>	 I'm not getting anything with the debug for some reason.
[14:51:53] <marktraceur>	 Weird.
[14:52:02] <theatrex>	 Very.
[14:52:11] <marktraceur>	 theatrex: OK, next up, I need you to tell me what the most popular street in Corning is so I can test it myself.
[14:52:22] <theatrex>	 market street
[14:53:18] <marktraceur>	 Worked for me
[14:53:31] <marktraceur>	 theatrex: What changes were you trying to make?
[14:53:57] <theatrex>	 I was just trying to edit the page and I added the Seealso extension.
[14:54:06] <marktraceur>	 Seealso...hm
[14:54:18] <marktraceur>	 theatrex: You just installed it, right? And this is your first time using it?
[14:54:20] <theatrex>	 But removed the seealso tags.
[14:54:24] <theatrex>	 Yes.
[14:54:29] <marktraceur>	 theatrex: Did you run update.php?
[14:54:43] <marktraceur>	 J'accuse!
[14:54:47] <theatrex>	 After installing it?
[14:54:50] <marktraceur>	 Yes!
[14:54:54] <theatrex>	 Nope :P
[14:54:57] <marktraceur>	 Tryyyy
[14:55:11] <theatrex>	 And that's the ONLY page I used the seealso stuff too :P
[14:55:39] <theatrex>	 Done!
[14:56:35] <theatrex>	 Still got the same issue except now the problem is all the way at the bottom of the page. Bypassing my browser's cache.
[14:56:44] <theatrex>	 I mean I'm going to do that now
[14:57:03] <theatrex>	 Nope, still got the issue.
[14:59:37] <marktraceur>	 Hm.
[15:00:11] <marktraceur>	 theatrex: Where are the see also tags?
[15:01:13] <theatrex>	 I deleted them a few hours ago thinking that was the issue.
[15:01:34] <marktraceur>	 Ah.
[15:01:46] <marktraceur>	 OK, let's try something radical like removing all the text.
[15:02:09] <marktraceur>	 theatrex: First you try, then I will since I don't have any problems
[15:02:30] <theatrex>	 Okay one moment.
[15:03:07] <marktraceur>	 BRB
[15:03:52] <theatrex>	 Well what do you know. It saved without an issue.
[15:04:26] <marktraceur>	 Add stuff back in one section at a time
[15:05:31] <theatrex>	 Well. I just removed the infobox and it saved without an issue.
[15:08:13] <theatrex>	 Huh. I put the infobox code back in and it saved perfectly fine.
[15:08:49] <theatrex>	 I also disabled OpenSearchXML and removed the blacklist thing for pageimages.
[15:09:18] <marktraceur>	 Try re-enabling them, then do the same thing
[15:14:14] <theatrex>	 Probably a noob mistake, but I used the code in the blacklist pageimages in the example here: https://www.mediawiki.org/wiki/Extension:PageImages#Configuration
[15:15:04] <marktraceur>	 theatrex: Did re-enabling the blacklist break it?
[15:16:03] <theatrex>	 One moment. I'm bouncing in between this and something else :P
[15:16:32] <marktraceur>	 No problem :)
[15:16:40] <theatrex>	 AH HA! It broke it!
[15:16:44] <marktraceur>	 Hm.
[15:17:00] <marktraceur>	 theatrex: I don't think that blacklist is *doing* anything, if you have that config
[15:17:25] <marktraceur>	 Your local page is empty, so is the one on Commons
[15:17:37] <theatrex>	 Yeah I just purged it from my config.
[15:17:39] <marktraceur>	 Neato
[15:17:50] <marktraceur>	 Glad I could help, though damned if I know why it wasn't working
[15:18:04] <theatrex>	 I did it just to try and get PageImages to work.
[15:18:59] <theatrex>	 I like the Popups extension but I don't get any images popping up :(
[15:19:07] <theatrex>	 And thanks for the help by the way. :P
[15:19:12] <marktraceur>	 Of course!
[15:26:06] <theatrex>	 Gaaaah why aren't any pictures showing!? :(
[15:31:24] <Segfault_>	 Hello. Is it possible to make the sidebar visible to sysops only, or at least only to users that are logged in? Thank you
[15:58:40] <theatrex>	 Yes, I would like to know this as well Segfault_
[15:59:17] <Reedy>	 !e DynamicSidebar
[15:59:18] <wm-bot>	 https://www.mediawiki.org/wiki/Extension:DynamicSidebar
[16:06:38] <theatrex>	 Oooooo me likey <3
[16:14:49] <Segfault_>	 Thank you Reedy, that seems to do what I want. Lots of other features as well, but it works. Thanks!
[17:13:41] <keisetsu_>	 Is there a way, in php or through the api, to get the sortkey prefix for a page in a category? I've been able to get it using the category members api, but in that case I have to get ALL of the categories and pages under a category, then test to see if the id is the same. 
[17:15:13] <marktraceur>	 keisetsu_: Well, that information is in the wikitext, so if you got the page text you could probably find it
[17:16:02] <marktraceur>	 keisetsu_: https://commons.wikimedia.org/w/api.php?action=parse&page=File:Foobar.jpg&prop=categories gives you nice sortkey :)
[17:17:23] <keisetsu_>	 marktraceur: right. I was hoping to get what the wiki thinks is the prefix, in order to avoid parsing the wikitext (though that is an option)
[17:17:50] <keisetsu_>	 marktraceur: I'll have to try that, I can't believe I haven't seen it!
[17:33:02] <keisetsu_>	 marktraceur: Thanks again. I found the query action gives the same information. Feel pretty silly now.
[17:35:10] <marktraceur>	 keisetsu_: Aw, sorry :)
[17:35:57] <keisetsu_>	 marktraceur: No problem! Thanks for pointing me in the right direction. The API has so much functionality, it's easy for me to get lost sometimes
[17:37:44] <marktraceur>	 Mmhmm.
[17:37:55] <marktraceur>	 keisetsu_: But those nice new API doc pages are very helpful, I gotta say
[17:38:04] <marktraceur>	 Thank you so so much anomie
[17:53:15] <aelevadoan>	 o/
[17:53:35] <aelevadoan>	 DanielK_WMDE_: o/
[18:07:00] <aelevadoan>	 DanielK_WMDE_: do you have some time to explain a little bit more about the mediawiki farm installation?
[18:24:59] <srlt>	 Hey Guys, I want to start contributing to wikimedia. Can you give me a head-start as to how I should go about it?
[18:25:51] <Yaron>	 srlt: do you mean Wikimedia or MediaWiki?
[18:27:48] <marktraceur>	 !wikipmediawiki
[18:27:48] <wm-bot>	 Confused about the differences between MediaWiki, Wikimedia, Wikipedia and wiki? See https://www.mediawiki.org/wiki/Wikipmediawiki
[18:37:12] <srlt>	 I want to contribute to Wikimedia movement
[18:43:25] <marktraceur>	 srlt: As an editor? As a programmer? By taking pictures?
[18:44:27] <srlt>	 As a programmer
[18:44:30] <domas>	 by moving things
[18:45:16] <srlt>	 As a MediaWiki hacker
[18:46:08] <marktraceur>	 OK, srlt, then you can start by getting the code and finding an easy bug to work on, maybe
[18:46:11] <marktraceur>	 !easy | srlt
[18:46:11] <wm-bot>	 srlt: We keep a list of bugs that are easy to solve, in case new developers want a simple step to start out with. Check out https://phabricator.wikimedia.org/tag/easy/ and let us know if you need any help fixing your first bug!
[18:46:36] <Vulpix>	 !start | srlt
[18:46:36] <wm-bot>	 srlt: https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker
[18:48:57] <MaxSem>	 g particular you're interested in?
[18:49:18] <MaxSem>	 srlt, anything particular you're interested in?
[18:57:14] <srlt>	 Nothing particular as yet. Just figuring them out.
[19:49:47] <albertcoder>	 Hi MWikians!
[19:50:11] <albertcoder>	 I am getting an error with an extension. "A database query error has occurred. This may indicate a bug in the software."
[19:50:28] <marktraceur>	 albertcoder: Did you run update.php after installing the extension?
[19:50:31] <saper>	 check the ogs
[19:50:34] <albertcoder>	 I just checked the LocalSettings.php for the database settings are perfect
[19:50:40] <albertcoder>	 NO
[19:50:40] <saper>	 logs
[19:50:45] <DanielK_WMDE_>	 aelevadoan: pretty busy right now, but just ask, maybe I can answer later, or someone else will jump in
[19:50:46] <saper>	 !errorlog
[19:50:46] <wm-bot>	 To see PHP errors, add this to the very top of LocalSettings.php: error_reporting(E_ALL); ini_set("display_errors", 1); Fatal PHP errors usually go to Apache's error log - also check the error_log setting in php.ini (or use phpinfo). For more details in wiki error reports, set $wgShowExceptionDetails = true; $wgShowSQLErrors = true; For full debug output, set $wgDebugLogFile to some path you like.
[19:51:01] <saper>	 albertcoder: ^^
[19:51:03] <marktraceur>	 Pretty sure it's gonna be update.php.
[19:51:08] <DanielK_WMDE_>	 aelevadoan: ideally, post the relevant settings files somewhere (with passwords removed)#
[19:51:10] <albertcoder>	 How can I check the logs? and run update.php?
[19:51:16] <Vulpix>	 !update
[19:51:16] <wm-bot>	 update.php is a script that updates the database tables. You usually need to run it after upgrading MediaWiki or installing certain extensions. For details, see <http://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script>
[19:51:21] <Vulpix>	 ^
[19:51:35] <albertcoder>	 k
[19:51:40] <albertcoder>	 let me see
[19:59:53] <albertcoder>	 Hi marktraceur, it seems the problem is something else. 
[20:00:00] <albertcoder>	 Let me explain 
[20:01:25] <Vulpix>	 knowing the database error message would help
[20:01:26] <albertcoder>	 My extension creates tables with InnoDB as ENGINE
[20:01:28] <Vulpix>	 set $wgShowSQLErrors = true;
[20:01:57] <albertcoder>	 Can there be any problem? marktraceur
[20:02:07] <albertcoder>	 alright Vulpix let me try
[20:02:27] <Vulpix>	 MediaWiki uses innodb by default, if available
[20:03:38] <albertcoder>	 alright thanks Vulpix, I think $wgShowSQLErrors = true; has helped. :)
[20:15:25] <aelevadoan>	 DanielK_WMDE_: http://pastebin.com/QMzmRBFt these are my two virtual hosts wiki1.conf wiki2.conf
[20:15:39] <aelevadoan>	 DanielK_WMDE_: both pointing to a basedirectory with the mediawiki code
[20:25:33] <aelevadoan>	 DanielK_WMDE_: I have in /var/www two directories for two wikies: /var/www/wiki1  and /var/www/wiki2
[20:26:00] <aelevadoan>	 each with an independant LocalSettings.php file with seperate databases and users
[20:26:31] <impacific>	 where should I place a newly created function? I mean do we have any convention of placing it towards the end of file..?
[20:27:01] <Reedy>	 Usually
[20:27:16] <Reedy>	 Unless the file functions are grouped by something
[20:27:22] <Reedy>	 And it fits in with those
[20:30:56] <flexpaint>	 can i format results from an rss feed into a table using the rss extension
[20:37:26] <flexpaint>	 anyone know?
[20:37:47] <flexpaint>	 seems like i could use a template but idk
[20:38:49] <Reedy>	 Try it?
[20:39:02] <flexpaint>	 i dont know how haha :/
[20:39:15] <flexpaint>	 im reading the extension:rss page but its a little confusing
[20:44:36] <impacific>	 Wouldn´t it make sense to put a function first which will implement something that will be used by following functions? coz that would require me to put it somewhere in the middle
[20:59:52] <DanielK_WMDE_>	 aelevadoan: the dir with the code should be in /var/www/w, and your "main" LocalSettings.php would be in /var/www/w/LocalSettings.php. In there, you should have a few common settings, and then a switch statement, picking /var/www/xyz/LocalSettings.php as appropriate.
[21:00:38] <DanielK_WMDE_>	 in /var/www/xyz/ you have the "subordinate" LocalSettings.php file, and a directory for fiel uploads. Can't think of anything else to put there.
[21:00:56] <DanielK_WMDE_>	 the "subordinate" LocalSettings.php file would contain all the wiki-specific settings.
[21:01:19] <aelevadoan>	 can /var/www/w be /var/www/mediawiki_farm instead
[21:01:24] <aelevadoan>	 or is it a specific name?
[21:01:35] <DanielK_WMDE_>	 (note that if you need per-wiki settings for extensions at some point, you'll need a second file in each of the wiki dires, called ExtensionsSettings.php or some such... but that's for later)
[21:01:55] <DanielK_WMDE_>	 aelevadoan: using /w/ is just a convention, it can be whatever you like
[21:02:01] <aelevadoan>	 ok
[21:02:08] <aelevadoan>	 so i already have this base directory
[21:02:38] <DanielK_WMDE_>	 aelevadoan: ah, wait, let me think a second.
[21:03:02] <aelevadoan>	 I get confused with what should go in the general LocalSettings and what should go in the subLocalSettings
[21:03:14] <DanielK_WMDE_>	 so, /w/ should be the directory with the code *below* the document root (by convention). Otherwise, it will be difficult to set up pretty urls later.
[21:03:55] <DanielK_WMDE_>	 aelevadoan: basically, the sub-localsettings contains everything that is specific to a wiki. everythign else can be in the top level (or a commonsettings.php) file.
[21:03:59] <aelevadoan>	 when you say below you mean all its contents in this folder instead of a subfolder inside w?
[21:04:34] <DanielK_WMDE_>	 let me think a second how i would set this up...
[21:07:38] <sarkis>	 hey all - is there a plugin that will allow to hook into github auth?
[21:07:54] <sarkis>	 i'd like to have our developers access the wiki via their github accounts
[21:11:46] <DanielK_WMDE_>	 aelevadoan: https://etherpad.wikimedia.org/p/Farm101
[21:12:29] <DanielK_WMDE_>	 sarkis: typüically, you would just back both by the same LDAP
[21:12:31] <DanielK_WMDE_>	 !LDAP
[21:12:31] <wm-bot>	 There is no such key, you probably want to try: !ldap, !ldapdebug, !ldapsupport, 
[21:12:35] <DanielK_WMDE_>	 !ldap
[21:12:35] <wm-bot>	 http://www.mediawiki.org/wiki/Extension:LDAP_Authentication To get support, open a new thread on the support page http://www.mediawiki.org/wiki/Extension_talk:LDAP_Authentication
[21:12:49] <sarkis>	 yea :/
[21:13:04] <sarkis>	 we don
[21:13:14] <sarkis>	 we don't have ldap yet
[21:13:57] <aelevadoan>	 DanielK_WMDE_: I will write to you directly in the pad chat
[21:14:05] <DanielK_WMDE_>	 sarkis: but afaik, git does not offer an authentication service
[21:15:27] <DanielK_WMDE_>	 sarkis: maybe you could write an auth module that talks to PAM? I know to little about this.
[21:16:41] <DanielK_WMDE_>	 sarkis: looks like you could use http://pecl.php.net/package/PAM to implement an Auth plugin for MediaWiki. Sounds like a cool project :)
[21:16:48] <DanielK_WMDE_>	 auth plugins are pretty easy to write. 
[21:17:42] <aelevadoan>	 DanielK_WMDE_: you mean to move the mediawiki code in a subdirectory "w" instead of it being immediately below /var/www/mediawiki_farm?
[21:18:37] <DanielK_WMDE_>	 aelevadoan: yes. not absolutely necessary, but keeps things nice and clean.
[21:18:56] <DanielK_WMDE_>	 also, gets you the classic /w/index.php setup that wikipedia uses.
[21:19:31] <DanielK_WMDE_>	 aelevadoan: your sub-localsettings looks sensible
[21:19:38] <DanielK_WMDE_>	 can't promise you didn't miss anything, but
[21:19:44] <DanielK_WMDE_>	 oh, right, the upload dir and upload path
[21:19:58] <aelevadoan>	 im searchin the parameters
[21:20:05] <DanielK_WMDE_>	 but uploads are disabled per default, so you can do that later
[21:20:19] <aelevadoan>	 i enabled them
[21:20:22] <DanielK_WMDE_>	 https://www.mediawiki.org/wiki/Manual:Image_administration
[21:20:47] <DanielK_WMDE_>	 !wg UploadPath
[21:20:47] <wm-bot>	 https://www.mediawiki.org/wiki/Manual:%24wgUploadPath
[21:21:04] <DanielK_WMDE_>	 !wg UploadDirectory | aelevadoan
[21:21:05] <wm-bot>	 aelevadoan: https://www.mediawiki.org/wiki/Manual:%24wgUploadDirectory
[21:22:52] <DanielK_WMDE_>	 aelevadoan: oh, another magic hint many people miss: your "dispatcher" switch should switch based on the requested server *or* MW_DB, if it is defined. 
[21:23:09] <DanielK_WMDE_>	 MW_DB is set when maintenance scripts are called with the --wiki XYZ parameter
[21:23:24] <DanielK_WMDE_>	 that's how you pick the right wiki from the command line, if your dispatcher is smart.
[21:23:41] <DanielK_WMDE_>	 hm... i'll put something into the etherpad
[21:39:16] <aelevadoan>	 DanielK_WMDE_: i asked you two things in the pad
[21:39:39] <DanielK_WMDE_>	 aelevadoan: that etherpad is strating to look good - once you get it working, would you put it on the help page? or replace the help page :)
[21:39:50] <aelevadoan>	 DanielK_WMDE_: of course
[21:40:06] <aelevadoan>	 DanielK_WMDE_: i have written done things that we talked about yesterday aswell
[21:41:23] <DanielK_WMDE_>	 aelevadoan: what do you not understand about  $conf = __DIR__ . '/../' . MW_DB . '/LocalSettings.php';
[21:41:24] <DanielK_WMDE_>	 ?
[21:41:42] <aelevadoan>	 is this correct?
[21:41:44] <aelevadoan>	  case ""wiki2.nad-ege.net":                        define( 'MW_DB', 'wiki2' ); 
[21:42:06] <DanielK_WMDE_>	 it'S valid, i don't know if it is correct :)
[21:42:24] <aelevadoan>	 i get confused in where i should replace a value or not
[21:42:48] <aelevadoan>	  $conf = __DIR__ . '/../' . MW_DB . '/LocalSettings.php';
[21:42:52] <aelevadoan>	 in this section
[21:42:56] <aelevadoan>	 do i have to put something?
[21:43:28] <DanielK_WMDE_>	 no. MW_DB is defined by us, __DIR__ is magic provided by PHP.
[21:43:30] <DanielK_WMDE_>	 so, __DIR__ would be /var/www/mediawiki_farm/w, and MW_DB would be wiki1. That would make $conf = "/var/www/mediawiki_farm/w/../wiki1/LocalSettings.php"
[21:43:33] <DanielK_WMDE_>	 magic!
[21:44:01] <aelevadoan>	 so i dont have to replace any value in the dispatcher?
[21:44:09] <aelevadoan>	 except the case values?
[21:44:33] <DanielK_WMDE_>	 indeed
[21:44:51] <DanielK_WMDE_>	 i like to write my config files with as little hardcoded absolute pathes as possible
[21:45:00] <DanielK_WMDE_>	 makes it a lot easier to move them around or re-use them
[21:45:46] <DanielK_WMDE_>	 if i'm not mistaking, you could take that file and put it anywhere, and it would work, provided the other directories are in the correct place *realtive* to the primary LocalSettings.php
[21:46:24] <aelevadoan>	 so should i leave case "wiki1.nad-ege.net":                        define( 'MW_DB', 'foo' ); 
[21:46:35] <aelevadoan>	 or put case ""wiki1.nad-ege.net":                        define( 'MW_DB', 'wiki1' ); 
[21:46:36] <aelevadoan>	 ?
[21:47:07] <DanielK_WMDE_>	 "foo" and "bar" are to be replaced
[21:47:28] <DanielK_WMDE_>	 oh, and the exaple pathes use "barwiki", not "bar". will fix that
[21:48:17] <DanielK_WMDE_>	 hm, or... well... attaching "wiki" to the actual name is good tradition. maybe we should stick to it. the switch statement can do that.
[21:48:42] <DanielK_WMDE_>	 but "wiki1wiki" seems silly.
[21:48:59] <DanielK_WMDE_>	 aelevadoan: do you really want "wiki1" and "wiki2"? foo and bar are better metasyntactic variables :)
[21:49:00] <DanielK_WMDE_>	 !foo
[21:49:00] <wm-bot>	 For changing the page footer, see the FAQ (!) <http://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_change_the_footer.3F>. More information at http://www.mediawiki.org/wiki/Footer and http://www.mediawiki.org/wiki/Manual:Skinning#Footer
[21:49:08] <DanielK_WMDE_>	 o_O
[21:49:13] <DanielK_WMDE_>	 silly bot
[21:49:23] <aelevadoan>	 oh, ok, i didnt know that
[21:49:27] <DanielK_WMDE_>	 https://en.wikipedia.org/wiki/Foobar
[21:52:54] <DanielK_WMDE_>	 aelevadoan: one difficulty is actually running the installer for each. the web installer will only run if you remove (move, rename) the main LocalSettings.php
[21:53:19] <aelevadoan>	 i already ran the LocalSettings twice
[21:53:26] <DanielK_WMDE_>	 I tend to just make a database dump of an empty wiki and copy that around. you also copy & modify the settings. no need to run the installer then
[21:53:49] <DanielK_WMDE_>	 aelevadoan: yea, but after you have this set up, it's a bit tricky the third time. doable, though
[21:53:59] <aelevadoan>	 and saved in /var/www/wiki1
[21:54:03] <aelevadoan>	 /var/www/wiki2
[21:54:06] <aelevadoan>	 hmm
[21:54:13] <DanielK_WMDE_>	 i recommend having a mysql dump of an empty wiki, import it as needed, and run update.php --wiki foo 
[21:54:16] <aelevadoan>	 i could copy paste the LocalSettings file and replace the values
[21:54:24] <DanielK_WMDE_>	 yep
[21:54:33] <aelevadoan>	 do i need to do more than that?
[21:54:38] <DanielK_WMDE_>	 there isn't that much that actually should be in the wiki-specific files
[21:54:49] <DanielK_WMDE_>	 to install a wiki?
[21:54:52] <aelevadoan>	 yes
[21:55:03] <DanielK_WMDE_>	 you need to have the pathes in place, the database with all the tables, and a config file.
[21:55:04] <aelevadoan>	 in the installation, is anything written to my mysql tables?
[21:55:21] <DanielK_WMDE_>	 if you import or copy a database, run update.php with the right --wiki param, to make sure the db structure is up to date
[21:55:23] <DanielK_WMDE_>	 that's it
[21:55:40] <aelevadoan>	 ok
[21:55:44] <aelevadoan>	 but before that
[21:55:55] <DanielK_WMDE_>	 aelevadoan: yes, a few things are written to the tables. so just keep a dump of a freshly installed wiki around.
[21:56:07] <DanielK_WMDE_>	 before what?
[21:56:11] <aelevadoan>	 how does foo know how to go to wiki.nad-ege.net
[21:56:13] <aelevadoan>	 ?
[21:56:59] <DanielK_WMDE_>	 what do you mean by "go to"?
[21:57:38] <aelevadoan>	 case "foo.nad-ege.net":
[21:58:19] <aelevadoan>	 well, perhaps i will read more before
[21:58:31] <aelevadoan>	 where does the dispatcher go in the localsettings?
[21:58:37] <aelevadoan>	 before the rest of the settings?
[21:58:46] <DanielK_WMDE_>	 yes
[21:59:19] <aelevadoan>	 before if ( !defined( 'MEDIAWIKI' ) ) { ?
[21:59:41] <DanielK_WMDE_>	 aelevadoan: "foo.nad-ege.net" is a placeholder for "yourstuff.nad-ege.net". it could be "wiki.nad-ege.net", but that seems silly. you don't call your car "car" or your kid "kid", right?
[21:59:58] <Rug>	 I am really confused and I hope somebody can help.  I am trying to create a simple wiki for internal use by my company.  It is divided into 2 'projects' or areas.  (1) sales-wiki (2) service-wiki  It will have 10-20 people assigned to each group/area.  On the main page I have created those 2 pages.  I have created 2 groups. I don't want 'Service' users being able to read 'sales' pages and vice-versa.
[22:00:11] <DanielK_WMDE_>	 if there is more than one wiki, give them better names. also, when following the convention of attaching "wiki" to the name, "wikiwiki" is kind of silly
[22:00:34] * DanielK_WMDE_ notes that the internal MW_DB for wikidata.org is wikidatawiki.
[22:01:18] <aelevadoan>	 DanielK_WMDE_: im trying it out, afterwards I will change the names
[22:01:19] <Rug>	 how about sales-team & service-team?
[22:01:54] <DanielK_WMDE_>	 Rug: the easiest way is to use two wikis. the nicer way is to use lockdown. be advised that mediawiki is not designed for air tight secrecy. it's leaky.
[22:02:03] <DanielK_WMDE_>	 !access | Rug
[22:02:03] <wm-bot>	 Rug: For information on customizing user access, see <http://www.mediawiki.org/wiki/Manual:User_rights>. For common examples of restricting access using both rights and extensions, see <http://www.mediawiki.org/wiki/Manual:Preventing_access>.
[22:02:21] <DanielK_WMDE_>	 !lockdown | Rug
[22:02:22] <wm-bot>	 Rug: Lockdown is an extension for preventing read or write access by namespace and limiting access to special pages, see < http://mediawiki.org/wiki/Extension:Lockdown >. For per-page access protection, see !ppp. For general information on preventing access to your wiki, see !access.
[22:02:52] <Rug>	 2 wiki's?    as in 2 different servers? 
[22:02:56] <DanielK_WMDE_>	 aelevadoan: i'm just saying that using "wiki" as your example is going to be confusing :)
[22:03:12] <DanielK_WMDE_>	 Rug: could be the same codebase, ask aelevadoan how to do that :D
[22:03:24] <DanielK_WMDE_>	 (one install, two sites)
[22:03:37] <Vicyorus>	 Hello
[22:03:51] <Rug>	 alright I'll give that a try.  thanks.
[22:03:54] <DanielK_WMDE_>	 Rug: naw, go with Lockdown. IF you need things to be super secret, don't use mediawiki.
[22:04:05] <Vicyorus>	 I want to know: is it possible, using the API, to search for text inside pages
[22:04:34] <DanielK_WMDE_>	 Vicyorus: yes, but the default search sucks, and the good search (Cirrus) is rather complex to set up.
[22:04:40] <DanielK_WMDE_>	 !search
[22:04:40] <wm-bot>	 http://www.mediawiki.org/wiki/Special:Search/?go=Go
[22:04:47] <DanielK_WMDE_>	 hrmf, not what i wanted
[22:04:54] * DanielK_WMDE_ is doing the 1 guy help desk today
[22:05:05] * DanielK_WMDE_ found a new way to procrastinate
[22:05:14] <Vicyorus>	 But that's not the API, or is it?
[22:05:31] <Rug>	 Thanks for the suggestions.
[22:06:23] <DanielK_WMDE_>	 Vicyorus: the API will use whatever search backend you configure
[22:06:29] <aelevadoan>	 DanielK_WMDE_: so now I can create a general LocalSetttings.php with what we put in the pad?
[22:07:08] <DanielK_WMDE_>	 Vicyorus: https://en.wikipedia.org/w/api.php?action=help&modules=opensearch
[22:07:26] <DanielK_WMDE_>	 aelevadoan: should work. didn't test, there may be typos.
[22:08:16] <DanielK_WMDE_>	 Vicyorus: https://en.wikipedia.org/w/api.php?action=help&modules=query%2Bsearch
[22:09:08] <DanielK_WMDE_>	 ok, will mind my own business for a while now
[22:09:17] <DanielK_WMDE_>	 will probably be hanging out here tomorrow too
[22:09:30] * DanielK_WMDE_ should get a different nick for help desk mode
[22:11:11] <Vicyorus>	 God damn you, Wikia...
[22:11:33] * Vicyorus grumbles
[22:11:37] <aelevadoan>	 DuesenFaq: thanks
[22:11:53] <Vicyorus>	 DuesenFaq: Well, thanks for the help.
[22:12:55] <DuesenFaq>	 aelevadoan: good luck!
[22:13:08] <DuesenFaq>	 i may look back on this channel in an hour or two. or maybe not :)
[22:13:54] <aelevadoan>	 DuesenFaq: $wgScriptPath = '/w/';'  --- i have to change this variable in the sub LocalSettings?
[22:14:09] <DuesenFaq>	 no.
[22:14:16] <DuesenFaq>	 the path is always /w/, for all domains
[22:14:43] <aelevadoan>	 I dont have to change that manually?
[22:14:55] <DuesenFaq>	 uh, no?
[22:15:02] <DuesenFaq>	 that'S what the dir is called, right?...
[22:15:51] <DuesenFaq>	 you are calling the same index.php on the same path using different subdomains.
[22:15:56] <aelevadoan>	 yes, but i changed the code to w after doing the installations of the seperate wikis , i mean
[22:16:00] <DuesenFaq>	 the subdomains cause different databases to be used
[22:16:00] <DuesenFaq>	 that's it
[22:16:24] <DuesenFaq>	 wgScriptPath has to match the actual path
[22:16:33] <DuesenFaq>	 that's it. if you move the files, change wgScriptPath
[22:17:00] <DuesenFaq>	 mediawiki writes no pathes to the database. nor domains. you can move wikis around freely, by just changing the config
[22:18:26] <aelevadoan>	 thanks DuesenFaq
[22:21:45] <aelevadoan>	 DuesenFaq: you commented that the $wgServer value  MUST be the domain that corresponds to this config file
[22:21:52] <aelevadoan>	 which config file?
[22:27:04] <DuesenFaq>	 aelevadoan: the one that $wgServer is set in. each sub-localsettings file should have this, and set it to the domain that uses that config.
[22:28:37] <aelevadoan>	 but in each sub LocalSettings its a different value, right?
[22:28:38] <aelevadoan>	 ## The protocol and server name to use in fully-qualified URLs
[22:28:38] <aelevadoan>	 $wgServer = "http://wiki1.nad-ege.net";
[22:35:42] <aelevadoan>	 DuesenFaq: should wgServer be defined in the general LocalSettings and not in the subLocalSettings?
[22:46:33] <aelevadoan>	 DuesenFaq: when I searched wiki1.nad-ege.net on my browser I got an index of /var/www/mediawiki_farm
[22:46:42] <aelevadoan>	 with "w" directory listed
[22:47:01] <DuesenFaq>	 yes. there is nothing there to tell the web server what to do
[22:47:20] <DuesenFaq>	 if you go to wiki1.nad-ege.net/w/, you should see the wiki
[22:47:59] <DuesenFaq>	 for the root directory, you can set up a rewrite rule that would trigger a redirect
[22:48:07] <DuesenFaq>	 !prettyurls
[22:48:07] <wm-bot>	 To create simple URLs (such as the /wiki/PAGENAME style URLs on Wikimedia sites), follow the instructions at <http://www.mediawiki.org/wiki/Manual:Short_URL> or try the new beta tool at <http://shorturls.redwerks.org/>. There are instructions for most different webserver setups. If you have problems getting the rewrite rules to work, see !rewriteproblem
[22:48:15] <aelevadoan>	 http://wiki2.nad-ege.net/w/
[22:48:28] <aelevadoan>	 something is failing
[22:48:37] <DuesenFaq>	 yes.
[22:48:40] <DuesenFaq>	 !filepermissions
[22:48:40] <wm-bot>	 http://www.mediawiki.org/wiki/Manual:Configuring_file_uploads#Check_directory_security
[22:48:47] <DuesenFaq>	 hm, no not for uploads
[22:48:54] <DuesenFaq>	 but things must be readable
[22:48:59] <DuesenFaq>	 aelevadoan: check the apache error log
[22:49:02] <DuesenFaq>	 !debug
[22:49:02] <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
[22:49:59] <DuesenFaq>	 aelevadoan: maybe a syntax error in a config file. try php -l LocalSettings.php 
[22:50:55] <aelevadoan>	 [Fri Jan 09 17:49:44.129824 2015] [:error] [pid 23701] [client 189.162.236.95:60755] PHP Parse error:  syntax error, unexpected '' );' (T_CONSTANT_ENCAPSED_STRING) in /var/www/mediawiki_farm/w/LocalSettings.php on line 32
[23:01:27] <DuesenFaq>	 aelevadoan: can you fix it?
[23:01:34] <aelevadoan>	 DuesenFaq:  define( 'MW_DB', 'barwiki'' );
[23:01:37] <aelevadoan>	 thats the line
[23:01:47] <DuesenFaq>	 the last ' shouldn't be there
[23:02:20] <aelevadoan>	 foowiki has two
[23:02:21] <aelevadoan>	 define( 'MW_DB', 'foowiki'' );
[23:02:32] <DuesenFaq>	 yea, also a mistake
[23:11:25] <aelevadoan>	 DanielK_WMDE: my internet connection failed
[23:14:43] <willwh>	 hi folks :)
[23:14:49] <willwh>	 having trouble getting an iframe widget working
[23:14:55] <willwh>	 anyone have any experience there?
[23:15:00] <willwh>	 Can I pick your braiiiiiiiiiiiin?
[23:21:42] <willwh>	 !iframe
[23:21:42] <wm-bot>	 To embed iframes on wiki pages, you can use <http://www.mediawiki.org/wiki/Extension:Website_in_iFrame>. Alternatively, see !html for information on using full HTML on your wiki pages.
[23:21:50] <willwh>	 !html
[23:21:50] <wm-bot>	 For allowing any and all HTML, see <http://www.mediawiki.org/wiki/Manual:%24wgRawHtml>. This is of course VERY DANGEROUS. Safer options include <http://www.mediawiki.org/wiki/Extension:HTMLets>, <http://www.mediawiki.org/wiki/Extension:RawMsg> and <http://www.mediawiki.org/wiki/Extension:SecureHTML>.
[23:24:47] <DanielK_WMDE>	 aelevadoan: getting the syntax fixed? i figured out how to set the etherpad to a monospaced font, so this kind of error is easier to spot :)
[23:25:13] <aelevadoan>	 $wgGroupPermissions['*']['edit'] = false;
[23:25:27] <aelevadoan>	 Fri Jan 09 18:24:53.660987 2015] [:error] [pid 24288] [client 91.39.26.138:46018] PHP Parse error:  syntax error, unexpected 'edit' (T_STRING) in /var/www/mediawiki_farm/w/LocalSettings.php on line 93
[23:26:09] <DanielK_WMDE>	 aelevadoan: that line looks fine, sure you are looking at the right file / line?
[23:26:18] <aelevadoan>	 yes
[23:26:22] <DanielK_WMDE>	 also, do use php -l for checking files, much quicker
[23:26:51] <DanielK_WMDE>	 actually, you could have an unmatched ' or " in a line before that somewhere
[23:27:02] <DanielK_WMDE>	 use an editor with syntax highlighting, then it's easy to spot
[23:27:31] <aelevadoan>	 which editor do you recommend?
[23:27:51] <willwh>	 phpstorm :)
[23:28:00] <aelevadoan>	 i can install that on my vps?
[23:28:28] <DanielK_WMDE>	 if you need a command line editor on the server, use vim
[23:28:49] <DanielK_WMDE>	 vim is powerul, and some people swear by it. i can use roughly 1% of it's features and prefer a proper ide locally
[23:29:16] <DanielK_WMDE>	 but it's very good to have vim on the server, and learn how to use it. it has syntax highlighting and a lot more features
[23:29:19] <willwh>	 vim is awesome, but you need to practice with it (I do tons of work from the console)
[23:29:26] <DanielK_WMDE>	 but it's quite different from other editors.
[23:29:33] <willwh>	 but when you're trying to track something nasty down, nothing better than a GUI IDE tbh :p
[23:29:42] <willwh>	 now guys
[23:29:45] <willwh>	 anyone of using Widgets?
[23:29:52] <willwh>	 this iframe:widget will just not play ball
[23:29:56] <willwh>	 I turned on debug and got nada
[23:29:59] <DanielK_WMDE>	 willwh: nope, but i write HTMLets :P
[23:30:19] <willwh>	 Widget:Iframe is in the Widgets namesapce in Special:AllPages
[23:30:23] <willwh>	 I just asdhfasgasdfagsfgfasdd
[23:30:36] <willwh>	 I'm a pretty seasoned sysadmin, and should be able to figure this out :X
[23:30:42] <DanielK_WMDE>	 and: i agree wrt the ide. a proper source code debugger and point-and-click to go to class and function definitions is and absolute must for serious development
[23:30:44] <willwh>	 but there is no info to go on really
[23:31:12] <DanielK_WMDE>	 willwh: well, what do you want to achieve, what have you tried, and what happened?
[23:31:15] <willwh>	 "Error in widget IFrame" ;x
[23:31:20] <aelevadoan>	 # The following permissions were set based on your choice in the installer
[23:31:21] <aelevadoan>	 $wgGroupPermissions['*']['edit'] = false;
[23:31:26] <aelevadoan>	 what does that mean anyway?
[23:31:43] <willwh>	 don't give every group edit permissions
[23:31:48] <willwh>	 I'd guess
[23:31:54] <DanielK_WMDE>	 aelevadoan: it means that visitors are not allowed to edit unless logged in.
[23:32:01] <aelevadoan>	 oh, ok
[23:32:04] <willwh>	 DanielK_WMDE: followed this: http://www.mediawiki.org/wiki/Extension:Widgets#Installing
[23:32:10] <DanielK_WMDE>	 aelevadoan: if logged in, $wgGroupPermissions['user']['edit'] applies
[23:32:28] <willwh>	 chgrp www-data compiled_templates && chmod g+aw
[23:32:28] <aelevadoan>	 is that value correct?
[23:32:36] <willwh>	 and created the widget
[23:32:39] <DanielK_WMDE>	 aelevadoan: yes
[23:32:44] <willwh>	 I'll try adding a different widget and see if it works
[23:32:49] <aelevadoan>	 I dont know why it gives error then :(
[23:32:59] <DanielK_WMDE>	 willwh: i have no idea how Widgets works. do you *need* widgets?
[23:33:07] <willwh>	 I guess not
[23:33:11] <willwh>	 I do need iframes :P
[23:33:58] <DanielK_WMDE>	 willwh: well, you found the bot already, it told you some easy ways to get them
[23:34:11] <DanielK_WMDE>	 willwh: do you want your users to be able to control what goes into the iframe?
[23:34:30] <aelevadoan>	 DanielK_WMDE: by the way, when I do php -l LocalSettings.php I get a Could not open input file: LocalSettings.php
[23:34:33] <willwh>	 DanielK_WMDE: context: it's a wiki for a company for public facing troubleshooting docs basically
[23:34:34] <DanielK_WMDE>	 or is it a one-off thing, somethign specific you need in an iframe, that nobody should really touch?
[23:34:42] <willwh>	 will be edited by a few trusted company users
[23:34:50] <DanielK_WMDE>	 aelevadoan: then you are in the wrong directory
[23:35:05] <aelevadoan>	 I have to be in the specific directory where the LocalSettings file is?
[23:35:12] <DanielK_WMDE>	 aelevadoan: provide the path to the file, wherever it may be relative to your current working directory
[23:35:13] <willwh>	 aelevadoan: php -l /path/to/LocalSettings.php
[23:35:40] <DanielK_WMDE>	 aelevadoan: that's how parameters for command line tools generally work, yea
[23:35:58] <aelevadoan>	 ok
[23:36:13] <willwh>	 !html
[23:36:13] <wm-bot>	 For allowing any and all HTML, see <http://www.mediawiki.org/wiki/Manual:%24wgRawHtml>. This is of course VERY DANGEROUS. Safer options include <http://www.mediawiki.org/wiki/Extension:HTMLets>, <http://www.mediawiki.org/wiki/Extension:RawMsg> and <http://www.mediawiki.org/wiki/Extension:SecureHTML>.
[23:36:15] <DanielK_WMDE>	 either give the path, or change to the respective directory and use the name
[23:36:24] <aelevadoan>	 so im getting the same syntax error in line 93
[23:36:25] <aelevadoan>	 :s
[23:36:38] <DanielK_WMDE>	 so fix the syntax :)
[23:37:48] <aelevadoan>	 DanielK_WMDE: what does the red text in vim mean?
[23:38:01] <DanielK_WMDE>	 that depends on a lot of things :)
[23:38:24] <willwh>	 aelevadoan: usually unclosed tags
[23:38:30] <willwh>	 if you have :syntax on
[23:38:31] <DanielK_WMDE>	 type i to get into edit ("insert") mode. hit esc to get out again. type :q to quit when not in edit mode
[23:38:47] <DanielK_WMDE>	 aelevadoan: look where the red starts, it's probably where the error is
[23:38:57] <willwh>	 in regular mode, you can just type 93 shift+g
[23:39:00] <willwh>	 takes you to line 93 :P
[23:39:09] <aelevadoan>	 $wgScriptPath = '/w/';'
[23:39:09] <aelevadoan>	 $wgScriptExtension = ".php";
[23:39:10] <willwh>	 it's like "line number -> GO"
[23:39:12] <DanielK_WMDE>	 ...use :w to save, :qw to quit and save, :q! to quit without saving
[23:39:15] <willwh>	 or that's how I remmeber it anyway
[23:39:20] <aelevadoan>	 in $wgScriptExtension = ".php"; the red starts
[23:39:57] <DanielK_WMDE>	 aelevadoan: i'm flying blind, poaste the file (and x passwords)
[23:40:14] <DanielK_WMDE>	 aelevadoan: http://pastebin.com/
[23:40:16] <aelevadoan>	 is there an easy way of exporting the file?
[23:40:39] <DanielK_WMDE>	 aelevadoan: well, if you add .txt to the file name, i can just read it from your web server as a plain text file :)
[23:40:48] <DanielK_WMDE>	 but then, anyone can. with all the passwords
[23:40:49] <aelevadoan>	 ok
[23:41:14] <willwh>	 cp LocalSettings.php debug.txt :p
[23:41:28] <willwh>	 but yank your db passwords
[23:41:33] <aelevadoan>	 ok
[23:42:59] <aelevadoan>	 DanielK_WMDE: willwh: http://wiki1.nad-ege.net/w/debug.txt
[23:43:48] <willwh>	 $wgScriptPath = '/w/';'
[23:43:51] <willwh>	 that's your prob
[23:44:17] <willwh>	 line 56 of that txt file
[23:44:19] <DanielK_WMDE>	 oh, nice - pastebinit
[23:44:39] <DanielK_WMDE>	 https://help.ubuntu.com/community/Pastebinit
[23:44:42] <willwh>	 DanielK_WMDE: it rocks, but tons of people scrape it now all the time
[23:44:46] <willwh>	 looking for passwords
[23:44:49] <willwh>	 so be really careful
[23:44:50] <willwh>	 ;]
[23:44:57] <willwh>	 it's like the github changes feed
[23:45:04] <DanielK_WMDE>	 willwh: sure, but the tool allso supports other sites, not just pastebin
[23:45:05] <willwh>	 people scraping that hoping for gold too
[23:45:20] <willwh>	 aelevadoan: that is your problem though
[23:45:45] <willwh>	 change: $wgScriptPath = '/w';' to just: $wgScriptPath = '/w';
[23:45:54] <willwh>	 i.e. remove the offending '
[23:46:12] <willwh>	 which is exactly what DanielK_WMDE said (you are probably missing a closing tag or something on a previous line) ;)
[23:47:52] <aelevadoan>	 willwh: thanks!
[23:48:08] <willwh>	 aelevadoan: all working now?
[23:48:09] <aelevadoan>	 now php -l LocalSettings says no syntax errors
[23:48:12] <aelevadoan>	 but still not working
[23:48:13] <aelevadoan>	 :b
[23:48:22] <aelevadoan>	 im going to check the apache error log
[23:48:34] <willwh>	 tail -f /var/log/apache2/error.log 
[23:48:35] <willwh>	 :P
[23:48:38] <willwh>	 I <3 tail -f
[23:49:18] <DanielK_WMDE>	 willwh: and screen
[23:49:22] <aelevadoan>	 im getting a syntax error here
[23:49:22] <aelevadoan>	  $conf = __DIR__ . '/../' . MW_DB . '/LocalSettings.php';
[23:49:29] <willwh>	 DanielK_WMDE: tmux nowadays for me
[23:49:30] <willwh>	 :p
[23:49:37] <DanielK_WMDE>	 willwh: yes, so i hear.
[23:49:47] <DanielK_WMDE>	 willwh: btw... love perl? hate perl? watch this https://www.youtube.com/watch?v=gweDBQ-9LuQ
[23:49:56] <willwh>	 I am indifferent to perl
[23:50:23] <DanielK_WMDE>	 you may still have fun watching it. or be scared, if you run anything on the web which uses perl
[23:50:59] <willwh>	 I run irssi, which is the only thing that is close to perly (scripts are in perl)
[23:51:26] <aelevadoan>	 sorry, I mean syntax error in this line
[23:51:26] <aelevadoan>	  require_once( $conf );
[23:52:37] <DanielK_WMDE>	 aelevadoan: both lines seem fine, and both pass if i check the file you published
[23:52:49] <aelevadoan>	 well, i get an error there
[23:53:27] <aelevadoan>	 oh wait
[23:53:39] <aelevadoan>	 '/var/www/mediawiki_farm/w/../none/LocalSettings.php
[23:53:45] <aelevadoan>	 thats another LocalSettings file
[23:53:53] <DanielK_WMDE>	 one that doesn't exist
[23:53:56] <DanielK_WMDE>	 so you get an error there
[23:54:01] <DanielK_WMDE>	 not a syntax error though
[23:54:17] <DanielK_WMDE>	 see the comment that sais "this will fail hard for the none cayse"?
[23:54:23] <DanielK_WMDE>	 that's what you are seeing now.
[23:54:32] <aelevadoan>	 ok
[23:54:40] <aelevadoan>	 so this mean its not finding the cases
[23:54:40] <DanielK_WMDE>	 you have accessed the config with a domain that isn't handled
[23:54:41] <aelevadoan>	 right?
[23:54:46] <DanielK_WMDE>	 yes
[23:54:59] <aelevadoan>	 and why could that be?
[23:56:00] <DanielK_WMDE>	 you have configured "foo.nad-ege.net" and "bar.nad-ege.net", and are now accessing it via "wiki.nad-ege.net", perhaps?
[23:56:11] <DanielK_WMDE>	 i chose foo and bar because the are obviopus exaples
[23:56:24] <DanielK_WMDE>	 if your setup is different, you need to change them.
[23:56:33] <aelevadoan>	 i have wiki1 and wiki2
[23:56:42] <DanielK_WMDE>	 so change them to wiki1 and wiki2.
[23:57:10] <DanielK_WMDE>	 MW_DB should be set to the name of the respective directories.
[23:58:06] <aelevadoan>	 oh
[23:58:27] <DanielK_WMDE>	 the switch thing maps domaisn to directories. that's all.
[23:58:28] <aelevadoan>	 the whole path?
[23:58:33] <DanielK_WMDE>	 no. just the name
[23:58:48] <DanielK_WMDE>	 we build the path from that, in the line with $conf = ....
[23:59:05] <DanielK_WMDE>	 aelevadoan: you havn't done any programmign before, have you?...
[23:59:25] <aelevadoan>	 DanielK_WMDE: no