[00:02:10] I'm also looking for alternatives to postfix:) [00:02:33] how is the MTA relating to MediaWiki? [00:03:23] Wikimedia prod uses exim for all mail routing [00:03:59] Sander^work: dpkg-reconfigure exim4 and there is some dialog ..and then usually select "sattelite system".. but it depends [00:04:37] satellite [00:05:41] mutante, i'm trying to set up a full fledge mailserver on an raspberry pi, where I also got the mediawiki:) [00:06:38] so I guess sattelite system is wrong. [00:07:57] Sander^work: "full-fledged mailserver" is complex and involves mutiple daemons and can mean different things. you just asked for "the easiest" though, so i just answered that [00:08:06] it's kind of off-topic [00:08:34] i assumed you just want the feature that MW can send mails out [00:09:11] Sander^work: https://www.digitalocean.com/community/tutorials/how-to-configure-a-mail-server-using-postfix-dovecot-mysql-and-spamassassin [04:04:47] Hi, I was wondering if it is possible to define a default sort order for a sortable table? Currently, they entries are simply listed in the order they were given and one has to click one of the headers to sort. https://www.mediawiki.org/wiki/Help:Sorting#Sorting_rows_of_a_table [04:06:31] Laibsch: if you want to change the default just re-order the rows in the wikitext? [04:12:16] Yes, that's of course an option. But I'd just like the sorting happen automatically and based on the table content. [04:15:44] I don't think that's possible with the current table sorter stuff [04:16:02] it would cause a flash as the JS loads and then content rearranges itself [06:19:26] thanks, legoktm [12:49:14] Seems like I can't do a git clone on gerrit anymore, something wrong with the repo? [12:51:48] Verified that a correct pubkey is entered at gerrit, and it is… [12:52:28] Checked with an attempt to clone a different repo, and it failes [12:52:33] git clone ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/SandboxLink [12:53:13] I get an error like "Permission denied (publickey)." [12:53:52] anyone awake? [12:58:38] Bah, buggy page at gerrit [15:22:10] I'm loading an extension, but the resourceModules defined in extension.json (JS and CSS) are not being loaded. I'm not seing any errors. What can I inspect in the console, or what hook can I use to introspect the extension during registration to figure out why the CSS and JS aren't loaded? [15:22:35] mw1.31 php7.2 [15:22:57] Nothing in Debug log or Apache log [15:26:01] freephile: modules aren't loaded by default; you need to explicitly add them to relevant pages. See https://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader for more info [15:32:33] Skizzerz: thanks [15:46:18] Hey, is there a way to run two wikis one database? I mean to only sharing users, but also pages. I work with a game wiki, we will release another version of the game soon. We want to keep the old game version data accessible while having the new data also on the wiki. We thought about simply copying the wiki, but then changes in the old version dont happen for the new version. Is there a way we could share the database between two [15:49:05] Bilka: How about one wiki but 2 name spaces? You can create custom ones, so page names like Old:Page and New:Page (or just Old:Page and Page), so it's one wiki but content is separate. Question is kind of what makes a wiki 2 wikis if they share users [15:49:28] (and pages) [15:49:33] Skizzerz: that was it exactly... I just needed `$wgOut->addModules( 'ext.dcssearch' );` where the extension is being invoked [15:49:45] I recommend against using $wgOut [15:49:54] figure out a different way to get the OutputPage object from your hook [15:50:09] $wgOut doesn't work in every context [15:50:34] mutante: Right, namesspaces would also be possible. However, that would mean copying all pages on the wiki, and would not allow sharing changes. [15:50:38] OK thanks, will look further. Inherited codebase and learning as I go [15:50:56] Bilka: namespaces seem like exactly what you want. Take a look at the dwarf fortress wiki for inspiration [15:51:26] for example, http://dwarffortresswiki.org/index.php/DF2014:Creature [15:51:32] Bilka: you could move all the current pages to Archive:Page and start new ones and keep it all one wiki [15:51:47] and see the nav at the top of the page, which links to different versions of the page for different versions of the game [15:51:56] note how each version is a different namespace [15:51:59] Bilka: or.. on each page just have a TOC item for "=== Old Version ===" [15:52:17] I think you are missing a detail I didn't provide: We don't want to keep the old version data around once the new game version is stable [15:52:24] oh [15:52:29] I mean, writing a script to delete old pages isn't hard [15:52:30] then just edit the page for the new version [15:52:55] you can make use of categories to track which pages have or haven't been updated yet [15:53:17] e.g. put [[Category:Version X]] on a page, and then when you release X+1 replace that on updated pages with [[Category:Version X+1]] [15:53:35] looking at the list of pages still in Category:Version X will show you the pages that are outdated so you know what to focus on for updates [15:53:52] I can't simply change the page because we have a period were both versions are available to users, once as "experimental" opt-in, and the other as the default (stable) version. That means we cannot update the wiki to the experimental version without losing the data of the stable version [15:53:54] Bilka: why? deleting stuff is bad as in "good uris dont change" :) [15:54:14] https://www.w3.org/Provider/Style/URI [15:54:34] Bilka: the experimental/stable sounds exactly like FlaggedRevs, which means it should be easy enough to do that [15:54:35] Bilka: ok, so if you really want 2 separate wikis, you can make them share users by using an LDAP backend [15:54:57] don't mark your edits as checked/stable until you want to make it default [15:55:14] are you already using the FlaggedRevs extension? [15:55:25] Skizzers: that looks like something that might work, I will take a better look and then come back to you [15:55:27] https://www.mediawiki.org/wiki/Extension:FlaggedRevs [15:56:44] I can send you the config I'm using on my wiki to achieve basically what you just described [15:57:42] how does it work with transcluded pages? [15:58:01] you can configure it to "freeze" the transclusions to the version that was transcluded when you marked the page [15:58:27] or you can have it always transclude the latest version, up to you [15:58:48] and if I then go to the "unchecked" version, does it also transclude the unchecked version of the transcluded page? [15:58:56] yep [16:00:40] that sounds pretty good. From what I have seen, I have to switch to the unchecked version for every page and can't simply choose to only see unchecked version. Did I miss something that would allow that? [16:05:00] Bilka: you can configure it so that regular users are shown the checked version by default and admins are shown the latest (possibly unchecked) version by default [16:06:19] That is not what I am after. I am thinking of a "switch" so that a user can choose to see either the stable or the experimental things by default. That might exist in the options, but I cannot find info on it on the extension page [16:06:34] yeah I'm looking to see if there's anything like not, not sure if that exists [16:07:45] not seeing it; best I can find is configuring it per-group [16:08:04] nvm spoke too soon [16:12:39] Bilka: looks like there's a user preference "When to show the stable version of content pages by default" that can be tweaked in Special:Preferences [16:12:58] options are "Use the default settings for each page", "Always show the stable version (if there is one)", and "Always show the latest version" [16:15:11] That is very good, though I not an option for users that are not logged in (not that I expected such an option). This makes the extension sadly not usable for us because most of our users are not logged in, but should be able to choose what version they see by default. It was a good idea though. [16:16:57] $wgDefaultUserOptions can change the option set for users that are not logged-in [16:17:26] if you want logged out users to be able to configure this, you can work around by setting a cookie and then setting $wgDefaultUserOptions appropriately depending on the cookie value [16:17:52] That's a bit above my skill level :) [16:19:20] fair enough :) [16:23:24] Hi, I'm trying to install MW - I downloaded tar.gz from https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.1.tar.gz, then went to https://tech.wikimedia.cz/mw/ and clicked Complete the installation. It directed me to https://tech.wikimedia.cz/mw/mw-config/index.php and showed a traceback. Any tips what can be wrong? [16:25:40] what's the traceback? [16:25:42] What was the traceback? [16:25:51] * Reedy thinks Urbanecm should know better :P [16:26:07] Skizzerz: but I have a co-worker who know cookies from biscuits, so I will try to get him to do that :) Thank you for the help! [16:26:11] WFM when i click the link :P [16:27:09] bawolff, for me, it shows https://paste.ee/p/vx8Fd [16:27:12] WHY :D [16:27:31] On the first page? [16:27:47] I didn't want to click far enough into the install to actually do any write actions [16:28:16] I get this error on clicking "Complete the installation" [16:28:25] I didn't do anything - in fact, I'm not able to [16:28:52] Umm, looks like that method doesn't check the status object [16:29:22] https://github.com/wikimedia/mediawiki/blob/REL1_31/includes/installer/MysqlInstaller.php#L244 [16:29:54] Yeah... I guess your connection attempt to the db failed [16:30:16] The lack of error reporting is definitely a bug [16:31:11] Reedy, but why does it try to connect to DB? Actually, how does it know where my DB is? [16:31:43] Not sure [16:31:51] you have to tell it where the db is as either the first or second screen after the welcome splash [16:32:23] Skizzerz, the problem is the welcome splash doesn't show anything [16:32:24] unless that's customized [16:32:30] it shows the traceback [16:32:32] and works for others [16:33:02] https://tech.wikimedia.cz/mw/mw-config/index.php?page=DBConnect ? [16:34:08] clear your cookies and try again [16:34:30] Thanks, that works Skizzerz. How the session get there through... [16:34:58] *did the session [16:35:16] to be clear, which worked. going to the url directly or clearing cookies [16:35:21] ? [16:36:41] clearing cookies [16:37:32] not sure, in that case, since I would've expected when you filled out initial db connection details for the connection to fail and give up [16:38:41] well I was trying to adapt LocalSettings.php from another wiki, after that didn't work, I tried to run the webupdated, maybe it set the cookie somehow. Thanks for your help [16:39:25] hmm, I missed one important detail [16:39:38] Still might be worth putting some extra handling in... Even if it's just a "reset" button for weird state [16:42:19] Hmm. Filled the details, tried to install the wiki and after submitting, https://paste.ee/p/yqxSE showed [16:42:39] (that's the same what showed after running update.php with the self-created LocalSettings.php [16:43:03] let the installer generate the LocalSettings.php for you [16:43:07] don't put one in yourself [16:43:38] then apply whatever customizations to the installer-generated on [16:43:40] *one [16:44:05] Hmm, fixed that myself, sorry for bothering. [16:44:22] Is update.php supposed to work with empty DB? [16:44:53] No [17:08:23] I just filed https://phabricator.wikimedia.org/T212236 for the issue with error reporting [17:44:38] hi [17:45:56] trying to add a tag with addMeta, how is it possible to add [17:46:00] ?« [17:48:44] addMeta( 'somethig', 'etc' ); [17:49:07] nvm [17:49:09] tried it [17:49:13] i was doing it wrong [17:49:15] sorry [17:49:19] heh, np [17:49:22] i changed before the answer [17:49:26] thank you [17:49:27] :D [18:40:53] :D [19:44:07] what would be the best way to take a MW SQL dump from v 1.27 and import into v1.31 while also changing the table prefix/naming scheme? [19:44:46] freephile: Honestly, I would just rename the tables to the new prefix [19:44:54] and then run update.php [19:45:03] Probably the easiest [19:45:15] thanks Brian [19:45:23] In an ideal world, have a separate DB for it and use no prefixes [19:45:25] Provided you are just moving the wiki, and not merging two wikis together [19:46:32] it's complicated. multiple language wikis in a single database using lang prefixes ==> multiple databases (with shared user and interwiki) [19:48:45] I might end up using Sed on the dump file to get things ready to import and then run update.php [19:49:07] but I'll need to do that for each language [19:50:39] * freephile wishing I could use a nice ETL tool besides sed :-) But sed works [19:51:06] Hello. I'm trying to use the TemplateStyles extension on MediaWiki 1.27, but it appears that I do not have the css-sanitizer content model. Does this need to be added separately, or is it something that was added to a later version of MW? [19:51:37] This page was not very straightforward about implementation: https://www.mediawiki.org/wiki/Css-sanitizer [19:53:39] Why don't you just upgrade? 1.27 will be out of support in a few months anyway [19:54:18] I rely heavily on LDAP, and I haven't seen a good replacement for the LDAP Auth extension, yet. [19:55:46] Even though that extension says it doesn't work with 1.27, I was able to get it going. But I could not make it work in later versions. [19:57:20] So you need to install it via Composer [19:58:11] Also, you need not content model, but a library, this confused me for a while [19:58:57] Yeah, me too. I'll give it a shot. [20:01:47] freephile: People make fun of sed, but it always gets the job done [20:43:40] Hi, I try to instal mmediawiki using cli! MediaWiki has been successfully installed. but when I access my domain redirect me to http://index.php/?title=Main_Page inside of http://domain.org/index.php/?title=Main_Page [20:44:25] did you configure your base url right? Because that sounds like you've misconfigured MediaWiki [20:45:47] Ah, it was because --scriptpath=/ [20:45:54] there you go :P [20:45:57] :D thanks [20:55:39] teward, but if I want to install in the web root? [20:55:46] like wiki.example.or/ here [20:55:54] not in wiki,examle.or/wiki/ [20:56:01] I need to add --scriptpath=/ ... [21:10:48] deepfreez: now that it's installed you can modify LocalSettings.php to correct paths and such [21:11:31] thanks [21:11:45] if the wiki is installed directly in the root, script path should be the empty string (not '/') [21:12:30] yes with cli i use only --scriptpath= and works [21:53:23] I have a very a short and very simple question. I create a gallery by https://pastebin.com/zdqQPK8p When I click on an image, it redirects me to the info page of the image. However, I would like to link to the full-scaled image directly. I have tried several {{filepath:image.png}} variants, but haven't figured out a working solution. Any ideas? [22:07:47] star314: generally not possible using , but you can get something of a similar effect by installing https://www.mediawiki.org/wiki/Extension:MultimediaViewer [22:08:38] Skizzerz: Thanks, I will have a look at the link. [22:08:53] in which clicking an image gives you a full size version of the image instead of taking you directly to the description page (and controls to view full screen, download, go to description page, etc.) [22:09:37] star314: you can demo MediaViewer by going to https://en.wikipedia.org/wiki/Main_Page and clicking on any of the images there (assuming that you are either logged out, or if you are logged in and have mediaviewer enabled) [22:34:09] star314: [[File:Foo.png|link=Media:Foo.png]] might work maybe [22:34:19] but generally not a great experience IMO [22:34:59] I don't think linking to the original was a good idea in MediaViewer, either [22:39:20] tgr: Yes, links= works. However, not in a gallery environment. [22:40:14] tgr: I have tried that before. link=..., {{filepath:..}}, etc. [22:41:43] oh, right, gallery [22:41:59] yeah, no way to modify linking behavior there [22:45:39] although looking at the gallery code it does actually have logic for a link parameter [22:50:36] so Example.png|link={{filepath:Example.png}} works fine for me [22:51:09] although I'd still recommend against doing that [23:03:21] tgr: Let me try. [23:05:32] tgr: What doesn't work is [23:05:32] nakivo_transporters.png|link={{filepath:nakivo_transporters.png}}|Repositories [23:06:11] I.e., a thumbnail with a label [23:07:48] works fine for me on enwiki [23:08:52] Hm, here on MediaWiki it doesn't.