[00:14:58] https://usercontent.irccloud-cdn.com/file/cW2ZcINl/help.PNG [00:15:04] does anyone know how to fix this [00:15:32] Cocopuff2018: Are you one of the developers for the Discord extension? [00:16:09] Nope [00:16:46] In that case, I suppose you can either report it to them, or consider writing a patch. [00:17:06] ok were do i report this to [00:17:07] the extension has a program problem and as such it is not compatible with the version of MW you are using. [00:17:23] Are you using the latest version of MediaWiki (MW) and Discord extension? [00:17:37] yes [00:17:42] http://neko.kazdel.com/index.php/Special:Version [00:18:50] Cocopuff2018: https://github.com/jaydenkieran/mw-discord/commits/REL1_35 [00:18:59] It seems this problem was already reported and fixed [00:19:18] Updating Discord extension should have you all good to go [00:20:25] ok any idea how i update the extension [00:23:34] That depends, how did you install it? [00:23:45] i am not sure how someone else did it for me [00:25:33] Cocopuff2018: OK, well, it looks like you have a git-based installation. so presumably you have a terminal access somewhere. You can find the mediawiki/extensions/Discord directory and then use git to fetch and checkout the latest REL1_35 from that repository. [16:26:44] hello, I just transferred a wiki to a new server and while on the old wiki the main page was addressed as "index.php?title=Main_Page" on the new wiki the main page is addressed as "index.php/Main_Page" [16:26:49] what am I doing wrong? [16:26:55] and is this a problem? [16:36:57] cloudcell: It's not a problem if pages load for you. You can use the old behavior setting this to false: https://www.mediawiki.org/wiki/Manual:$wgUsePathInfo [16:38:14] thank you Vulpix , I was just about to read this: https://stackoverflow.com/questions/49089224/trying-to-use-ugly-urls-with-mediawiki-install ... [16:39:08] both ways work, but I think I prefer 'pretty' urls now... I just thought there was something wrong... [16:40:25] If you want even prettier URLs, see https://www.mediawiki.org/wiki/Manual:Short_URL [16:40:46] thank you [21:13:01] I've been following the manuals for ResourceLoader, but my extension's scripts aren't being called properly. I checked the console on page load and found that it's just appending the value I set under packageFiles to the install path. https://pastebin.com/vVhTVuj5 is relevant section of extension.json, and I've tried using scripts instead of packageFiles, as well. Same result. [21:13:26] The manuals say that the formatting there is correct [21:13:56] I even tried relative paths "./resources/" but again, that's just appended to $IP [21:14:12] Are the manuals out of date? [21:15:15] Like I can make this work by doing "/extensions/MyExtension/resources/etc" [21:15:20] But that seems unintended [21:27:16] Have you set ResourceFileModulePaths? [21:27:21] "ResourceFileModulePaths": { [21:27:21] "localBasePath": "modules", [21:27:21] "remoteExtPath": "CodeReview/modules" [21:27:22] }, [21:44:36] No, I didn't. Didn't know I needed that one. [21:47:00] Might be worth noting that's a difficult addendum to find. There's only a small bit about it in https://www.mediawiki.org/wiki/ResourceLoader/Package_files#Module_definition_(extension), and I would've missed it entirely if I wasn't looking for it. [21:48:19] Yeah, you can do localBasePath/remoteExtPath in each.. but if they're all in common directories, it's not needed [21:49:47] Right. I just have one script I need to inject for this special page, and setting those did the trick [22:46:20] hello [22:46:28] !help [22:46:28] There are a lot of topics you could be asking about. Besides, this bot is mostly for experienced users to quickly answer common questions. Please just ask your question and wait patiently, as the best person to answer your question may be away for a few minutes or longer. If you're looking for help pages, we moved that to !helpfor. [22:46:45] i have questions [22:46:53] !ask | RodneyAraujo [22:46:53] RodneyAraujo: 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. :) [22:47:13] i dont have ansers, you should visit the Tyrell Corporation [22:47:45] what mean the tag "campaign-external-machine-translation"? [22:48:51] what means the tag "campaign-external-machine-translation"? [22:49:26] that's a good question RodneyAraujo. That tag does not have a description on https://en.wikipedia.org/wiki/Special:Tags [22:50:26] RodneyAraujo: it seems to be related to T212405 [22:50:27] T212405: Customize the editing experience when directing users from a translation - https://phabricator.wikimedia.org/T212405 [22:50:31] Okay, I finally figured out why this extension is so weird. The author started putting the messages into an i18n.php file, but then ended up using the MediaWiki namespace instead. Am I correct in assuming that wfMessage() will check the MediaWiki namespace for the relevant message before pulling from the available pool of internally defined ones? [22:51:36] jfolv: yes. message lookup first looks for a MediaWiki: namespace page with the name of the message and then falls back to the .js translation files. [22:52:08] jfolv: https://www.mediawiki.org/wiki/Help:System_message has more details [22:54:48] Will take a look; thanks! [22:57:26] other question: what means the cx campaign: "interlanguage-link"? [23:04:18] bd808 What means the "campaign interlanguage link"? [23:05:33] RodneyAraujo: T208399 describes "campaigns" a bit. I have no idea why anyone setup that particular campaign [23:05:33] T208399: Extend URL campaigns to be more customizable - https://phabricator.wikimedia.org/T208399 [23:06:52] bd808 the grey interlanguage links could be disabled? [23:07:34] RodneyAraujo: I do not understand your question [23:08:44] bd808 the grey missing interlanguage links can be disabled?