[02:30:01] i suppose google indexing an RSS feed instead of any other content on the main page is a matter of placement? [02:31:22] c: Placement of what? [02:31:49] If only the RSS feed is getting indexed, maybe robots.txt or meta tags are doing something stupid. [02:32:14] Yvette: referring specifically to the meta description of the main page [02:32:39] You mean the blurb that Google shows in search results? [02:32:45] yes [02:33:02] I think it's hit-or-miss whether that blurb is the meta description. [02:33:47] is there a way to prevent the crawlers from indexing the RSS feed entries without removing the rss tag from the main page [02:34:16] By setting a decent meta description tag, maybe? [02:34:48] yes that's what I'm after [02:34:57] but all i found were extensions to do that [02:35:09] Sure. [02:35:12] Probably not in core. [02:36:25] cor blimey [02:57:51] how to update the postgresql db on a mediawiki? [03:06:02] Hi newbee. [03:06:08] Did you run maintenance/update.php ? [03:06:40] yes! I want to install of an extension that requires a schema update. [03:07:39] The sql file of the extension is mysql version. [03:08:34] I don't know how to check that I have succeed creating a table in postgresql db. [03:08:43] Some extensions are not compatible with postgress [03:09:17] You could try and use the extension. If you didn't install the table there will be errors all over the place [03:10:36] bawolff: Can you show me how to access the postgres db schema? [03:11:06] The postgress docs should have instructions on how to see the current schema [03:34:40] Oh, newbee is gone already? [03:34:46] bawolff: I think it's \dn+ or something. [03:34:49] psql is pretty nice. [03:35:15] \du for users, \dn for schemas (namespaces), \dt for tables, \d+ for... something else? [03:53:02] Is the collapsible extension supposed to work on mobile view? If you go to the extension page none of the "show/hide" buttons are visible and everything is uncollapsed by default https://m.mediawiki.org/wiki/Manual:Collapsible_elements [03:53:40] I found some Phabricator tasks about MobileFrontend not fully supporting it, some saying it's intentional design and others saying it's something to fix eventually [05:52:14] hello im in need of some help [10:08:07] Hello, anyone got a way to disable lastmod? The wiki doesn't make sense? [10:34:04] Ryan_: what is "the wiki" and why would you disable lastmod? [14:33:09] I finally came to know why it is showing a long list of things to be modified without any errors I have previosly downloaded the code from rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git but run the git pull origin master unknowingly my git remote -v have my git repository to pull instead of [14:33:09] ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git, So when I have run git status by changing my remote origin to ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git due to difference in versions it gave me almost entire code to gt updated [14:34:43] grr. https://www.mediawiki.org/w/index.php?title=Extension:QuestyCaptcha is inaccurate and the updated information is on https://www.mediawiki.org/wiki/Extension:ConfirmEdit. How to deal with this? [14:40:04] I have then downloaded vector skin from sh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/skins/Vector and moved it to core/skins I have made changes in few files in it but when I press git status in the directory it gives me the changes made but when I come out to vector directory it says nothing to commit, and as I cloned vector from gerrit it remote was [14:40:04] automatically set to https://gerrit.wikimedia.org/r/mediawiki/skins/Vector but my core was set to ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git, So how to commit the changes I have done and to which of above links should I commit? [14:56:51] balrog, you could add {{outdated}} to the top with an explanation parameter [14:57:27] rammanoj_: why did you move it to core/skins ? [14:58:19] rammanoj_: to answer your question: You'd move the changes back to the original repository before "git commit". [15:43:48] rammanoj_: I guess by saying "I moved it to core/skins" you meant "I cloned the mediawiki/skins/Vector repository to /any/path/on/my/system/Vector and moved that folder to /path/where/mediawiki/core/is/installed/skins/Vector afterwards"? [15:57:41] @eddiegp no I have cloned it in directory /var/www/html/core/skins/ by running git clone ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/skins/Vector.git [16:00:11] but when I want to commit my changes to gerrit I can see the changes only in directory Vector but outside to that inside the core directory it gives nothing to commit [16:02:21] rammanoj_: That's exactly how it's supposed to be [16:04:21] rammanoj_: Those are two repositorys. When you are in your /var/www/html/core/skins/Vector folder you are looking at the mediawiki/skins/Vector repository. Changing files there and running "git status" afterwards will tell you basically "Hey, you've changed things (for this repository, which is mediawiki/skins/Vector), look what files you have changed". When you leave the /var/www/html/core/skins/Vector folder and are anywhere else in /var/www/html/ [16:04:21] core you are no longer looking at the mediawiki/skins/Vector repository but are now looking at the mediawiki/core repository. Hence "git status" will tell you "You haven't changed anything (in this repository, which is mediawiki/core), so there's nothing to commit." meaning you haven't made any changes to be committed to mediawiki/core. In difference to my wording above "git status" will probably not tell you at which repository you are looking at [16:04:21] the moment. [16:08:09] So to git, mediawiki/core and mediawiki/skins/Vector are two completely unrelated different projects in different folders. Git doesn't care that the folder you store the latter project (skins/Vector) in is a subfolder of some folder you store the first project (core) in. It's simply two different projects to git. So the result of "git status" depends on at which directory you are looking - that is to git, at which project you are looking. [17:16:30] @eddiegp so I want to submit the the patch I have made to the repository ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/skins/Vector.git and can you say me where th changeid is used? [17:17:54] it's used by gerrit to identify a change [17:18:06] So you can upload multiple versions/patchsets and have them associated as the same [17:20:15] rammanoj_: IIRC correctly you had a strange setup of remotes when coming here a few days ago, so you'd likely like to check your remotes first. To do this, cd into your skins/Vector folder first and tell us, does "git remote -v" tell you "origin ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/skins/Vector (push)"? [17:33:12] @eddiegp yes I have checked it ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/skins/Vector (push) is my remote for push and fallowing the following link https://www.mediawiki.org/wiki/Gerrit/Tutorial#How_to_submit_a_patch to submit a patch but I dont know what is use of changeid can you say me why changeid is used? [17:34:12] rammanoj_: Reedy just answered it ... [17:35:41] thankyou @eddiegp so is there no need of submitting with changeid? [17:36:50] rammanoj_: Of course there is! Gerrit won't like your patch if there's no patch id in it as far as I know. [17:37:05] rammanoj_: Have you installed git-review? [17:37:27] yes I have installed it [17:38:13] rammanoj_: So then, given your changes are committed locally ... [17:38:30] Just cd into you repository and run "git review" [17:39:26] This will automatically amend your patch to have a change id if it hasn't already. [17:39:42] yes I have runned it already it displayed me nothing [17:41:52] rammanoj_: Are you sure your changes have been committed locally? If you run "git status" you should see a message like "Your branch is ahead of 'master' by 1 commit." [17:44:16] rammanoj_: If it says "Changes not staged for commit:" or "Changes to be committed:" followed by a list of the files you changed you haven't committed your changes to your local repository yet. You'll need to do that first. [17:44:36] * eddiegp must leave now, may help out more later [18:08:59] thanks@eddiegp [20:00:57] IP: 49.228.113.246 [20:08:06] Pattanapongmai: huh? [21:37:37] How can I change the text that appears in a tab with my wiki open? I tried $wgSitename but it didn't have any effect. [21:38:01] i.e. the in html [21:39:46] <bawolff> Ecliptica: Edit the page named MediaWiki:Pagetitle on your wiki [21:40:53] <bawolff> The mainpage has a different message [21:41:50] <Ecliptica> Yes, sorry, I should have specified I want to change the text for the main page. It appears correct on other pages [21:42:12] <Ecliptica> MediaWiki:Pagetitle doesn't seem to affect the main page [21:42:40] <bawolff> Try MediaWiki:Pagetitle-view-mainpage [21:43:13] <Ecliptica> Didn't have an effect :/ [21:43:19] <Vulpix> !qqx [21:43:19] <wm-bot> If you want to find a particular system message being used on a page, you can append the uselang=qqx parameter to the URL. That will replace all system messages used on the page by their message names. See https://www.mediawiki.org/wiki/Qqx [21:44:36] <Ecliptica> Vulpix, it appears that works for everything except the <title> [21:44:42] <Ecliptica> Which still shows the string literal [21:45:01] <Vulpix> Ecliptica: are you asking about wikia? [21:45:07] <Ecliptica> No, mediawiki [21:45:21] <Vulpix> ok, because wikia disabled that [21:45:23] <bawolff> yeah, pagetitle-view-mainpage is a content language message for some reason, so uselang=qqx won't work [21:45:39] <bawolff> But that should definitely be the message name [21:46:10] <Vulpix> indeed [21:46:19] <bawolff> Really odd that mediawiki:pagetitle is user language but mediawiki:pagetitle-view-mainpage is content [21:46:44] <Ecliptica> When I went to MediaWiki:Pagetitle-view-mainpage it showed my updated $wgSitename [21:47:10] <Ecliptica> The source had {{SITENAME}}, I changed it to the literal but neither seems to affect the main page [21:47:25] <Ecliptica> Tried restarting apache for good measure but nothing changed [21:47:49] <bawolff> Maybe caching of some sort. Did you try hard refresh, or making a random edit to Main_Page for good measure [21:49:09] <Ecliptica> Tried both with no luck, also tried it in a different browser which I never use [21:49:37] <Ecliptica> Kind of bizarre, pagetitle-view-mainpage sounds like the right thing to modify [21:50:25] <bawolff> yeah, that's odd [21:51:38] <Vulpix> be sure you haven't disabled explicitly https://www.mediawiki.org/wiki/Manual:$wgUseDatabaseMessages/es [21:54:02] <Ecliptica> I haven't, don't have that variable in LocalSettings [21:55:21] <bawolff> If you have weird localization caching settings set up - that could be an issue (although that aort of thing is very uncommon) [21:55:49] <Ecliptica> I haven't set up any localization at all, things are mostly set to the default settings [21:56:08] <bawolff> You could also try making a dummy edit to LocalSettings.php - that will clear all caches, but it really shouldn't be needed [21:56:17] * bawolff basically has no idea [21:57:18] <Ecliptica> No luck ._. tried rebooting the entire server to no avail [21:57:42] <bawolff> Do editing other things in the MediaWiki: namespace work? [21:58:17] <Ecliptica> MediaWiki:Sidebar works [22:40:49] <rossp_> Hello Channel, I'm having problems with syntaxhighlight with 1.26 on FreeBSD 11. The thread: https://phabricator.wikimedia.org/T128993 discusses somebody having a similar issue on SELinux. I couldn't parse a solution out of that discussion. Is there somewhere I should report this bug? [22:44:34] <bawolff> rossp_: That sounds more like a support request than a bug report [22:45:03] <bawolff> rossp_: Verify that mediawiki is allowed to execute extensions/SyntaxHighlight_GeSHi/pygments/pygmentize [22:45:47] <bawolff> (The proper place for this is https://mediawiki.org/wiki/Project:Support_desk or the mediawiki-l mailing list if you like mailing lists, but here is also a fine place to ask for help) [22:46:49] <bawolff> Generally speaking that bug sounds like a combination of issues where syntaxhighlight didnt work because mediawiki could not execute the python dependency of that extension (for various reasons that don't have much to do with each other) [22:47:14] <bawolff> First step would be to enable various types of logging and determine why mediawiki cannot execute pygmantize [22:53:04] <rossp_> well, if you (or others) would be willing to help guide me, I'd happily go through it here. I'll try and turn on most of the debugging suggested in the thread I posted and see what I get. If we can't figure out what's going on, I'll at least have more info for the mailing list. [22:54:18] <bawolff> I unfortunately have to go to dinner. Maybe someone else would be willing to? [22:54:38] <rossp_> Damn my pacific time zone [23:05:32] <rossp_> I guess the thing that is really strange is that if I change the variable $wgPygmentizePath to equal the external library, things work fine. [23:07:02] <Reedy> Why's that strange? [23:12:31] <rossp_> Well, it indicates, to me, that the problem lies with the bundled pygmentize file, which is something I think would have been caught and fixed. [23:12:51] <Reedy> Well, if you were complaining of a SELinux.. [23:12:55] <Reedy> *problem, not really [23:13:10] <Reedy> Or did you just point it at the one that was bundled? [23:14:07] <rossp_> When I point it to the bundled pygmentize, it doesn't work. When I point it to the pygmentize I installed separately, it works. [23:14:23] <rossp_> and, of course, when the variable is commented out, it also doesn't work. [23:14:35] <Reedy> Ok, so that is more evident of a SELinux problem [23:14:53] <Reedy> The one you installed seperately, is probably allowed by the OS by default [23:14:54] <rossp_> And FreeBSD, which is what I'm running. [23:14:58] <Reedy> So of course it's gonna work [23:16:58] <Reedy> FWIW, the binary works fine for many other people, under different environments