[02:48:44] When using {{#tag:ref}} is it possible to conditionally specify a name? [03:07:41] Andrio: no. however, you can wrap the entire thing in an {{#if:}}, like this: {{#if: {{{name}}} | {{#tag:ref|contents...|name={{{name}}} }} | {{#tag:ref|contents...}} }} [03:09:57] That's what we did, yeah. [03:10:07] I'd rather not duplicate the whole thing if possible. [03:10:20] Also it's {{{name|}}} [04:04:44] hey guys, we restarted our server which hosts our mediawiki and now it doesn't work any more. im getting a "You don't have permission to access /mediawiki on his server." error [04:05:08] do access permissions get defaulted on restart or something? [05:19:40] Swiggie: work with your host, that error could mean any number of things [05:19:54] if you are the host, check the error logs for more details [11:01:18] duesen: around? :D [11:04:36] addshore: hey [11:04:42] woo! [11:04:55] Could I get some thoughts from you on https://phabricator.wikimedia.org/T233520 ? :) [11:05:12] I hope the intro in the description explains the exact issue [11:12:51] If I have elements inside elements, is there a way to make it so 1) transclusion skips the tags 2) no extra funny tags appear as translatable strings ? [11:13:31] I mean, if I wrap inside , I get the onlyinclude tags as translatable strings etc. [11:13:57] Is using "Labeled Section Transclusion" the only answer? [11:25:23] addshore: i'll have a look in a bit [11:36:15] [= [11:38:02] addshore: i didn't do a full analysis, but I added a quick comment from my first take on this. [11:38:38] I'm pretty swamped, if you need more input from me or brad, tag #core-platform-team to get it on our board [11:38:41] sounds like using RevisionDataUpdates might be the right thing to do! [11:38:49] I wonder why we didn't. [11:38:53] I think that is already the pointer that I needed! [11:39:04] RevisionDataUpdates looks quite new [11:39:14] That may actually be code I wrote. And I also introduced DataUpdates. I should know better ;) [11:39:16] considering how old that change prop and update code is [11:39:22] :P [11:39:54] maybe there is a specific reason. would be good to know. may tell us something abotu how to best fix this [11:40:07] * addshore is going to stare at RevisionDataUpdates for a little bit [11:42:20] although duesen for the general dispatching, we actually want the re parse, so probably not quite that simple, but anyway, the page prop bit should definitely be a doSecondaryDataUpdates [11:43:53] I think until now though, wikibase has been depending on the fact that a links update job would reparse the page [11:46:46] addshore: i think i got this wrong, actually. I'll comment, and maybe look again later. [11:47:01] if it doesn't re-parse, it should be using an existing ParserOutput that already has the right info, though [11:48:49] updated my comment [12:24:20] duesen: It might actually stem all the way back to https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/465157/ still trying to figure out if that change would also have ended up either using cached parser output or no triggering the hook / writing the parseroutput at the end [12:25:13] addshore: is the hook really the problem? isn't the problem much rather that the reparse doesn't happen? if a change is relayed, the page *must* be reparsed. [12:25:30] yes, that the reparse doesnt happen. [12:25:58] just I got to that by figuring out the hook didn't fire [12:26:04] so the update job thinks everything is already up to date, and skips? [12:26:24] well, it still does the doSecondaryDataUpdates stuff [12:26:26] may need to introduce some kind of force flag [12:26:28] even if it doesnt reparse [12:26:47] but then, what'S the problem? all the relevant info should already be in the ParserOutput [12:26:57] including page_item in page_props [12:27:25] so, item creation happens on wikidata which adds a sitelink, this then causes the linksupdate on client, which should add the pageprop [12:27:57] right now, the links update sees the revision on the client page is the same, and there is a parser cache entry, so just uses that, then does doSecondaryDataUpdates stuff [12:28:18] old behaviour seems to have been at that stage, page would always be reparsed? [12:28:45] then https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/465157/ is middle ground where I'm still trying to find out exactly what would have been happening [12:48:00] i had to dive into meetings now [14:26:31] * addshore is back [19:04:58] Anyone know what's wrong with the image here at the bottom? https://unofficial-tesla-tech.com/index.php?title=The_Unofficial_Tesla_Tech_wiki [19:05:47] quantum, please describe what is "wrong" [19:07:43] Just a link to Media:Disass_-_underhood_front.JPG. Used to be when I insert an image it gave all kinds of choices, like size, frame, etc. [19:08:15] [[Media doesn't present the picture at all now. [19:08:32] quantum, have you tried File: instead of Media: ? [19:08:59] Ok File gives the image, but what happened to all the options with pulldowns? [19:09:09] I have no idea what options you refer to :( [19:09:23] Apart from that, there a quite some 404 errors on that page. See the "network" tab of your web browser's developer tools. [19:09:44] No doubt. [19:09:55] It's under sconstruction. [19:10:59] And why does this say use Media? https://www.mediawiki.org/wiki/Help:Images [19:11:12] where? [19:11:22] https://www.mediawiki.org/wiki/Help:Images#Syntax does not. [19:11:37] "Directly linking" [19:11:49] quantum, that's exactly what you're doing. I don't see any bug. [19:12:04] it says Media: because your website DOES directly link. [19:12:09] Exactly what the docs say. [19:12:28] pfff... [19:13:05] ? [19:13:12] linking is not embedding. [19:13:39] Not exacty what the docs say. Setting [[Media:image.png]] just shows the text. [19:14:03] Yes, because YOU LINK to that image. [19:14:12] I need to turn off the frame, size the picture, and that's been removed now. [19:14:14] Just like the docs say. [19:14:42] No idea what "removed now" means and what is the thing before "now". [19:15:06] Ok... [19:16:24] You wanted a link to the image. So you got a link to the image. :) [20:29:16] hello, is there any way how to have a template parameter contain several = characters? {{Template|blabla=hello secondblabla=yeah third=sdfsdfsdf}} the thing is I want to have the whole parameter as string and process it with scribunto [20:42:02] baruna: the only way is to use named parameters. Or use 1= for the first parameter: {{Template|1=blabla=hello secondblabla=yeah third=sdfsdfsdf}} [21:17:09] Vulpix: well and in the template {{Template|blabla=hello secondblabla=yeah third=sdfsdfsdf}} [21:17:42] Vulpix: there's one parameter blabla and the rest is parameter value? [21:18:02] yes [21:18:14] I guess that's enough then [21:18:19] should work as well [21:18:49] just not with arg[1] but arg[parameter_name]