[06:30:26] what is "suggest" meant to do in composer.json? [06:30:33] is there some way to actually install those packages? [06:34:32] TimStarling: no; they're purely informational, and thus a bit dumb. [06:35:04] so you are just meant to clobber your composer.json by running composer.phar require? [06:37:34] I'm trying to figure out how to run phpunit [06:37:38] you can create a composer.local.json, according to lego [06:37:44] right... [06:37:53] you know running phpunit requires monolog [06:37:53] for mediawiki? [06:37:59] yeah [06:38:09] err, it shouldn't [06:38:13] mediawiki has phpunit for requires-dev [06:38:25] yeah, I have phpunit, just not monolog [06:38:35] an accidental dependency might have slipped in though [06:38:48] or at least, I had no monolog until I ran composer.phar require monolog/monolog and clobbered my composer.json [06:39:31] create composer.local.json with {"require": {"monolog/monolog":"version"}} [06:39:38] includes/debug/logger/monolog/LineFormatter.php [06:39:41] since July 31 [06:39:42] and then run composer update [06:40:22] https://gerrit.wikimedia.org/r/#/c/228053/ you merged it [06:41:27] oops :/ [06:41:59] * legoktm works on a fix [06:42:27] the monolog class that is being extended is not trivial [06:42:48] so you'll have to declare the dependency or get rid of this thing [06:43:19] TimStarling: https://gerrit.wikimedia.org/r/234949 [06:43:53] ori: huh? MW doesn't require monolog unless you specially configure it [06:44:02] looks fine to me but I guess ori wants to comment on it [06:44:49] no, it looks fine [06:45:37] i still don't entirely understand what is the value added by the eleven classes that make up the MediaWiki\\Logger namespace [06:48:22] ...to provide logging? [06:49:37] some of the complexity is to handle both MW's old "legacy" logging and monolog [06:50:47] $this->bug29408File = __DIR__ . '/bug29408'; [06:50:47] file_put_contents( $this->bug29408File, "\x00" ); [06:50:49] wtf? [06:51:02] either we stay honest and use no more than the PSR-3 interface specifies [06:51:16] this unsurprisingly fails with "Permission denied" [06:51:33] no, phpunit, you may not screw with my source directory [06:51:48] or we have code that depends on monolog and we just declare the dependency, like symfony2, silex, laravel, lumen, ppi, xoops, aura, and proton apparently already do [06:52:42] ori: PSR-3 just dictates log levels and an interface to pass messages to some implementation, nothing about where those messages end up or how they're formatted [06:53:13] right, but i think we're talking across each other [06:55:30] what i'm complaining about is basically this: we don't declare a dependency on monolog to give users the flexibility of choosing any PSR-3-compatible logging library [06:56:26] this flexibility comes at a cost of having to jerry-rig a composer.local.json and doing your own version management to get a modern logging setup working [06:58:25] we should just depend on monolog, like the frameworks i mentioned above do already. users prefer opinionated setups that work over software stacks that score academic points by maintaining loose coupling where it doesn't matter [07:00:02] yeah, that makes sense. [08:03:12] anyone have any idea what could cause pages to go blank after submitting a edit? [08:05:59] Reception|away: countless things; https://www.mediawiki.org/wiki/Blank_page [08:06:25] ok thnaks [08:06:46] *thanks [08:09:09] I'm using Collections 1.7.0, and we use it for PDF, OpenDocument and ePub. We're using mwlib to render, and I gather OCG doesn't yet to ePub. Are we stuck with mwlib for now as long as we want ePub? Does anyone know which Collections we have to revert to for best mwlib support? [08:47:25] Temporus: yes you have to use mwlib; the version of Collection shouldn't matter much for the rendering. You can use the PediaPress server anyway. [08:47:42] If the default configuration doesn't work, please report it. [08:48:32] Nemo_bis thanks - we have a few customizations so run our own render server, but are having trouble getting renders to output with two columns. [08:49:19] Temporus: why do you want two columns? for what output? [08:50:44] In Special:Book there's the option for outputting a book as one or two columns. Both options show, but we can't get render as two columns (many of the texts are fairly large, and some users prefer the 2 column output). [08:51:47] At present I'm testing PDF output. [09:54:27] Nemo_bis - sorry forgot to add your name! In Special:Book there's the option for outputting a book as one or two columns. Both options show, but we can't get render as two columns (many of the texts are fairly large, and some users prefer the 2 column output). I'm testing with PDF output. [09:59:39] ori: well, it was the first proposed composer requirement [09:59:48] it's easier to go from 12 to 13 than from 0 to 1 [10:04:26] also MediaWiki\Logger contains things that are not in monolog, like a configuration and management interface, which allows monolog to be configured via LocalSettings.php [10:07:50] Temporus: the double-column output only worked with some versions of mwlib IIRC, it's mainly done with OCG [11:43:35] hi all [11:43:39] beginner's question [11:43:54] the doc on custom namespaces says that "Manipulation of $wgExtraNamespaces must be completed during MediaWiki initialization" [11:44:17] does this mean I can do it in LocalSettings.php or must I do it elsewhere? [11:44:56] Should be fine in LocalSettings [11:45:14] I think there's a hook you can do it in if you want [11:46:55] Reedy: you mean I cannot just write '''$wgExtraNamespaces[NS_FOO] = "Foo";''' at the end of LocalSettings? [11:47:08] You can [11:47:20] ok cool [11:47:37] I never used hooks yet so I think I should keep things simple [11:50:03] You only need to use the hooks in extensions if you need dynamic/runtime type manipulation [12:01:31] Reedy: ok thanks [16:45:33] MatmaRex, how to debug missing css/js with a new-style skin? [16:46:17] Platonides: why would it be different than with a "old-style" skin? [16:46:34] unless you mean pre-RL [16:47:32] no, it was ~1 year old [16:47:47] but clearly something is not loading properly [16:47:58] compare http://www.wikimedia.es/wiki/Portada (old) [16:48:04] with http://wiki.wikimedia.es/wiki/Portada (new) [16:50:39] hmm [16:50:47] perhaps the easiest part is the "Error: Unknown dependency: jquery" [16:51:14] (still, that doesn't explain the css problems...) [16:51:54] Platonides: interesting skin; why moving to wiki. subdomain? [16:52:41] Platonides: it actually does. although the new wiki is kind of hard to debug, since i can't see Special:Version on it [16:53:16] Nemo_bis, we had both wiki. and www. subdomains pointing to the same place [16:53:31] Platonides: a lot of the styles on the old wiki comes from http://www.wikimedia.es/w/extensions/HomePageWMES/style.css , which is being loaded via RL only when JavaScript is enabled [16:53:31] ok [16:53:34] now I played with it when migrating to the server [16:53:51] Platonides: since basic JS features fail to load on the new wiki, this doesn't get loaded either [16:54:39] Platonides: don't add 'jquery' or 'mediawiki' as dependencies, they're implied. Adding them causes things to break [16:54:48] Platonides: "Unknown dependency: jquery" means that one of your RL modules depends on 'jquery'. it shouldn't, just remove the dependency and it will work. never add dependencies on 'jquery' or 'mediawiki', they are guaranteed to be loaded before your script, and depending on them blows up since a few MW versions ago [16:55:12] I wonder why that needs js [16:55:20] $wgResourceModules['ext.homepage-wmes'] = array( [16:55:20] 'scripts' => 'js/home.js', [16:55:20] 'styles' => 'style.css', [16:55:20] 'dependencies' => 'jquery', [16:55:21] 'localBasePath' => dirname( __FILE__ ), [16:55:21] 'remoteExtPath' => 'HomePageWMES' [16:55:21] ); [16:55:27] you might be using addModules() instead of addModuleStyles() ? [16:55:29] it will be this module [16:56:25] probably someone put jquery to fill the dependencies with a dummy value [16:56:59] wow, just removing that line fixed everything :) [16:57:12] Vulpix, that someone was me [16:57:23] but I don't remember why [16:57:58] it was probably copied from some example [17:01:54] other special pages work fine [17:02:04] no idea why Special:Version redirects infinitely [17:18:07] Platonides: that's weird, because appending any random query string stops the redirect http://wiki.wikimedia.es/wiki/Especial:Versi%C3%B3n?asda [17:18:33] funny [17:18:44] turns out it's related to the encoding [17:21:47] * Platonides sets $wgDebugRedirects [17:22:59] and the server version [17:23:20] the same code works in one server but fails in the other [17:25:02] hi! [17:25:16] say are there any essential improvements from mediawiki 1.24 to 1.25? [17:25:44] see the changelog? [17:25:44] we would like to update from 1.21, but it seems 1.25 needs more things to change, so i'd use 1.24 if this makes sense [17:25:51] the rewrite rule is very simple... [17:25:53] RewriteRule ^wiki/(.*)$ /w/index.php?title=$1 [L,QSA] [17:26:49] Flexman: there are a lot of improvements in 1.25, see https://www.mediawiki.org/wiki/MediaWiki_1.25 [17:26:51] Platonides: hmm, can't you just redirect to /w/index.php ? (sans that ?title=$1) [17:27:20] Platonides: MW will see the original request URL and figure it out, i believe [17:30:18] legoktm: hm. they seem to be no need for my purpose, i guess [17:30:42] or are there some major improvements for internationalization too? [17:33:09] Flexman: in general its good to stay current as it makes upgrading significantly easier, there are lots of minor bug fixes that we don't necessarily document. 1.25 made the i18n of log entries much better AIUI [17:36:45] legoktm: ok. well depends on how we do the i18n. i didn not want to do it like on the wikipedia and rather wanted to add the different languages to one entry (since there is not so much text). is that possible with some plugin? [17:37:01] MatmaRex, that makes it unable to connect to db �! [17:37:43] Flexman: maybe you want https://www.mediawiki.org/wiki/Extension:Translate ? [17:38:32] Platonides: D: [17:38:57] I know... [17:38:58] legoktm: hmm, wo took a look on it - i guess the probelm is that we use semantic forms and try to find a way where this works together [17:41:20] I'm not sure how it works with SF, Nemo_bis might know? [17:41:47] SemanticForms? [17:42:02] yeah, with Translate [17:42:08] http://tieteentermipankki.fi/ is the flagship example :) [17:42:24] See also relevant publication with some examples https://www.mediawiki.org/wiki/MSMW [17:42:34] * reynaldo Hello [17:43:13] I’m using the wiki API and I’m trying to parse article text and images [17:43:25] https://en.wikivoyage.org/w/api.php?action=query&prop=extracts&format=json&titles=San Francisco&exsectionformat=raw [17:43:45] I can gather the text, but I’m not sure how to hook up the images... [17:46:32] Anyone have any tips? :) [17:47:20] reynaldo: there's prop=pageimages, or something [17:55:40] * reynaldo Oh, awesome [17:55:53] How do I know where to place the image though? [17:56:06] There are no references from the raw text... [17:59:47] reynaldo: hmm, what are you trying to do? [18:00:23] Display a WikiVoyage page, with text and images, in my iOS app [18:03:23] https://en.wikivoyage.org/w/index.php?title=San%20Francisco&action=render ? [18:07:34] Hm, thanks, I think I might use this — I’ll experiment with my app [18:07:41] :) [20:30:09] are the debian maintainers for mediawiki present? [20:32:40] juri_: no [21:22:40] Is there anyway I can render the mobile html? [21:22:50] https://en.wikivoyage.org/w/index.php?title=San%20Francisco&action=render [21:27:16] https://en.m.wikivoyage.org/w/index.php?title=San%20Francisco&action=render seems to be the same, despite the en.*m*. [21:29:04] reynaldo: https://www.mediawiki.org/wiki/Extension:MobileFrontend#Extended_action.3Dparse [21:33:15] I get “No such action” for wikivoyage.org [21:33:30] Wait…sorry [21:34:57] Hm, this doesn’t seem to generate the mobile web HTML [21:34:59] https://en.m.wikivoyage.org/w/api.php?page=San_Francisco&action=mobileview&format=json [21:35:59] I seem to have IDs for the sections — there must be an API for requesting mobile HTML for those sections [21:36:02] ...maybe [21:38:11] reynaldo: Yes, there is. Hold on. [21:38:24] https://en.m.wikivoyage.org/w/api.php?page=San_Francisco&action=mobileview&format=json&prop=text§ions=1 [21:38:37] reynaldo: https://en.m.wikivoyage.org/w/api.php?action=mobileview&page=San_Francisco§ions=all [21:38:40] Ah [21:38:58] So that generates the Mobile Web HTML? [21:39:04] I’m trying to confirm... [21:39:11] I linked to it... https://en.m.wikivoyage.org/w/api.php?page=San_Francisco&action=parse&prop=text&mobileformat= [21:39:19] I see mw-headline [21:39:37] reynaldo: Yes, that's the HTML that's used on mobile web and the mobile apps. [21:39:47] (Although Wikivoyage doesn't have mobile apps made by the WMF) [21:40:00] Ah [21:40:43] Is there anyway we can change the content type to text/html and just display the html? [21:40:54] Without the wrapping JSON? [21:41:05] reynaldo: Not to my knowledge. [21:41:17] Hm, alright [22:01:30] how do i tell mediawiki i'm serving it as / ? [22:02:36] juri_: https://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory [22:02:58] thanks! [23:54:02] Woah there are a lot of people here.. Okay hopefully one of you guys can help me.. I'm a system administrator (mostly) for Orain.org, and several of the user's we've attempted to globally rename can no longer login (for the last several jobs) I've tried manually running the entire job queue on every applicable wiki, no luck. I also read the CentralAuth [23:54:02] guide for unlocking accounts (for system administrators) but the first account I tried it on it appears to not have worked [23:54:21] legoktm: ^