[02:55:16] Hello all, I am new to mediawiki and wiki's in general.. i am writing an article (basically this wiki is for docuemnting config files and setups on my various servers) - when i copy and paste some text for instance a linux config file, it obviously unformats the text.. removes line feeds etc.. how do i get it to keep the formatting when i copy the file over? [02:57:56] zoidberg-: Simplest solution is to wrap it in
 .... 
[02:58:08]
Your multiline example text here
[03:04:08] RoanKattouw: does't appear to work right like that :( [03:04:16] ? [03:04:19] Can you link to an example? [03:04:23] RoanKattouw: for instance, i have a large file i just want to copy and paste, using pre it messes up the formatting [03:04:26] sure [03:05:00] pm the link [03:05:08] thats the file i want to simply copy and paste in and keep it as is [03:05:11] formatting wise [03:06:11] No I mean, can you link me to a wiki page that you saved where it went wrong [03:07:07] hrm no i can take a screenshot [03:07:09] its a local server [03:07:15] OK that works too [03:08:09] RoanKattouw: nm, when i copied the text to MS word, then copied it out of there usng .RTF it worked when i pasted it in and used
[03:08:19] 	 now i just need to figure out how to wrap lines of text in a 
 ??
[03:08:30] 	 You don't need to wrap the individual lines
[03:08:41] 	 Just put 
 before the whole thing and 
after the whole thing [03:09:03] i have some lines go off the page [03:09:13] Oh right [03:09:16] Yeah that can be fixed separately [03:09:33] how? [03:11:40] Edit the MediaWiki:Common.css page and add pre { white-space: pre-wrap; } [03:13:01] where is that located? [03:13:10] Actually sorry ,that's the wrong rule, let me find the right CSS for this [03:13:29] There is a page on your wiki called MediaWiki:Common.css , you can go to it by typing its name into the search bar [03:13:37] If you're an admin, you can edit it and put CSS in it [03:13:50] ah [03:14:20] no idea how u do that [03:14:27] i searched for it in the search function it doesnt find it [03:14:30] but i doubt thats what u meant [03:14:59] RoanKattouw: how do i get that file where is it located? [03:15:08] zoidberg-: It's not a file, it's a page [03:15:28] its not there then [03:15:34] how do i access it give m the exact link? [03:15:38] Alternative way of finding it: in the URL, look for "Main_Page" or whatever the name of the page you're on is, and replace it with "MediaWiki:Common.css" [03:15:44] There were no results matching the query. [03:15:45] Create the page "Common.css" on this wiki! [03:16:00] Yeah it's called "MediaWiki:Common.css" [03:16:10] i see [03:16:21] Also the CSS I gave you was right after all [03:16:44] ffs [03:16:47] that page doesn't exsit [03:16:55] and everytime i go to it it wants me to create ti? [03:16:58] It might let you create it though? [03:17:00] Yeah [03:17:09] ok [03:17:16] yeah it appaers as though its correct but nothing in there [03:17:22] so i just add: { white-space: pre-wrap; } [03:17:25] and save? [03:17:31] pre { white-space: pre-wrap; } [03:17:53] ok.. [03:18:06] BTW the URL you're at should look something like http://localhost/w/index.php?title=MediaWiki:Monobook.css&action=edit [03:18:18] Sorry, I mean http://localhost/w/index.php?title=MediaWiki:Common.css&action=edit of course [03:18:43] argh [03:18:44] ok [03:18:52] the
 screwed it up in the end
