[01:14:16] Greetings. Looking for assistance with update to 1.23 from 1.22.2 on shared hosting (no shell). Trying to use the web updater, however, after entering the upgrade key, the installer hangs and times out. This doesn't happen with the installer of 1.22.2. [01:14:58] Ascarion: can you see any logs on the server? [01:15:10] Unfortunately not. [01:19:02] Error display is also disabled and I can't override this through any of the usual means, htaccess, user.ini, php commands, etc. It's a weird setup, that I cannot influence at all. I was hoping that this was something that you'd had encountered already. [01:26:17] hi, I've just finished my project, but how do I move it under mediawiki/extensions/MyExtension like the list at https://gerrit.wikimedia.org/r/#/admin/projects/ [01:26:32] I'm wondering also whether I should ask to move it to core instead [01:27:47] withoutaname: request a new repo at https://www.mediawiki.org/wiki/Git/New_repositories/Requests [01:28:37] legoktm, should I ask someone else to also look over my code [01:42:12] withoutaname, you don't need it to be reviewed to get a repo I don't think... [01:44:09] Krenair: well, what i mean is if I should get a +2 or someone to look over the code before pushing it, even though it's my project [01:44:20] like the git reviews for other patches [01:47:38] I feel like in code-review giving +2 to yourself would not be impartial [01:51:11] withoutaname, the +2 policy applies to core and extensions deployed by WMF [01:51:22] your extension is not deployed by WMF [02:02:50] Self-merges should be avoided everywhere, if possible, I think. [02:03:20] But many times that's not possible. [02:03:32] I don't think it makes sense when importing existing code [02:32:37] hey uh is anyone actively maintaining https://www.mediawiki.org/wiki/Extension:GroupPermissions [02:32:48] dont wanna be duplicating work someone else is doin [02:33:54] no [02:34:41] If that does what it sounds like, I think I've also written something similar [02:35:00] I've just written up something similar... [02:35:37] https://www.mediawiki.org/wiki/Extension:GroupPermissionsManager [02:35:42] another one [02:36:55] withoutaname, https://gerrit.wikimedia.org/r/#/c/74678/ ? [02:37:24] sysop around? there's a bot flooding rc and it's hiding some of the crap that went through [02:38:15] well, not exactly meant for CA [02:39:35] Nemo_bis, ^ [02:41:21] .... [02:41:44] im gonna go check further back the RC logs for more advertisements [02:43:01] Nemo_bis, are you actually watching or shall I just block your bot? [02:59:29] So, I seem to be having some kind of Problem with wfShellExec on my server. I have commented out the two places in the Installer class where it gets used and now the environment checks run through and I don't get a timeout, but I probably shouldn't update to 1.23 now, right? ^^ [03:09:38] I must be missing something about the terminology of "page touching" http://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide/mk&curid=148178&diff=1030316&oldid=1030279 [03:11:31] p858snake|l: that bot is essentially doing the same thing that would happen if you were to try to null-edit https://meta.wikimedia.org/wiki/Help:Recursive_conversion_of_wikitext [03:12:08] though it's not changing anything, the fact that it's editing is making something change. the only problem is it's not using its bot flag [03:12:18] Krenair: ^ [03:12:49] Ascarion: i don't think that's a problem. i think it's just an installer issue. what two lines did you comment though? [03:17:32] As I said, the only two ocurences of wfShellExec() in Installer.php. Should be line 1027 and 1274-1276. At least the pages loads now. No more timeout. [03:17:56] jackmcbarn, thanks for pointing that out. I've blocked it [03:24:47] was wfShellExec disabled in php.ini [03:28:50] No. If it was, wfShellExec should just return and not cause a timeout. [03:40:13] Unfortunately the function is too complex for my php knowledge to try and troubleshoot and I'll have to postpone upgrading for now. I'll be idling if someone has a suggestion. Thank you both for trying to help. [03:43:38] Ascarion: If you enable debug logging, the debug log will show the exact command run by wfShellExec [03:43:50] might help in debugging [05:03:35] Krenair: what's wrong with the bot [05:06:25] Oh. [13:38:54] !install [13:38:55] Installing MediaWiki takes between 10 and 30 minutes, and involves uploading/copying files and running the installer script to configure the software. Full instructions can be found in the INSTALL file supplied in the distribution archive. An installation manual can also be found at . See also: !download [13:54:31] !dump [13:54:31] For information on how to get dumps from Wikimedia Wikis, see http://meta.wikimedia.org/wiki/Data_dumps . For a how-to on importing dumps, see https://www.mediawiki.org/wiki/Manual:Importing_XML_dumps . [13:54:41] !backup [13:54:41] See http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki for information about backing up your wiki. For restoring your wiki, see http://www.mediawiki.org/wiki/Manual:Moving_a_wiki#Import_the_database_backup for more. If you don't have database access, try !grabber. [14:15:44] Nice, 1.21! Till short ago they were on 1.4 according to wikistats :) http://www.modellbau-wiki.de/wiki/Spezial:Version [14:16:44] 1.4 ◉ _ ◉ [14:20:40] Vulpix: thats what I was saying.... yikes [14:21:32] Hi :D [14:43:28] Would it be possible to make a template which transcludes headlines from one page onto another and includes a link to the page it's grabbing the headlines from? [14:44:52] I want to make a meta-page which has the table of contents of other pages on it [14:52:32] debdrup: that's not possible, even with Extension:DynamicPageList [14:52:39] :( [14:52:40] Hi, everyone. Is there a way to have custom display titles used in the page title? (ie, between ) [14:52:57] JoshDreamland: DISPLAYTITLE [14:53:05] yeah, that isn't working [14:53:10] it's only updating the h1 [14:53:30] JoshDreamland: works for me [14:53:35] look at https://en.wikipedia.org/wiki/IPhone [14:53:55] we have the setting enabled that lets you force underscores, etc [14:53:56] debdrup, Vulpix: yes there is [14:54:10] jackmcbarn: oh? [14:54:18] you just have to set parts of the page to be shown with the right parameters [14:55:02] like {{#if:{{{headline1|y}}}|== The headline ==}} [14:55:26] err, noinclude rather than includeonly [14:55:33] then the same thing for body1 and headline2, etc... [14:55:35] onlyinclude, rather? [14:55:42] noinclude [14:56:21] that doesn't seem to be correct [14:56:26] Vulpix: why not? [14:56:29] i'm currently extracting a list of headlines by using onlyinclude around them and making a {{:Page}} reference on the page where I want it displayed [14:57:22] or if you always want the page to show all of its headlines with links when transcluded, you can do that too [14:57:32] jackmcbarn: {{:PageSection|headline1=yes}} would include the whole page, plus the headline, and [[PageSection]] would have no headline? [14:57:40] but i'd like them to also be links to the article itself, jackmcbarn [14:57:54] hold on, i'll just set up a demo of it. that'll be easier than explaining it [14:58:04] sure [15:05:32] debdrup: https://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&oldid=612087915 [15:06:44] (if this is for your own wiki, and you don't have the Scribunto extension, that will be significantly more complicated but still doable) [15:07:56] how do i see the source for that? [15:08:29] for which part of it? [15:08:39] what you're trying to demonstrate [15:09:01] see https://en.wikipedia.org/wiki/Module:Sandbox/Jackmcbarn and https://en.wikipedia.org/w/index.php?title=User:Jackmcbarn/Sandbox&action=edit [15:09:10] right [15:14:27] jackmcbarn: I don't know if it's just because it's sunday, or because my brain has turned to mollases, but I can't make head or tails out of how to impliment that. [15:16:29] debdrup: does your wiki have Scribunto? [15:16:41] jackmcbarn: it's just mediawiki+bluespice [15:16:53] debdrup: can you add Scribunto to it? [15:17:03] i don't have root access to the server so no [15:17:13] debdrup: you don't need root access. it's just more php files [15:17:14] but it can be added when the guy who has gets up [15:17:28] i don't have access to the webserver, sorry [15:17:39] i don't mean root access in that sense [15:18:04] oh. when the person who does gets up, tell them to set up https://www.mediawiki.org/wiki/Extension:Scribunto [15:18:10] also, what version of MediaWiki do you have? [15:18:11] are you on 1.23? [15:18:50] 1.22.7 and bluespice is 2.22.2 [15:20:41] jackmcbarn: if you feel like it, can you make a list of steps i need to take to make that happen and i'll get on it as soon as he's installed scribunto [15:20:58] Assume I don't know shit, because that's almost true. [15:21:06] I'm just getting my feet wet, so to speak. [15:21:39] if you're on 1.22 it needs some extra work [15:22:22] Maybe I should just drop it - it seems like a lot of work for a tiny feature that probably won't be used that much. [15:24:56] jackmcbarn: thanks for the help though, but it's sunday and I'm simply too lazy to put that much effort into it when I've got the basic functionality I wanted (headlines listed on another page, done with onlyinclude and {{:page}} where i want it displayed [16:10:45] What's the best way to make it so that only sysops can edit most pages, but they can create a page for a specific user and allow only that user (and sysops) to edit that page? [16:11:37] !cms [16:11:37] Wikis are designed for openness, to be readable and editable by all. If you want a forum, a blog, a web authoring toolkit or corporate content management system, perhaps don't use wiki software. There is a nice overview of free tools available at including the possibility to try each system. For ways to restrict access in MediaWiki, see !access. [16:12:29] Mmmmm. [16:12:45] !access [16:12:45] For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [16:13:30] Moonlightning: authorizing a single user to edit a specific page is not possible in MediaWiki [16:14:47] the most reasonable approach is to restrict editing an entire namespace (or more than 1) only to sysops, and allowing general users to edit other namespaces (for example, a "Draft:") namespace [16:15:59] then you can move pages from that Draft: namespace to the main one so it will be editable only by sysops again [16:34:28] Hmm, okay. [16:34:31] Thanks, Vulpix [16:45:09] !import [16:45:09] To import pages a few pages, use Special:Import - you can also import pages directly from another wiki (see !importsources). For mass imports, use importDump.php - see for details. NOTE: when using content from another wiki, follow the LICENSE TERMS, especially, attribute source and authors! [17:58:53] what's the best way to get a list of all the pages in a category which has ~20,000 members? API gives 500 without logging in; Special:Export is giving me 10,000. [18:05:17] Canada: use the cmcontinue parameter to get the next 500 / 10000 until you get all [18:08:59] Vulpix: so there's no workaround to dump everything at once? :p [18:09:14] Canada: for so large categories, no [18:09:24] 20000/500 is 40 [18:09:27] I can live with that [18:09:39] thanks! [18:09:58] np :) [18:14:14] " Moonlightning: authorizing a single user to edit a specific page is not possible in MediaWiki [18:14:14] " user js and css? [18:14:49] ...while not able to edit anything else? [18:15:17] deny createpage and protect all other extant pages? [18:20:23] "protect all" is a solution, although not a neat one. [18:21:46] or you could use namespace protections [18:22:06] or abuse filter [18:22:27] Vulpix: think outside the box :P [18:22:50] Betacommand: hah, abusefilter! that's a nice one :P [18:23:15] abusefilter isn't that good of a solution since it doesn't tell users they can't edit until they hit save [18:23:27] Vulpix: or use the block page option to limit their editing to their talk page and transclude that where you want the output displayed [18:24:08] and somehow block all new accounts as soon as they're made [18:24:30] jackmcbarn: what is your actual goal here? [18:24:44] Betacommand: not for me. some user in here earlier wanted to [18:24:57] (who is still here, actually) [18:25:43] jackmcbarn: it all depends on exactly what they want to do, using NS protection is one way, and having a single page thats in its own namespace that users can edit [18:26:19] or using JS hacks in combination with several of the above methods [18:26:34] JS hacks fail as soon as a user realizes they can disable JS [18:26:57] jackmcbarn: /faceplam like I said in combination [18:27:09] how would JS hacks help then? [18:27:25] jackmcbarn: tie JS hack with abuse filter [18:27:32] oh. that makes sense [18:27:39] use JS to rename tabs/redirect users [18:27:58] and the AF as a hard stop [18:29:28] jackmcbarn: Think outside the box, Ive been doing this crap for long enough I can pretty much achieve anything :P [18:29:48] Hell I can almost divide by zero [18:38:22] Yep, yep, still here. [18:40:02] I suppose it's not that much of an issue since you can't edit with an acount, and accounts have to be approved by sysops ( https://www.mediawiki.org/wiki/Extension:ConfirmAccount ) [18:47:59] Moonlightning: what is your goal? [19:07:14] depends on the specific page [20:10:03] Nemo_bis: What is the progress in this: [20:10:04] https://bugzilla.wikimedia.org/show_bug.cgi?id=65245 [20:10:55] Nemo_bis: Sorry for bothering you, But I think it's take too much time. [20:13:36] Ahmed_Sammour, the bug is fixed. [20:14:00] There will be no more progress on our end. It's done, yay [20:17:18] Krenair: It seem to me it's not fixed. [20:18:02] The request was about adding a new format to preference. [20:18:03] Ahmed_Sammour, well the patch was merged. It should be working [20:19:16] Krenair: Take a look to this link: https://ar.wikipedia.org/wiki/%D8%AE%D8%A7%D8%B5:%D8%AA%D9%81%D8%B6%D9%8A%D9%84%D8%A7%D8%AA#mw-prefsection-rendering [20:19:23] Ahmed_Sammour, you don't understand [20:19:26] The bug is fixed [20:19:43] You will need to wait before wiki operators, e.g. the ones behind Wikipedia, to deploy the fix to their site [20:20:25] They'd be crazy to instantly take every patch by us and instantly deploy it to their production sites. [20:23:10] Krenair: Sorry for the misunderstanding, Now all I have to do is wait?. [20:23:43] Nemo says wikipedias are expected to have their next update, which should include this patch, on Thursday the 12th of June. So yes [20:33:52] Krenair: Thank you for this explanation. [20:34:28] you're welcome [20:50:02] To be fair I'm not sure it's going to work, need to retest based on last comments on the patch. Testers were unclear in their feedback :) [21:07:37] Would anybody know how/where Mediawiki handles the text on the bottom of the page, such as "This page was last modified on XXX"? I'm looking to redo the footer but I'm not sure where it handles things like page views. [21:10:04] I simply find it increadibly difficult to modify the footer. [21:38:32] TennaFox: well, what are you trying to do? 'modify' is quite a big concept and can include everything from changing link color to removing old stuff, reorganizing new and adding new stuff :) [21:39:34] ashley: Tough explaination... I'd like to rearrange/add speciffic things. I'll make an abbreviated list to give you an idea. [21:40:33] Short list, actually: 1. Remove "Powered by Mediawiki" and instead add "All content owned by XXX, used with permission" in that space... [21:40:52] 2. Add "powered by Mediawiki" + pther buttons below the "userd with permission" segment [21:40:56] *other [21:41:28] 3. Do so in a way that uses pre-existing classes so user CSS will render correctly. [21:41:41] *used [21:42:07] what skin are you using? one of the core ones or your own, custom skin? render "all content owned by X" as text or as an image? (because if the latter, you could just hijack the copyright icon for that ;-) [21:42:39] Modified vector. [21:42:59] "Used with permission" would likely need to be text too. [21:43:43] I've sort of got something working, but it's using "

