in the wikitext and update that

if the user object has a valid ID. [16:18:19] Alright then, I'll have a look at that JavaScript solution. As far as I see, jQuery is available. This should make changing page content rather easy. [16:18:48] Joergi: you can use user groups for IDing logged in users [16:19:35] Betacommand: How so? What I want to know is, if a user is logged in... [16:20:04] wgUserGroups [16:20:34] if it contains "user" they are a registered user [16:21:30] Joergi: ah never mind, parser functions wont work [16:22:10] you would need to use javascript [16:22:11] That's what I think as well. A missing feature I would say. [16:22:25] Joergi: No, otherwise it kills caching [16:23:00] Joergi: what is your end goal here? [16:23:09] Not really as I would only have two different cases. The gender condition already has more. [16:23:41] It's simple: If the user is _not_ logged in, show a text. If he is, do _not_ show it. [16:24:22] Joergi: when using the gender parser function you reference 1 user and its static [16:24:33] thus caching is kept [16:24:50] Joergi: in your use case, I would use a span tag around the text [16:25:27] and for logged in users .display none [16:25:35] which hides that block [16:27:40] Joergi: and throw the hide JS code in [[MediaWiki:Group-user.js]] and its done [16:32:18] Betacommand: That sounds good. I guess you mean MediaWiki:Group-user.css instead of MediaWiki:Group-user.js, right? [16:32:38] That way it will be possible to directly hide the tag with CSS. No JavaScript needed at all. [16:36:48] Yeah, that's the easiest way as far as I can tell. So simple. [16:37:05] Simplicity is beauty. [16:37:18] Thanks for the help, guys! [16:47:41] Joergi: Yeah [17:35:06] o/ [17:35:24] Im trying to edit my Mediawiki:Common.css but Im getting an 404 not found error [17:35:35] is it possible that this file doesnt exist and I have to create it somewhre? [17:41:09] aelevadoan, a 404 error for which exact URL? [17:42:05] https://wiki.kefir.red/MediaWiki:Common.css [17:42:10] andre__: ^ [17:43:39] aelevadoan: your server seems to have problems with virtual URLs ending in .css [17:43:59] aelevadoan: compare https://wiki.kefir.red/P%C3%A1gina_principal and https://wiki.kefir.red/P%C3%A1gina_principal.css [17:45:26] Vulpix: where do I configure that? [17:46:04] I don't know, I have no experience with nginx [17:50:09] thanks for the tip though [17:50:12] I'll have a look into it [18:31:18] ashley: I finished a tally. 70% of the MW extensions I work on are closed source. :( [18:31:58] Trela: oh dear, so sorry to hear that :/ anything you can do to (try to) change that? [18:33:08] I just sent a huge proposal over to the director. About half of the closed source extensions could be immediately open sourced with no issue. We just haven't. The other half need hard company approvals and code review. [18:36:06] splendid, let's hope for the best :) open source is awesome since it allows other developers from the wider MW community to submit bug fixes, general stability/code quality patches and translations, for example [18:37:34] Yep. Some of them are just tiny helper extensions that we just never put out because we figured no one would want them. That is a silly assumption. [18:44:39] Trela: thanks a ton for working on this. Where is your code hosted? [18:47:22] Nemo_bis: Currently a mixture of github.com/CurseStaff and some of our personal GitHub accounts. Assuming the proposal goes through everything will be consolidated at github.com/HydraWiki. [18:48:07] We can't invite external people into CurseStaff because of the private repositories we host there which is why some extensions were hosted to personal accounts. [18:50:38] Oh, ok. A bit messy. :) [18:51:59] Very. Consolidating will be the key to making everything manageable and inviting community members to join the GitHub organization.(I would love to create an actual organization around this.) [19:32:53] Hey, it says I shouldn't use $wgUser in extension, so what's the correct approach to get user preferences? https://www.mediawiki.org/wiki/Manual:$wgUser [19:33:24] I did $wgUser->getOption( 'option ); [19:34:32] Get the user from the most appropriate context boject [19:44:13] hmm [19:44:17] Okay [19:44:23] let me see what I can find [19:57:57] by chance does anyone know a multifile upload extension for mediawiki that reads the local licenses you set on a wiki? [19:58:20] the Mediawiki:Licenses article I mean [20:06:00] hi. any roadmap or similar, when to expect the public release of 1.27? [20:06:22] https://www.mediawiki.org/wiki/Version_lifecycle [20:06:28] May 2016 [20:08:18] Reedy: thankyou. is there any other release until then, which works well with php7? [20:08:27] Nope [20:08:43] Why do you want/need to use php 7? [20:09:02] Noting, PHP 7 was only released about the same time as 1.26 [20:10:53] on archlinux, php is shipped in version 7. php5 is not supplied with updates anymore (at arch) [20:20:04] I wouldn't say that's an explicit reason to switch to php 7 [20:21:20] dropping support for php 5 would be quite silly (to put it *very* nicely) [20:21:35] there's still debate about whether to still support PHP 5.3 in the next release... https://phabricator.wikimedia.org/T118932 [20:22:45] 5.3 needs to die [20:22:56] RobotsOnDrugs: lol [20:23:56] RobotsOnDrugs: Then we find out tests are broken on php 5.5.9 due to a php/glibc [20:23:57] https://phabricator.wikimedia.org/T124574 [20:26:54] linux package maintainers are so braindead at times [20:27:23] we need old security-problem-infested patch versions because _______! [20:27:34] I think that's the crux of it [20:27:46] We shouldn't be encouraging people to keep using old outdated versions [20:28:38] decisions like this by distros are a big reason i avoid linux :S [20:29:14] Certainly upgrading php on windows is easy [20:29:46] probably [20:33:21] well guys, php7 is released since the devs regarded it production ready. not my decision. but seems to work with 1.26.2 so far [20:34:11] Do you know much of hte PHP release history? [20:34:15] anyway, thanks for the pointer to the lifecycle page and the otherhints [20:34:24] Most people don't consider it stable till the first, second or third point release [20:34:30] There's often major bugs [20:34:49] Reedy: fortunately not. trying to get rid of php whereever i can, but wiki-software seems to be in php mainly… [20:35:53] yeah, php isn't exactly the most well-written project out there [20:37:11] but a php-free web is far out of reach atm. anyway. stopping to complain/flame here. thanks all and nice start of new week y'all [21:15:24] Hi i have a question. I've setup mediawiki and mod rewrite for urls like Http://mywiki.com/Main_Page. that works and all but now ive enabled ssl on my server and each time i go to https://mywiki.com: it takes me to http://mywiki.com/MainPage no back to non ssl. how can i fix this? [21:22:04] use the right value for $wgServer in localsettings.php [21:24:25] But if i change it then it will alwyas be ssl? [21:25:58] it controls what links mediawiki generates [21:26:27] having https links is a good thing [21:27:12] Yeah but i don't want to force it [21:28:34] why not? [21:29:52] Well perhaps your right. Completly disabling http would be better and more securer [21:30:04] Thanks for the helps