" [13:50:01] you'll need to construct the style yourself, like so: Html::element( 'div', array( 'style' => "background-image: url($foo);" ) ) [13:50:12] this is assuming that $foo doesn't contain any user input, or otherwise anything evil [13:50:28] like a javascript: url [13:50:49] $foo is meant to be used as an extension configuration variable [13:52:14] right, so it's probably safe [13:52:24] MatmaRex: thanks, I get the idea :) [14:31:33] Hi. I'm trying to programmatically set a conf value with config.php in a custom extension I'm toying with. I can get() just fine, but I'm not sure how to set() on a configuration value like $wgDefaultUserOptions['usebetatoolbar'] [14:32:48] I took a $conf = $this->getConfig() and I can see the syntax for set(), but I'm unsure how to access the value of an element in an array? [14:33:06] (apologies in advance if this is poorly described, I'm quite new) [14:33:35] You should be setting that directly in the extension.json [14:33:48] or ExtensionName.php if your extension hasn't migrated yet [14:34:55] I am in fact in ExtensionName.php [14:35:23] I'm trying to modify specifically $wgDefaultUserOptions['usebetatoolbar'] in case that's significant [14:36:36] Yeah we usually just set that directly with $wgDefaultUserOptions['key'] = 'val'; there [14:37:21] ah, ok. I'll give that a shot then [14:37:27] ty for your patience Krenair [17:40:21] hi. I'm trying to upgrade from 1.15.1 to 1.24.2 and after i execute the maintenance/update.php script my wiki pages are blank. Is there a way to solve this? [17:41:00] I found this: http://www.mediawiki.org/wiki/Thread:Project:Support_desk/Upgrade_from_1.15.2_to_1.23.0_with_section_errors which seems to be related, but I don't see a solution .... [17:42:48] from 1.15.1? wow [17:43:03] dystant, check your web server error log [17:48:39] ok thanks i will have a look [18:00:34] any luck dystant? [18:48:53] !blank | dystant [18:48:54] dystant: A blank page or HTTP 500 error usually indicates a fatal PHP error. For information on debugging (including viewing errors), see . [19:55:42] Hi, confused about installing Uploadwizard extension. You're supposed to add require_once( "$IP/extensions/UploadWizard/UploadWizard.php" );, but on the install page there's no extension file. It just says instal ImageMagick. [19:57:24] I don't understand [19:57:24] Cory_1975: There are links to download it, one sec [19:57:24] you're expecting a file on the extension page? [19:57:25] Krenair: Chill, I got it [19:57:30] Yes, other extensions I've installed do that. [19:57:32] Cory_1975: Where it says "download" [19:57:39] Click on pretty much any of those links [19:57:48] Cory_1975: What version of MediaWiki do you have? [19:57:59] latest I think 24.1 [19:58:12] 1.24 is nowhere near the latest version [19:58:17] Well. It's close-ish. [19:58:24] 24.2 is the latest [19:58:31] Cory_1975: https://www.mediawiki.org/wiki/Special:ExtensionDistributor/UploadWizard [19:58:46] Yes, I just checked version page, it's 24.2 [19:58:55] *1.24.2* [19:59:06] Sorry, correct, 1.24.2 [19:59:27] Cory_1975: If you've only had to install single files from wiki pages, then welcome to the wide world of complex extensions [19:59:48] Complex extensions? [20:00:30] i.e. ones with more than one file. [20:00:30] Well the 1. is getting a bit silly now if you ask me [20:00:37] !2.0 [20:00:37] No, seriously, 2.0. Have a tracking bug: https://phabricator.wikimedia.org/T72000 [20:01:07] Krenair: We just have a hard time breaking backwards compatibility. [20:01:20] marktraceur Thanks for the provided link. I don't know why that's not on the uploadwizard page [20:01:26] I like how we never added anything blocking that tracker [20:01:27] Cory_1975: It is. [20:01:35] You just didn't look for the "download" link [20:01:39] But why would you? :P [20:01:53] Hmm, let me take another look! [20:02:23] I am working on an instrumentation for PHP and MW is my main test subject. :) I have been getting ~30% coverage running PHPUnit tests and casually browsing the application. Are there other tests / utilities that would execute other parts of the code? [20:02:48] malaverdiere: Noooope, unit testing is not high priority 'round here [20:03:11] well, the extension infobox is a nice example of usability worst practices [20:03:13] marktraceur, so its more manual tests? [20:03:27] Is there a documented test procedure? [20:03:28] marktraceur: Ha, it's on the sidebar! Duh. Now I'll know to look there; thanks again. [20:03:51] malaverdiere: You *are* new here. :) [20:04:00] indeed! [20:04:14] malaverdiere: Basically reviewers "know" how to test changes and we watch for regressions as best we can [20:04:32] There are some browser tests and more complete unit tests scattered through the codebase, but a lot of it isn't covered [20:05:03] malaverdiere: it depends on the area. some stuff has really strong test suites (like the parser), a lot has nothing :( [20:05:27] is there a culture of leaving dead code behind, like cobol programmers do? [20:05:44] hm? no [20:05:55] malaverdiere: Not really, but tech debt is quite a mountain to climb [20:06:16] Its called 'debt' for a good reason :) [20:07:29] Are there good chunks of code that are guaranteed not to run based on configuration? Like the mutually exclusive DB classes? [20:09:01] malaverdiere: I'd imagine the postgres code wouldn't run if you don't enable it. I'm not sure I can guarantee that, but maybe someone else can. [20:09:32] I meant - is there another part of mw that has that kind of characteristic? [20:09:41] malaverdiere: Remote image repositories come to mind. [20:09:45] Like, if cldr is installed, then clearly X won't be used? [20:09:48] Hm. [20:09:55] You could disable uploads, that might disable a bunch of code [20:10:12] (uploads may or may not be disabled by default) [20:11:20] as far as I can tell, its disabled by default. [20:12:35] so I can try uploading a bunch of different file formats and see what I can get :) [20:13:38] malaverdiere: Preprocessor_DOM and Preprocessor_Hash classes are mutually exclusive [20:14:12] malaverdiere: only one of them is used depending on configuration. one of them is usually much more performant than the other, depending on the system configuration [20:14:37] MatmaRex, cool - and do you know remember what is that option? otherwise I'll start grepping [20:14:39] (see Parser::__construct for the logic used to choose one) [20:14:56] Documentation is also hard. :P [20:15:23] don't tell me about it - I suuuck that documenting stuff [20:16:25] (Wikipedias actually recently switched from _DOM to _Hash, since the latter is faster under HHVM, and the former under Zend PHP) [20:17:46] :'( [20:19:21] that's the line - $conf['preprocessorClass'] [20:20:20] since I've tested only on zend vm, that means I didn't use _Hash [20:20:38] I want to get the absolute url of an image from 'File:foo.jpg', in a parser function. I can manually parse '[[File:foo.jpg]]' and then extract the src attribute from resulting text. However, does there exist a better way? [20:20:49] I wanted to know if the REST API was representing a lot of code on its own, or its really a thin wrapper over the rest of mw? [20:35:30] malaverdiere: "REST" is a strong word. [20:35:47] malaverdiere: The API is tying together a lot of code but I think is actually not too thick of a wrapper. [20:35:50] In most cases. [20:37:09] is there an automated test for it? [20:38:02] Errrm. [20:38:06] I don't know [20:38:46] I'm going to go with "no" [20:38:50] We have something for the upload API, I think, but not the rest of it. Maybe anomie knows something I don't. [20:39:36] I think there were some api tests [20:41:55] marktraceur, malaverdiere: Tests for code in includes/api/ are in tests/phpunit/includes/api/. Coverage isn't all that great in general, although ApiResult and ApiFormat* are well covered. [20:43:23] ok cool [20:43:27] thanks everyone [20:57:40] YES! this exists! [20:57:42] * spectralsun praises [20:57:47] my shit is on fire [20:57:50] well [20:57:56] i did an update and things are broken! [20:57:59] that is what mean! [20:58:04] please help me! [20:58:45] I updated from 1.16.2 to the latest [20:58:51] followed the guide, step by step [20:59:07] all the media data itself seems to be fine [20:59:14] but what is broken is special pages and user login [21:00:58] Hi spectralsun [21:01:04] marktraceur: hello! [21:01:08] your name is very familiar [21:01:09] You upgraded straight through 8 versions? [21:01:14] I guess so :\ [21:01:15] spectralsun: I'm in #openhatch with you probably [21:01:22] Or...something [21:01:30] nope, i think i saw you on github when i was crawling or something [21:01:32] it wasnt irc [21:01:34] anyway [21:01:35] #etherpad-lite-dev [21:01:37] yep [21:01:39] bingo [21:01:41] anyway [21:01:47] ill pm you some links... [21:01:49] spectralsun: Anyway! Try upgrading one version at a time [21:02:05] Going straight through can cause trouble I think [21:02:07] !upgrade [21:02:08] http://www.mediawiki.org/wiki/Manual:Upgrading [21:02:24] marktraceur: ok [21:02:37] i got the impression from the upgrade guide i could just upgrade to the latest [21:03:19] Hmm. [21:03:31] spectralsun: Can you enable debugging so we can figure out what kind of fatal is happening? [21:03:34] !debug [21:03:34] For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging [21:03:50] yep, one moment [21:04:25] Thanks! [21:04:28] its on [21:04:41] Warning: A skin using autodiscovery mechanism, Chick, was found in your skins/ directory. The mechanism will be removed in MediaWiki 1.25 and the skin will no longer be recognized. [21:04:42] is the start of it [21:04:46] then a lot of text [21:04:56] That's...not a warning [21:04:58] It's a fatal [21:05:01] Stupid MediaWiki [21:05:07] !fire MediaWiki [21:05:07] Please install http://getfirebug.com/ . It will help you to fix problems with your website. Use the console to see JavaScript bugs. Right click your page and pick "Inspect Element" to track down CSS problems. See also !console and !webinspector [21:05:11] lol ^ [21:05:18] spectralsun: Maybe you should remove the skin? [21:05:23] ye, ill try that [21:05:26] they are using monobook [21:05:31] so it should be fine [21:05:34] I see that, yeah [21:05:50] I mean, it means fewer options, and you might need to set a new default for people who had Chick enabled [21:05:56] But who likes those people anyway [21:06:15] haha, I don't think that will apply to this case [21:06:23] Looks like same issue with Modren skin [21:06:28] removing that too now [21:07:06] hmm [21:07:12] i removed modern but it still says [21:07:18] Warning: An old copy of the Modern skin was found in your skins/ directory [21:08:00] marktraceur: are teh old version the lower case folder y'think? [21:08:09] looks like there is monobook and MonoBook [21:08:13] Uhhh [21:08:17] I have no idea [21:08:21] mk [21:08:32] well [21:08:36] i copied over their old skins folder [21:08:41] maybe ill just try a fresh one [21:08:48] Good plan [21:11:50] ok that narrowed some things down [21:11:52] marktraceur: Fatal error: Call to undefined function wfLoadExtensionMessages() in /var/www/wiki.apparmor.net/extensions/ConfirmAccount/UserCredentials_body.php on line 10 [21:12:13] probably grab the latest confirmaccount extension? [21:12:20] Probably, yes. [21:12:26] :) [21:12:30] So begins the long tail of chasing error messages! [21:12:33] Goooood luck. [21:12:50] hey, it's what im paid to do ;) [21:12:57] if you treat it like a game, it's quite fun [21:23:48] marktraceur: well, updating the ConfirmAccount extension made that go away [21:23:53] now I'm just getting a blank page :\ [21:24:02] on the index too.. :\ [21:24:06] which was working before [21:24:43] Uh oh. [21:24:49] spectralsun: Check the webserver error log maybe? [21:32:40] !blank [21:32:41] A blank page or HTTP 500 error usually indicates a fatal PHP error. For information on debugging (including viewing errors), see . [21:35:54] Hi, i updated the version of my wiki [21:36:07] But looks bad: [21:36:19] http://wikimedia.org.ve/wiki/P%C3%A1gina_principal [21:36:28] any idea for fix it? [21:36:48] !burndown MediaWiki [21:37:37] uh