" rather than an ID or class. [21:43:58] !audio [21:44:10] !install [21:44:10] Installing MediaWiki takes between 10 and 30 minutes, and involves uploading/copying files and running the installer script to configure the software. Full instructions can be found in the INSTALL file supplied in the distribution archive. An installation manual can also be found at . See also: !download [21:44:57] monpauvrelieu: Was that meant for me, or...? [21:46:31] ashley: Main issue I'm having is that I cannot find a suitable pre-existing class, and vector's CSS seems to be all over the place, I've had a difficult time getting to where I am now. [21:46:43] I've seen that a ! with something did indicate a link to the something, so I tried with audio [21:47:08] if you can't find a suitable class, chances are that there aren't any out-of-the-box classes which would suit your situation [21:47:13] and Vector is, well, Vector... [21:47:39] but i've found finally what I was wondering about on the mediawiki wiki [21:47:49] monpauvrelieu: What sort of information are you looking for [21:47:59] or nevermind I just read what you wrote [21:48:05] !botbrain [21:48:05] Hello, I'm wm-bot. The database for this channel is published at http://bots.wmflabs.org/~wm-bot/db/%23mediawiki.htm More about WM-Bot: https://meta.wikimedia.org/wiki/wm-bot [21:48:19] http://www.mediawiki.org/wiki/HTML5 [21:48:22] monpauvrelieu: http://bots.wmflabs.org/~wm-bot/db/%23mediawiki.htm gives a full list of the bots commands [21:51:17] My wiki is in fact my new self-hosted personnal site, and I would try to get the same player that on my former one, e.g. http://remuflot/a/Chicken-and-mushroom-pie.htm [21:51:48] so I try to gather first infos on the audio tag [21:52:10] and for the or equivalent, I'll see later [21:52:19] before to do anything wrong [21:54:55] TennaFox: are you perhaps looking for https://www.mediawiki.org/wiki/MediaWiki:Lastmodifiedat [21:55:29] http://www.mediawiki.org/wiki/Extension:TimedMediaHandler isn't exactly what I'm seeking for, I would to put several sources in an audio tag, by safety. Sometimes, one site with my audio is offline, but another one is still up. [21:55:39] Yes, but the thing is I'm not sure how to render that on a page. [21:56:03] My idea would be more to allow the html5 audio tag as is. [21:56:35] monpauvrelieu: Hmm, I'm not sure if anyone has actually made an extension to let the audio tag full on through [21:56:42] and the audio is never on the same server [21:57:01] self hosted = not enough bandwidth [21:57:02] There is of course raw html support, but you only want that if nobody else can edit your site [21:57:10] !rawHtml [21:57:10] For allowing any and all HTML, see . This is of course VERY DANGEROUS. Safer options include , and . [21:57:21] I'm the only editor [21:57:33] ok, well then you can enable $wgRawHtml = true; [21:57:45] thank you for the help :) [21:57:46] and just do

