[02:31:59] * JeroenDeDauw autofixes legoktm [02:35:15] JeroenDeDauw: :D it's the best! [02:35:50] I'm working through https://codesearch.wmflabs.org/extensions/?q=DB_SLAVE&i=nope&files=&repos= mostly [03:42:53] is calling Parser::doBlockLevels() from a tag extension a bad idea? [03:44:25] Umm. Probably. Why would you want to do that? [03:45:26] keep in mind, that much of that sort of thing is done on the result returned by the parser function [03:45:27] i want to make a tag that accepts list items (`* foo` or `# foo`) and then does various things to the result of that list [03:47:35] So calling doBlockLevels is kind of like jumping into the middle of the parse process. It is probably not safe to do that on untrusted user input (unless you also untrust the results) [03:48:02] hm [03:49:08] i would more suggest fully parsing your list and than postprocessing that (keeping in mind that you have to be very careful post processing stuff after escaping since you can easily give yourself an XSS that way) [03:50:47] by fully parsing you mean have the extension call recursiveTagParseFully()? [03:50:58] or you mean hook into a later step of the process [03:51:27] Or that. RecursiveTagParse isnt quite full, but probably enough for your purposes [03:51:51] fully would be taking recursiveTagParse and running unstripBoth on it [03:52:56] recursiveTagParse() is what i'm doing now (and what the documentation recommends), but it doesn't expand lists [03:53:38] Oh hmm. Thought it did. I should check these things rather than just working from memory [03:54:40] hmm, the documentation for recursiveTagParseFully() does say that it can be called from an extension tag [03:54:46] that sounds promising [03:54:59] Yeah, i think thats what you want [03:55:47] if all else fails you can use $parser->getFreshParser()->parse( .... ) [03:56:00] but thats more a method of last resort [03:57:03] looks ok at first glance, we'll see what happens [03:57:05] thank you [10:34:04] @relay-on [10:34:04] Relay was enabled [10:34:04] @token-on [10:34:04] New token was generated for this channel, and it was sent to you in a private message [14:07:10] hi [14:08:01] i wrote same information again and again on my page [14:08:13] i want to delete one of them [14:08:35] but need to contact with someone [14:08:40] how can i find?\ [14:10:36] farid, ? [14:10:57] farid, Hi, it is unclear what you mean, please elaborate. [14:11:18] i wrote same information twice on my page [14:11:26] and i want to delete one of them [14:11:27] farid: If you for some reason want to change some content of some website on the internet, you need to contact the maintainers of that website. [14:11:33] and "your page" is what? [14:11:41] wikipedia page [14:11:49] Which of the 300 Wikipedias? [14:12:25] farid: In general, feel free to edit the page if you want to edit the page. If you cannot edit the page you need to explain why you cannot edit the page. [14:13:04] thanks [14:13:52] farid: And whatever Wikipedia you refer to, that Wikipedia community might have some rules. You may want to check them too. [16:59:53] I have a simple CSS skin for MediaWiki 1.14 and I'd like to update it to achieve the same look on MediaWiki 1.23.6, can anyone please be of assistance? [17:16:30] Stilett0: Which kind of assistance do you need? [17:16:40] Also note that 1.23 is an old unsupported insecure MediaWiki version. [17:37:08] Hi, when I changed language of my hosting wiki e-balkan.tk and runned update.php script, I have error Fatal exception of type MWException. Version of mediawiki is 1.31 [17:37:29] !debug [17:37:29] For information on debugging (including viewing errors), see https://mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging Also see https://mediawiki.org/wiki/Manual:Errors_and_symptoms [17:37:50] Zoranzoki21: see above for how to flip on debug message logging/display and report back with the error message you get after doing that [17:38:02] Skizzerz: Will do [17:38:30] ($wgShowExceptionDetails is what you're after at a minimum) [17:38:56] Warning: fopen(/var/www/html/wiki/cache/l10n_cache-sh.cdb.tmp.872255073): failed to open stream: Permission denied in /var/www/html/wiki/vendor/wikimedia/cdb/src/Writer/PHP.php on line 50 [1861083f8fa46c41f15943ee] 2018-07-27 17:38:34: Fatal exception of type MWException [17:39:22] Which chmod I should set for cache folder? [17:39:26] ok, so it sounds like the user account you're running update.php as doesn't have write access to that directory [17:39:35] I run as root user [17:39:38] uh [17:39:59] ok was update.php erroring or was it erroring when you visit the website AFTER running update.php? [17:40:15] I updated default language. I runned update.php [17:40:23] After that, I have errors [17:40:31] when visiting the wiki on your browser? [17:40:33] Yes [17:40:35] ok [17:40:44] Here you can see: http://e-balkan.tk/wiki/ [17:41:02] ls -l in your wiki directory and let me know what the entry is like for "index.php" [17:41:17] in particular the owner/group [17:41:38] we'll need to reset some things to fix the permissions [17:41:47] https://pastebin.com/f1CRUxiE [17:42:17] k all of that looks kinda wrong tbh [17:42:32] running apache? [17:42:47] Yes [17:42:56] what OS/distribution? [17:43:07] Debian [17:43:20] Hello everyone [17:43:41] I have a question regarding Wikieditor. I recently updated to 1.31.0. Can I somehow bring back previewing in WikiEditor? [17:44:17] Skizzerz: Debian 9 [17:44:58] Zoranzoki21: ok, run chown -R www-data:www-data /var/www/html/wiki/cache [17:45:42] and triple-check that you have the path right before submitting; you'll brick your system if you accidentally run that on the root directory [17:45:50] metalhead33: previewing? Isn't there a "preview" button? [17:46:03] Skizzerz: Everything works now. Thank you! [17:46:12] Vulprix: There is no preview button anymore. [17:46:25] It is said that this was removed in the 1.31.0 release of WikiEditor, which deeply saddens me. [17:46:31] Is there any known workaround to bring it back? [17:46:34] Zoranzoki21: I also recommend as a security precaution the following: chmod 640 LocalSettings.php and chgrp www-data LocalSettings.php [17:46:38] metalhead33: paste a screenshot here: https://snag.gy/ [17:46:46] right now your db passwords and such are world-readable [17:46:52] so other users on the system could in theory grab them [17:47:03] I have wikieditor on 1.31 and I have a preview button [17:47:22] Oh wait, that does exist. [17:47:23] those commands set them to user and group readable only, and then grants www-data (which is the user account apache runs as) access to read them by setting the group to that [17:47:29] Yes, I just noticed it. [17:47:51] Strange, earlier on, I remember there being another preview button, at the top too, not just the bottom. Weird. [17:48:21] Skizzerz: Ok, thank you very much [17:48:35] metalhead33: I haven't seen it before. Maybe you were using a custom script or gadget? [17:49:18] Vulpix: On earlier WikiEditor, I remember there being two ways to preview one's work. Maybe it was a custom script then. [17:49:58] I think "live preview" was removed (which automatically updated the preview as you typed) [17:50:08] it didn't work particularly well iirc [17:50:36] Yes, I was talking about live preview, yes. [17:55:06] I though LivePreview was the same preview but with ajax (without reloading the page), not preview as you type. In that case I understand why it was removed... that would be pretty resource-intensive for the server [17:55:57] So sad. [17:59:58] Vulpix: maybe? I used it all of once [18:00:07] so I don't recall exactly [18:00:39] looks like you're right [18:00:54] metalhead33: you could look into setting up VisualEditor perhaps [18:01:04] I already set it up.