[00:00:45] Yaron, Reedy: if it's minor just do a small version increment maybe - I'm looking to deploy it on production and I don't think switching to getting new releases from git is a good idea for that thing (I can follow up with its admins but I think releases would be easier for them) [00:01:09] I can't remember how semantic versioning works... [00:01:16] Should it be 0.7.3 or should it be 0.8.0? [00:01:37] probably 0.7.3 [00:01:44] Only breaking changing is bumping of MW version support from 1.19 to 1.21 [00:06:51] gry: Reedy: sorry, I only saw all this now. [00:07:10] . [00:07:45] gry: are you talking about this? https://phabricator.wikimedia.org/D392 [00:08:04] If so, it hasn't been checked in yet, though I hope to do it soon. [00:08:41] Reedy: which diff is this? [00:09:25] https://github.com/wikimedia/mediawiki-extensions-ApprovedRevs/commit/b81e8bb4985d52413d44b390ca7b3f09d92861a8 [00:09:45] gry: That one is to do the reviewing via the API [00:09:45] Yaron, you already merged it, https://phabricator.wikimedia.org/T149480 https://gerrit.wikimedia.org/r/#/c/318676/ [00:09:46] Not querying [00:10:06] Yes, I understood it's the wrong diff - just didn't know which one was right [00:10:44] :) [00:11:51] Reedy: we can close T149480 - it's probably indeed not worth writing an api module and I was simply using smart words without knowing what they do [00:11:51] T149480: Extension:Approved Revs is missing an API module - https://phabricator.wikimedia.org/T149480 [00:12:02] heh [00:13:48] gry: the patch I linked to is different frm the one you linked to... is the one I linked to irrelevant now? [00:14:36] Frankly, I'm confused. [00:14:40] it's relevant but we were not discussing it - if you include them both it should be fine [00:14:43] Yaron: No, one is write, one is query/read [00:15:48] Yaron: specifically the original query I had made had to do with viewing the review queue through the api and not with doing review through the api, but these two changes are kind of related and come at the same time, so including them both and then making a release would work [00:16:47] Yes, okay... why were there two API-related patches to AR at pretty much the same time? Just a coincidence? [00:17:45] Possibly [00:18:22] I see no task for that one [00:19:05] Alright. [00:19:40] Anyway - sure, it makes sense to release a new version of AR, given the API additions. [00:19:50] Thanks Yaron :) [00:20:19] ...and I would think it should be 0.8, for what it's worth... [00:20:41] sure - I don't mind. it's up to you :) [00:20:58] Great. [00:21:37] Yaron: FWIW... That API module for the messages to work will need a newer MW min version too [00:21:51] Not sure what version exactly added that [00:21:58] Back compat is easily added if deemed appropriate [00:27:48] Oh. [00:33:16] Anyway. CR left on the revision in phab [00:37:50] Right... might be a while before that code is ready, but we'll see. [00:38:41] bah :) [00:39:32] Not much effort to fix it up [00:39:41] Though using phab may be a barrier ;) [00:42:38] gry: this is all an issue for you because the people in charge of the wiki at your company don't like to call "git pull"? [00:43:13] ...or rather, because they don't like to use Git for production code? [00:45:25] I can see not wanting to just use a random snapshot, though in this case the released/tagged version probably wouldn't have any more testing done on it than the current latest code in Git. [00:45:32] Yaron: yes - I'm begging them to upgrade their mediawiki for weeks now [00:45:59] They are heavily understaffed and I am thinking that a release would make their tasks a bunch easier [00:46:21] Ah. [00:46:44] If they're just downloading a zip file, though, you could just generate such a zip file yourself... [01:23:52] 1/3 [05:08:30] @Urbanecm, @Reedy you were helping me a couple of days ago with upload size. Turned out I had to do three things: 1. create a php.ini file with upload_max_filesize and post_max_size, 2. tell my docker-compose.yml file to copy that file into the appropriate container, and 3. add `client_max_body_size 0;` to my nginx.conf (which I didn't even tell you about). [05:08:30] I also had to give the mediawiki user permission by confirming their email by hand, which was a whole nuther ball of wax. [05:08:53] uploads are now working, I'm happy to report [05:36:44] Hrm. Has anyone ever made a Mediawiki tool that handles extensions, skins, updates and backups, or something like that? [05:37:55] Is there a way to vertically align text in a mediawiki table? [05:38:27] Think I found it [05:40:26] nope, didn't work halp [05:40:39] vertical-align doesn't vertically align [10:16:11] It would be nice if the Special:Watchlist page had a 'x' next to each page which removes it from watchlist with usage of ajax. Or a check box next to each edit listed in the watch list, so that I can select any edits I feel bored about, and click 'remove selected pages from watch list' button at the top. [10:20:21] Hi to all! [10:21:21] I 'm working on project auth without pass. I have couple of questions to more expierenced developers with mediawiki. Is it possible to meet here developer with expierence in authorization apps? [10:22:30] Hi Latvian26. Ggive full detail - nobody can say 'yes, I know' before seeing the question. (Some developers use IRC, some use the mailing list. One can only try.) [10:23:58] Details: I have premaded authentication provider on my website and I need autologin in my media wiki when i get my usrenam from my website [10:26:37] and? [10:49:36] auto-creation source [10:49:40] What source list? [10:53:43] ok [11:10:16] $authManager->autoCreateUser($u,SessionManager::class); [11:10:23] user logs in [11:10:32] How to log in user after it is created ? [11:30:49] How to get user object [11:30:52] existing from DB? [11:31:18] Depends which db an wmf or your own? [11:36:44] Zppix my Db [11:36:52] $authManager->autoCreateUser($u,SessionManager::class); [11:37:01] I can loog in user object with this [11:37:13] But after i cant get aqny function which allows to log in [11:37:55] If you read the db tables look for user id or whatever your looking for and go from there, otherwise i have no clue login stuff is not my specality [13:13:33] hi, i can't upload a pdf to mediawiki from any browsers other than IE. any thoughts? [13:14:01] what happens when you try? [13:14:03] picture files with extensions svg,jpg,png are all working fine [13:14:49] I click the choose file button select the pdf and nothing happens. when i do that for a picture file it loads the name of the file and i am able to hit upload button [13:15:25] i initially thought we were restricting users from uploading pdf in LocalSettings.php. but thats not the case as it works from IE [13:19:31] is pdf allowed in the processable mimetypes of your webserver [13:20:03] Hi everybody! I'm getting a 504 Bad Gateway Error msg when I try to request a new account (page = http://mediaewiki.de). Any ideas what I could do to fix this? [13:20:31] arseny92: how do i check that? [13:21:49] BHW 504 is gateway tmeout, bad gateway is 502 ;) [13:22:34] aaaah you're right :D It's 504 Gateway Time-out nginx [13:22:54] manlin , apache, nginx, or iis? [13:23:51] arseny92: apache [13:24:45] We are sending temporal passwords via email. I specified the the details (SMTP, user, password) in the LocalSettings.php. Is there anything else I have to keep in mind? [13:44:31] any ideas? [13:46:26] aaah; now I get another error msg: Failed to add recipient:xxx@yyyy.de [SMTP: Invalid response code received from server (code: 454, response: 4.7.1 : Relay access denied)] [13:54:08] BHW: you may need to specify a sender address, either $wgNoReplyAddress or $wgPasswordSender (I'm unsure which). most mailservers won't (shouldn't) let you send from a non-local address, to a non-local address, so the autogenerated @hostname likely won't pass muster [14:22:47] I solved my problem [14:22:51] I m happy [14:23:07] I want develop more solid knowledge about mediawiki [14:23:24] Someone can teach me something? [16:25:07] I found the problem. The way this extension code was originally written is that at the top of the function stack it is actually a function hook so $this->mInParser is true which prevents message transformation. Using the companion function User::makeGroupLinkWiki() would be "more appropriate" to use in that context, but it has the same issue with User::getGroupPage(). So the end result is that I will put a work around into this code [16:25:08] because of the awkward way this code I am working on was original written. [16:25:30] amrits: pong? [16:25:33] *originally [16:54:15] So I have scribunto installed on my wiki and the special:version page shows both it and Lua installed but when I try to use a basic {{#if: || }} it won't parse it, I cannot figure out why [16:54:46] it looks like you want ParserFunctions rather than Scribunto. [16:54:47] !e ParserFunctions [16:54:47] https://www.mediawiki.org/wiki/Extension:ParserFunctions [16:55:01] ...dammnit [16:55:06] thanks [16:55:15] (if you want to copy content from Wikipedia, you need both) [16:55:29] Not copying the content from wikipedia, making my own stuff [16:55:43] but it's hairtearing either way [16:59:12] It works, thank you MatmaRex [17:01:16] hi [17:01:22] Hey Bombo [17:15:53] Pongles ;) [17:18:28] i'm trying to understand that short url stuff https://www.mediawiki.org/wiki/Manual:Short_URL [17:18:48] using https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Short_URL/Nginx [17:19:07] Have you tried the Builder tool? http://shorturls.redwerks.org/ [17:19:28] nope *reads* [17:20:15] i almost got it ;) [17:25:50] rewrite ^/wiki/(.+)$ /w/index.php?title=$1 last; [17:26:52] that kind of works, when i go to /wiki/Page i get redirected to /w/index.php?title=Page, but i don't want to see that in the address bar [17:34:51] I can't help you further, I followed the instructions from the builder tool [17:35:55] that doesn't help, i'm using a testserver on localhost [17:36:53] Bombo, do you have root access? [17:38:03] also you installed to /w/ right? [17:39:09] yes i got root on localhost, and installed to /w/ now i'm closer: /wiki/Page works and loads and stays in adress bar, but no theme is visivle [17:39:15] visible even [17:44:52] got it! $wgScriptPath = "/w"; $wgArticlePath = "/wiki/$1"; [17:45:14] they need to be different, i always used $wgArticlePath = "$wgScriptPath/$1"; [17:45:39] and $wgScriptPath="/wiki/" didnt work [17:45:48] thx Pongles for the hints1 ;) [17:46:23] You're welcome, it's always good to pass on help [17:46:35] @Winslow: have you seen Pintsize around? [17:50:46] but there are some links in recent history that are using /w/ urls... hmmm [17:51:01] purge then [17:51:04] purge them [17:51:08] and/or nulledit [17:51:16] should fix them as long as people aren't using hardcoded ones [17:53:09] when i'm going to /wiki/Testpage i get a page with a link 'create page' which redirects to /w/index.php?title=Testpage&action=edit [17:54:48] That's expected [17:56:37] unless you shorturl the action pages it's gonna look like that [17:57:02] I don't suggest you shorturl your action pages as it's more annoying then the regular ones to deal with [17:57:25] hmmkay i think i'll leave that then ;) [17:57:28] thx [18:41:42] hi, where can I set up the message which shows in the search input box? [18:42:29] for example on english wikipedia it says "Search Wikipedia" [18:58:10] you can view the page with ?uselang=qqx to see the message name [18:58:23] e.g. https://en.wikipedia.org/wiki/Main_Page?uselang=qqx [18:58:30] searchsuggest-search [18:58:47] so you can edit it on the page called "MediaWiki:Searchsuggest-search" on your wiki. e.g. https://en.wikipedia.org/wiki/MediaWiki:Searchsuggest-search [19:00:09] MatmaRex: thank you! [19:26:18] Is there a way to force a password change for each user in a wiki with about 200 users where the users don't have local passwords (using an external auth service)? [19:26:41] We have a custom extension that hits the auth service but we want to stop using that, but the users don't have local passwords. [19:31:20] justinl , ensure all MW local users have valid emails, turn off the extension and have each user request a password reset [19:44:03] arseny92: Good idea, let me look into that. Thanks! [19:51:26] You may have to announce the change on MediaWiki:loginprompt [21:28:30] IIRC somewhere in the blocks mechanism there is a restriction that limits IPv6 blocks no higher than /64, so you can't block e.g. a /48 or a /56 but have to block each /64 from them if you have to. In what file is that? [22:20:24] nvm