[03:18:56] 	 lemme take a screenshot
[03:18:58] 	 OK
[03:19:00] 	 god this is so annoying :(
[03:20:13] 	 http://188.165.30.10/hmm.png
[03:20:16] 	 RoanKattouw: ^^
[03:20:22] 	 WTF
[03:20:24] 	 Ooooh
[03:20:29] 	 Hash symbols
[03:20:30] 	 D'oh
[03:20:47] 	 yeah but you should be able to tell mediawiki to not interpret them as special chars
[03:20:50] 	 or markup
[03:20:50] 	 OK instead of 
 ..... 
try
 ..... 
[03:20:54] ok [03:21:00] I thought markup was turned off in
 tags but apparently not
[03:23:00] 	 oh my days, how bad is this
[03:23:14] 	 this is supposed to help with documentation not be such a pita to use its worth going back to static pages
[03:23:18] 	 wth
[03:23:18] 	 i've tried
[03:23:23] 	 

[03:23:26] 	 
[03:23:33] 	 

[03:23:40] 	 all break the damn formatting :|
[03:23:51] 	 Did you actually do  instead of 
? [03:23:55] pre [03:24:02] How does
 break?
[03:24:10] 	 just does one line
[03:24:11] 	 not wrapper
[03:24:14] 	 all one line
[03:24:15] 	 WTF!
[03:24:20] 	 yes wtf indeed
[03:24:25] 	 Really MediaWiki?
[03:24:25] 	 doing my head in now
[03:24:29] 	 tempted to go back to wordpress lol
[03:24:39] 	 first attempt at a wiki and its so hard to get information down
[03:24:46] 	 Works for me though
[03:24:52] 	 wtf
[03:24:57] 	 well then 
[03:25:01] 	 You're sure you didn't typo pre there?
[03:25:01] 	 im at a loss
[03:25:10] 	 let me copy and paste what i have in th eedit box
[03:25:24] 	 http://codepad.org/TSQoo49z
[03:25:26] 	 there ya go
[03:25:26] 	 I have 
     Foo     Bar     Baz    
(with line breaks instead of spaces) and it works fine [03:25:32] it even copied the crapy formatting [03:25:36] Well that pastebin has everything on one linoe [03:25:40] YES [03:25:44] so does damn mediawiki [03:25:47] it fucked it up [03:25:48] Well yes [03:25:48] grrr [03:25:54] Because you *gave* it everything on one line [03:26:01] dont worry about it mate, this is far too much hassle [03:26:15] If you delete it and copy it again from your earlier pastebin, it'll be fixed [03:26:15] for such a simple thing if i ever come to write complicated docs this just isn't going to handle it [03:26:18] ll [03:26:21] lol [03:26:23] it isn't mate [03:26:27] i've deleted that page numerous times [03:26:29] and remade it [03:26:34] it either borks and goes on one line [03:26:39] or just what it did earlier [03:27:26] Have you tried http://codepad.org/HUe265tY ? [03:28:02] Cause that works for me [03:28:41] whats the difference with that and what i had? [03:28:48] You had everything on one line [03:28:55] Even in the source text [03:29:15] ok copied and pasted that [03:29:17] lets see [03:29:20] lol [03:29:25] it makes it one line [03:29:27] i paste in [03:29:29] hit save page [03:29:32] shows e it on one line [03:29:37] * zoidberg- cries [03:29:39] That's scary [03:29:47] If you click edit now, does it show it on one line in the edit box? [03:30:32] it just removes all line breaks and is jumble up [03:30:36] this is so annoying [03:30:42] I put an (anonymized) example on https://www.mediawiki.org/wiki/User:Catrope/Sandbox [03:30:52] Hmm I wonder if your server is broken somehow? [03:31:00] Or maybe you're using an old version of MediaWiki that has a bug in it? [03:31:09] well [03:31:12] lets see [03:31:17] Or maybe it's getting screwed up when you copy+paste? [03:31:31] It should work if you copy from https://www.mediawiki.org/w/index.php?title=User:Catrope/Sandbox&action=edit for sure [03:32:26] ok just copied from there puts it all on one line [03:32:34] i wonder if that css i added is doing this [03:33:02] It shouldn't, but removing it should be safe [03:33:05] Iam using mediawiki from the debian repo's [03:33:15] You have no ridiculously long lines in there so you shouldn't need my CSS [03:33:29] (I mean you EXPECT to have no ridiculously long lines, right now you do) [03:33:37] Hmm, which version of the Debian packagee? [03:33:49] (You can go to Special:Version to get the version number) [03:34:17] Debian has been known to ship old and/or broken versions in the past [03:34:29] So I wouldn't be surprised if there was a bug causing this [03:34:56] zoidberg-: Maybe to confirm that your server is at fault, you can try pasting your thing (or something, at least) here: https://www.mediawiki.org/w/index.php?title=User:Catrope/Sandbox&action=edit ? [03:36:07] MediaWiki1.19.18+dfsg-0+deb7u1 [03:36:32] OK that's old but not so old that I would expect horrible bugs [03:36:38] ok [03:36:51] The latest version is 1.23, and 1.24 should come out soonish [03:37:00] 1.19 was probably released in ... 2012? [03:37:09] ok [03:37:22] well i like to run with this for now i dont see any known bugs that cause this issue [03:37:30] Yeah exactly [03:37:39] Could you try pasting your thing into that URL I gave you up there? [03:37:41] wtf [03:37:50] Then we can rule out if it's an issue on your end as opposed to on your wiki [03:38:01] ok two mins [03:38:23] https://www.mediawiki.org/wiki/User:Catrope/Sandbox [03:38:41] that was what i had originally - but now i can't get it too look like that (see how it has two liens off the page) [03:38:54] thats what happened with me but then u gave me the csss and since then it doesnt show it lik ehta [03:38:55] Oh, yeah there's two that get cut off there [03:39:25] but it doesnt even go like that anymore [03:39:29] it just wraps one line now [03:39:47] Yeah the CSS I gave you is used to wrap very long lines [03:40:12] If you resize the window on that sandbox page of mine, you'll see you can get things to off screen by making the window narrow enough [03:40:15] My CSS makes it wrap instead [03:40:29] But if everything is on one line, that wrapping is gonna produce some funny effects [03:40:32] i give up mate [03:40:34] i deleted the page [03:40:42] raddeed it with the copy from the mediawiki.com page [03:40:46] and it still wraps to one line [03:40:49] WTF really [03:40:52] yes [03:40:56] im not playing with it anymore [03:41:03] And if you go back to the edit form afterwards, does it give it to you on one line? [03:41:06] over something so simple, this has killed it forme [03:41:08] yes [03:41:10] Cause that's some broken crap man [03:41:12] no matter what i do [03:41:15] i know [03:41:18] its bloody annoying [03:41:25] whol eevening wasted on such a stupid bug [03:41:27] OK, well, lesson learned: don't use the Debian package, it's total garbage [03:41:39] meh [03:41:44] I knew to avoid the Debian packages for MW because they've been shady in the past but I didn't know it was this bad [03:41:47] anyway thanks for the help [03:41:51] Yeah, sorry [03:41:56] not your fault [03:41:59] :) [03:42:11] In case you care, you can download a tarball from mediawiki.org and do an install with that [03:42:33] yeah maybe i try that [03:42:42] https://www.mediawiki.org/wiki/Download [03:42:45] this is for only documenting my note so i may look for a easier solution [03:42:53] Yeah I understand [03:42:54] gonna go sleep on it anyways thank you [03:43:00] As someone once said in this very channel [03:43:10] "Using MediaWiki to keep your personal notes is like mowing your lawn with a tank" [04:02:21] better than using tomboy [04:03:01] I've got over 100 notes in tomboy, and I noticed it was starting to get slow [04:03:09] which I thought was a bit strange, 100 notes is not many notes [04:03:28] checked the code, sure enough, it stores all notes in a single XML file which it parses on startup [04:05:05] sorry, actually 100 separate XML files, all of which need to be loaded on startup in order to display a MRU list [04:16:23] https://www.quora.com/Is-the-MediaWiki-codebase-beautiful uhhh... hmmmm... [07:50:06] I need help being able to execute composer on my server with semantic media wiki. I have been unsuccessful [07:50:50] Operations such as... does not seem to work [07:50:51] php composer.phar require mediawiki/semantic-result-formats "1.9.*" [07:51:17] I confirmed with host that php and composer are set up correctly [07:51:52] These extensions seem to require that they be installed via composer but I may be missing something [07:54:30] morning gentlemen [07:55:19] any thought to my question? [07:55:49] if you're looking to execute a composition you should probably consult an orchestrator [07:57:14] the program composer is the way in which some of these semantic mediawiki extensions are installed [07:57:37] have you installed orchestrator? [07:58:27] Composer is on the server I am using. [07:58:35] Here is what I am trying to install: http://semantic-mediawiki.org/wiki/Semantic_Result_Formats [08:08:39] DKGenius: what do you mean by "does not seem to work"? What happens if you try? [08:09:49] DKGenius: first thing to check after running composer: file permissions. Make sure the web server / php process can read the files composer installed [08:10:02] for me, that is routinely not the case, and i have to change access rights manually [08:16:59] let me check Daniel [08:20:44] I added execution permissions to composer.phar [08:20:55] php composer.phar require mediawiki/semantic-result-formats "1.9.*" is the line I am trying to do [08:21:27] I am using Putty, and it won't do anything, just give me a another line starting with ?????? [08:22:57] Still no luck [08:25:19] Should I be able to use Putty to working with composer on my server? [08:25:32] the instructions seem to assume that this will work [08:26:24] I also tried to update the composer.json file directly, no good [08:33:56] any further thought Daniel? [08:46:25] DKGenius: as far as i know, composer *unpacks* the phar file. [08:46:37] the important thing is that the *resulting* files have the correct permissions [08:48:00] ah, no, i was wrong about unpacking the .phar. that's just an alternative way of invoking composer. [08:48:26] "won't do anything" is quite strange [08:48:40] you should get *some* response if you try to execute that line. [11:26:12] !debug [11:26:13] 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 [12:29:13] what property type for wikitext? for use in a caption attribute in gallery [12:31:56] I don't know what you're asking. [12:33:40] aw shit wrong channel [12:33:44] semantic media wiki sorry [12:34:49] Hi [12:35:15] is there a parameter to hide to content of an edit in rss? [12:35:22] like here: https://en.wikipedia.org/w/api.php?hidebots=1&days=7&limit=50&hidewikidata=1&action=feedrecentchanges&feedformat=atom [13:08:57] Good day all, please is there someone who can help me on installing infoboxes [13:10:02] !infobox [13:10:02] https://en.wikipedia.org/wiki/Template:Infobox [13:10:07] !exportinfobox [13:10:11] helpful :/ [13:10:20] !infoboxexport [13:10:23] the infobox is working but the CSS formatting is missing, this means that the infobox doesn't show at the right [13:10:44] hello Reedy, I viewed the link you've posted [13:10:53] Hamma: you'll need any css wikipedia uses for styling infoboxes. [13:10:57] Right [13:10:58] ^ [13:11:08] generally, copying infoboxes from wikipedia is the most complicated way to get infoboxes [13:11:15] because the ones on wikipedia are extremely convoluted [13:11:22] !wikipediatemplates [13:11:27] o_O [13:11:31] Reedy I don't know how to hook the infobox to the CSS [13:11:39] !css [13:11:39] To change styles for your wiki, go to one of the MediaWiki:xxx.css wiki page (NOT a file) and put your custom styles there (sysop/admin rights required). MediaWiki:Common.css is for all skins and should be used for content styles. MediaWiki:Vector.css is for the Vector skin (default), etc. For more information, see !skins and https://www.mediawiki.org/wiki/Manual:Interface/CSS [13:11:46] I can give you administrator right if you can help me [13:11:53] Hamma: you'll need to put the appropriate css rules into MediaWiki:common.css [13:12:02] what those rules are or where to find them, i have no idea [13:12:26] I think a lot of people just end up copying all the CSS [13:12:32] site CSS [13:13:04] eek... [13:13:55] I don't like to touch any code because I fear to alter the website, please if someone is an expert in deploying infoboxes I can give him an adminstrator account [13:15:09] you don't need an admin account to do that [13:19:10] can someone come to Skype ? [13:31:41] MC8: you do need one to fix Hamma's css problem [13:52:38] sorry I forgot how computers worked [13:53:24] I will repeat all the procedure of the infobox installation and I will see if something is changed [13:58:45] i have a special page which takes over the output by calling $wgOut->disable(); then i curl binary data from an webservice and print the result from curl_exec like: $body = curl_exec($ch); print $body; when open the webservice url directly in a browser it works. but wenn i us the special page i get an network error. the request accept header shows: Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 the [13:59:30] the response: Content-Type:application/msword. can someone give me a hint how to fix this? [14:04:00] Hi MatmaRex are u here?!:) [14:04:24] i have a special page which takes over the output by calling $wgOut->disable(); then i curl binary data from an webservice and print the result from curl_exec like: $body = curl_exec($ch); print $body; when open the webservice url directly in a browser it works. but wenn i us the special page i get an network error. the request accept header shows: Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 the [14:04:26] the response: Content-Type:application/msword. can someone give me a hint how to fix this? [14:04:49] no idea :( [14:05:16] thank u [14:07:49] Hey folks, I'm trying to export a template from my mediawiki installation using Special:Export but when I click the Add button, nothing happens [14:08:00] also submitting the form does nothing either [14:08:35] Any suggestions? Basically I need to export Reflist and Mbox templates to import into another wiki. [14:13:13] same issue on mediawiki.org [14:15:16] apparently im supposed to use the giant text area not the text box with the "Add" button next to it [15:29:48] is there an extension I can install on a self-hosted wiki to get the wikipedia citation styles, like Template:Cite journal and similar? [15:30:20] !wptemplates [15:30:20] To copy templates from Wikipedia, use Special:Export and check the "Include templates" option to get all the sub-templates, then upload the file with Special:Import on your wiki. You'll also likely have to install the ParserFunctions extension, Scribunto extension and install/enable HTML tidy. You also might need some CSS from Wikipedia's Common.css. You'll also need a lot of... [15:31:08] marktraceur: Thank you! [15:34:50] No problem :) [15:35:01] But how can I get that citation style template? Exporting Template:Cite Journal and Template:CS1 gives me an empty XML file (minus some headers) even though I have Include Templates checked. [15:35:11] Weird [15:36:25] hmm, ditto [15:36:37] I think I just got the link wrong; exporting the entire category gives me what I need, and it uses Template:Cite_Journal in the export box instead of a fully-qualified link [15:36:58] though there is a fully-qualified link for Cs1 [15:36:59] I think it's a redirect issue [15:37:10] Template:Cite Journal -> Template:Cite journal [15:37:21] If i put the latter into special export, I get a much larger file [15:37:42] Yeah [15:37:52] CS1 doesn't exist on enwiki either [17:33:03] <_shawnguts> anyone here [17:33:54] !ask [17:33:54] Please feel free to ask your question: if anybody who knows the answer is around, they will surely reply. Don't ask for help or for attention before actually asking your question, that's just a waste of time – both yours and everybody else's. :) [17:36:15] <_shawnguts> I am trying to log into my account and have forgotten my password. I entered an email address but I guess I never confirmed my email and so I cannot receive the forgot password email on that address. The support pages informed me to make a new account which I have done. How do I use the "move" function like the support pages say? [17:36:52] <_shawnguts> I have submitted a wiki page for review and I would like to retrieve that page back. [17:37:35] <_shawnguts> When I say I entered an email address I mean I entered the address when I created the account. [17:43:31] Bye [18:23:15] Is there anyone here that might be able to help me with a Semantic Mediawiki issue? [18:23:39] I am trying to use composer to execute on my server so that I can install extensions [18:23:50] try asking in #semantic-mediawiki? [18:28:15] there is no one in #semanitc-mediawiki. There are extensions of mediawiki that seem to only work if they are installed via composer. Anyone familiar with this process? [18:28:42] did you go to the right channel? or a typo? ;) [18:29:06] #semantic-mediawiki [18:29:22] typo [18:29:27] one moment [18:31:10] is using composer only a semantic issue, or are there mediawiki extensions that require it to? [18:32:43] I have spent more than 10 hours on the issue and just to find someone who knows what they are doing. Is there another location where I can ask my question? [18:34:21] to be honest, I'm not sure if any other extension actually requires composer. [18:34:45] did you install orchestrator? [18:35:34] The instructions ask for Composer. There is no alternative mentioned. [19:03:43] Is there a way to allow non-authenticated users to view content in a MediaWiki instance without having to change PHP files? [19:04:02] I mean, my wiki is configured like that. I want to change it so that non-auth people can see contnet. [19:04:46] By default they can [19:05:13] !access | mribeirodantas [19:05:13] mribeirodantas: For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [19:05:40] undo any configuration change that is now preventing unauthenticated users to "read" [19:16:14] Vulpix: thank you :) [19:16:28] yw :) [19:16:31] but I have to change the PHP files in order to do that =/ [19:16:38] And it's a hosted instance that I have no access to such files. [19:16:39] shoutwii [19:17:10] mribeirodantas: if your wiki is in shoutwiki, you should ask shoutwiki staff to do it [19:17:21] I did, and nothing was changed so far :( [19:17:41] ask again, maybe they missed something [19:18:18] they're the only people able to change that, unless you find a way to hack into their servers :P [19:18:21] also, gtg [20:25:18] I created an extension that is intended for putting a wiki into debug mode. There are a number of different debug settings in MediaWiki and this should help simplify things for developers. It is a fully functional work in progress. If anybody would like to do a formal code review or just share their thoughts, I would appreciate it. Thanks in advance! https://gerrit.wikimedia.org/r/#/c/161362/ [20:53:20] Ike: pet peeve of mine: don't make a member private, just to provide a getFoo() and setFoo() around it that make it effectively public. just make it public. [20:54:19] eh, [20:54:41] having setters and getters can be useful when you want to validate things [20:54:48] yes, but he's not validating [20:54:49] or log when things change [20:55:17] makes it harder to do that in the future then :P [20:57:16] also, in general, it seems a bit on the enterprisey-java-classes-everywhere-for-everything side [20:57:54] specifically VarSetter [20:58:19] jackmcbarn: It is a good point. I am kind of thinking of the future. Maybe I should get rid of the getters/setters until they're useful? [20:58:49] Ike: unless you really expect a reason to log, then yes [21:00:50] Wouldn't it just be better spending the time writing a decent debugging documentation? [21:01:15] jackmcbarn: I actually like the classes-everywhere idea :). Is it bad? [21:01:39] Ike: people hate java because of that [21:01:57] when you have a class with one one-line method, and that's it, and that's a whole 20+ line file, something seems wrong [21:02:45] jackmcbarn: Would you just combine all the classes into VarSetter? [21:03:23] Reedy: That should probably be done too, but I like the idea of setting debug in one line. [21:03:28] Ike: i'd combine everything into DebugMode.class.php (except DebugMode.php) [21:03:46] also, instead of having a function that returns DebugMode::DEBUG_MODE_ALL ^ DebugMode::DEBUG_MODE_VERBOSE, just put that directly in DebugMode.php [21:04:06] Ike: by the way, have you done a lot of java before? [21:04:21] jackmcbarn: You got me :). Trained on Java way back when. [21:04:54] I don't think this makes much sense as an extension. [21:05:07] docs with a block of code to copy [21:05:20] ^^^ [21:05:37] users are lazy, though [21:05:39] for one, this only runs during ExtensionFunctions, which can be pretty late. [21:05:45] So installing an extension is easier? [21:06:00] jackmcbarn: users !== developers [21:06:14] who is the extension aimed at? [21:06:27] Developers, as above. [21:06:28] legoktm: how many times on the support desk or #mediawiki do we ask users to turn on debugging, and they have problems doing so? [21:06:52] Some struggle to install simple extensions [21:08:08] The extension was born as a "simple block of code" that I've been using for years. The problem is that these settings change with each MediaWiki version. I work on a number of wikis, each sometimes running different versions. Having an extension with branches would make my life easier. [21:08:32] The debugging stuff doesn't really change... [21:09:44] Also, people don't upgrade extensions and then get confused when shit breaks :) [21:10:17] Ike: I think a .php file with the right settings configured, that people just require_once into their LocalSettings.php would be way more useful. [21:10:29] There were a few settings added in the last few verions. And some deprecated. [21:12:14] $wgEnableDebugging = true; [21:13:08] legoktm: I think there are uses for both. [21:14:48] Reedy: What do you mean about "$wgEnableDebugging" [21:15:09] I was being slightly sarcastic [21:15:20] Suggesting a "super global" in mediawiki itself to enable the functionality [21:16:20] I don't think it's a terrible idea, based on jackmcbarn's comment. Users have trouble debugging and such. [21:16:50] $_ENABLEDEBUGGING; [21:16:53] Not that I'm suggesting it [21:16:55] Reedy: i seriously like that idea too. Poe's law strikes again [21:17:19] Adding one line to a file is easier than downloading a tar/zip to the server, getting them to put it int he right place, then add one line to the same file they could have just added one line to to begin with [21:18:04] Reedy: As I said, it's targeted to devs. Your super global idea may help users, but not to be confused with the extension. [21:18:16] But the point still stands... [21:18:21] Why do it as an extension? [21:18:26] Bar for "older" versions of mediawiki [21:18:59] I'm guessing the newer versions will continue to change the debug settings. [21:19:10] Probably add a few more [21:19:21] But if it's a feature in core, people will be prompted to update it during code review [21:19:31] extensions are known to bitrot [21:20:15] My extensions generally don't... I hope. [21:21:39] when i see this sort of thing, i know that no matter how easy we make it, someone will mess it up: https://www.mediawiki.org/wiki/Thread:Extension_talk:Scribunto/error [21:23:29] ouch. [21:23:59] Is there a consensus I should abandon? [21:24:08] legoktm: that's not ouch. ouch is the 3 threads above and below it are others users making the exact same mistake [21:24:40] ....... [21:24:42] damn [21:24:49] Ike: not really abandon it, but put it in core instead of an extension [21:24:50] maybe Scribunto should have saner defaults ;) [21:24:57] legoktm: it does. Scribunto needs no config at all to work [21:25:06] * legoktm facepalms [21:25:07] but users see example config on its doc page on-wiki, and copy it blindly in [21:33:53] jackmcbarn: I'm thinking to leave the extension for 1_23 and then get it in core for future releases. Does that work? [21:34:04] if you want [21:42:24] what is the preferred naming for database patches? patch-image-img_id.sql or patch-img_id.sql? [21:42:50] assuming it's a core patch to add a new field [22:17:42] 'ello persons! [22:17:59] I have questions about ParserFunctions, anyone available to answer a few? [22:19:58] >.> Why is this channel always so quiet. [22:21:24] hi [22:21:32] !ask [22:21:32] Please feel free to ask your question: if anybody who knows the answer is around, they will surely reply. Don't ask for help or for attention before actually asking your question, that's just a waste of time – both yours and everybody else's. :) [22:26:33] :P [22:26:47] ((I disagree with that, but okie)) [22:27:27] *thinks* May have answered my own question, will ask it in chat when I return if not. [22:27:56] Nope... Okay. [22:28:30] Using the following Code: [22:28:36] {{#Ifeq: {{{type}}} | Mushroom | | }} [22:28:52] I'm wondering if there's a way to get it to accept: [22:29:36] To accept {{{type}}} as being Mushroom when {{{type}}} is actually [[:Category:Mushroom|Mushroom]] [22:32:28] hi Kuu_Otava - btw not sure whether you know that if you don't get an answer here, mediawiki-l might be able to help you [22:32:31] !lists | Kuu_Otava [22:32:31] Kuu_Otava: mediawiki-l and wikitech-l are the primary mailing lists for MediaWiki-related issues. See https://www.mediawiki.org/wiki/Mailing_lists for details. [22:33:45] hey guys. is there any way to get a back to the top link in the section titles... the java script on wikipedia for user js doesn't seem to work in 1.23 [22:35:29] woops, I got disconnected. does anyone know a way to do this? [22:47:54] hmm, it seems editsection was replaced by mw-editsection-bracket [22:50:14] I mean, mw- editsection [22:52:02] hi, grapefruit - btw not sure whether you know that if you don't get an answer here, mediawiki-l might be able to help you [22:52:04] !lists | grapefruit [22:52:04] grapefruit: mediawiki-l and wikitech-l are the primary mailing lists for MediaWiki-related issues. See https://www.mediawiki.org/wiki/Mailing_lists for details. [22:53:05] it works! :-) just replaced the text in http://en.wikipedia.org/wiki/Wikipedia: Back_to_top with the new as noted. I.e editsection is replaced with mw-editsection [22:53:34] maybe wikipedia admin update that page. thanks! :-) [22:54:43] :) glad it all worked out, grapefruit [22:54:47] how is your day going overall? [22:58:29] Sumanah what's mediawiki-l? [22:58:48] Oh, found it. XD Thanks. [22:58:49] Kuu_Otava: mediawiki-l and wikitech-l are the primary mailing lists for MediaWiki-related issues. See https://www.mediawiki.org/wiki/Mailing_lists for details. [22:58:51] :) [22:59:29] Why are these all split up so weird. [22:59:38] I figured mediawiki would be mediawiki issues, ya know? [22:59:45] Kuu_Otava: see https://en.wikipedia.org/wiki/Module:Delink [22:59:58] Kuu_Otava: your confusion is understandable [23:00:16] Kuu_Otava: there are a bunch of historical reasons [23:00:26] mediawiki-l [23:00:30] The one that noone is in? [23:00:44] Kuu_Otava: there are several people subscribed to the mediawiki-l mailing list [23:01:02] Oh wait. [23:01:04] and they send and receive messages https://lists.wikimedia.org/pipermail/mediawiki-l/2014-September/thread.html [23:01:16] It's not a IRC channel? [23:01:24] No it's not [23:01:39] We talk in different places when we want to have different kinds of conversations. Each open source community has "a mailing list, a wiki, and an IRC channel.... a platform for discussion, storage for documentation and real-time communication." [23:01:48] An IRC channel is a constant waterfall of conversation and you aren't expected to be there all the time or catch everything. A mailing list is more like a slow-moving river, and a wiki changes slower, like a marsh. [23:01:54] Sumanah, thanks so much for being so helpful. :) [23:02:01] so for some kinds of help requests, mailing lists are better [23:02:12] jackmcbarn I'll try that, thanks so much. [23:02:14] Kuu_Otava: thank you for using MediaWiki and for being good at accepting help :) [23:02:20] Kuu_Otava: is this for your own wiki? [23:02:28] Yes. [23:02:52] ((I was about to get into the semantics of whether or not it's 'Mine', but I'm Admin and developing it.. So yes is close enough)) [23:02:56] Kuu_Otava: note that for you to be legally allowed to use code from Wikipedia on your wiki, it needs to be cc-by-sa licensed. is it? [23:03:08] I have no idea what you just said. [23:03:17] :) [23:03:29] Kuu_Otava: have you heard of "licensing" (the intellectual property term)? [23:03:34] who is allowed to copy and reuse what? [23:03:36] Every word that came out of your mouth was the Queen's English, and I didn't understand a word of it. [23:04:19] Everyone? [23:04:19] It's a wiki for a game. [23:05:23] You may find it useful to check out https://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License Kuu_Otava (it's linked-to from the bottom of every Wikipedia page) [23:06:20] So... I think everyone could? Not really sure how to answer that question. [23:07:03] Kuu_Otava: actually, the easy way to answer that question, is look at the CC logo at the bottom of every wikipedia page. see if your wiki has it. if it does, you're all good. if not, enable it in LocalSettings.php, provided you're okay with the terms of it [23:07:44] jackmcbarn: I don't think Kuu_Otava ever mentioned using anything from Wikipedia, by the way. [23:08:42] Yaron: i suggested to him Module:Delink [23:08:52] Oh, okay. [23:09:06] Well, no one's going to sue him for using it, anyway... [23:15:10] Kuu_Otava: btw would you prefer I refer to you as he/him, she/her, or something else? [23:16:09] "I can't remember what something else said to me, but it was rather intersting" [23:16:12] * Reedy grins [23:20:45] .... [23:21:06] Kuu_Otava: I'm a woman for instance [23:21:07] I'm a CIS-White Male. ;) [23:21:13] ok, got it [23:21:23] Who hates political correctness with the fiery passion of a thousand suns. [23:21:40] sorry to hear it - to me, "political correctness" is a way of saying "respectful courtesy" [23:21:44] So you can call me racial epithets if you want to... I go well with cheese. [23:21:47] in any case, back to your MediaWiki problem [23:22:09] * Kuu_Otava nods. "Right. Different topic entirely." [23:22:12] so, if you'd like, I'd be happy to walk you through the basics of licensing [23:22:25] * Kuu_Otava nods. "I'd really appreciate that. [23:22:44] That being said, sumanah, your preferred pronoun? [23:22:49] She/her. Thanks! [23:23:08] ((Dislike it, yes.. But went to a liberal arts school.. Which is where I simultaneously learned to respect the protocol, and hate it with the fiery passion of a thousand suns. XD )) [23:23:11] So, in order to make it easier to share and reuse stuff, Wikimedians share our work under a free license [23:23:44] GO on. [23:23:53] Ahem. [23:23:53] Go on. [23:23:54] Stupid caps. [23:24:04] No prob :) [23:24:22] that is to say, specifically, we use the Creative Commons Attribution-ShareAlike License, or legal terms that are *at least that free if not freer* [23:25:13] in the United States and a lot of other countries (basically most countries if not all), unless you specify that you're putting out text/pictures/etc under a particular license, you're defaulting to standard copyright [23:25:28] which is very restrictive, legally, concerning what other people are allowed to do with your work [23:25:37] (translation, remixing, reusing, podcasting, etc etc etc) [23:25:57] so Scribunto Jack? Anything else? [23:26:11] jackmcbarn: ^ [23:26:38] Kuu_Otava: in IRC, if you want to get someone's attention, if you say their nickname, usually their screen pings or flashes to notify them [23:27:01] thus my possibly-redundant repetition there :) [23:28:00] Kuu_Otava: once it's installed, go to https://en.wikipedia.org/wiki/Special:Export and type each of these things on their own line: "Template:Delink", "Module:Delink", and "Module:No globals". uncheck the first checkbox and hit Export. you'll get an xml file to download [23:28:08] *laughs* Thank you sumanah. [23:28:08] Kuu_Otava: anyway, we encourage you to explicitly specify a reasonably share-y license in your MediaWiki installation -- it's reasonably easy to do that during installation or in the config settings somewhere -- and this also makes it easier for you to comply with the Creative Commons Attribution-ShareAlike License legal terms [23:28:12] then go to Special:Import on your own wiki, and upload the file you just downloaded [23:28:29] oh, wait [23:28:35] in the list, also include "Module:Arguments" [23:28:57] sumanah Alright.. What are the details of a cc-sl license? [23:29:24] Kuu_Otava: https://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License is a good explanation [23:30:18] by the way Kuu_Otava if you want a little more of an overview regarding why we use the Lua scripting language for MediaWiki templates, check out http://blog.wikimedia.org/2013/03/11/lua-templates-faster-more-flexible-pages/ and https://blog.wikimedia.org/2013/03/14/what-lua-scripting-means-wikimedia-open-source/ which I wrote [23:30:23] Thank you.. I'm pretty sure that's what it is. [23:30:34] I'll see to having it updated. [23:31:30] jackmcbarn, so that will install Scribunto, is it fairly simple to install the module? [23:31:45] Kuu_Otava: no, the steps i gave you will install the module ,after Scribunto's already installed [23:31:54] if you do them before you install Scribunto, you'll make a big mess [23:32:06] OH. [23:32:17] to install Scribunto, go to https://www.mediawiki.org/wiki/Extension:Scribunto and download it, then add it to LocalSettings.php [23:32:28] you don't need any configuration for it except the require_once line [23:32:46] Ok, I may have missed a step then. [23:33:48] sumanah Thanks for the link to that page. [23:34:28] jackmcbarn: once it's installed, go to https://en.wikipedia.org/wiki/Special:Export... This is once Scribunto is installed? [23:34:31] yes [23:34:41] if you did the export early, that's fine. just don't do the import until scribunto is installed [23:34:52] ... Having not done this before, I may be confused. [23:34:59] How does the module get put into all this? [23:35:09] Is it uploaded, installed? Copy pasted? [23:35:19] the last step i gave you, the Special:Import step, will install it [23:36:15] * Kuu_Otava nods slowly. "That part makes sense to me. Perhaps my mistake is I'm thinking of a 'module' as a file. [23:36:30] And somehow I missed the part where you 'get' the module. [23:36:34] right. it's not. a module is a wiki page like any other [23:36:43] ... That makes a bit more sense. [23:36:50] Right.. It's a template. [23:37:00] >.< {{Suddenly puts the words together}} [23:37:03] So what does the export do? [23:37:22] Kuu_Otava: it takes the content from wikipedia and makes it easy to put on your wiki [23:37:30] XD [23:37:30] Ah-HAH. [23:37:37] Much becomes clear. [23:37:49] \o/ [23:38:19] jackmcbarn, sumanah, thank you so much. [23:39:01] :) [23:39:06] Thanks for using MediaWiki! [23:39:43] May I pass you a private message sumanah? [23:39:53] yes [23:54:57] incidentally I am watching "Jeopardy!" right now and am pleased that I absolutely swept the physics category, but dismayed that I am evidently crap at facts about Rhode Island