[08:06:19] Okay why is inline HTML being ignored here - https://en.wikisource.org/wiki/Page:The_Columbia_River_-_Its_History,_Its_Myths,_Its_Scenery_Its_Commerce.djvu/151 ? [08:09:06] Anyone? [08:15:06] ShakespeareFan00: you can't use in wikitext [08:17:27] Since when? [08:18:08] Also - https://en.wikisource.org/wiki/Page:The_Columbia_River_-_Its_History,_Its_Myths,_Its_Scenery_Its_Commerce.djvu/19 [08:18:14] Doesn;t like an [08:18:30] DESPITE that precise method being used in some templates on other projects [08:18:36] since always? [08:18:44] you can't use either [08:18:45] Please provide a list of banned tags [08:18:49] just use a standard [[ ]] [08:19:00] It's using a class [08:19:26] Please indicate by editing the relevant page how it's SUPPOSED to be done. [08:19:33] it's a whitelist [08:19:34] https://meta.wikimedia.org/wiki/Help:HTML_in_wikitext#Permitted_HTML [08:19:55] Thanks [08:20:35] Personally, I'd like to see HTMl eleminated outside of Template: 's [08:20:38] and Module's [08:20:38] https://en.wikisource.org/w/index.php?title=Page%3AThe_Columbia_River_-_Its_History%2C_Its_Myths%2C_Its_Scenery_Its_Commerce.djvu%2F19&type=revision&diff=7857064&oldid=7856899 [08:21:58] Thanks [08:22:07] I've left a note for the uploader [08:24:14] legoktm: I'll consider filing a Phab ticket as there was no warning issued in the edit mode about the use of non-permissable tags [08:24:24] that's intentional [08:29:07] https://phabricator.wikimedia.org/T201809 [08:29:25] It would have been nice to know there were sequences that should be removed [08:29:43] Like there are with mismatched tags and obselete sequences [08:33:09] legoktm: Thanks for the fast explanation [08:33:22] np [09:02:40] And no-one's actually able to respond to it on Phabricator because it's not "in precisely the right format" [09:02:42] sigh [13:46:22] Has anyone used MariaDB TX 3.0 with mediawiki and encryption? [13:49:03] Err, I mean installed Mediawiki and used MariaDB TX 3.0 with encryption? [13:52:52] OR, suggest any other way to have an encrypted database with mediawiki? [13:53:38] Encrypting the data where? At rest? In memory etc? [13:53:56] At rest [13:54:40] I take it that means as data files -- at rest [13:55:14] yeah, on disk etc [13:57:01] I've honestly not heard of anyone using that software, or trying to do that elsewhere (apart from potentially some of the people that use Oracle stuff etc) [13:57:06] Try it? :) [14:02:50] Been reading about MariaDB TX 3.0 with the newer features of firewalling etc. I was hoping someone advanced has tried some encryption and advanced security on enterprise usage of mediawiki. [14:03:30] Quote: "MariaDB TX supports both data-in-motion encryption (e.g., connections and replication) and data-at-rest encryption (i.e., transparent data encryption), data protection via roles and dynamic data masking (full or partial) and database protection from denial-of-service attacks. In addition, it includes a database firewall capable of blocking queries based on syntax, role, frequency and/or time." [14:04:02] Ref: https://mariadb.com/database/competitive/oracle-ms-ibm [14:07:37] Do we have an expert on using databases here? I have installed MariaDB on CentOS and Ubuntu, but not yet with Mediawiki using it as well. [14:09:26] MariaDB vanilla is fine with MW [14:11:12] OK. Then I will give it a shot at installing on a clean box with MariaDB TX 3.0. [14:12:31] We'd certainly be interested in bugs/patches if you find them [14:40:56] Ah finally in the right channel I think . . . In my SideBar the pages are all orphans (Main Page etc). Is that correct ? [14:41:18] No idea [14:41:24] What are you talking about? :) [14:42:27] Reedy, :) , if you goto special pages > orphans. it shows all the pages not linked anywhere [14:42:51] Reedy, however my orphans are showing the pages in the SideBar (Main Menu on the side) like "Main page" etc [14:43:03] Ah [14:43:08] Yeah, so those are special links [14:43:15] Which aren't tracked in the links tables [14:43:22] So will be considered orphans from that point of view [14:43:53] ah fair enough. didn't seem to be true for main mediawiki page, but i guess they linked their main page from somewhere else then :D [14:44:03] Reedy, thanks for the speedy reply. I can get on now. :D [14:44:12] https://www.mediawiki.org/wiki/Special:WhatLinksHere/Main_page [14:44:16] lots of links :P [14:45:02] oh nice, that will help me (what links here page) !! cheers! [14:45:25] If you haven't found it already... https://www.mediawiki.org/wiki/Special:SpecialPages [14:45:40] Some of the wording of the page titles isn't always the most obvious as to what it does [15:03:42] Hallo. I have a question about the PoolCounter extension. It's installed everywhere on MediaWiki sites, and it has translatable messages ( https://translatewiki.net/wiki/Special:Translate?filter=&action=page&language=my&group=ext-poolcounter ), but these messages ever seen by any users? [15:04:08] First one is on Special:Version [15:05:06] Reedy: of course :) ... but other than that? [15:05:21] I think so, yes [15:05:26] But would be shown fairly rarely [15:06:23] So I'm wondering: where? I'm cleaning up the organization of MediaWiki extensions on translatewiki, and I'm moving the most technical ones to another group to save the volunteer translators' time. [15:06:33] Users seeing those messages translated in their native languages would probably have the same effect as them being untranslated :P [15:06:39] heh [15:06:53] I don't even know how to get the system to ever show them. [15:06:56] I guess on error pages, if an error was to occur, and not obscured [15:07:09] Install PoolCounter locally, enable it, then disable the service? :P [15:07:21] Should get a connection error [15:08:54] aharoni: I'd definitely agree with dropping their "priority" in some way [15:34:48] On the other hand, if you see a PoolCounter message we really want you to understand what you have to do (reduce the rate of whatever you're doing) [15:51:54] That's not poolcounter [15:52:11] That's rate limiting [16:15:17] Hey guys, is there a complete documentation of git-review anywhere, where any valid commands are listed? All I can find is "How can I do xy" style explainations instead of a comprehensive summary. [16:17:37] git review --help? [16:18:25] https://linux.die.net/man/1/git-review [17:04:33] Thank you! [17:04:44] [18:17:37] git review --help? < yields an error for me by the way [17:26:28] What error? [17:26:30] Works locally for me [17:28:34] > No manual entry for git-review [17:29:21] GIT-REVIEW(1) BSD General Commands Manual GIT-REVIEW(1) [17:29:21] NAME [17:29:21] git-review — Submit changes to Gerrit for review [17:29:22] SYNOPSIS [17:29:27] Depends how you've installed it I guess? [17:29:40] Mines from apt IIRC [17:30:08] opensuse here, no man page [17:31:17] * Reedy thinks Vulpix is strange [17:43:03] git push gerrit HEAD:refs/for/master > git-review ;) [19:38:03] Hello I upgraded my mediawiki to 1.27 and MultimediaViewer extension loses your scroll position when you X out of it. It did this anyway with 1.26 but I redownloaded the extension freshly from mediawiki.org and it still doesn't work. Also tried the 1.29 version and it doesn't work. Is there a way to fix this or what? I think there might be a patch of some kind here... somewhere ...? -- https://phabricator.wikimedia.org/T6389 [19:38:19] -- but I haven't the first clue of how to apply the patch or whatever. Any help is appreciated. [19:39:12] Is that an "official extension"? [19:40:06] MultimediaViewer is used on virtually all Wikipedias so I would say it's "official", if that's what you mean. I downloaded it from the extension distributor on mediawiki.org. Saw a lot of talk of "we're gonna backport the scroll fix" on random Wikipedia discussion pages but as far as I'm concerned the extension distributor hasn't got it. [19:41:21] If it hasn't been fixed, it probably isn't "official". Have you tried a newer mediawiki version? [19:42:51] https://www.mediawiki.org/wiki/Extension:MultimediaViewer if it is this, it states it is stable [19:43:14] doubletropius: what browsers have you tried? does the problem occur in all browsers? [19:44:11] we don't typically backport non-critical fixes, and 1.27 is over two years old [19:45:06] harmaahylje -- I see, it looks like Mozilla Firefox doesn't do the scroll glitch. [19:45:29] Chrome is where the scroll position is reset to going back to the top. [19:46:02] https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MultimediaViewer/+/125383 is an old fix for preserving the scroll position but that should have been merged well before 1.27 [19:47:13] you are talking about MultimediaViewer, not the mobile image viewer, right? [19:47:38] 1.27 is on LTS though so I would assume that patches would be applied to critical extensions such as MultimediaViewer... in any case this scroll position glitch seems to be exclusive to Chrome as it isn't there on Firefox or Microsoft Edge. [19:48:07] Yes I'm talking about MultimediaViewer. The extension that is used universally across all the Wikipedias. [19:48:49] well, they aren't, unless it is a security vulnerability or a particularly high-impact bug [20:04:40] Any clue why this wouldn't be working on Chrome ONLY? [20:09:29] hello [20:11:17] I moved a 1.30.0 install from one server to another, and now I get the following error: https://paste.cybertinus.nl/p/Y5NiUBYWE2 [20:11:20] what could cause this? [20:12:02] I'm still using the same databasesserver (for now), but the website has moved to a different directory on the filesystem (from /sites/wiki.domain.tld/ to /var/www/wiki.domain.tld) [20:13:07] and from a Ubuntu 16.04 to a Debian 9 machine. Both are running PHP 7.0.30 tough [20:13:56] Ref: [16:12] <@Reedy> We'd certainly be interested in bugs/patches if you find them. [20:15:13] Managed to install a VCS with MariaDB 5.5.56 and upgraded to MariaDB 10.3.8 [20:19:04] Cybertinus: well, even the exception renderer is broken so hard to tell what's going on [20:19:38] tgr: hmm, that's bad [20:19:55] But I just realised that the mysql php module wasn't installed on this new server [20:20:03] on master this would be considered a MediaWiki bug (error reporting should fail more gracefully) [20:20:04] when I installed it, everything started working :) [20:20:22] but 1.30 is a year old so maybe it's known/fixed alreadyű [20:20:29] ok [20:20:41] I'm planning on upgrading this install to 1.31.0 [20:20:58] but I'm doing one thing at a time. First moving it to a new server, then upgrade it to a new version :) [20:21:19] well, if you can reproduce the error on 1.31, please file it :) [20:21:23] doing multiple things at once will make it less clear where an issue is, when you hit one [20:21:28] I will