[03:32:10] question: is it a poor practice to write access tokens to cookies? [03:34:37] (oauth access tokens, namely) [03:51:27] Is doing that supported by some library or framework? [03:51:39] It sounds like you're working around some other problem. What's your real question? [10:28:28] Crazy things Confluence people do http://webmasters.stackexchange.com/questions/86937/render-external-page-content-via-rest-call/89947#89947 [13:52:13] hi [13:53:13] I am a student and have some questions about mediawiki customizing [13:53:29] Can anyone help me? [13:53:39] How do I block a user from inside PHP? [13:53:46] Is there a maintenance script or something? [13:54:21] Or do I have to do a direct database query to the ipblocks table? [13:54:56] imnick: Just ask! [13:55:39] thanks [14:02:53] Currently each individual wiki pages can be locked or unlocked. Is it possible to do this templete by template? [14:03:08] For example, is the administrator able to make a specific template that can be locked in a wiki page? And if this is possible, which files and which classes do we have to change to do so? [14:05:22] What you are talking about is called section protection. https://www.mediawiki.org/wiki/Extension:ProtectSection aimed to allow this. [14:05:33] In theory this allows a user to protect one section of a page so that unauthorized users cannot change it. [14:05:54] In real life however, there is not really a way to actually enfore such mechanism. [14:06:19] Such functionality is what you would normally use a CMS for - and MediaWiki is no CMS. [14:06:57] There most likely always will be a way around such protections. [14:07:44] Depending on your use case, you can however add things to the wikitext of a page in such a way that the users cannot influence this adding at all. [14:08:28] E.g. there are hooks, which allow you to modify the wikitext before it is rendered. This modification happens in PHP - wiki users cannot influence what is happening there. [14:09:15] That way it e.g. is possible to always have a certain text at the top of a page; without the user being able to change that. [14:09:42] Thank you so much! I'm reading it! [14:24:19] Coming back to my question "How do I block a user from inside PHP?": [14:24:38] I guess it is a good idea to just use class "Block" and to go from there: [14:26:42] Block::newFromTarget() allows to add a block with the according parameters. [14:27:52] Ahh, not to _add_, but to _show_ a block. [14:28:31] And if none is there, Block::insert() allows to _add_ one. [14:31:44] I'm currently experiencing a proble where "invalid magic word 'bidi'". Have rebuilt localisation cache. http://pastebin.com/EhPhJ0DS Any help? [14:35:14] hallo [14:35:17] Hi [14:35:22] Alter [14:35:24] lol [14:35:30] §4Hi [14:35:37] hmm [15:37:36] what do i need to do in order to duplicate Vector and rename the duplicate to Custom and play with it and leave Vector alone? [15:38:34] i'm not asking for your help in playing with it, but only for help duplicating and registering it. [15:45:10] by the way, found all the answers already [17:13:59] Oh, they enabled action=credits too :) https://wiki.documentfoundation.org/WikiAction/credits/Feature_Comparison:_LibreOffice_-_Microsoft_Office [19:39:13] has anyone had issues setting up a MediaWiki installation on nginx on ubuntu 14.04? I'm getting a blank white page when attempting to access the site, and I don't even get to set up the thing [19:46:21] !blankpage [19:46:21] A blank page or HTTP 500 error usually indicates a fatal PHP error. For information on debugging (including viewing errors), see . [19:46:43] teward: Are you cloning from git? If so, that can happen if vendor subdirectory is not up to date [19:47:04] Otherwise, enable php error logging [19:47:12] and check your php error log [19:47:36] bawolff using the tarball, have error logging neabled, and nginx intercepts the errors [19:47:53] and display_error on, in PHP, as it's a local testing environment [19:48:06] bawolff: i can't even get to setup to create localsettings :/ [19:48:17] poking #nginx to see if they can figure the nginx side [19:48:34] Hmm, and you don't get any errors even with php error logging enabled? That is odd [19:48:53] bawolff: indeed [19:49:09] just a blank, empty page [19:49:20] i've tried the nginx.org sample conf and one on the mediawiki documentation [19:49:34] teward: If you goto mw-config subdirectory (e.g. localhost/wiki/mw-config ), do you get any output [19:50:08] zip [19:50:15] so no [19:50:33] Other php things work though? [19:50:52] * teward drops a phpinfo file in to test [19:52:20] teward: do you have this? location ^~ /mediawiki/mw-config/ { internal; } [19:52:34] I guess you could add a bunch of var_dump( __LINE__ ); into mw-config/index.php to see how far into execution the script gets before dying [19:52:40] * bawolff doesn't know [19:53:07] RobotsOnDrugs: if you had answered my request for a config that works in #nginx i might [19:53:12] in any case [19:53:28] i was just looking over what i had and saw that [19:53:58] hmmm [19:54:33] looks like even a pure phpinfo file doesn't work. [19:55:20] ok. Probably an nginx/php problem then [19:55:24] indeed [19:55:38] * bawolff unfortunately does not know very much about nginx [19:55:56] * teward grumbles [19:56:06] this same config worked fine when i was running mediawiki a while ago [19:56:08] * teward grumbles [19:58:52] so, i need to set my rewrite rules for my MW installation [19:59:43] the wiki is located at http://rocketpedia.rf.gd [20:02:57] the directory to upload to is called htdocs [20:03:33] so, i need to set my rewrite rules for my install [20:03:48] we did this before [20:04:24] please help? [20:05:46] i don't know how to set this [20:07:58] please help? [20:09:52] please help me? [20:10:07] hello? [20:11:22] rocketmaster: which webserver do you use? apache2, nginx, ??? [20:12:01] um, i saw that the folder to upload files was called htdocs [20:12:22] some kind of Windows thing [20:12:43] nginx? [20:13:19] how did you setup the rewrite rules before? With a .htaccess file? [20:13:27] yes [20:13:47] ok. that is probably apache2 [20:14:26] htdocs means Windows, right? [20:14:54] not necessarily, no [20:15:14] have you looked at https://www.mediawiki.org/wiki/Manual:Short_URL ? [20:15:26] maybe you could see for yourself? [20:15:30] yes [20:15:43] i see only for root access [20:16:06] i tried the auto wizard, didn't work [20:16:37] https://www.mediawiki.org/wiki/Manual:Short_URL/Apache explains how to make rules in a .htaccess file [20:16:42] they must be running PHP, i installed Wordpress fine [20:18:00] i don't have root access, shared host [20:18:42] MediaWiki throws PHP error after I added my images shared wiki to $wgForeignFileRepos. You can see the error here: http://ru.autowiki.xyz/w/index.php?title=User:Nirvanchik/Test/Interwiki I checked the code and it looks like it really should not work. [20:18:46] http://rocketpedia.rf.gd/ responds with headers that indicate it is using nginx as the web server [20:19:59] They use $this inside of anonimous function. [20:20:24] that works with PHP >5.4 [20:20:29] or is it 5.5? [20:20:38] okay, how do i set it for nginx? [20:20:48] one or the other fixed the $this in anon scope problem [20:20:52] the software worked [20:21:05] i don't know [20:21:06] rocketmaster: good question. I'm googling. I don't use nginx often [20:23:25] it is 5.3 [20:23:41] okay, so... [20:24:07] how do i set rewrite rules? [20:24:32] oh, and going to the domain gives a 404 [20:24:53] i used an index.php file [20:25:04] I'll try 5.5 but I have some problems with it (hosting provider misconfig). Or I will have to write some patch :( [20:25:17] i installed the wiki under /w [20:25:53] Nirvanchik: It looks like you are running MediaWiki 1.26.0 so something that doesn't work with PHP 5.3 is certainly a bug [20:26:13] 1.27.0 is raising the min PHP version to 5.5.9 [20:27:11] wow. So I'm should be ready to switch to 5.5. thanks for this info! [20:28:00] now it's giving me error 500 [20:28:08] So, there's no sense to issue a bug (a ticket). With 5.5 no sense to fix. [20:28:09] rocketmaster: you may need to get help from your hosting provider. [20:28:43] bd808: it worked before! [20:28:53] ok! [20:29:04] I didn't break it :) [20:29:31] debugging a HTTP 500 response needs access to log files on the server [20:32:00] bawolff: i think i fixed it [20:32:13] bawolff: but I had to abandon a large portion of the PHP settings set forth in the MediaWiki docs, and nginx docs [20:32:39] and steal PHP settings from my wordpress site :/ [20:32:56] I don't think our docs have any suggestions for php settings (?) [20:32:56] YAY! It Worked! It Worked! [20:33:04] i set it up! [20:33:07] Which docs were you looking at? [20:33:15] i managed to do it! [20:33:25] woo! [20:35:00] bawolff: there's a section regarding getting shortlinks working, it was Google'd to obtain [20:35:08] but either way the nginx.org example linked to breaks just as easily [20:35:09] so... [20:35:12] * teward shrugs [20:35:16] i'll have to poke the nginx wiki [20:35:28] Some of the shortlink docs on mw.org are kind of old and unmaintained [20:35:35] bawolff: suggest:removal [20:35:37] :P [20:36:54] Well it is a wiki. Feel free to edit :P [20:36:57] :P [20:42:56] what's the page name to view version info? [20:43:19] like, what MW version you have? [21:07:10] Special:Version [21:53:28] i created the new skin, it complained about the autodiscovery issue, i moved the the Myskin.php file inside its corresponding directory, and now i'm left with two questions: [21:54:12] why are the other ones allowed to stay in skins/ without it warning me about the autodiscovery mechanism? [21:54:59] why does Myskin still fail to get listed on Special:Preferences? [21:56:45] jkale: Maybe you need a wfLoadSkin() call in LocalSettings.php [21:57:07] bawolff: 1.23 doesn't support wfLoadSkin() [21:57:27] 1.23 is old though :P [21:57:46] In the 1.23 case, you need a require_once( ); [21:57:48] I think [22:00:55] bawolff: the latest lts can't be old, can it? [22:01:16] jkale: The latest is 1.26.2 [22:01:34] 1.23 is apparently still LTS though [22:01:55] so I guess its not that old [22:01:58] bawolff: i think 1.26.2 is not an lts but just a ltst. [22:02:12] "ltst" as in "latest". nothing to do with "lts". [22:02:34] Next lts is 1.27 I think [22:03:00] oh i see what you mean [22:03:06] sorry, I misread what you wrote [22:03:13] np :) [22:04:18] Despite the fact 1.23 is an LTS release, its still quite a long time ago, and a fair bit behind current master [22:04:36] Yup [22:04:41] Many things changed [22:07:03] Reedy: when is 1.27 available? any estimate? [22:07:23] https://www.mediawiki.org/wiki/Version_lifecycle [22:07:26] May 2016 [22:19:04] Reedy: i simply duplicated the Vector skin. i guess "class VectorTemplate extends QuickTemplate {" was not the only thing i needed to modify. what other skin differentiators are there? [22:20:50] Reedy: i need the complete list of things i need to modify before i can call a forked skin mine. (is there a better way to ask this very question, by the way?) [22:21:21] I guess you should search for all usages of the vector text and evaluate if you need to change it [22:21:49] Reedy: yeah... it's used everywhere and it looks mostly decorative. [23:00:09] * White_Master .