[17:25:26] anomie, might as well poke you in here instead of using Phabricator as a support platform -- sorry. [17:36:30] Hi. I went through the documentation present on this link : https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker. Would like to start contributing. From where should I start? [17:36:54] Interested in the development as well as the documentation sections. [18:09:27] Hi folks, I'm trying to import the mediawiki "Imbox" template into my own mw instance. However when I try to use it I just see {{#invoke:Message box|imbox}} [18:11:04] Ah, nevermind. I did some searching about "invoke" and found this explanation that I don't have the Scribunto extension (https://www.mediawiki.org/wiki/Manual:Using_content_from_Wikipedia#.7B.7B.23invoke:_...) [18:11:31] * OmSai once again does rubber duck debugging [18:14:33] you'll have lots of fun importing wikipedia content [18:15:20] RobotsOnDrugs: hehe... is really doable? [18:15:35] s/doable/practical/ [18:15:47] depends on what you want to import, but yes [18:16:00] some things are just annoying [18:16:18] once you get a feel for how it works, it gets easier [18:17:09] Is it easy to sane to try and all the images that go with the templates? [18:17:46] * OmSai thinks maybe not [19:40:20] saluton brion! [19:46:28] "Esperaaanto" (https://www.youtube.com/watch?v=TN3GzeaOZtc) [19:47:53] p/close [20:39:09] hello [20:39:41] upgrading from 1.23 to 1.25 I get the following error [20:39:43] PHP Fatal error: Interface 'Psr\Log\LoggerAwareInterface' not found in /var/www/vignalewiki/w/includes/libs/objectcache/BagOStuff.php on line 47 [20:39:53] (php update.php) [20:40:10] I'm a bit at a loss trying to find the source of this error [20:41:31] steko: did you download from git or tarball? [20:41:36] steko: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Fatal_error:_Interface_'Psr%5CLog%5CLoggerInterface'_not_found [20:41:39] Nemo_bis: tarball [20:42:12] that shouldn0t happen on tarball, though, unless you unpacked new files over the old ones and some files were missing... [20:42:14] Well that shouldn't happen [20:42:19] Either way https://www.mediawiki.org/wiki/Download_from_Git#Fetch_external_libraries [20:42:25] Vulpix: I need to use a better search engine :( [20:42:52] Or read documentation for things you did NOT do :D [20:43:15] This installation procedure is driving many people crazy, it's not just you [20:46:45] Nemo_bis: glad to hear I'm in good company [20:47:18] Vulpix: suggested solution is to get the vendor git repo, but I already have the vendor directory in my root [20:49:47] I unpacked in a new directory and copied only LocalSettings.php and images/ [20:54:46] it worked for me when I installed 1.25 from tarball... I hope 1.25.2 release isn't broken... well, I guess it isn't, otherwise the support desk would be full of such errors [20:56:05] Vulpix: apparently psr/log dependency is missing, after adding manually to composer.json it worked [20:58:45] (I removed the vendor directory and got it from git) [21:13:07] steko: psr/log is missing from the 1.25.x tarball? [21:16:54] legoktm: that was my impression, but no, it is there in vendor/composer.json [21:18:00] so it was there and you were still getting the fatal? wtf... [21:19:52] I've seen sometimes cases where there's some sort of PHP opcode caching in place which caches old php files... but 1.23 didn't had composer to fail that blatantly... [21:20:28] legoktm: on the other hand, Composer is only mentioned in the "Using Git" section on https://www.mediawiki.org/wiki/Manual:Upgrading [21:20:59] I thought I would need composer only to update some extensions, not core [21:21:41] Vulpix: psr/log was backported to 1.23: https://gerrit.wikimedia.org/r/#/c/203779/ [21:22:59] hmmmm, so maybe a php cache bug? [21:25:29] uhm, now for the record I also get this error: [21:25:31] [Wed Aug 19 17:24:29.334307 2015] [:error] [pid 1717] [client 82.215.162.23:62382] PHP Fatal error: Class 'UtfNormal\\Validator' not found in /var/www/vignalewiki/w/languages/Language.php on line 3040 [21:25:56] PHP Fatal error: Class 'UtfNormal\\Constants' not found in /var/www/vignalewiki/w/includes/title/MediaWikiTitleCodec.php on line 233 [21:27:11] I guess you'll get one error for each composer dependency [21:27:24] steko: does the directory vendor/wikimedia/utfnormal exist? [21:28:07] legoktm: yes, it's there [21:28:50] ok...this is weird... [21:29:18] what php version are you using? [21:29:19] wait [21:29:21] steko: it's feasible to restart your apache? in old computer science, that may solve things :P [21:29:56] Vulpix: yes it's feasible. [21:58:28] ah, skipping 1.24! I should have looked at the release notes for 1.24, too, you're right [21:58:55] in the 1.25 world, composer.json is exclusively for MediaWiki core's dependencies, and any extensions being installed through composer should go into composer.local.json [22:00:59] I'll update the docs to reflect this in a little bit [22:03:55] <[1]hypergrove> Hello, I have 3 skins loaded (Vector, Chameleon and Nexus) which are listed on Version page but I don't see them listed in Preferences... is this unexpected? [22:09:31] legoktm: thank you very much for your patience and kind suggestions [22:10:14] Vulpix is gone now but please pass my gratitude on [22:10:22] and Nemo_bis [22:21:44] <[1]hypergrove> Hello, I have 3 skins loaded (Vector, Chameleon and Nexus) which are listed on Version page but I don't see them listed in Preferences... isnt this an unexpected problem? [22:22:45] <[1]hypergrove> Vector and Nexus are loaded via require and Chameleon is loaded by Composer iirc [22:36:15] <[1]hypergrove> strange, as i am reducing the number of skins loaded, and when I eliminate halcyon (iirc it's another bootstrap variation) then the skins are not shown in Preferences.... with it in, they do .... what is going on? [22:40:53] <[1]hypergrove> i'm doubting this is a code problem, I just need to work it through -- there's duplicate skins being loaded, this bootstrap (uk) code is something of a mess [22:41:00] <[1]hypergrove> thanks for listening! [22:45:49] !access [22:45:49] For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [22:46:02] [1]hypergrove: welcome. If you do find something that could be improved to have (in particular) chameleon play nicely with other skins, raise an issue on phabricator. [22:46:43] !cms [22:46:43] 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. [22:56:18] <[1]hypergrove> FoxT, thank you, I have and certainly will continue to provide comments, suggestions and code changes (well, mostly for extensions) because this software of course, need I say it.... rocks! [23:03:00] <[1]hypergrove> question please. We want to have one skin if a user is not logged in, and then another default skin if the user is logged in... How does My LocalSettings find out? I note wguser is deprecated (mw 1.25..1) [23:03:34] <[1]hypergrove> but i have doubts the user object has been set at the point of LocalSettings [23:06:00] [1]hypergrove, the users can set a Skin in their preferences [23:06:16] you can use a hook on user sign up that assigns them the logged in skin [23:06:44] <[1]hypergrove> ok that's the trick, thanks [23:09:28] these 5 lines are all you need: [23:09:32] $wgHooks['AbortNewAccount'][] = 'fixupNewAccountSkin'; [23:09:33] function fixupNewAccountSkin($user, $abortError) { [23:09:33] $user->setOption( 'skin', 'monobook' ); [23:09:33] return true; [23:09:33] } [23:09:47] (change monobook for whatever skin you wanted, of course) [23:10:04] oh god [23:10:05] place the anon one in $wgDefaultSkin = 'wmes'; [23:10:05] no [23:10:12] Krenair, it's old code :P [23:10:18] Yes, I would hope it is :p [23:11:23] in fact, the wiki is still at 1.24alpha since the "let's change skin registration" broke the anon skin :( [23:15:24] <[1]hypergrove> getting a wholly unexpected msg: http://demo.myoffice.wiki/Special:Version [23:15:50] <[1]hypergrove> says nexus not loaded, but it is, per Skin list below that message [23:17:38] it says it's disabled [23:17:41] <[1]hypergrove> and the list of skins it (the message) shows is wholly inaccurate - chameleon (loaded via composer) is available ... oh, I guess it's scanning the skins subdir [23:17:45] you have it in $wgDisabledSkins ? [23:17:56] <[1]hypergrove> ah let me check that\ [23:18:28] I meant $wgSkipSkins [23:19:49] <[1]hypergrove> neither is set (grpped) but let me confirm [23:22:15] <[1]hypergrove> [wgDefaultSkin] => nexus [wgFallbackSkin] => fallback [wgSkipSkins] => Array ( ) [wgSkipSkin] => nothing [23:23:29] do you have a require to nexus? [23:23:34] <[1]hypergrove> yes [23:26:25] <[1]hypergrove> yes... require_once( "$IP/skins/nexus/nexus.php" ); [23:31:44] <[1]hypergrove> i see this in nexus.pho:p: $wgValidSkinNames['bootstrapnexus'] = 'Nexus'; .. is the skinname not 'nexus' but rather 'bootstrapnexus'? [23:36:27] <[1]hypergrove> when that is changed to 'nexus' then: [23:36:27] <[1]hypergrove> Fatal error: Class 'SkinNexus' not found in /var/www/core-251/includes/Setup.php on line 288 [23:39:06] <[1]hypergrove> i get the same error as ^^^^ when $wgDefaultSkin = "bootstrapnexus"; [23:43:57] <[1]hypergrove> indeed, SkinNexus does not exist - SkinBootstrap does, in the /skins/nexus folder [23:44:20] <[1]hypergrove> that sounds truly broken to me, any agreement? [23:46:33] <[1]hypergrove> ok i am going to do some surgery here to make nexus skin align with mw standard [23:51:04] Trying to figure out if I can call into the mySql database of media wiki and extract the text from a given page, or perhaps there is an experter plugin available somewhere for just that purpose???? [23:51:28] looking at the raw export its quite the jungle in there [23:58:53] ?action=raw is your friend