[00:45:32] MatmaRex: Thank-you for that link! It works perfectly. [00:45:57] Now is there anyway to change the site logo based on selected theme? Last question hopefully. [00:52:04] TennaFox: not natively in mediawiki, i guess. if you're writing custom skins anyway, just use a hard-coded logo URL instead of $wgLogo [01:17:28] legoktm: what's https://www.mediawiki.org/wiki/Requests_for_comment/Extension_registration [01:17:46] specifically "we are planning to move away from configuring things in global scope." [01:19:18] !blank [01:19:18] A blank page or HTTP 500 error usually indicates a fatal PHP error. For information on debugging (including viewing errors), see . [01:24:38] does anyone know where the navbox function is defined for the Navbox template? I'd assume in the Module? But the Template is throwing a script error. [01:27:06] wmat: it is in the module [01:27:23] what error specifically are you getting? [01:50:33] !cache [01:50:33] General information about caches can be seen at , for configuration settings see [03:14:08] should I still use $specialPageAliases for writing extensions? I thought we used i18n json files now [03:14:45] withoutaname: i think json is just for messages [03:15:30] yeah, you still need PHP for special page or parser function aliases [04:56:55] jackmcbarn: oh, I almost forgot, should I store the aliases with $wgExtensionMessagesFiles or with $wgMessagesDirs [04:59:24] withoutaname: yes [05:15:40] Should I use InnoDB or MyISAM for local copy of english wikipedia in mediawiki? [05:32:12] !bureaucrat [05:32:12] There is no such key, you probably want to try: !rightssql, !userapproval, [05:32:26] #mediawiki, Why are bureaucrats called bureaucrats? [05:33:21] Honestly, I have no idea [05:33:40] Because they're involved with approving adminship requests I suppose [05:56:33] Should I use InnoDB or MyISAM for local copy of english wikipedia in mediawiki? [06:05:09] Anyone know how to do $this->someMethodReturningAnArray()[0] in php? [06:05:17] without generating a syntax error? [06:07:53] hmm, googling says not possible until php 5.4 [06:50:39] Sigh over-invalidation by newbie translation admins. https://www.mediawiki.org/w/index.php?title=Multimedia/Media_Viewer/es&diff=prev&oldid=1031496 [06:55:00] Hi! I've upgraded from 1.23wmf15 to 1.24wmf7 and collapsible navs are gone. Is there a simple way of getting them back? [06:55:54] I don't want to copy collapsibleNav.js and place them into Resources.php because that's not clean way. [06:56:48] QuestPC: no, collapsiblenav was removed from the Vector skin due to performance issues [06:57:28] (it's in the 1.24 release notes) [06:57:41] legoktm: ok, thanks for the answer. A bit strange though because it was existing for years. If there were performance issues I doubt it would be in Vector / core anyway. [06:57:48] https://bugzilla.wikimedia.org/show_bug.cgi?id=39035 [06:58:01] legoktm: Ok, I see. So writing an extension is probably the only way of brinding them back. [06:58:37] yeah [07:01:13] legoktm: Still, these could be just disabled by default, removing them is a little bit evil. [07:05:41] I guess [07:16:01] is it possible to check if a beta feature is enabled from a gadget? [07:18:36] wgBetaFeaturesFeatures is intended to be empty? [07:35:47] ebraminio: check mw.user.options? [07:35:54] betafeatures are just normal user preferences [07:45:33] legoktm: thank you, have a look https://www.wikidata.org/wiki/MediaWiki:Group-sysop.js [07:47:29] ebraminio: looks good, I think you might need a dependency upon medawiki.user though [07:47:53] * legoktm checks [07:49:02] ebraminio: 'user.options' actually [07:50:54] legoktm: done [07:51:08] :D [07:52:42] um, heyo [07:53:17] If I want a template to check a value of a template on another page, is it possible to do so without JS? [07:53:18] legoktm: is it working actually there? [07:54:15] ebraminio: I didn't test it. But Group-* pages might be cached for up to 5 minutes iirc [07:54:53] let's say a template on PageA has |age=3 and I want another template on PageB to refer to that in one way or another, kinda like "Blahblahblah and PageA's age is {{{|age}}}" [08:02:19] ostPavel: probably possible with a LUA module [08:02:51] aha, gotcha [08:03:04] legoktm: http://i.imgur.com/h8XAFNt.png [08:03:04] we have lua module installed, but I've never looked into it [08:03:12] shame on me, I suppose :P [08:03:59] ebraminio: oh that looks awesome [08:04:16] legoktm: great! [08:05:04] ostPavel: am finding where I saw such thing [08:05:19] oh, that would be very nice of you [08:16:44] Hmm, I wanted suggest https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#frame:preprocess but that will not useful without more tweaking, better to refactor PageA to show only |Age when a special argument is passed [09:42:12] lol - "'sblood man, discussions are complicated." [10:41:12] what was the command for the bot to notify me when someone joins? [10:41:43] @notify MatmaRex [10:41:43] I'll let you know when I see MatmaRex around here [10:54:46] !e Thanks [10:54:47] https://www.mediawiki.org/wiki/Extension:Thanks [10:59:00] uh, parsing is hard [10:59:40] to find a position of "|" symbol, I have to use {{!}} as a parameter for #pos, right? [11:00:33] yes [11:00:46] for some reason it's still a bit offset for me [11:01:10] could you share an example? :) [11:01:31] sure, mind if I use query? :P [11:01:45] no problem [15:29:02] Urgent. I have ftp access to my mediawiki installation dir, and since a few days ago, thousands of strange files have been automatically created and are still being created, every few minutes or seconds! they are all called "core.###", where the hashes are random digits, in seemingly ever increasing order [15:29:27] J_McKalling: that are "core dumps" files [15:29:40] this happens when the Apache service crashes badly [15:29:53] every few seconds at random interval, a new file is created. they all seem to be of similar size, all 14 megs [15:30:07] oh! what does that mean? the wiki still functions properly online [15:30:27] J_McKalling: that's a dump of the memory for the process it crashes, in case you want to debug the crash [15:30:45] when that happens, you usually see a "connection refused" error [15:31:33] can I fix this, or do I need someone with shell excess? [15:31:54] well, apparently, it's not apache who creates those dumps, but PHP, now that I'm reading... [15:32:18] http://www.webhostingtalk.com/showthread.php?t=704042 [15:32:22] the files themselves are unreadable to me [15:33:21] they're binary files, don't try to read them by a normal text editor [15:33:52] you can use hexdump -C to see something legible, though [15:34:55] I don't think I can perform those commands [15:35:30] I only have ftp access, but I'll see what I can do [15:36:12] J_McKalling: what version of MediaWiki do you have? [15:36:19] 1.22.6 [15:36:28] I'm thinking of the damn job queue again :S [15:38:00] J_McKalling: try setting $wgPhpCli = false; in LocalSettings.php and see if core dumps stop being generated - https://www.mediawiki.org/wiki/Manual:Job_queue#Changes_introduced_in_MediaWiki_1.22 [15:42:00] ok, I've added the new setting, awaiting result [15:42:53] try reloading some pages :P [15:43:22] also, if you have access to error logs, they may contain more info about the error [15:45:45] so far, no new dump files have been created yet, and pages load normally as ever. I only have access to the wiki installation directory though, so I have no access to apache error logs [15:47:32] as I though, job queue 1.22 fubar in all its glory [15:48:03] what does this mean? [15:48:53] on-request job queue handling for 1.22 is broken. At least there's the $wgPhpCli workaround [15:49:34] also note, I have noticed an issue while working on the wiki as well, that may conform what you're saying. previously, I remembered that when I changed a template that auto categorizes its articles, that those articles would be auto recategorized in due time. but this effect does not activate anymore, since I upgraded to 1.22 [15:49:52] J_McKalling: the details are on the URL I've shared before [15:51:08] ok, I will read, moment [15:54:47] ok, I've read it. think I understand. would you recommend upgrading to 1.23? [15:57:26] Vulpix: ? [16:03:38] J_McKalling: It would be a good improvement, but since has been released just now, be prepared to test it and have a current backup in case there's some unexpected problem [16:04:49] ok, I understand. this should not be a problem for me as I'm the only one who uses the wiki at this point, but I'm not a tester [16:07:08] wow! I didn't know 1.23 was released only four days ago! [16:08:35] J_McKalling: you can wait a few weeks in case some problems arise and they're fixed for 1.23.1 [16:08:55] all right, thank you very much [16:10:20] it seems the CLI setting stopped the core dump files from being created. I'll leave it there, until upgraded to 1.23(.1) [16:11:26] thanks for your help [16:11:36] yw :) [16:21:56] robla: this is not urgent at all, but, http://kottke.org/14/06/pioneering-hypertext-project-xanadu-released-after-54-years Ted Nelson finally released a version of Xanadu, one of the great failed dreams, and I thought you would want to know [16:39:13] sumanah: (you know he's on vacation this week, right?) [16:39:35] ah, that wasn't work related [16:39:38] :) [16:40:31] oh right. vacation. forgot [16:40:38] I was too excited about Ted Nelson [16:41:18] :) [17:16:55] I am having trouble enabling Short URLS on my wiki, it redirects to the Short URL yet a 404 error comes up [17:18:03] hi hiyo - hmm, this is using the short url extension? [17:18:53] https://www.mediawiki.org/wiki/Extension:ShortUrl ? [17:20:39] sumanah: no it is using the Short URL Manual https://www.mediawiki.org/wiki/Manual:Short_URL/Apache [17:21:25] hiyo: in that page I see: [17:21:27] "The %{DOCUMENT_ROOT} in the config ensures that Apache has the correct non-ambiguous path. However it does not work on some badly configured free hosts. If you have 404 or 403 issues with your RewriteRules, remove the "%{DOCUMENT_ROOT}" parts and try again." [17:21:41] did you try that? [17:27:54] sumanah: yup, still 404 [17:28:22] sumanah: and it isn't a badly configured free host, it's just a local server of mine [17:28:25] I don't know hiyo - you might ask mediawiki-l [17:28:28] !lists | hiyo [17:28:28] hiyo: mediawiki-l and wikitech-l are the primary mailing lists for MediaWiki-related issues. See https://www.mediawiki.org/wiki/Mailing_lists for details. [17:29:20] jackmcbarn: the specific error is Script error: The function "navbox" does not exist. [17:29:45] jackmcbarn: sorry for the long delay on that reply [17:50:41] How do i upload a new patchset to an existing change on git review? [17:51:32] rohan: https://www.mediawiki.org/wiki/Git/TLDR [17:52:23] Ohh....I feel stupid now [17:53:36] wmat: is this a public wiki? if so, what's the URL? [18:01:03] hiyo: Look at the apache access logs. It should tell you what URL is trying to get (and that it doesn't find) [18:01:29] well, actually, error_log [18:02:32] [Mon Jun 09 13:45:51 2014] [error] [client 192.168.1.3] File does not exist: /var/www/wiki [18:05:04] hiyo: does that path on the server make sense? [18:08:09] yeah [18:09:06] hiyo: apache apparently expects it to be a file, but it's a directory [18:09:46] hiyo: could you put on dpaste your rewrite rules? [18:11:20] http://pastebin.com/8QYzD4xr [18:21:59] hiyo: could you try using a URL with a page name on it? And see if you get an error message? I'm guessing that there's a problem if you go to yourdomain/wiki instead of yourdomain/wiki/ (note the leading "/"), if apache thinks it's going to look for a file called "wiki" instead of a directory, but that shouldn't be [18:25:29] It all gives a Not Found error [18:25:40] whehter it has a page name, traliling slash or not [18:41:55] heatherw: hi, and I hope you are doing well. [18:43:33] sumanah: Hi! Yes, thanks :) [18:43:41] You? [18:44:21] heatherw: I'm pretty good. :) [18:44:47] hiyo: If you want, we can talk in private about your problem, but I'll have to make you several questions :) [18:46:56] Vulpix: okay sure [18:58:49] hi, i upgraded from 1.13 to 1.23 and am experiencing problems with the new site. it doesnt appear to be loading the header html code at all [18:59:10] which means no css or js gets loaded either [19:00:06] limpc: 1.17 added a new entry point (load.php) [19:00:18] If you have interesting rewrite rules, you may have to add an exception for load.php in addition to index.php and api.php [19:00:39] i have no rewrite rules. [19:02:53] any other ideas? [19:09:20] limpc: is your site public to the internet? [19:09:36] !help [19:09:36] There are a lot of topics you could be asking about. Besides, this bot is mostly for experienced users to quickly answer common questions. Please just ask your question and wait patiently, as the best person to answer your question may be away for a few minutes or longer. If you're looking for help pages, we moved that to !helpfor. [19:10:11] jackmcbarn, no, it's internal [19:10:37] limpc: can you open up your browser's web developer console and see what error gets returned when it tries to load the css? [19:11:21] it's not loading the header part at all [19:11:21] theres no .. .. [19:11:21] it just starts with the body content [19:11:35] weird, I've never seen that before [19:11:49] did you upgrade all your extensions alongside with core? did you clear out the whole directory except for LocalSettings when you upgraded? [19:12:13] i copied over extensions. i dont think they are upgraded. [19:12:16] hello, the collapsible of the left navigation bar are all broken [19:12:20] wouldnt that produce errors though? [19:12:24] my error log is empty [19:12:34] limpc: you need to upgrade your extensions when you upgrade core [19:12:45] zerabat: that feature was removed [19:12:57] zerabat: could you be more specific about "broken"? [19:14:33] jackmcbarn , why? [19:14:45] zerabat: it was really bad for performance [19:15:18] but that makes very long the nav bar [19:15:30] (sorry if my english is poor) [19:15:56] zerabat: most people have big enough screens that it all fits these days [19:16:29] but maybe I am not among these people (my screen is 1366x768) [19:17:14] and that is not a very small screen resolution [19:18:27] zerabat: 1366x768 fits all of wikipedia's (large) sidebar except for the list of language links [19:18:34] is your sidebar bigger than wikipedia's? [19:21:58] please see the following screenshot: [[File:Desplegables barra lateral no funcionan.png]] [19:22:16] @link [19:22:16] https://www.mediawiki.org/wiki/File:Desplegables_barra_lateral_no_funcionan.png [19:23:12] zerabat: like i said, that's intended behavior now [19:24:10] OK, but there is a way to set the previous configuration individually like a gadget? [19:26:04] zerabat: not in mediawiki itself, but i think someone wrote a gadget for that [19:26:54] (trying to find it) [19:27:07] MatmaRex , I know that it cannot be in mediawiki itself, because that I asked for a way to implement a gadget [19:27:55] zerabat: it's available on the english wikipedia as "Allow navigation menus to be collapsed." [19:28:11] MatmaRex , Thank you. [19:28:30] called "CollapsibleNav" on https://en.wikipedia.org/wiki/MediaWiki:Gadgets-definition [19:29:40] by the way, when did mediawiki developers remove this feature and where I can find the logs? [19:31:05] zerabat: in may. https://bugzilla.wikimedia.org/show_bug.cgi?id=39035 [19:37:02] by a unknown reason the gadget works on Internet Explorer 9 but not in Firefox 23 [19:38:46] sorry, maybe I need to erase the caché [19:38:52] thank you again [19:43:18] bah, composer [19:43:25] zerabat: You also might want to check your javascript console for errors in Firefox just in case [19:51:57] does anyone know if their is a stop forum spam plugin for mediawiki [19:51:58] the console log found an error in another gadget ([[voy:es:MediaWiki:Gadget-DetectaDesambiguaciones.js]]) [19:54:17] !spam [19:54:17] For information about combating and handling spam in MediaWiki, see and . [20:20:59] ok, extensions was NOT the problem [20:21:17] i deleted all extensions and still no header [20:22:24] limpc, you got a link to the site [20:22:28] its internal [20:22:45] the body is loading, but no header or footer [20:23:00] and since the header is not loading, there's no css/js includes and no skinning [20:23:38] no errors [20:23:45] (on page or in logfile) [20:25:29] limpc: If you add ?useskin=vector to the end of the url does it work (or &useskin=vector if there's already a ? in the url) [20:26:07] Some really old custom skins don't handle loading JS/CSS properly in newish (e.g. 1.17+) MediaWiki [20:44:07] sumanah, is now a good time to check in? [20:44:28] fhocutt_: in about 3 minutes, yes, will ping you [20:48:03] ok fhocutt_! I am back! and drinking tea! albeit Tetley [20:48:22] tea! [20:48:28] ok! [20:49:05] I feel as though there are actually 6 people in our mentorship of you [20:49:18] you, me, Brad, Tollef, Merlijn, and tea [20:49:27] pretty much! [20:49:36] it’s too hot to drink tea here :( [20:49:41] iced tea? :) [20:49:53] maybe! [20:49:55] and/or cold-brewed tea? [20:49:57] bawolff, nope, same result [20:50:22] i should make a batch of ice tea [20:50:54] the bay area is getting another mini heat wave [20:51:00] sumanah: I worked with Merlijn to check over/expand on my simplemediawiki evaluation: https://www.mediawiki.org/wiki/API:Client_code/Evaluations#simplemediawiki [20:51:01] limpc: Hmm, beats me. Check to make sure all the files (especially things in the Skins directory) is from the new version of MediaWiki [20:51:28] yes i deleted the entire folder and copied over the new mediawiki skins [20:52:02] fhocutt_: ok, looking! [20:52:03] And you did that for the other folders too? (As in, all the code is the new code) [20:52:05] sumanah: he added a few things to think about (standard has been slightly modified) and generally agreed with what I have [20:52:29] bawolff, yes, i have a clean install, i only copied over my LocalSettings.php file [20:52:36] limpc: And there's like no headers at all in the output. Not a single tag [20:52:44] none [20:52:50] * bawolff has no idea. But that's super odd [20:52:56] no , , etc [20:53:23] limpc: Could you maybe put the html of a page in a pastebin, and your LocalSettings.php (minus passwords) in a pastebin? [20:53:52] fhocutt_: so, this "unknown" maybe I can help you with [20:53:52] Platinum standard: library maintainers contact MediaWiki API maintainers with feedback on the API's design and function [20:53:52] Unknown [20:54:09] did you say that no one ever has? [20:54:57] I was also thinking of emailing maintainers to check that one as a part of a "heads-up, I'm evaluating your library against this standard; please comment on the talk page if you have any input" [20:55:21] fhocutt_: I would not be surprised if some API client library maintainers had contacted us [20:55:30] you could run their names through http://hexm.de/mw-search [20:55:32] to check [20:55:50] that would hit the mailing lists (I think) and bugzilla and mediawiki.org talk pages [20:55:57] true, can do [20:56:05] I think your suggested "heads-up" email is a good idea! [20:57:19] hmm i notice a 404 error now [20:57:25] when it tries to call /load.php [20:57:43] sumanah: so this week, I can try to get through the rest of the Python libraries [20:57:52] I've started looking at wikitools [20:57:58] e.g. /load.php?debug=false&lang=en&modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles&only=styles&skin=vector&* [20:58:10] sumanah: they are considerably more complex and will take longer though [20:58:20] fhocutt_: Am looking at your simplemediawiki evaluation. You might find it useful to use the checkmark & X templates, e.g., I'll give you an example [20:58:40] limpc: Ok, that would prevent css [20:58:49] sumanah, yes, that would be useful [20:58:52] but in order for that to even be loaded, the page would need some sort of headers [20:58:53] https://www.mediawiki.org/wiki/Template:Check [20:59:05] unless maybe $wgWellFormedXml is off [20:59:10] https://www.mediawiki.org/wiki/Template:Cross [20:59:26] bawolff, yeah its got headers now, im not sure what i did exactly that fixed that. [20:59:52] Well hey, if it works don't question it ;) [21:00:10] So yeah, load.php is a new script that was added in 1.17 [21:00:21] Sometimes people have rewrite rules that can mess it up [21:00:38] sumanah: handy, thanks [21:00:41] fhocutt_: the Check and Cross templates will maybe make things more readable. Yeah [21:01:57] fhocutt_: ok, so about how long did it take you to get through each of the other libraries you evaluated? [21:02:02] bawolff, my rewrite condition is: RewriteCond %{REQUEST_FILENAME} !^/(images|skins|secure|load)/ [NC] [21:02:31] so that should be working right? [21:02:45] sumanah, I think I will use check/cross when there is an obvious answer & leave more complicated cases in text [21:02:52] let me see. [21:03:12] limpc: That by itself doesn't do anything [21:03:13] !wikipmedia [21:03:13] Confused about the differences between MediaWiki, Wikimedia, Wikipedia and wiki? See https://www.mediawiki.org/wiki/Wikipmediawiki [21:03:31] limpc: First thing, verify you actually have a load.php in the mediawiki directory [21:03:34] well its the condition. otherwise it redirects to index.php [21:03:38] yes its there. [21:03:43] fhocutt_: there's probably some kind of "kinda" mark you could leave if you want, in the complicated cases, alongside text https://www.mediawiki.org/wiki/Template:In_progress [21:03:59] sumanah: I think that was about a day and a half for simplemediawiki, and have spent another 0.5-1 d on wikitools which is definitely not done yet [21:04:12] hey folks, I inherited a wikimedia server that is totally locked down. Talking to the team, we've decided to allow anonymous viewing. however, I don't know how to turn that on (or turn off the restriction). [21:04:14] Can someone point me to the correct page to do that? the last admin just gave me admin rights but I'm at a loss as to where to go [21:04:27] hi mkjackson - welcome to mediawiki :) [21:04:55] limpc: Well in that case its probably not sufficient. as it looks for a directory named load, but not load.php [21:04:55] ty sumanah [21:05:11] ? [21:05:40] limpc: maybe try adding below that line RewriteCond %{REQUEST_FILENAME} !^/load\.php [NC] [21:05:42] fhocutt_: so, in the end, what did you grade simplemediawiki ? [21:05:51] thats the same thing [21:05:57] * bawolff isn't that great at rewrite rules, they always confuse me [21:06:19] what mine is doing is checking if the request_filename doesnt begin with 'images', 'skin', 'secure', or 'load' [21:06:53] limpc: You sure. I think its checking if the request_filename doesn't begin with images/ skin/ secure/ or load/ [21:07:16] sumanah: haven't written up TODOs. I think it's a basically solid syntactic sugar-ish library that could use some updates, especially using a library that is better for https. [21:07:24] oh you're right. good catch [21:08:05] fhocutt_: ah, so you are not calling it gold? [21:08:39] sumanah: I don't think any of these will get to gold overall, but I could also split the "gold" determination up by section. [21:08:43] bawolff, now it works :) thanks! [21:08:53] fhocutt_: no, I think it makes sense to call a whole library gold or not [21:08:57] (in my opinion) [21:09:24] :) [21:10:41] fhocutt_: I think the best course of action is for you to continue evaluating the rest of the Python libraries at the same level of detail, with Merlijn & Tollef [21:10:42] it's closer than most from what I recall, because it is so simple. I think that most of the work would fall under "easy to use". [21:11:09] including handling continuations, or at least providing code samples to demonstrate. [21:11:47] fhocutt_: and then look at the shortlist for the rest of the languages, extrapolate from this experience, figure out how much time it will take to do all of them, and cut a language or 2 if the time won't fit [21:11:59] sumanah: sounds good. [21:12:49] it would be good for me to learn JS/NodeJS, but I think that is the obvious one to cut if needde [21:12:51] needed. [21:13:20] it has ~4 libraries and it's a brand new language to me. [21:13:56] got it [21:14:03] ok fhocutt_ does that give you enough to go on for today? [21:14:38] yep. I'll keep going on wikitools, start to draft TODOs for smw, and keep an eye on time [21:14:44] thanks sumanah! [21:14:49] Cool! [21:14:52] Glad as always [21:14:59] * fhocutt_ waves [21:24:02] hey folks, is there a page where I can change the setting or will I have to dig into the PHP files? this server is completely undocumented so I'm hoping that there's just a page where I can change the setting and allow anonymous browsing [21:25:20] hmmm [21:25:22] !cms [21:25:22] 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. [21:25:28] !access [21:25:28] For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [21:25:30] that's it [21:25:41] mkjackson: I think http://www.mediawiki.org/wiki/Manual:User_rights and http://www.mediawiki.org/wiki/Manual:Preventing_access might help you [22:08:38] greg-g: I wanted to +2 gerrit change 135756, which is a schema change. Is there a special procedure I have to follow for that (modern version of tagging scaptrap?) , or can I just +2 it (springle has given it a +1 already) [22:08:59] bawolff: one sec... [22:11:16] bawolff: simply https://wikitech.wikimedia.org/wiki/Schema_changes [22:11:19] "simply" [22:11:51] but, basically, springle still needs to do the schema change, afaict [22:12:12] so, you can merge things, but only if they are backwards compat and can wait weeks until springle gets that done [22:12:18] (in the worst case scenario) [22:12:30] Well this one isn't going to be used for months [22:12:43] And then only by an extension, assuming the gsoc project is succesful [22:13:13] k, well, they should file a schema change bug then and get it on springle's list [22:13:27] s/they/someone not me/ ;) [22:13:54] someone like bawolff ;) [22:14:05] or possibly rillke [22:34:14] qchris: can we talk about the repository name for XMLContentExtension? [22:34:25] wibby: Sure. [22:34:38] qchris: (on https://www.mediawiki.org/wiki/Git/New_repositories/Requests ) [22:34:58] there is already a class called XMLContent [22:35:13] so i renamed it to XMLContentExtension [22:35:20] i realize it is a bit redundant [22:36:20] Not sure I understand ... where is already a class called XMLContent? [22:37:58] not sure where... i forgot ): a quick google gives me https://github.com/wikimedia/mediawiki-extensions-examples/blob/master/DataPages/XmlContent.php but i am not sure how that was related. sorry, i wrote the whole thing months ago [22:38:39] anyways, if the repository would be renamed to XMLContentHandler, would I have to change the extension's name as well? [22:38:57] repo names don't have to be the same as extension names [22:39:08] e.g. intersection repo has DynamicPageList in it [22:39:22] but often that causes confusion [22:39:37] Also class names don't have to be the same as your extension name [22:39:39] Typically repo name == extension name. [22:41:26] i've already called id XMLContentExtension in a paper that is about to be released. basically, i would like to just call it that, if that's ok. if not, XMLContentHandler would probably be the best alternative [22:42:16] I typically defer to ^d, as he is the one in charge of gerrit. [22:42:33] But seems he is away. [22:42:45] mhmm okay [22:44:24] I'll shoot ^d an email and ask ^d's opinion. [22:45:03] cool, thanks [22:46:15] Please try to keep repo name and extension name synced, if at all possible. [22:46:29] It makes auto-linking way easier. [22:46:36] Gloria: Full ACK. [22:47:12] Cool. :-) [23:58:19] Greetings. I regard to my question about the installer hanging recently, I've contacted someone who was able to look at the error log. There was nothing in it, but when we extracted the bits that caused the hanging, here's what we got: https://dpaste.de/1aZA - We already contacted the hoster and they're not accomodating.