[01:33:41] @MatmaRex_mobile : Thank you very much for your help! Good night. [01:48:28] :) [03:58:53] Hello! [08:51:17] I installed and configured Extension: parser functions in my localhost it got installed as it displays the name in Special: version under the list of extensions but how actually to run tests on it i.e how to test it if any changes were made in it locally? [08:58:59] by using a parser function on a wiki page (I'd guess) [09:02:13] can you say where can i use it on wiki page ? [09:04:23] and how can i do it? [09:58:40] rammanoj_, depends on which parser function you want to test. [09:58:49] how? by using that parser function on a wiki page. [09:59:08] Hard to explain. Are you familiar with editing wikitext? If not, see https://www.mediawiki.org/wiki/Help:Editing [10:29:39] yeah thankyou @andre I got it and even run some tests in my localhost [10:32:38] Hello everyone, i got a litte question. I was wondering if there is a possibility to set this bevaiour of "you can only see the latest stable (reviewed) version of a page" to all pages - even if they have not been created yet. I am using the extention flaggedreviews but in the docs it says you have to configure the siteconfiguration for each page in order to achieve this behavoir. I do not want configure every new page, every ti [14:48:27] Hi - does anyone know how the "Reply to"/"Ping" template in mediawiki.org works? (https://www.mediawiki.org/wiki/Template:Reply_to) [14:48:43] Hi Yaron. [14:48:47] If you put a person's username there, that person gets an alert that they were mentioned. [14:49:02] Is it just due to the "@" symbol that the template puts? [14:49:08] No, due to the user link. [14:49:42] Oh... so any time you link to a user page in a talk page, that person gets notified? [14:49:52] Sort of. [14:49:54] https://www.mediawiki.org/wiki/Extension:Echo [14:50:13] It's called "mention" in the documentation. [14:50:14] actually I think Flow is the thing that adds the @Username mention [14:50:24] (although it uses Echo to share that fact with the user) [14:50:38] > It might not be obvious to some users, but this particular notification only works when the person linking to another user's page also signs (~~~~) the post. [14:51:01] Skizzerz: That's certainly a thought, but I doubt it. [14:51:13] Ivy: ? [14:51:19] Ah, "mention"... I looked through that page before but couldn't find this. [14:51:30] it very clearly says on both extension pages that Echo doesn't do jack by itself, and Flow's doc page explicitly mentions the mention feature [14:51:46] Skizzerz: Which page? [14:51:51] https://www.mediawiki.org/wiki/Extension:StructuredDiscussions [14:51:54] search for "mention" [14:52:17] > Also, update.php will create {{FlowMention}} to support Flow's mention feature in VE (either @ or a toolbar menu provides a convenient auto-complete interface for mentions). [14:52:26] And $wgFlowMaxMentionCount. [14:52:31] I don't know what you're talking about. [14:52:36] Echo's page mentions the "mention" option too: https://www.mediawiki.org/wiki/Extension:Echo#Usage [14:52:43] User pings/mentions work outside of Flow. [14:52:48] And were developed outside of Flow, AFAIK. [14:52:54] They're part of Echo. [14:53:21] And the Flow docs make barely a passing mention of mentions. [14:54:40] Yaron: Yeah, maybe the docs should mention "ping" or "reply" more explicitly. [14:54:48] hmm [14:55:19] ok yeah you're right [14:56:24] Yeah, that might help - the thing I was mainly looking for was "@", but that's hard to incorporate, since this doesn't use "@". [14:56:42] (Outside of, er, structured discusssions, that is.) [14:57:26] Or individual wiki sometimes use "@" in a template. [14:57:47] Or individual wikis sometimes use "@" in a template. Like {{ping|foo}} becomes "@Foo:" or whatever. [14:58:59] Sure. [15:00:06] Anyway, Ivy (and Skizzerz): thanks for your help. [15:00:18] No problem. [16:14:00] I am writing you to see about taking this page down that was put up about me years ago by some jeolious boyfriend [16:15:47] https://encyclopediadramatica.rs/Nude_Greg is the page [16:17:02] I would like the page https://encyclopediadramatica.rs/Nude_Greg taken down it has been up for years it was originally pit up by a jeolious boyfriend [17:44:56] Hello, I need some help here. My script directory is /var/www/wiki and fastcgi is giving me a 500 whenever I try to access /var/www/wiki/index.php [17:45:27] !500 [17:45:27] A blank page or HTTP 500 error usually indicates a fatal PHP error. For information on debugging (including viewing errors), see . [17:45:55] oh cool, I'll come back if I need anymore help [18:00:48] Reedy: Thanks I got it worked out! Just forgot to specify a database user [18:01:53] heh [19:36:48] I am trying to get my bot to login to MediaWiki (after having upgraded to 1.27 a while ago) and all I can get is "WrongToken" [19:37:00] trying to follow the directions on mediawiki.org, but they're not working. [19:37:28] I get a login token just fine [19:37:31] but the action=login fails [19:38:48] QuasAtWork: Does normal login work ok (For like ordinary web users) [19:38:54] yes [19:39:20] Is your bots code anywhere? [19:39:32] Can you log in by hand using Special:ApiSandbox ? [19:42:04] Hello, I wanted to work on mediawiki newsletter extension. Is this the right place to talk about it ? [19:42:40] I have already set up mediawiki [19:42:46] nope [19:42:55] going through ApiSandbox gives the same result [19:43:09] "login": { "result": "WrongToken" } [19:43:27] QuasAtWork: let's start at the top. How are you retrieving the token? [19:43:48] action=query&meta=tokens&type=login [19:43:58] ok cool [19:44:36] then you're doing a POST to action=login with that login token as the lgtoken param? [19:44:41] in the POST body, not as a GET param [19:45:18] my framework always uses POST if action=login, so yeah [19:45:40] is your framework handling the cookies correctly? [19:45:47] (if there are any, can't remember) [19:45:56] it handled cookies fine under 1.24 [19:45:58] but pretty sure that grabbing the tokens sets a cookie [19:46:01] ok [19:46:03] it's just using cURL under the hood [19:46:17] can you get the raw log of what you're sending/receiving? [19:46:21] that way you can double-check the values [19:47:27] I suspect that the token might be getting mangled somehow, then [19:50:16] not sure how to get that [19:51:01] depends on your bot's code/framework [19:51:17] there is not one solution I can give you (well, you could always do a packet capture I suppose) [19:51:39] I thought of that but all it sees is encrypted https traffic [19:51:57] then yeah, you'd have to figure it out in the bot framework itself [19:55:53] QuasAtWork: It doesn't work from Special:ApiSandbox? That probably means something in mediawiki is broken not your bot (Or your doing something wrong) [19:57:25] well on ApiSandbox it's very easy to not realize there should only be one \ at the end of the token [19:57:37] let me try that again [19:57:45] the json has \\ because json needs to escape it, so when copy/pasting token in ApiSandbox, ensure you only copy one of the two trailing \ [19:57:51] (token ends with +\, not +\\) [19:58:33] ok that worked [19:59:11] but when the bot framework parses the json, it should transform that to a single \ automatically (assuming you're using json format) [19:59:42] yeah there's only one %5C at the end if I output the full query as a string [20:09:39] *snort* [20:09:40] ok [20:09:49] apparently encoding + in a POST argument is not optional [20:10:01] first time I ever ran into that. [20:10:09] correct [20:10:12] it's URL encoding [20:10:16] + is space if unencoded [20:10:48] (this is why the tokens all end with +\ btw, to catch scripts/bots that don't encode or parse things properly) [20:10:54] ah. [20:11:20] seems query continuation has entirely changed though so I gotta recode all that now :> [20:12:30] correction to above: encoding + is required if your Content-type is application/x-www-form-urlencoded [20:12:38] (which is the default type for POST requests) [20:13:09] other types have different encoding requirements [20:13:44] not sure where cURL determines that at [20:13:57] if you don't tell curl otherwise, it'll set that one [20:13:59] I don't seem to be overriding it in my own code anyways [20:14:03] makes sense. [20:14:26] It seems like redlinks to categories no longer show the list of pages in the category [20:14:29] what language is your framework written in? [20:15:10] well, the JSON request and MW api stuff is in JavaScript [20:15:22] but this is built to run in a custom embedding of SpiderMonkey that I developed [20:15:34] which is in C++ [20:16:09] ok [20:16:14] it was something I built for my job which I just kept adding more and more stuff to ;) [20:16:22] so the bits that generate the params, just ensure to pass everything to encodeURIComponent() [20:16:38] that will automatically translate the + and \ to the %-sequences, as well as any other problematic characters [20:16:51] yeah I need to add that in at the lower layer [20:17:01] right now I just hacked it in in the doLogin method [20:20:59] Niharika: #MediaWiki is the one channel to rule them all :D [20:21:06] I do wish more people would hang out here [20:27:16] 320 is still pretty respectable [20:27:18] granted some of that is bots [20:29:35] looks like I got the new continuation logic down. [20:29:37] <3