[02:33:52] <bedivere>	 Hello there. Is there a way to hide external links on a wiki?
[02:34:31] <bedivere>	 I mean, making them unavailable for non-logged users, but available for those that are logged in
[03:06:05] <moonmoon>	 bedivere: uh, you could do it with group-specific CSS, but it seems a bit odd
[03:07:14] <bedivere>	 yeah, I thought so. In fact, it only matters to me to hide references, so I used some CSS to do the trick, but found no way to actually hide (unlink) external links to non-logged users
[11:08:13] <MTRNord[m]>	 Hi :) I have a custom docker image with lots of plugins. I am currently using ExtensionDistributor where possible to fetch the plugins from. However this doesnt seem to provide permalinks (aka REL1_37 for example or permalinks to the commits) which makes reproducible docker images hard and updating a pain (Its well over 70 plugins iirc). Does there exist a smarter way to do this? 🤔 Is using git the better solution maybe?
[11:18:04] <zuzak>	 bedivere: you could do a.external { display: none; } in Mediawiki:Common.css and then undo it with an !important in Mediawiki:User-group.css but it won't be a secure method
[13:19:38] <rundg[m]>	 I use composer.local.json to specify my components and then have composer update in my app docker file.
[13:29:38] <Reedy>	 MTRNord[m]: ExtensionDistributor is designed to purposefully give the latest commit of that branch of that extension
[13:33:48] <MTRNord[m]>	 Reedy: Yeah and I guess that makes sense for the usecase it was designed for :) but I guess that's not the usecase I have :D 
[13:34:02] <MTRNord[m]>	 <rundg[m]> "I use composer.local.json to..." <- Interesting. So you just make the file and copy it over to the docker? 
[13:34:49] <Reedy>	 You can use github to basically provide zip tarballs of specific commits etc
[13:34:55] <Reedy>	 if you really wanted to continue doing it that way
[13:38:18] <MTRNord[m]>	 Well I would love to switch to a way that is possible to get automated away in a ci :)
[13:38:31] <MTRNord[m]>	 So composer seems like a more proper solution to that
[13:53:36] <rundg[m]>	 Right. It's versioned in git, and part of the docker build context 
[14:07:08] <MTRNord[m]>	 <rundg[m]> "Right. It's versioned in git..." <- Sounds good. Thanks I will try that :) 
[14:32:46] <Guest91>	 Hello everyone. I have a wiki that is running on MW 1.26. It was working fine till last week and then suddenly some pages started showing error that "the revision of the page named does not exist." I restored the database from my back but it's still showing the error. Some pages are working fine but most of them giving this error.
[18:38:00] <MTRNord[m]>	 Hm ok somehow I have an issue with using the composer approach. https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/tree/REL1_37 has no name set and makes composer "explode" trying to install it. So I wonder what I am doing wrong :)
[18:39:24] <MTRNord[m]>	 The MobileFrontend is not published hence I am using the git :)
[18:41:50] <Reedy>	 there's a flag you can use to make it not do that validation
[19:05:17] <MTRNord[m]>	 rundg: seems not to work for me with composer.local.json as most plugins in https://github.com/wikimedia have no name set in the composer.json which makes it impossible to require them :/ judging from https://packagist.org/packages/wikimedia/ there are barely any of these published and it looks like the ones that are not published have no name field
[19:05:26] <MTRNord[m]>	 thats like 3/4 of my plugins :/
[19:08:47] * MTRNord[m] switches to using git submodules for now
[19:09:24] <MTRNord[m]>	 Installing extensions in mediawiki is sadly my major pain point with it when using a big amount of extensions
[19:34:26] <Reedy>	 https://phabricator.wikimedia.org/T311321
[19:35:30] <MTRNord[m]>	 thanks. I switched to git modules now. It seems easier than to do that
[19:35:44] <MTRNord[m]>	 Its also more git native which is nice
[19:39:43] <MTRNord[m]>	 Also the suggested fix to run it with "--no-check-publish" doesnt work for installing as that option does not exist on the update command it seems :)
[19:56:52] <bedivere>	 zuzak, thanks. Will do that for the time being.
[22:12:23] <mporubovic22>	 Hello, I'm trying to wrap my head around the wikidata API - is it possible to get an entity with all of its properties including the property labels, and not just ids, in one query? Put another way, what query will return all the data present here - https://www.wikidata.org/wiki/Q42 ?
[22:12:23] <mporubovic22>	 https://www.wikidata.org/w/api.php?format=json&action=wbgetentities&ids=Q42 does return the property ids but not the actual label of the property. Any suggestions for a newbie? Thanks