[04:48:46] I moved my wiki from one host to another and now when I try to view certain pages (MediaWiki:Common.js for example) it acts like I'm not logged in and clicking on login doesn't do anything? [04:58:56] Hi Zackary. [04:59:05] Is your wiki public? Can you provide a URL? [04:59:12] its not public [04:59:34] What do you mean by view certain pages? [04:59:48] Like going to https://example.com/wiki/MediaWiki:Common.js in your browser? [04:59:53] yep [05:00:15] What does acts like you're not logged in mean? [05:00:25] Like you don't see your personal tools in the top-right? [05:00:31] yep [05:00:45] and when I click on login in the top right it does nothign [05:00:47] *nothing [05:00:54] What happens if you visit another page on the wiki? [05:00:58] Is it only pages that end in .js? [05:01:01] works fine [05:01:04] Only pages that have "MediaWiki:" in them? [05:01:09] nah, theres also a file page that does it [05:01:26] What happens if you append "?1" to the URL? [05:01:50] nothing [05:01:55] Same behavior? [05:01:59] yep [05:02:19] You're saying this is also happening with some "File:foo.jpg" wiki page? [05:02:25] yes [05:02:35] Is it happening with any other file pages? [05:03:17] I don't know, since I don't have any other files on the wiki [05:03:32] also the file doesn't show up in Special:AllPages [05:03:49] Did you upload the file using the Special:Upload wiki page? [05:04:33] Or did you select "File" from the namespace drop-down menu on Special:AllPages? [05:04:59] That sounds like a separate issue either way. [05:05:32] The open question is whether you can reproduce the issue on another "MediaWiki:" page or another non-"File:" page. [05:05:38] o weird, if I go to /wiki/File:foo.jpg I run into it acting like I'm not logged in, but if I go to w/index.php?title=File:foo.jpg it works [05:05:39] idk if I uploaded it that way, its been a while, problly did it tho [05:05:39] yep, if I go to Special:AllPages, and select File from the dropdown it doesn't show up [05:05:51] I can't reproduce it on another MediaWiki page [05:06:05] Zackary: What about MediaWiki:Common.css ? [05:06:37] same issue, acts like I'm not logged in [05:07:00] If you go to Special:Contributions/yourUserName [05:07:11] And select "File" from the namespace drop-down menu and submit. [05:07:16] Do you see any File edits/uploads? [05:07:24] no [05:07:42] All right, well, I'd try an upload via Special:Upload. [05:07:44] And see if that works. [05:08:16] Does /w/index.php?title=MediaWiki.Common.js have the not logged in issue? [05:08:23] no [05:08:47] So just /wiki/MediaWiki:Common.js and /wiki/MediaWiki:Common.css ? [05:08:51] And /wiki/File:Foo.jpg ? [05:09:06] yes [05:09:12] But the index.php versions of all of those work fine? [05:09:16] yes [05:09:17] Sounds like you have a busted rewrite rule? [05:09:19] I guess. [05:09:36] huh, other pages like /wiki/User:username work tho [05:09:48] Right, it might be the extension? [05:10:02] I guess you could try User:Username.jpg [05:10:15] Or try MediaWiki:SomeFakeTitle.js ? [05:11:11] /wiki/MediaWiki:FakeFile.js also gives the issue [05:11:50] So in order for /wiki/Article_title -type URLs to work, you probably had to configure rewrite rules, probably. [05:11:56] That's in the Web server configuration. [05:12:12] My guess is that when you moved hosts, those settings went/got weird for URLs ending in file extensions. [05:12:46] is my .htaccess, I think it looks correct tho? https://www.irccloud.com/pastebin/fTvVRceL/ [05:13:54] !shorturl [05:13:54] To create simple URLs (such as the /wiki/PAGENAME style URLs on Wikimedia sites), follow the instructions at or try the new beta tool at . There are instructions for most different webserver setups. If you have problems getting the rewrite rules to work, see !rewriteproblem [05:15:31] Zackary: Are you using a directory named "w"? [05:15:37] yes [05:15:54] You moved hosts and the issue started happening? [05:16:00] yes [05:16:11] Did you copy over the .htaccess from the previous host? [05:16:15] And the application code? [05:16:18] yes [05:16:26] No upgrades, should be same code on both hosts? [05:16:33] yep [05:16:58] You're using Apache on both? Different versions of Apache? [05:18:43] Or maybe it's not the Web server. [05:18:54] It could be a rogue extension? [05:19:22] I dunno, it's difficult to debug over chat. [05:20:00] Apache 2.4.18 on the new host I can't find the version number for the old host but I'm pretty sure it was Apache too [05:20:28] Does the page "Special:Version" work on the old host? [05:20:35] It may list the Web server version. [05:20:47] theres nothing on the old host anymore [05:21:07] Do you know if this was an issue before? [05:21:09] On the old host? [05:22:10] no I haven't had issues with this before [05:22:11] SyntaxHighlight_GeSHi, WikiEditor, CodeEditor, Echo, CheckUser, MaintenanceShell, Maintenance, and AbuseFilter are the only extensions I have loaded [05:23:28] Zackary: You said it happens with "/wiki/MediaWiki:FakeFile.js" ? [05:23:33] yes [05:23:47] What about "/wiki/MediaWiki:FakeFile.fake" ? [05:24:50] idk, I've changed the .htaccess rules based on what the redwerks.org site gave me [05:24:54] and now I can view the pages [05:25:07] but it still acts like I'm not logged in [05:25:40] Right, isn't that the same issue you've been having this whole time? [05:25:56] Why do you say "now"? [05:26:38] before it replaced the whole page with "you need to login to view pages", but now I can view the contents of the page [05:27:19] You can view the contents without being logged in? [05:27:33] Have you configured the wiki to be that way? [05:27:49] I don't really understand what issue you're trying to solve at this point. [05:28:32] I can view the contents because I'm logged in, but the top right of the page doesn't show it on that page [05:28:46] the wiki is configured to not show anything until you're logged in [05:29:36] Hmmm, I don't think that's really how it works. [05:31:57] can you see http://twi.x10.mx/wiki/MediaWiki:Common.js ? [05:32:37] Yes. [05:33:02] what about http://twi.x10.mx/wiki/Main_Page ? [05:33:08] No. [05:33:26] But that's because MediaWiki:Common.js is explicitly whitelisted, I think? [05:33:38] !access [05:33:38] For information on customizing user access, see . For common examples of restricting access using both rights and extensions, see . [05:34:11] yep, thats what I do [05:34:13] $wgGroupPermissions['*']['read'] = false; [05:34:31] https://www.mediawiki.org/wiki/Manual:$wgWhitelistRead [05:35:50] huh, I don't have anything whitelisted [05:36:12] Is it set in include/DefaultSettings.php? [05:36:24] includes/DefaultSettings.php rather. [05:38:52] its set to false in DefaultSettings.php [05:40:29] I only see the issue at MediaWiki:Common.js [05:40:39] Every other page gives me "Login required". [05:40:49] Except Special:UserLogin [05:41:19] ye, except for MediaWiki:Common.js that's intended [05:41:36] Then there's no issue? [05:44:11] The MediaWiki:Common.js and File:Foo.jpg pages showing to users who arn't logged in and the page acting like I'm not logged in are the issues I have [05:46:23] It is curious. [05:46:57] That "/w/index.php?title=MediaWiki:Common.js" is "Login required", but "/wiki/MediaWiki:Common.js" shows the page contents. [05:51:53] ye [05:52:09] Zackary: You have a caching layer in front? [05:52:33] Varnish, I guess. [05:52:57] I don't have Varnish [05:53:00] but I do have $wgCacheDirectory = "$IP/cache"; [05:53:46] That .mx URL is responding with X-Varnish. [05:53:48] I think you have Varnish. [05:53:59] It's also listing an Age: for the resource and some other data. [05:54:10] I think this is a front-end caching problem. [05:58:04] huh, I tried clearing the cache with cloudflare and with x10's cachewall [05:58:17] also tried logging out and back in [05:59:27] "/wiki/MediaWiki:Common.js" says "Login required" for me now. [05:59:36] ye, but it also gives me that [05:59:39] and I'm logged in [06:00:26] !varnish [06:00:43] https://www.mediawiki.org/wiki/Manual:Varnish_caching [06:00:53] It sounds like you're inadvertently/unintentionally using Varnish. [06:01:07] And that's going to cause weird behavior if MediaWiki and Varnish aren't aware of each other? [06:02:08] would cloudflare do cache? [06:02:17] *do varnish [06:02:45] oh nice [06:02:47] Maybe. [06:02:55] I disabled x10's cachewall and now its working [06:03:51] Cool. [06:09:51] thanks for the help [06:39:54] No problem. [14:38:41] Hi, I'm looking for a way to de-alias the "Project:" alias to use for myself instead of it defaulting to meta pages. Is this possible? I've been looking up how for an hour but I haven't quite found a way [14:57:30] neochronomo: it's possible although you may break various bots/scripts that rely on it (nothing internal in mediawiki should break) [14:58:17] note that this is not a documented config var, so there is also no guarantee this will continue to work in the future [14:58:50] but in your LocalSettings.php, add $wgCanonicalNamespaceNames[NS_PROJECT] = 'Something'; and $wgCanonicalNamespaceNames[NS_PROJECT_TALK] = 'Something_talk'; (where "Something" is what you called your meta namespace) [15:01:55] (actually now that I look at it, that won't quite work; you'll need to throw that into a hook which runs early on in the process -- CanonicalNamespaceNames is initialized *after* LocalSettings is loaded) [15:02:27] putting it in $wgExtensionFunctions should do the trick [15:40:25] Hiya and thanks thanks thanks for the awesome wiki software [15:42:33] I migrated a Mediawiki without installing Composer at all but the wiki seems to be working fine so maybe there weren't any extensions that have dependencies but the next Mediawiki I'm going to migrate (to a different server) does have some things that were installed with composer [15:43:43] I wrote a blog post about the migration (partially for my own reference but I think it turned out quite useful to others too) https://byjuho.fi/2018/01/29/migrating-a-mediawiki-to-a-new-linux-server/ [15:44:32] I guess I will have to go through each extension's documentation and see if it has some dependencies (and install those with Composer) [15:44:45] jubo2: the composer thing is only needed if you install mediawiki by cloning the git repo [15:44:54] Skizzerz: ahh ok [15:44:54] if you downloaded and extracted the .tar.gz, composer is not required [15:45:06] No. I'm on the stable branch [15:45:14] I mean 1.30 [15:45:50] some extensions may require composer, it depends on the extension docs [15:46:06] the vast majority do not [15:47:15] (I typically recommend the tarballs for most users since it's easier to get set up originally, but if you have the technical knowledge to use git, cloning the git repo makes future upgrades a lot easier) [15:50:37] Next thing I'm going to do is install is the https://www.mediawiki.org/wiki/Wikibase client on http://develop.consumerium.org/wiki/. That way we can in an easy manner move on to actually providing some information by querying Wikidata database data with SPARQL [15:51:54] Should I go for the latest master? Is that safe? Is that maintainable? [15:53:49] the git repo has branches for all releases; I'd say run the stable releases for production wikis [15:53:55] e.g. the REL1_30 branch is 1.30.x [15:54:14] (there's also tags for each point release) [15:55:34] but say you're on REL1_30 and want to upgrade to 1.31? Change branches to REL1_31, cherry-pick any custom patches you may have, and run the updater script. This ensures you don't have any files lingering around that were deleted between 1.30 and 1.31. [15:56:01] With tarballs the advice is to extract the tarball to a new directory and copy over images/LocalSettings to avoid that lingering files issue, so this saves that effort at the expense of requiring git knowledge [15:58:40] also git requires dealing with composer, and composer is probably the worst package manager thing I've ever had the displeasure of working with from an ops standpoint... make sure to explicitly pass --no-dev when running the update command in composer as it assumes by default that you want to pull in a bunch of usually irrelevant dependencies, and this HAS caused security vulnerabilities in the past [16:12:18] Skizzerz: Can you please elaborate briefly how the 1.30 -> 1.31 upgrade goes if I have the 1_30 branch of Wikibase installed on a Mediawiki 1.30 because I don't quite understand what you are saying [16:15:38] change branches on core, migrate over custom commits, repeat for each extension that's in git as well (each extension is its own independent repo, and core is an independent repo), run update.php [16:15:50] (step 0 is "take a backup") [16:16:17] oh, and run composer update --no-dev on core before running update.php [16:16:28] although update.php will yell at you if you forget that step [16:17:21] And how to do this without Composer Skizzerz? [16:17:32] use the tar.gz files and ignore git entirely [16:17:55] https://www.mediawiki.org/wiki/Manual:Upgrading has details [16:18:37] I know how the upgrade process is for the core but not sure about extensions.. how to upgrade them [16:39:22] hello [16:41:19] jubo2: same as core. Run update.php after you're done updating core + all extensions [16:42:41] i am here to ask how to run php with putty [16:43:03] i write pwd and it says home/username and wont change cd [16:43:44] sometimes its not answering pwd as well [16:44:11] get a better internet connection [16:44:54] 100mb/ul i dont think it is my connection [16:45:20] if you're typing things and the other end isn't being responsive, that is indicative of one of two things: 1) network issues, or 2) CPU is maxed out on remote server [16:46:41] putty closes itself after second command it's rare but happens [16:46:56] i actually can't run php [16:49:17] run it in screen/tmux which should help prevent network issues from getting in the way [16:49:39] if you have no idea what I just said, I suggest looking online for guidance/tutorials on using SSH [16:56:21] I'm migrating antother MW today. Suggestion for the '? he;[ [16:57:04] I'm migrating antother MW today. Suggestion for the '? help' prompts I'd like to see length restrictions in additon to the illeagel characters and such.... [16:58:48] For instance I've created a db user name that was to long. some jquery validation on the length during entry would be cool. The form input box is way longer than the valid length too. [17:16:16] GumShoe: excellent suggestion, do you mind adding it to the tracker? [17:16:38] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/ [17:17:14] (leave "Assigned To" and "Subscribers" blank, and type "MediaWiki-Installer" as the tag) [17:29:13] howz this; https://phabricator.wikimedia.org/T185905 [17:34:02] Hi, I am using mediawiki. I had a multilingual wiki, now I'm trying to port to commons. I did the works and commons is running now. but when I am trying to login, when i change the page my session is removed and I'm not login any more. anyone can help me [18:42:32] Cool! Another mw moved and implementing short URLs. Now to integrate it's VisualEditor with existing install... [19:06:42] Anyone using multiple VisualEditor against a single parsoid server? Syntax for mwApis: do I just add multiple domain: lines to uniquely idetify each instance? Or is it an array or json or ??? [19:09:09] This page looks a bit dated https://www.mediawiki.org/wiki/Parsoid/Troubleshooting [19:13:58] i suppose wikimedia wikis do. although we also use restbase, which probably makes our config much mroe complicated [19:59:43] Remember just because you can edit VisualEditor setting in LocalSettings.php doesn't mean you actually installed the extension! ;-) [20:08:21] @Skizzer Are you a developer on mw? I enhanced the 'Linking with Parsoid' section of this page https://www.mediawiki.org/wiki/Extension:VisualEditor to clarify the config.yaml syntax for multiple sites using a single parsoid instance. [20:09:03] I added three lines begining with - # and another MediaWiki [20:19:07] thanks :) [20:19:16] mw.org is a wiki, so anyone is welcome to contribute [20:20:09] I maintain a handful of extensions and a bit of core stuff, but I'm not super active as far as development is concerned right now [20:20:22] do the docs get flagged for review? particularly as I just created that login today? I have edited en.wikipedia... sure can't remember my login though... [20:21:22] nah, we don't have any sort of moderation/approval queue on mediawiki.org -- either you can edit a page (in which case edits go live on save), or you can't (due to it being protected) [22:01:03] So what are these folks up to? Check out my apache log I've dig -x'ed a few the don't seem like crawlers. Are they looking for exploits? https://pastebin.com/QLKsShNM [22:02:53] GumShoe: most probably, or a random crawler trying to find a form to submit spam [22:03:41] the IP address is a web hosting, no legitimate traffic should come from one of these [22:03:50] are there any "best practices" I might look at concering these? Or just shrug as the internet is always mischevious... [22:05:24] just keep your software updated. There's nothing more you can do. I get hundreds of login attempts to my ssh everyday [22:06:35] when some spammer bypasses one of my filter, and I find from a whois query that it comes from a hosting, I ban the entire IP range from sending POST requests to the site at the nginx level [22:08:01] ColoCrossing, Interconnects, HOST1PLUS and QUALYTYNETWORK are full of open web proxies used by spammers, I have a lot of IP ranges blocked for them [22:13:12] I wonder if there are any ipchains hooks into know spaming hosts kinda like spamassassin? [22:14:23] I think there's an extension which checks ip of people submitting edits against a blacklist [22:14:48] actually, I think core supported a dnsbl… [22:17:08] supported, removed in 1.24 https://www.mediawiki.org/wiki/Manual:$wgSorbsUrl [22:17:21] ah, https://www.mediawiki.org/wiki/Manual:$wgDnsBlacklistUrls [22:53:31] Qu. Im using Blue Spice visual editor. When I cut text which includes internal wiki hyperlinks, then paste it a new page, the result is an HTML ,mess. Is it possible to paste and get an exact copy? [22:55:19] ie. displaying links as colored text, but not the underlying markup text. [23:01:56] larry__: i don't think many people working on bluespice are in this channel :/ [23:02:16] ok. thanks