[01:12:21] Woodpecker: what did you find? [02:55:03] hello, is anyone around to assist with what is more than likely a very simple issue? [03:09:36] Anyone around? [03:25:26] ? [03:44:24] Hello? [04:59:20] GauchoDude: hi [04:59:26] GauchoDude: what is the issue? [05:00:18] @Sveta, probably fairly simple ... want to rectify the "Error creating thumbnail: File with dimensions greater than 12.5 MP" issue [05:00:45] GauchoDude: okay, please hang on [05:00:46] Its a config var [05:00:58] Surely there has to be more than just increasing $wgMaxImageArea [05:01:00] $wgMaxImageArea or something [05:01:27] Gif images use different var [05:02:08] also 12.5 MP hasnt been the default for years i think. Is this really old version of mw? [05:03:07] although im not really sure of that. Maybe 12.5 really is default but that seems extremely low [05:03:16] Not to my knowledge? Running an XAMPP package downloaded in January of this year [05:03:35] Unless an old version is included in that, but I would imagine not? [05:04:01] I suspect xampp package is probably outdated [05:04:28] Interesting ... would it be too difficult to upgrade without throwing everything out of wack? [05:04:34] except for debian package most packages are really old [05:05:11] you can check by going to the page Secial:version on your wiki [05:06:27] usually upgrades are painless but going from package to non package might be complicated. Depends if package modifies stuff [05:06:46] GauchoDude: https://www.mediawiki.org/wiki/Manual:Errors_and_symptoms#Error_creating_thumbnail:_File_with_dimensions_greater_than_12.5_MP suggests increasing $wgMaxImageArea [05:06:47] Product Version MediaWiki 1.30.0 PHP 7.2.0 (apache2handler) MariaDB 10.1.29-MariaDB Lua 5.1.4 [05:07:02] ok, thats modern [05:07:10] so you are up to date. [05:07:31] ireally thought default img area was higher. Guess i was wrong [05:08:19] For what it's worth, the file that first tripped this was a 1.46 MB jpg which is 4448x3872 pixels [05:08:59] it is 17,222,656 pixels [05:09:05] oh. Non progressive jpgs shouldnt trip this at all [05:09:22] maybe the jpg was in progressive format though [05:09:58] but if the jpg is in "baseline" format the image area restriction shouldnt apply [05:11:05] So how should I proceed? [05:11:26] make the jpg in baseline format, or increase wgMaxImageArea [05:11:43] Set $wgMaxImageArea = 5e8; [05:11:54] or some higher number [05:12:34] That's what I thought, but wanted to check with smarter people :) [07:55:42] For what date is MW 1.31 planned>? [07:56:57] Found it: June https://www.mediawiki.org/wiki/Version_lifecycle [07:57:02] Any more precise date? [08:53:54] I'm trying to install Mediawiki with composer, and I got a vendor-folder with different libraries. I think that's good. However, what about images, LocalSettings.php and the skin? I'm helping with an existing installation that runs 1.24 and would like to get it 1.30 [08:54:47] mads: I'm not sure I understand the question [08:55:17] composer is usually used to install library dependencies of MediaWiki, but its not used to install MediaWiki in general [08:59:43] bawolff: Hmm. I'd like also to put the project in version control, and having the Mediawiki core code there seems to be a bit silly. My question was mainly if I should touch something inside the vendor-folder? [09:00:38] mads: what type of project are you doing? [09:02:11] https://comicwiki.dk so basically, a Mediawiki installation which has a custom skin that the current owner made. I'm unsure if that answers the question. [09:02:47] mads: Ok, so its for managing your deployment? [09:03:17] Often people clone mediawiki's git, and then use submodules for extensions and whatnot [09:03:35] yes, I guess, and making it easier to upgrade than currently is the case. [09:03:56] (e.g. Wikipedia uses the branch origin/wmf/1.32.0-wmf.3 ) [09:05:04] people then use composer to get libraries as a separate step from git, although other people cmmit the libs to git (For example, for security reasons so there is a clear audit trail of precise library code that was deployed) [09:05:45] OK. PHP's way of handling base project dependencies is different from Ruby and Python. [09:06:27] e.g. Wikipedia, commits it all to a repo (https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/vendor/ ) but that's more for a security thing [09:36:06] I see. The security aspect about library code in a repository is weird to me, instead of handling everything through a package manager. [09:39:06] Well old versions of composer didn't use https to fetch things. I think that's fixed now [09:39:32] A lot of it is an auditing thing - its nice to be able to ensure we can figure out always what code we are running, and what code we were previous running [09:39:48] If you're not a high profile site like wikipedia, its probably not something you need to care about [09:42:08] The number of daily visitors is less than 1000, so yes, definitely not a high profile site. [11:09:16] Updated ubuntu from 17.10 to 18.04... I have not been able to get it working again. https://www.irccloud.com/pastebin/W5mmdopy/ [11:20:21] ignore that. [13:22:57] I reinstalled my mediawiki, and now I get this when I try to access my api. What is the issue here? https://www.irccloud.com/pastebin/jlHLmSZ2/ [13:23:58] It's not being processed by your webserver as a PHP file [13:29:02] Reedy: okay... wonder how I can fix this. [13:32:43] hi, what is the most preferred extension to show graphs on mediawiki? (atm 1.28) [13:36:52] the Graph extension, probably [14:30:13] anyone knows if there is any requirement to cargo format=bar chart ? [14:30:35] by following the doc seems that nothing is required [14:51:15] Dear pals, is there any way to calculate the number of links in page? [14:51:33] Have a page of links to categories, want to know how many links are there in this page. [14:51:39] Look it up in hte DB [14:51:41] Thanks! [14:51:54] Sorry, Reedy? [14:52:04] Database [14:52:11] What commands of mediawiki assist in this? [14:52:39] Well, let me speak in details. I have a list of NN categories to be created and filled. [14:52:56] From time to time I create a category & put the link in this list. [14:53:12] This means, I convert simple line to a linked line. [14:53:40] I know the number of lines. Could I calculate the number of links, I would know the %% of task completed. [16:18:24] hi, anyone familiar with good auto-complete (for wiki-text) extension? [16:52:23] niso: there's LinkSuggest for links and templates [16:52:26] !e LinkSuggest [16:52:26] https://www.mediawiki.org/wiki/Extension:LinkSuggest [18:00:27] legoktm: You are not by any chance in Barcelona, are you? [18:01:12] FoxT_: nope :( [18:02:01] I'm on IRC though! [18:02:44] He's here in our hearts [18:03:08] Ah, zut. Would have loved to talk about the RFC. It's easier in person. Maybe next time. [18:06:24] just need to convince my university to move finals a week earlier :p [18:10:26] legoktm: Should be easy. :) Your finals or somebody elses and you just have to be there? [18:10:40] My finals :p [18:10:47] Good luck then! [18:11:08] thanks :) [19:00:43] vulpix: looks great! [19:01:07] theres anything that know to auto complete params for the current template or the written templates? [19:06:27] best practice when calling templates is to write: {{template:my_tem}} or {{my_tem}}? [19:07:57] latter [19:08:08] if it's in the Template: namespace, don't include the Template: [19:10:25] ty, y that? [19:10:37] extra typing for no reason [19:10:54] the entire purpose of the template namespace is to use them in {{templates}} [19:10:54] it's why it exists [19:33:22] congrats Isarra https://meta.wikimedia.org/w/index.php?title=Grants_talk:Project/Isarra/Timeless:_Post-deployment_support&curid=10550666&diff=18056581&oldid=17970294 [19:34:00] \o/ [19:34:04] Nemo_bis: Thanks! [19:34:14] I'll fill out the paperwork later. Hackathon now. >.>