[03:16:08] _(:3_|<)_ [04:36:42] hi [04:36:55] I have a mediawiki installation but the multiple image template does not work [04:37:13] instead, if I try to use it, I get a red link. is there a way for me to enable it? [04:41:59] ente: Did you import the template? [04:42:31] no, I don't know where I get it from either [04:42:35] sorry, I'm very new to this [04:43:37] ente: No problem! Are you talking about https://www.mediawiki.org/wiki/Template:Multiple_image/doc this one? [04:44:55] yeah [04:46:57] ente: So you go to https://www.mediawiki.org/wiki/Special:Export [04:47:36] ente: And in the Add pages manually box, add the template name with prefix. "Template:Multiple image" in this case. [04:47:55] ente: And check "Include templates" which would include other templates this one depends on. [04:48:16] This would give you a .xml file. [04:48:20] got it [04:48:22] but that's sadly not very self-explainatory :( [04:48:27] Then you go to your MediaWiki install and go to Special:Import and upload the file. [04:48:48] ente: https://www.mediawiki.org/wiki/Help:Templates#Copying_from_one_wiki_to_another [04:49:08] alright [04:49:11] thanks a lot! [04:49:20] You're welcome. [04:49:56] hmm [04:50:01] it says import failed [04:50:35] ente: Do you have the required permissions? [04:50:45] the xml data looks like I exported it wrong [04:52:07] ah, looks like it's case sensitive [04:52:29] It's Template:Multiple image, not Template:Multiple Image [04:52:39] ente: Mentioned in the docs. :) [04:52:46] You'll be surprised how many people don't bother reading those. [04:53:09] just because something is documented doesn't mean it's intuitive ;) [04:53:22] and mind you, reading all the docs for everything is a lot of reading [04:53:50] okay, now I get this: No handler for model 'Scribunto' registered in $wgContentHandlers [04:53:56] I give up for tonight :) [04:54:20] do you know about the wikimedia hackathon next year in vienna? [04:55:00] ente: Not much. Why? [04:55:28] I'm involved with the local hackspace (metalab) and a friend of mine proposed that we do something together [04:55:50] so now I'm wondering that in the hypothetical scenario that I get to organise something, who I should poke about it :) [04:56:04] ente: Nice. It'd be great to have you there. [04:56:11] ente: Are you in Vienna? [04:56:53] yeah [04:57:46] ente: You should write an email to Rachel (rfarrand@wikimedia.org) [04:57:56] alright! [04:58:06] She's the overall organizer and will likely be able to put you in touch with local organizers. [04:58:27] ente: Thanks for volunteering! :) [04:58:51] sure thing :) [05:01:16] ente: For your new problem, you need to install https://www.mediawiki.org/wiki/Extension:Scribunto [05:01:28] Should be straightforward if you follow the directions on the page. [05:02:04] sounds like I need access to the machine where the wiki is running? [05:02:16] I'll try to poke the right people, thanks :) [05:02:41] Yep. [08:32:36] hello. i have a login issue. it keeps telling me too many recent login attempts but only from this machine. when i use a different machine i can log in fine [08:32:39] any tips? [09:49:40] Rein|VPS: Try another browser? [09:49:58] oh i got that sorted [09:50:04] but i have another issue :D [09:50:07] Good. [09:50:10] Which one? [09:50:34] Rein|VPS: What was the problem there? Caching issues? [09:50:57] i get this error when i try to confirm an account: Could not create directory ‘mwstore://accountcreds-backend/accountcreds-public/m/my/my_’. [09:52:13] Rein|VPS: Is this your own mediawiki install? [09:52:25] yes [09:53:31] Rein|VPS: Hmm. I'm not sure. Let's look it up. [09:53:43] i tried, couldnt find anything really [09:53:51] however, i think it might be a permissions issue somewhere [09:54:23] Rein|VPS: https://www.mediawiki.org/wiki/Topic:Qu6b34epvjzypniy [09:54:57] you have better search skills than me Niharika :D [09:55:22] :P [09:56:08] oh this is similar to what i found actually [09:56:11] its about image uploads [09:56:40] Rein|VPS: Yeah, it should be similar to your issue but I'm looking for that one. [09:57:27] I found https://www.mediawiki.org/wiki/Topic:Sf6zgc7plebtit4v [09:58:14] And http://stackoverflow.com/questions/34077569/mediawiki-can-not-get-confirmaccount-extension-to-work perhaps more useful. [10:00:25] Rein|VPS: And you might want to re-read https://www.mediawiki.org/wiki/Extension:ConfirmAccount#Installation [10:03:29] yeah i read it a bunch :P [10:03:33] thanks Niharika, i will work on it [10:03:53] Good luck! [10:09:05] the stackoverflow link is the one but there are a few lines that look like the one shown [10:09:09] do i change them all? [10:09:39] Rein|VPS: Which line, specifically? [10:10:35] $wgFileStore['accountreqs']['directory'] : $wgUploadDirectory . "/accountreqs", [10:12:39] Rein|VPS: Wait, you're talking about the step for adding {$IP}? [10:14:35] yes [10:16:01] Is it safe to install the 1.27 rc in productive enviroment [10:17:47] theGamer93: It's generally reccommended not to run non stable versions in production, unless you know what you are doing [10:18:23] Ok. We plan to maintenance our server, but we wait for 1.27 release. Is there a releasedate? [10:18:55] It should be this month [10:19:21] https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-June/000189.html [10:19:26] No specific date suggested [10:21:05] Okay. But in general 1.27 RC should be what to expect as stable [10:21:19] I can upgrade von 1.27 RC to 1.27 Stable [10:25:16] Yes, you could [10:25:24] Usually, there won't be many changes more [10:25:44] Rein|VPS: I think you can skip that step. What is your $wgUploadDirectory set to? [10:26:06] good question [10:26:58] how would i find that info? [10:27:07] theGamer93: If you're going to do it, I think you'd want to not use the rc, use the git branch. There's been some fixes ontop [10:27:28] thanks for that! [10:27:50] https://github.com/wikimedia/mediawiki/commits/REL1_27 [10:29:16] Rein|VPS: It should be in your LocalSettings. [10:30:55] there's nothing like that in there and i dont recall ever reading that i needed to add it [10:36:01] Rein|VPS: Then skip that step for now. [10:41:35] there is no /accountcreds [10:41:44] i feel like this is the issue [11:04:56] nothing works Niharika [11:04:59] i think i give up [11:05:38] Rein|VPS: :( Don't give up. Try asking again in a few hours when more people are here. [11:07:51] i dont need a wiki it was just something to do [11:08:02] and now the frustration is more than the value of using it [11:08:08] better to quit before i stab someone [11:09:28] Rein|VPS: Why do you need the COnfirmAccount extension in the first place? [11:10:47] i dont [11:11:19] i had nothing in place for registration at all. when i went to the wikipage for adding users i saw the extension and thought it looked like a good idea [11:12:26] Okay. I have no more ideas here. Sorry. [11:14:52] no worries [11:14:54] thanks for the help [12:49:26] Niharika: wiping server and starting again :P [12:50:07] Rein|VPS: That's the spirit! :P [12:50:23] haha [12:50:39] tbh, something went slightly wrong in the first place, but it wasnt enough for me to start over [12:50:51] just made things slightly messy. now, easier to just start over [12:51:15] Rein|VPS: Ah! You should save your logs. That'd help figure out what went wrong and how to fix it. [12:51:28] Probably some script didn't run or something timed out. [12:51:41] hah should have but too late now :P [13:24:06] morning [14:12:39] new wiki setup Niharika [14:12:46] got distracted by real work :( [14:28:39] Rein|VPS: Any errors this time? [14:29:48] everything is "so far so good" [14:29:55] havent installed the extension though [14:30:54] what does the $IP thing mean Niharika ? [14:32:44] Rein|VPS: Install path. https://www.mediawiki.org/wiki/Manual:$IP You should not be needing it, as far as I understand. [14:32:59] Rein|VPS: You can let people register accounts without using ConfirmAccount. [14:35:15] i know Niharika [14:35:21] but i want to use ConfirmAccount [14:35:29] at this point, just to prove i can make it work :P [14:36:55] Rein|VPS: :P Alright. Good luck. [14:37:33] Rein|VPS: Don't forget to save logs. [14:39:45] haha exact same issue [14:39:46] :D [14:39:57] Rein|VPS: On which step? [14:43:24] confirming an account [14:43:51] Rein|VPS: Ah, okay, did you go through all of the Installation steps? [14:44:24] need to do this bit: Ensure the wiki has write permissions on $wgUploadDirectory [14:44:41] but i have nfi what the $wgUploadDirectory is so i cannot check tha [14:44:42] t [14:45:39] cd to mediawiki directory [14:45:45] php maintenance/eval.php [14:45:51] echo $wgUploadDirectory; [14:46:22] cool thanks [14:46:25] it is the default.. [14:47:22] https://www.mediawiki.org/wiki/Manual:$wgUploadDirectory [14:48:17] Does this channel include VisualEditor support? [14:48:39] this is the error btw Reedy: Could not create directory ‘mwstore://accountcreds-backend/accountcreds-public/m/my/my_’. [14:48:44] not sure if oyu have seen that before? [14:48:51] VisualLearner: #mediawiki-visualeditor [14:49:13] or anyone else that has clue on it [14:49:40] andre_: thanks! [14:49:49] It's an abstraction ting [14:50:09] ok [14:50:55] any other tips ? [14:51:24] Hi, I have questions about mediawikis security. We are using foswiki (not the recent version) at the moment. We need to make articles only readable for specific people and only fewer need to edit them. How is the security done? [14:51:45] Wikis are designed to be open [14:52:17] Rein|VPS: The usual answer is to make sure the images dir is owned/writeable by the user your webserver is running as [14:52:42] ok i will do so [14:52:50] Niharika: i think we were really close earlier :P [14:53:11] tuor: you could use https://www.mediawiki.org/wiki/Extension:Lockdown [14:53:14] Rein|VPS: Yeah. :( [14:53:21] But it's highly insecure [14:53:26] Reedy, yes. We want to use it as an documentation platform and not as a "normal" wiki. [14:53:32] hm...yeah has correct owner :/ [14:54:05] Agent, if it's not secure, I will not realy consider using it. [14:54:31] It's when you want it half open, half not that the problems start [14:54:45] If you want it fully open, great [14:54:46] tuor: I mean, it is secure but you never know if it'll leave you hanging as MediaWiki was not developed to be an isolated platform [14:54:53] I've used it and it works great [14:54:56] If you want only the front page to be open, and require login etc, that's pretty easily done [14:55:00] But I mean, you never know [14:55:01] But 50:50 gets icky [14:55:37] It even has an alert template on the page warning MediaWiki wasn't designed like that [14:55:42] Reedy: any other suggestions on my issue? [14:55:57] The wiki will only be accessible from our intern network and only with a personal login. Some parts have to be accesible for different people. [14:57:05] Rein|VPS: It's almost certainly a permissions problem [14:57:09] Agent, ok. What would you use for an semi closed site? (confluence is not realy an alternativ because of license pricing) [14:57:24] We are a little but growing company. [14:57:30] there is only 1 user other than root and that user has ownership of the $IP [14:57:44] I suggest creating a new wiki [14:57:51] Befor we get to big, we need a working documentation platform. [14:58:07] And granting permission to the users you want [14:58:20] Hmm ok. [14:58:44] That would be a solution. [14:59:04] You could share the database so that everyone could login with a single login but only a few users can read [14:59:40] OK. [15:01:34] Rein|VPS: Can you become that user and then try editing that directory? [15:02:48] i am that user [15:02:49] :D [15:02:57] i did the whole install as that user [15:03:51] Rein|VPS: And you are able to edit that directory? [15:04:32] yep [15:04:57] But the webserver won't be running as your user [15:05:11] you mean apache? [15:05:41] Rein|VPS: if Apache is the web server on your environment then yes [15:05:50] indeed [15:05:52] Apache is likely running under a different user or group setup [15:05:59] with a different system user/group that it uses [15:06:08] Apache needs to be able to have access to those files, not just your user and root. [15:06:30] got it [15:06:40] if you don't wish to have Apache be the owner of the files, then the group it runs as should be given read/write permissions just as your normal user would have [15:07:01] (via the 'group' permission set for the files) [15:07:21] (and change the 'group' on the files/directories to the group Apache runs as) [15:08:33] i am so close to success i can taste it! [15:08:58] i have done almost no actual work today but nm [15:13:52] oh dear [15:13:53] hahah [15:13:57] broke it [15:18:12] fixed it, but it wont let me make apache the owner [15:18:16] lemme try root i suppose [15:18:51] changed owner, still doenst work [15:20:48] any final ideas? [15:31:23] ls [15:41:23] do i need to update or clear a cache somewhere for the perms change to take affect? [15:47:59] any other debug suggestions on this issue? [15:48:06] any other places i can go for help? [15:50:50] just for clarification, i have made "apache" the owner of the entire wikimedia directory and all subdirectories [15:50:55] still not working [16:00:08] holy shit people i did it [16:00:12] Niharika: i did it! [16:03:48] Rein|VPS: Woooooot! [16:03:54] How?! [16:05:27] made apache owner of wiki dir and all inside it and then changed this line in ConfirmAccount.config.php: $wgFileStore['accountcreds']['directory'] : $wgUploadDirectory . "/accountcreds", [16:05:38] to: $wgFileStore['accountcreds']['directory'] : "{$IP}/images/accountcreds", [16:07:14] Rein|VPS: Oh. Good. Congratulations! You proved you can do it. :D [16:07:24] indeed [16:07:59] thanks for the help Niharika and you Reedy and teward [16:08:37] :) [16:11:54] :) [16:12:27] now i just need some content :P [16:33:00] Hello, does anyone use mediawiki on xaamp here? [16:33:09] if so, How do I display images on a localhost article and how do I add the infobox? 7 [16:38:15] no? [16:39:24] ok [16:39:26] ciao [17:40:54] Hi all, I'm having trouble with page titles with ampersands. Previously based on feedback I'd hacked a couple of mediawiki php files, but I'm trying to undo that and fix this issue properly, bypassing our load balancer that I think is interfering... [17:41:37] The problem is editing a page like /wiki/Foo&Bar, where it will come up as /wiki/Foo%26Bar but editing it brings it up as /index.php?title=Foo&Bar&action=edit [17:41:50] so now it thinks it's editing a non-existent page [17:42:25] and canceling the edit returns to /wiki/Foo since it truncates everything from the first ampersand on [17:42:49] so for some reason it's un-encoding the url when rewriting to the index.php url format [17:42:56] this is MW 1.26.2 fwiw [17:47:05] I had also edited the same mediawiki php files based on feedback to fix plus sign encoding issues, but ultimately i'm trying to revert all of that because MW should be able to handle all of that correctly on its own, and I'm pretty sure our issues derive from the Microsoft IIS ARR load balancer fronting the wikis doing some kind of incorrect rewriting [17:47:31] The edited files, btw, are includes/GlobalFunctions.php and resources/mediawiki/src/mediawiki.util.js [19:17:28] Rein|VPS: Ugh. Don't do that. Change it in LocalSettings.php [19:17:33] Don't change core files [19:56:23] Is there an existing phab task for "clicking watchlist star too fast, whilst page still loading, takes me to action=watch page" ? My search attempts are giving way too many old/irrelevant results. [19:56:40] spammer [20:12:37] Does anyone have advice on how I can protect part of an article from editing? [20:13:35] You can't [20:13:43] Unless you transclude it from another page/template [20:15:58] If I do that, can I hide the original source article from search engines, and from being found through navigating within the wiki? [20:17:42] I'm planning to have many bot-generated articles, and want user editable sections below the protected bot-generated top sections. [20:18:40] So if I transclude all of the protected bot-generated articles into unprotected user editable articles, then the users will still see both copies of each article, correct? [20:41:30] maybe you want some sort of extension [20:53:36] There is an extension that does what I need. https://www.mediawiki.org/wiki/Extension:ProtectSection [20:53:53] It hasn't been updated in years, and none of the authors seem to have accounts anymore. [20:55:16] I tried installing it, but it just kills the Wiki. (No surprise considering the age) I wouldn't know where to begin to get it working with current release. [20:55:49] Transclusion from a protected page is probably the best solution. [20:56:19] of course, people can always just remove the transclusion... [20:56:36] You could use a separate namespace for the pages you transclude from. That'd let you hide it from search engines easily. [20:56:49] Combined with an extension like Lockdown, it'd also let you hide it from regular users. [20:57:26] Though I don't think you'd really need that, as only the mainspace is searched unless the user specifically types in the namespace. [20:58:09] So just a separate namespace (you can even protect the whole namespace with standard wiki settings) and an edited robots.txt would do the trick. [20:58:24] Namespace protection: https://www.mediawiki.org/wiki/Manual:$wgNamespaceProtection [20:59:38] That sounds great to me. [20:59:42] Thank you! [20:59:52] No problem. [21:00:05] On my wikis, I use namespace protection to limit editing templates to autoconfirmed users. Works great. [21:02:23] I'll need to figure out how to get a bot to make both the protected page and the transclusion page at the same time, but that doesn't sound too difficult. [22:10:28] Reedy: good point on core files. now i have that solution i will revert the core file and change local