[00:36:48] So have you heard bug reports of the recent changes breaking after updates? [00:37:06] It refuses to load at all [00:37:23] Refusing to load? :P [00:38:22] Well, it has the three dots [00:38:29] But it never actually loads [00:38:29] Three dots? [00:38:35] lol hang on [00:42:53] https://imgur.com/a/YiRUlU0 I get this forever [00:43:06] It's cropped, obviously, and everything else is normal [00:43:13] The RC list just doesn't ever load [00:43:23] Check your browser console [00:43:31] There's probably an error coming back from an API request/similar [00:44:16] Good call, I've got a few [00:44:41] Oh, looks like the old JS wg variables were finally removed, for one [00:45:01] numerous were yeah [00:45:05] loooots of deprecations and removals in 1.35 [00:45:26] Apparently our collapsibleTables script is also broken [00:45:42] And I get a js 404 for Special:RecentChanges, for some reason [00:46:40] I guess I saw this coming. I'll have to update our local javascript. [01:20:29] jfolv: you can flip $wgLegacyJavaScriptGlobals to push on for a few more months while you work on other migrations first. [01:21:16] Removal will be in the next release [01:38:01] Krinkle: Thanks for the heads-up! I'm already behind schedule, so if I can buy at least a bit more time so I can get this upgrade live, then it's worth it. [01:54:20] Upgraded to MW 1.35. Have an error and stack trace. Error is: Fatal error: Uncaught Error: Interface 'Wikimedia\Services\SalvageableService' not found in /home/iafstghq/digitalmatrixgroup.com/includes/HookContainer/HookContainer.php:44 [01:55:53] Is your vendor folder up to date? [01:56:08] Should be at vendor/wikimedia/services/src/SalvageableService.php [01:56:18] let me check ... [01:57:08] In theory... it should be as update.php would've probably complained [01:58:23] no /services folder at all. And I got the error triggering the update.php in Snowflake [01:58:40] *SSH for ubuntu on shared hosting [01:59:21] vendor/wikimedia does exist just not the rest of it [01:59:37] Is this from your providers "upgrade"? [01:59:45] https://github.com/wikimedia/mediawiki-vendor/blob/REL1_35/composer.json#L53 [01:59:48] https://github.com/wikimedia/mediawiki/blob/REL1_35/composer.json#L59 [01:59:50] It's definitely in there [02:00:32] No I downloaded from MW. Rolled it out. Upgraded all the extensions. Updated via Composer, etc. [02:00:59] Tarball? [02:01:47] It's definitely there in https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0.tar.gz [02:01:54] Yes sir, Idownloaded it direct from MW here https://www.mediawiki.org/wiki/Download [02:02:57] mediawiki-1.35.0.tar.gz is the file name I uploaded [02:05:19] Does your composer.json have a line with.. [02:05:23] "wikimedia/services": "2.0.1", [02:06:39] Negative [02:06:48] Have you made changes to your composer.json? [02:06:57] Like, copied in the version from your old install? [02:07:45] Not that I am aware of. Ah, yes I copied over the old composer.json thinking I needed it and the composer.local.json as well. [02:08:17] composer.local.json you will want [02:08:40] Copy composer.json out of the tarball again, then update the vendor folder using composer [02:10:02] very good. thank you. to verify, after I bring it over, remove, composer lock, and composer update --no-dev [02:11:17] you shouldn't need to remove the composer.lock [02:11:37] on it thanks! [02:17:22] Success! And only because of the invaluable help from you folks in here! @Reedy thanks for the several weeks of walking me by my hand! [02:19:22] Heh, np [02:20:08] Got a few errors around on the pages, but the upgrade is successful and now I can go to town on them. ;) [02:23:48] Special Pages, Forms, Uploads and such are all fine. Any page I have created generates: [366578c2f62e5295c424b1f9] 2020-10-04 02:22:23: Fatal exception of type "MWException" [02:23:59] Debugging on but doesn't display anythign [02:24:25] $wgShowExceptionDetails = true; [02:24:53] Yup it's on as is error_reporting( -1 );ini_set( 'display_errors', 1 ); [02:25:24] strike that just a mn [02:27:13] Had to uncomment. Lua - Scribuntu stuff. Baiscally Lua binary is not executable [02:27:30] https://digitalmatrixgroup.com/index.php/Federal_Information_Processing_Standard [02:27:31] path or permissions are wrong probably [02:28:50] So do I need to change extensions/Scribunto/includes/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua to an executable in cPanel? [02:29:26] you need to give it the executeable bit [02:35:32] Something so minor hidden away in the dark recesses. Almost like the ; missing. Worked. ThanksQ [02:35:36] Thanks! [02:47:25] As a footnote as I do not know if anyone tracks these logs, all of the Lua errors I had before on the WP Template:Infobox company are gone after upgrade from 1.34.2 to 1.35 [14:21:15] Hi, I need to have mediawiki in kubernetes using helm and with rolling update [14:21:37] is there is any instruction from sctach to do this? [14:23:29] Okay, next issue I have with my upgrade. Anybody here familiar with the Widgets extension? I have it complaining that it can't write to Widgets/compiled_templates, even after I chmodded it to a+rw. [14:24:05] Anandan: AFAIK, no, no instructions for that [14:24:12] I did definitely update it after I upgraded, and I even redownloaded it and tried again to no avaial [14:25:33] Is it definitely the full path you expect? [14:25:41] ie if you use eval.php and echo $wgWidgetsCompileDir; [14:26:02] Let me check [14:26:47] Yep, it's pointing the right spot [14:27:20] We are using a custom widget, but it's essentially just a way to throw our twitter feed on the front page [14:27:31] I checked the code for it and I can't imagine it would be the problem [14:27:48] It works live on our 1.29.1 [14:28:05] Anandan: so automated build? [14:28:21] what does kubernetes have to do with that [14:30:57] jfolv: how's your programming/php generally? [14:31:48] Moderate proficiency with both. I'm not god-tier but I can generally find my way through code. [14:31:57] Stuff like this doesn't fill me with a lot of confidence [14:31:58] https://github.com/smarty-php/smarty/blob/master/libs/Smarty.class.php#L632 [14:32:05] it's protected, but then is using __set... [14:32:35] Considering there's a setCompileDir... Why use the magic stuff [14:33:30] harmaahylje need to build with dockerfile and deploy to kubernetes [14:35:08] jfolv: Are you running any sort of OS type security things? firejail etc [14:35:45] No, not at all. I created this vm myself and installed everything on it. [14:35:54] No OS-level security [14:35:59] Anandan: Ok so you need an example dockerifle? [14:36:36] harmaahylje Yes [14:40:13] including database? [14:40:24] are you also hosting that yourself [14:40:53] @har [14:41:35] harmaahylje yes including database. Yes I have kubernetes in GCP [14:45:25] I guess you can lookup any apache hosted app with database [14:47:00] in docker hub? [14:47:09] harmaahylje docker hub? [14:48:27] Well where do they have example dockerfiles, I don't know :) github? [14:52:28] https://github.com/wikimedia/mediawiki-docker/blob/7fb7a88b3dd745fdd1115ad701a1e5f5c6236420/1.35/apache/Dockerfile [14:54:09] harmaahylje Thankyou! [15:11:10] I'm trying to set up an email server for my mediawiki. I'm using postfix and following these two guides: [15:11:14] https://raspberrytips.com/mail-server-raspberry-pi/ [15:11:24] https://samhobbs.co.uk/2013/12/raspberry-pi-email-server-part-1-postfix [15:12:19] This is my first time trying to setup an email server, and there are a few things I'd like to ask about for clarification on how to properly connect my mediawiki with my email server [15:13:39] I know my domain, but I'm not sure what user I'd put down before the @ in USER@mydomain etc when testing the SMTP capabilities [15:13:53] whatever you want [15:14:54] It's been a while since I last worked on my mediawiki installation, does mediawiki use a certain useragent? Does anyone know of a way I could find out how to properly form the email address? [15:15:17] does mediawiki use a certain useragent for what? [15:15:23] email [15:15:32] I don't understand the question [15:15:58] You can literally use whatever you want [15:16:02] sorry if I worded that poorly, let me think about it for a sec [15:16:05] wiki@domain.tld [15:16:09] noreply@domain.tld [15:16:17] it really doesn't matter as long as your mailserver will allow it [15:16:59] ^ [15:17:03] I don't think I've defined a user for my domain's email yet [15:17:58] In most cases, you probably won't [15:18:12] the mailserver is basically acting as a mail relay to send it onto other peoples email servers [15:18:22] You probably don't need to create a mailbox for that user/email address [15:18:38] You don't need a user for that mail. Just be sure any email sent from localhost (or the IP where mw is installed) is allowed to send mails [15:20:42] hm, I'm testing the postfix server at the moment, I've given its domain the same as my mediawiki domain (the .onion address I'm using) so I'm a little confused as to how I'd be able to test send an email if I haven't defined the email user mediawiki will use to send emails from the server [15:22:09] forgive me if I've misunderstood anything from the mediawiki wiki pages describing email. I'm using this as a learning experience to teach myself more about email I guess [15:24:28] You're using postfix to send emails, not to receive them. Hence, you don't need a working email address to send emails. You can simply put a noreply@domain.tld [15:24:51] MW 1.35: issue importing .svg listed in the localsettings but shows broken image square only. thx [15:24:57] Well, with postfix you can also receive them, but that's not your current problem :) [15:25:08] Foreclosurepedia: That sounds more like your thumbnailing is probably broken [15:25:56] All other image renderings are working. Importing from WP, with that said, where would u suggest I go read up to address? thx [15:26:15] !tumbnail [15:26:19] !thumbnail [15:26:19] For information on configuring thumbnailing on MediaWiki, please refer to . [15:26:37] It's possible your config is not quite right, or missing some packages etc [15:26:39] Vulpix: But I'm also trying to setup my mediawiki so it will send me emails to the server to notify me when people make edits, to allow them to be published [15:26:46] thx! [15:27:20] So, I can use a ! to call a general subject question here in the IRC? [15:27:58] Not quite, it's a predefined list [15:28:00] !botbrain [15:28:00] Hello, I'm wm-bot. The database for this channel is published at https://wm-bot.wmflabs.org/dump/%23mediawiki.htm More about WM-Bot: https://meta.wikimedia.org/wiki/wm-bot [15:29:34] burning: that still sounds like your server will *send* emails to other hosts, not *receive* them [15:30:26] hmm, does the edit notification system send notifs to the admin's inbox on the wiki? Like, is it accessible from the wiki itself? or is it email only? [15:30:53] MediaWiki has no mail inbox [15:31:04] because if it is email only, I was hoping this postfix server I'm making for the wiki could also act as my anonymous mailbox [15:31:07] You can visit Special:Notifications on the wiki [15:31:14] But it's not an inbox or an email system [15:31:20] so it is email only [15:31:21] ok [15:31:49] !echo [15:31:49] http://www.mediawiki.org/wiki/Echo_%28Notifications%29 [15:32:15] and when I say anon mailbox, I only mean for the wiki. I'd just prefer to keep my privacy from my wiki's users and remain as anonymous as possible [15:36:29] I just want to have a system where every time an edit is made, before it's published it needs to go through me the admin or one of the mods I delegate. I'm assuming that would be done via email? [15:38:19] That's not the normal MediaWiki behavior. You'll need an extension for that. Maybe the Moderation extension? [15:38:32] I do plan on using the extension [15:38:34] !e Moderation [15:38:34] https://www.mediawiki.org/wiki/Extension:Moderation [15:39:11] If you use $wgModerationNotificationEnable, it seems possible, yes [15:41:39] yes, my confusion comes from how exactly to setup my email server in conjunction with that extension [15:44:07] I'm using the confirmedit and confirm account extensions [15:45:02] oh, but this moderation extension looks like it makes things a lot easier by creating a dedicated page for confirming edits [15:45:05] interesting [15:55:42] Read up all I can. So weird stuff, png thumbs of svg work here: https://digitalmatrixgroup.com/index.php/File:Flag_of_Atlanta.svg but svg thumb does not here https://digitalmatrixgroup.com/index.php/File:Emera_Logo.svg [15:56:10] Second image was downloaded from WP as it didn't come through in the template [15:59:36] Foreclosurepedia: it works after requesting the thumbnail manually at https://digitalmatrixgroup.com/thumb.php?f=Emera_Logo.svg&w=512 [16:00:32] You probably uploaded the file *before* enabling SVG rasterizing or fixing it. It doesn't regenerate failed thumbnails unless you set up a 404 handler [16:01:15] Ah, absolutely correct. So, simply reupload? thx btw! [16:01:45] Or purge [16:02:55] No go on purge. [16:04:07] And delete and reupload change nothing [16:06:07] that's strange [16:07:27] To duplicate I carried over a Page from WP. Usually it trucks all images over, but it didn't on this one. I set 'svg' in localsettings. Purged and then deleted image and reuploaded MW 1.35 [16:08:15] ls: $wgEnableUploads = true;$wgUseImageMagick = true;$wgImageMagickConvertCommand = "/usr/bin/convert";$wgGroupPermissions['autoconfirmed']['upload'] = true;$wgGroupPermissions['autoconfirmed']['reupload'] = true;$wgGroupPermissions['user']['upload'] = true;$wgFileExtensions = array('png', 'gif', 'jpg', 'jpeg', 'doc', 'xls', 'mpp', 'pdf', 'ppt', [16:08:15] 'tiff', 'bmp', 'docx', 'xlsx', 'pptx', 'ps', 'psd', 'swf', 'fla', 'mp3', 'mp4', 'm4v', 'mov', 'avi', 'svg'); [16:08:37] You can also edit a page, use that file with the width you want, and preview. It should generate the thumbnail if missing [16:08:54] will try thx [16:09:55] Of course, leave $wgGenerateThumbnailOnParse to true (this is the default value), otherwise it won't generate them [16:12:21] That was it. Duh, thank you! Fixed the issue! [16:33:32] Hello benefactors of the commons. I'm looking for a solution where I could edit this one article in intrawiki, but publish it occasionally to a wordpress. Just copy-pasting the wiki page to a wordpress page works almost ok. There are not going to be any intrawiki links, so the only major problems are #1 how to fix the links to footnotes (multiple classes of footnotes are very useful in some tasks). I see they can be found by looking [16:33:33] for " [16:33:34] and remove the domain part [16:37:12] otherwise, when editing and doing a page preview, clicking a ref link will leave you from the edit window [16:37:21] Vulpix: Thank you for the information. The copy-paste is doing the absolute links I gather [16:38:29] Don't upload files to the wiki. Upload them to wordpress first, then reference them from MediaWiki [16:38:43] Vulpix: excellent idea. cheers [16:38:57] You'll need to set this to true: https://www.mediawiki.org/wiki/Manual:$wgAllowExternalImages [16:39:07] thanks. making notes [16:39:36] i.e. gonna copy-paste the irc log to my relevant irc-snippets stash [16:39:54] alternatively, set https://www.mediawiki.org/wiki/Manual:$wgAllowExternalImagesFrom to the domain where wordpress serves the images from, for a more fine grained control [16:41:54] Intrawiki is a really great way to keep notes and to draft entries into wikis, without needing to worry "Everyone will see any stupid/falsehood-containing/total-beginner edits until the end of the wiki or end of the world, whichever comes first" [16:45:16] In Wikipedia's case I hope the end of the world comes before the end of the wiki [16:47:03] Thanks for you help Vulpix. I searched for ' looks like latest RESTBase includes outdated references that are trying to connect to parsoid using the old parsoid-php URL structure instead of the rest.php URLs [17:09:10] produnis: Press the F12 key, and look at the error console for any javascript or server error [17:10:25] Potentially related to old JS variables being removed [17:11:23] thx vulpix, it states: [17:11:24] ResourceLoaderFileModule::getFileContents: style file not found, or is not a file: "/my/server/mediawiki.rcfilters/styles/mw.rcfilters.ui.FilterTagMultiselectWidget.less" [17:12:24] can you check that path on the server and see if the file exists, or has read permissions? [17:13:26] Did you remove resources when you added /my/server? [17:13:49] Vulpix, the file is there, but withou a ".less"-suffix [17:14:03] Sounds like the archive issues... [17:15:06] What did you use to extract it? [17:15:30] @reedy I am on linux, I used 7z or gz [17:15:36] 7z has issues [17:15:41] like this [17:15:48] @reedy :) oh no..... [17:16:03] Unforutnately... https://www.mediawiki.org/wiki/Download [17:16:07] >Windows users should note it is advised not to use 7-Zip to decompress the tarball, due to a bug with the PAX format. [17:16:18] so I should just try a new "fresh" upgrade bei extracvting all apackes using gz? [17:16:26] I guess we should remove the windows part [17:16:37] Yeah, that's probably going to be enough to fix it it [17:16:58] @reedy oki [17:25:34] @reedy thx, that helped!!! [17:26:02] works now [17:26:06] ;) [19:08:56] MW 1.35: Curiosity question. On pulling over WP pages (I open and copy source manually) why do some photos come along but others don't? thx [19:12:51] what are WP pages? [19:20:25] Wikipedia [19:20:35] It's possible some images come from commons, they'll work via instant commons [19:20:46] if they're from wikipedia itself (local upload) they won't [19:30:07] Ah, very good appreciate the insight! [20:53:34] Please consider building a new copy of https://releases.wikimedia.org/debian/dists/jessie-mediawiki/ looks like the repo files were rolled back at some stage, which means apt doesn't update. [20:54:07] Hack fix on client: sudo find /var/lib/apt/lists -maxdepth 1 -type f -print -delete [20:54:25] Without doing that, parsoid seems to get stuck at 0.10.0 [21:00:06] Firefishy: you'd be best filing a bug in phabricator and tagging it parsoid, I think [21:00:33] phabricator <--- runs away screaming. [21:01:36] Why? [21:04:21] I doubt I have an account and it a labyrinth of confusing UI. [21:04:42] Have you an account on wikitech or a wikipedia account? [21:16:39] Grudgingly done: https://phabricator.wikimedia.org/T264546 [21:17:18] User Since Mar 18 2015, 5:28 PM (289 w, 4 d) [21:17:18] ;P [21:44:17] Narrowed it down to the exact bug, repo version number was not incremented. https://phabricator.wikimedia.org/T264546 [22:22:43] I just want to confirm that it's not a terrible idea to perform my database upgrades on a staging server, then dump the upgraded databases and use them for production. [22:23:03] Shouldn't be any hardcoded links in the database, right? So it shouldn't matter what domain runs the script [22:23:58] Trying to minimize downtime, since the upgrade itself has been a nightmare of a process that took the better part of my week [22:27:31] jfolv: hey, as long as the database and code is same, it shouldn't matter (but i didn't try it) [22:27:50] however, if someone updates your wiki when you're running the update, you would delete that change [22:28:07] the "working" way would be to set it to read only, but then you wouldn't avoid downtime anyway :/ [22:28:12] Oh, I'm planning for that. [22:28:18] Well, "readonly" is still readable [22:28:38] I'd prefer to leave it readable instead of having a maintenance page for multiple hours [22:28:57] So yeah, I plan on setting $wgReadOnly before I do the db dumps [22:31:07] in that case, it should work [22:32:54] You can probably import the database to a new name, and rename it, or just change the dbname config in LocalSettings.php [22:33:19] +1 [22:34:27] Yeah, that was my plan [22:34:58] Just import the database, redirect everyone to a maintenance page while allowing my own IP through, change the db and check for any massive bugs, then go live. [22:35:13] That's how I always used to do it years ago [22:35:24] jfolv: you can also use this workaround https://www.mediawiki.org/wiki/Manual:$wgReadOnly#Upgrading [22:35:31] (or something similar, but IP based) [22:35:42] that way, you can set wgReadOnly for the world, but you still allow update.php to be runned [22:36:02] that way, wiki stays live (update.php shouldn't put it down), and you save some work [22:36:04] Did you guys find the learning curve steep for mediawiki, especially the content side? [22:36:21] I've been doing it... 15 years at this point [22:36:22] Thank you, I didn't realize that would be an issue! [22:36:24] It's hard to remember :) [22:36:50] The proper set up, with categories, templates and taxonomy, that doesn't even include semanticmediawiki. [22:37:02] I mean, I mostly taught myself, but I would say MediaWiki is one of the easier pieces of software to learn [22:37:04] jtm-lis: depends. templates can be tricky. or some "special" extensions with wired markup [22:37:12] Very well documented. [22:38:00] and talk pages are not easy (if outside of WP) for "newcomers". I have seen people simply not signing their comments, always creating a new section and so on [22:38:02] yes more the deployment regarding best practices has me stumped. I am starting Yaron Koren's book Working with mediawiki to bridge the knowledge gap [22:38:44] My only concern is that I know I will have some breaking bugs when I run the scripts [22:38:51] I ran into them during my test upgrades [22:39:03] I just don't want to serve busted content [22:39:29] Plus, if I do it on my test server, I can leave the debug options on to better confirm which bug I'm encountering.