[00:08:54] hi [00:08:58] anyone around [00:09:22] i restored deleted revision of a page but revision not showing in history of page. why [00:34:38] does anyone know what feature allows "Prevent editing own user talkpage while blocked" [00:34:59] that sounds evil [00:35:04] I see it in Special:Block on one of the wikimedia wikis, but I cant seem to find it while blocking in my vagrant install [00:37:04] Withoutaname: $wgBlockAllowsUTEdit perhaps? [00:37:25] I believe if talk page editing is always disabled, then you don't get an option in Special:Block [00:37:42] hm, I think that should be disabled [00:38:20] I'd be a fan of setting it to true by default [00:38:56] sounds good to me, too [00:40:37] my concern is, if it was disabled would it affect any existing blocks on itwiki, which has it set to false [00:41:15] otherwise I can pull some code from CleanDeleteReasons and modify it as a gadget for the itwiki fellows to always set true when blocking [00:43:25] hmm. /me doesn't know if it affects existing blocks [00:43:32] for reference (PS1) Brian Wolff: Set $wgBlockAllowsUTEdit = true; by default [core] - https://gerrit.wikimedia.org/r/139654 [00:45:12] it was discussed briefly in https://bugzilla.wikimedia.org/show_bug.cgi?id=28288 [00:46:19] Just checked, it doesn't seem to affect existing blocks [00:46:31] ok that's good [00:50:00] Ok. Now to let that patchset sit there unnoticed for the next 6 months [00:56:06] bawolff: don't you have to do a public beta [00:56:23] and set up a page for people to write feedback on [00:56:59] and then ignore any feedback criticizing your approach as fundamentally flawed because it overrides any normal user preferences [00:57:30] SamB: Don't forget, I need a "slide-deck" to explain how this change benefits the unheard voices of readers [00:57:39] yeah [00:57:55] bawolff: how come my common.js isn't highlighting js [00:58:11] i hit tab and instead of creating tabs it skips to the summary box [00:58:38] !e CodeEditor [00:58:38] https://www.mediawiki.org/wiki/Extension:CodeEditor [00:59:09] also you need to set $wgCodeEditorEnableCore [00:59:16] not sure why that's not default [00:59:34] that should be core, because it's difficult to write a custom user:admin/common.js page without indents [01:00:22] Personally I find it doesn't work that well, and the cursor gets separated from where its supposed to be [01:00:31] * bawolff always turns it off when editing site js [01:01:33] At the very least, it probably should be in the default extension bundle that comes with the installer [01:01:52] * bawolff also is weird and dislikes syntax highlighting, and finds it super distracting [01:02:12] When we used to have the "external editor" feature, I used to use it to edit js pages in vim [01:20:29] bawolff: is $wgAllowUserJS set to false by default? [01:21:26] nvm [02:10:05] are there any skins that extend the skin class instead of skintemplate [04:47:21] would it make sense to declare skins as final [04:57:26] Yaron, good morning! It's alright, I know we have to wait sometimes. :) It was late night here in India when you answered so I slept. Well, thanks a lot I think I got the solution. :) [04:57:40] Cool. [05:05:10] Yaron, this is my database design http://202.164.53.122/~albertcoder/images/photo%201.JPG Suppose I wish to display all the properties of Iron say melting point, boiling point, density, tensile strength and so on... What do you suggest I should do? [05:05:27] so many joins? [05:05:56] Yeah, JOIN it up. [10:47:25] The database lock file is not writable. To lock or unlock the database, this needs to be writable by the web server. [10:47:33] Which database lock file? [10:48:51] It's MediaWiki 1.19.16 with PHP 5.4 and MySQL 5.5 [10:49:43] SPF|Cloud: what steps are you doing to get that message? a normal page view? [10:50:14] Vulpix: going to Special:DBlock [10:50:30] Special:LockDB* [10:50:36] that looks like an extension [10:50:45] !e LockDB [10:50:46] https://www.mediawiki.org/wiki/Extension:LockDB [10:51:07] Vulpix: It's default installed in MediaWiki 1.19.16 [10:51:17] A function of mediawiki core, no extension [10:51:59] never though this was part of core [10:52:12] It is ;) [10:52:58] I've tried already giving the DBuser all permissions on the wiki database, but that doesn't work [10:53:27] you never go to sleep without learning something new! :P [10:53:48] undocumented feature, as usual :( [10:54:43] Couldn't find any bug on bugzilla or something on mediawikiwiki [10:55:32] SPF|Cloud: I guess it would simply try to write to the path specified in https://www.mediawiki.org/wiki/Manual:$wgReadOnlyFile [10:55:50] you may need to make that file writable by the webserver [10:56:42] I'll try [10:58:00] Vulpix: thanks! [10:58:11] yw :P [10:58:35] The solution is to chmod the images folder to 777 [10:58:55] that's strange, I'm the creator of the wiki and I can't access Special:LockDB :S [10:59:28] Which version? [10:59:36] 1.23 [10:59:48] You need the right "siteadmin" for it [11:00:29] SPF|Cloud: where did you guess that? giving that there's apparently no documentation... [11:01:09] https://www.mediawiki.org/wiki/Manual:User_rights#List_of_permissions [11:01:23] under "Administration" [11:02:14] wow, Lockdb was there since 1.5 at least [11:02:35] what a hidden gem [11:04:38] Hmm... [11:04:48] No 775, 755, works. Only 777. [11:05:17] I guess it isn't safe to chmod the images folder to 777 [11:06:08] SPF|Cloud: indeed, that's not safe. You should edit $wgReadOnlyFile to point to a specific path not used for anything else, and give full permissions to that folder [11:08:33] I don't know how exactly works that special page. $wgReadOnlyFile won't lock the DB if the file is empty, so assuming that the special page blanks the file instead of removing it when unlocking, you could add permissions just to the specific file and not the folder [11:30:21] on trying to run install.php for the checkuser extension I get this error: >Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in commandLine.inc on line 32 [11:31:20] tried to edit that line but it still results in that error [11:33:48] oom: what PHP version are you using for command like? try php --version [11:33:56] https://groups.google.com/forum/#!topic/wikiteam-discuss/OdCm7hLEfMc [11:34:14] Yaron, I saw the logs of this channel are not continuous. I asked you something later(5:10 IST) which is skipped in the log. Earlier to I noticed this. [11:34:49] Vulpix: ah, it's below 5, so that must be the reason... [11:35:36] oom: yes! you probably have php 5 on another path of your server, you may try using "php5" or look for another php binaries on the server [12:47:57] hello I'm retrieving data from openstreetmap which has tags as "wikipedia": "de:Badenburg_(Gießen)". I don't know wikipedia api very well, but I think these are called "interlanguage links". Can I use them to retrieve a wikipedia page content? For example "&titles=de:Badenburg_(Gießen)" [12:50:22] zPlus: the 'de' part defines the language, for example "de:Badenburg" would mean the article "Badenburg" on de.wikipedia.org [12:50:46] zPlus: and it seems that you have broken encoding somewhere, 'ß' doesn't look like correct German to me :) [12:51:04] it's probably Gießen [12:51:30] zPlus: note also that the language code might contain hyphens '-' in addition to letter 'a-z' [12:51:30] yeah [12:51:31] https://de.wikipedia.org/wiki/Badenburg_(Gie%C3%9Fen) [12:58:29] so I have to handle that string myself (split at the colon and use the first part as url prefix and the second part as suffix). There is no way I can just call wiki api with a "interlanguage link" and let it return the corresponding content? [13:02:53] zPlus: yes. every wikipedia's API only handles the articles on this wikipedia, the language editions are independent [13:03:17] ok thank you guys [13:03:20] if you pass "de:Badenburg" as a title on, say, the english wikipedia, you'll just get an information that this is an interwiki link [13:03:25] https://en.wikipedia.org/w/api.php?action=query&prop=revisions&titles=de:Badenburg&format=jsonfm [13:04:27] thank you mahatma [13:16:03] ah btw using the interwiki link at the correct wikipedia instance seems to work just fine https://de.wikipedia.org/w/api.php?action=query&format=jsonfm&prop=revisions&rvprop=content&titles=de:Burg_Gleiberg [13:41:23] Hi! What's correct way of obtaining current page action ('view', 'edit', 'purge' etc) via ResourceLoader mw moodule? [13:43:43] Found myself: mw.config.get('wgAction') [13:46:35] yes. :) [13:49:43] :) [14:27:22] Hi Guys [14:27:37] Any PHP experts with MediaWiki here? [14:28:41] This extension http://www.mediawiki.org/wiki/Extension:WYSIWYG is causing trouble with some ADSENSE plugin, on www.musicwiki.nl .... when i edit an article the adsense code shows up as plain text with this WYSIWYG editor [14:28:44] MusicWIki: what's your question? [14:28:50] Oh nevermind. [14:30:04] how could i solve this problem , so the wysiwyg editor doesnt cause the adsense code to show up in articles anymore [14:30:16] MusicWIki: The WYSIWYG extension isn't maintained at all [14:30:20] What version of MediaWiki? [14:30:25] lemme see :) [14:30:30] 1.17.0 Reedy [14:30:34] MediaWiki 1.17.0 [14:30:41] I would try Extension:VisualEditor in this case [14:30:44] Scary [14:30:50] !e VisualEditor [14:30:51] https://www.mediawiki.org/wiki/Extension:VisualEditor [14:31:12] Lemme try =D [14:34:15] when i download it , it asks me to choose a mediawiki version, but i cant find 1.17 [14:34:20] https://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor [14:35:29] Didn't notice that. I'm afraid the extension isn't available for MediaWiki 1.17, sorry, [14:36:20] ill try to use the current version on 1.17 [14:36:56] It will be likely it breaks MediaWiki, but I'm not sure. [14:38:10] So i'll beter find another plugin anyway? [14:38:22] http://www.mediawiki.org/wiki/Category:WYSIWYG_extensions [14:38:33] There really isn't much option [14:38:40] You're using a really old version of MediaWiki that isn't supported [14:38:54] You should be looking to upgrade to something that is [14:38:57] I can't manage to get it updated to the newest version [14:39:08] Are there errors? [14:39:10] yes [14:39:27] have tried it, but it takes lots of time [14:39:33] We can probably help you with those more easily than fixing Extension:WYSIWYG ;) [14:39:42] but it's working now, except the wysiwyg :P [14:39:44] Have you read and searched on https://mediawiki.org and found nothing? [14:39:49] yeah [14:40:21] Have you a screenshot or something like that? [14:41:04] not really, i reverted it with a backup [14:41:14] i'll try to get the editor fixed first [14:41:17] If that works [14:41:20] then there is no need for me to upgrade [14:41:21] Okay :) [14:43:07] Your wiki is now broken :p [14:48:12] yeahxD [14:50:45] well the only working extension is WYSIWYG [14:50:54] but that causes trouble with the adsense code [14:50:57] plugin [14:51:13] somehow... [14:51:24] MusicWiki: 1.17 is too outdated, better upgrade it to 1.23 or newer. You'll get compatibility with new extensions. [14:51:35] By the way, when you would consider upgrading: some of the extensions used aren't compatible with 1.22 or 1.23 [14:52:10] i use lots of extensions [14:52:19] MusicWiki: However be aware that Parsoid requires VPS or dedicated hosting. But these are cheap nowadays. [14:53:34] Iit's working fine now, the only thing that isn't is the editor, so I think it's better and takes less time for me to fix that one issue [14:53:49] it really pisses me off lol [14:54:07] I don't have edit access so I can't see the error :p [14:54:27] i can give you :D [14:54:39] MusicWiki: VisualEditor is a bigger issue that upgrade to 1.23. VisualEditor for wikitext is very complex thing. WMF already writes it for years and it is still beta. [14:54:59] MusicWiki: It's much harder to get it running in 1.17 [14:55:02] i don't use visual editor [14:55:09] MusicWiki: read your private message list. [14:55:18] http://www.mediawiki.org/wiki/WYSIWYG_editor [14:55:28] oops wrong link]\ [14:55:50] this one http://www.mediawiki.org/wiki/Extension:WYSIWYG [14:56:01] it works fine [14:56:06] but causes trouble with my adsense plugin [14:56:14] when i edit a text, the adsense code shows up as plain text [14:56:57] Would you have problems with switching to another extension? [14:57:26] no, but there isn't another extension for 1.17 :P [14:58:13] http://www.mediawiki.org/wiki/Extension:MeanEditor [14:59:12] https://github.com/jacopo/meaneditor/tree/mw16 Don't know if this can help (because of the mw 1.16 branch, it is possible it'll give errors) [14:59:25] Documentation listed at http://www.mediawiki.org/wiki/Extension:MeanEditor [15:02:51] trying it now :) [15:02:56] at least wiki did not crash haah [15:03:53] aww Fatal error: Call to a member function registerWatcher() on a non-object in /home/musicwiki/domains/musicwiki.nl/public_html/includes/parser/Parser.php on line 191 [15:04:09] Hum. [15:04:32] When do you get this error? While editting? [15:04:45] yeah [15:05:28] http://www.mediawiki.org/wiki/Extension:WikEd is the latest hopefully working solution without upgrading, but it's not really an extension. It's a script. [15:05:40] i tried :P [15:05:46] it uses the gadget extension [15:05:54] that isn't compatible with 1.17 [15:06:10] The extension Gadget isn't really required for it. [16:17:01] how do I revert vandalism on a translation page? the normal undo/rollback actions don't seem to work [17:12:55] In the languages/i18n/en.json file, what does the $1, $2 represent ? [17:16:00] rohan_: they're parameters to be replaced when those messages are used on the interface. The value of them depends on the message [17:17:31] Vulpix: Yeah i thought so too, but on testing i found that it just prints $1 rather than its value [17:17:57] that's a bug, then [17:19:42] i will check it out then [17:47:25] Would anyone care to help? [17:48:00] !ask [17:48:00] Please feel free to ask your question: if anybody who knows the answer is around, they will surely reply. Don't ask for help or for attention before actually asking your question, that's just a waste of time – both yours and everybody else's. :) [17:48:14] Ahh okay [17:48:35] Well I've been trying to create a theme for my site because another part of my site that's not a wiki uses this theme [17:48:47] I've followed the Manual on the site [17:49:03] and now I get this error Fatal error: Using $this when not in object context in /home/u256988678/public_html/wiki/w/skins/antique/antique.php on line 55 [17:49:09] Line 55 is for the logo [17:49:23] but it doesn't really matter because when I remove it, it just goes to the next $this [17:52:25] well I guess no luck :| [17:53:46] Snowstormer: You can not use $this in a static (or statically called) method [17:53:57] Yes I know this [17:54:09] but I just copied code from the manual, so don't blame me [17:54:15] and the manual had $this [17:54:23] and I tried replacing $this with something else [17:54:32] but then it just gave me another error [17:55:07] Fatal error: Call to undefined function wfMessage() in /home/u256988678/public_html/wiki/w/includes/Linker.php on line 2075 [17:55:08] that one [17:55:15] Snowstormer: which part of code is this, exactly? [17:55:18] uhhhh [17:55:21] Line 55? [17:55:23] what version of MediaWiki are you running? [17:55:33] 1.23 [17:55:49] Line 55 is the header code, which is from MonoBook [17:55:50] echo Html::element( 'a', array( [17:55:50] 'href' => $mklist->data['nav_urls']['mainpage']['href'], [17:55:50] 'style' => "background-image: url({$mklist->data['logopath']});" ) [17:55:50] + Linker::tooltipAndAccesskeyAttribs( 'p-logo' ) ); ?> [17:56:03] the $mklist is supposed to be $this [17:56:07] I just replaced it [17:56:54] line 55 specifically is this, 'href' => $this->data['nav_urls']['mainpage']['href'], [17:57:06] and it gives the error because it's the first place where $this exists [17:57:24] Snowstormer: this looks like you pasted the code in some entirely wrong place. can you pastebin the entire skin file (or files)? [17:57:38] might be so [17:57:55] because I copied over the code from my site + added the theme code [17:58:41] how does git review know which bug's patch i uploaded ? [17:59:09] rohan013: https://www.mediawiki.org/wiki/Git/Commit_message_guidelines [17:59:12] http://pastebin.com/27nq0PLN [17:59:31] that's the code for the main skin .php file [18:00:57] Snowstormer: all of the HTML in this file should be part of the SkinAntique class (or AntiqueTemplate, assuming you have one), which the code says is defined in Antique.skin.php [18:01:05] which tutorial are you using? [18:01:18] https://www.mediawiki.org/wiki/Manual:Skinning [19:53:34] I have a wiki running MediaWiki 1.23.0 and PHP 5.3.28. When trying to upload a file, I get the following error: : failed to mkdir "/public_html/1.23wiki/images/b/bc" mode 0777 [Called from wfMkdirParents in /public_html/1.23wiki/includes/GlobalFunctions.php at line 2625] in public_html/1.23wiki/includes/debug/Debug.php on line 303 [19:53:59] I've already searched for a solution and discovered this is a known problem. But still I can't solve it [19:55:17] additional debug information: De map "mwstore://local-backend/local-public/b/bc" kon niet aangemaakt worden. (translation: The directory "mwstore://local-backend/local-public/b/bc" couldn't be created.) [19:57:38] chmod 755 or chmod 775 or chmod 777 doesn't work [19:57:45] Someone have got another idea? [20:19:50] send it to a different dir? [20:20:21] SPF|Cloud: you need to make sure your root uploads directory (images) and all sub directories are writable [20:21:10] chmod 777 -R? [20:50:06] Hey, could anyone please tell me how is best to edit the html header (as displayed on a tab) for a main page? For example, Wikipedia's main page is Main_Page but the title is "Wikipedia, the free encyclopedia" [20:53:20] abc_wikis: doesn't every page on Wikipedia have that in the title? [20:55:38] SamB: every other page has the regular page title (i.e. the article title) followed by that, if anyone knows how to do that too, it would also be helpful (rather than just the regular page title)! [20:57:22] I think it might be MediaWiki:Tagline? [20:57:50] abc_wikis: take a look at https://www.mediawiki.org/wiki/Manual:Interface/Pagetitle [20:59:20] legoktm: thank you very much! [21:22:42] jayvdb: does pwb store the API responses in memory or does it write to disk sometimes? [21:23:14] With direct API access we sometimes have MemoryError upon XML downloads bigger than available memory. [21:30:59] Nemo_bis: if the api call uses api.CachedRequest, it will write to the disk [21:32:22] legoktm: in pwb that is? [21:33:06] yes [21:36:33] thanks [21:40:49] Nemo_bis: I'm reporting about the Italian Wikipedia and Wikidata (on people) right now [21:40:53] I hope you like it [21:41:45] Amir1: I'll sure like it :) but reporting what? [21:42:18] Nemo_bis: on two things: 1-conflict of dob or dod [21:42:28] https://www.wikidata.org/wiki/User:Ladsgroup/Birth_date_report/Conflict_with_Wikidata/it/1 [21:42:44] 2- if the date exists in it.wp but not in Wikidata [21:43:49] Ah, dates, that will be useful [21:43:50] https://www.wikidata.org/wiki/User:Ladsgroup/Birth_date_report/No_Wikidata/it/1 (warning: this report is about to change) [21:44:03] I had seen the other reports but they are too many na dtobig [21:44:10] horrible lag sorry [21:44:54] will check them tomorrow morning :) [21:44:54] yes, there were some issues I fixed them [21:45:02] cool :) [21:45:18] oh great [21:46:06] then we'll continue with missing recent dates and all the other countries we first skipped, I guess :) [21:48:10] Nemo_bis: sure [23:20:16] how do i get the job queue to be processed async? [23:20:30] is it automatic? or should I unset wgJobRunRate [23:21:12] By default, it should be [23:21:44] You can "improve" it further by them not being spawned by web requests [23:21:44] Setting $wgJobRunRate to 0 [23:22:03] !wg JobeRunRate [23:22:03] https://www.mediawiki.org/wiki/Manual:%24wgJobeRunRate [23:22:08] probably has instructions [23:22:47] !wg JobRunRate [23:22:47] https://www.mediawiki.org/wiki/Manual:%24wgJobRunRate [23:43:01] awesome thanks bawolff and legoktm [23:43:07] and Reedy :) [23:44:22] Reedy: so if i set it to 0, i then have to schedule the runJobs.php from cron or something? [23:45:00] Yup