[21:57:52] or any other html you want [21:59:36] As for tables, those are just generally allowed in wiki pages (although not some obscure features). You can use normal html table syntax, or custom wiki table syntax [21:59:38] !tables [21:59:38] For help on creating tables in wikitext, see and [22:00:14] the htlm table will allow me the embossed aspect with css [22:00:39] the wiki syntax, maybe difficulter to get the same [22:05:34] it works :D http://monpauvrelieu.info/fr/index.php?title=Test ___ I just have now to insert the css in addition :D [22:09:34] Betacommand: Ideally? I want everyone to be able to read all pages (no login required), but only sysops to be able to edit most pages or create pages. I also want sysops to be able to create pages editable to specific users. [22:10:31] Apparently the last part isn't possible, but given that I've already configured it so you can't edit without logging in and registrations have to be approved, it's not really necessary. [22:36:22] Random issue/question: Any reason why I can't display an .gif images (Either uploaded or external) anywhere? [22:37:28] TennaFox: Hard to say without knowing what you're doing [22:37:38] For external, I would ask if you have external images enabled [22:38:41] Moonlightning: The last part isn't totally impossible, its just very hard and would require custom extension development probably (Everything's possible if you try hard enough :) [22:38:59] !access | Moonlightning [22:39:00] Moonlightning: For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [22:39:08] Yeah, already saw that. [22:39:39] I think I'm just gonna leave it as it is and ask people when they register to not edit stuff unless they actually know about it. [22:39:49] Might end up being helpful anyway *shrug* [22:40:06] Moonlightning: Soft security is the wiki way :) [22:40:20] XD [22:40:31] Moonlightning: http://meatballwiki.org/wiki/SoftSecurity [23:35:42] Technically speaking, would it be possible to create a new skin, loading the layout of another skin while using seperate CSS? For instance, creating a red-themed Monobook skin that loads the monobook file(s) but instead uses other CSS. [23:36:13] TennaFox: sure [23:36:27] I've sttempted to implement such a feature on several occasioans, but it seems that when it tries to load the same skin twice, it treats them as seperate entities and conflicts. [23:36:46] TennaFox: in fact it should be pretty easy, MediaWiki skins are actually PHP classes – you can just inherit SkinMonoBook and add your magic [23:36:49] *attempted (Typing with on-screen keyboard) [23:38:31] MatmaRex: Just thinking about it quickly, what would you say the most logical was to do so would be? Would re-stating existing CSS classes override those previously loaded? [23:38:44] *way [23:41:03] TennaFox: class SkinMySkin extends SkinMonoBook { public $skinname = 'myskin'; public function setupSkinUserCss( OutputPage $out ) { parent::setupSkinUserCss( $out ); $out->addModuleStyles( 'skins.myskin' ) }, then define the 'skins.myskin' ResourceLoader module to include your additional skins [23:41:23] TennaFox: http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/ [23:41:48] TennaFox: this should be reasonably up-to-date, the skinning system hasn't changed much since 2012 :)