[00:00:04] /static.miraheze.org/allthetropeswiki/8/86/Logo-Square-v1-1x.png [00:00:07] //static.miraheze.org/allthetropeswiki/8/86/Logo-Square-v1-1x.png [00:00:37] how do you find that out [00:00:50] Look at the CSS [00:00:50] .mw-wiki-logo { [00:00:50] background-image:url(//static.miraheze.org/allthetropeswiki/8/86/Logo-Square-v1-1x.png) [00:00:50] } [00:00:51] the only markup i see for the link is this: [00:01:01] Reedy: ah i see [00:01:02] thanks [07:02:24] Hello, I asked a question on mediawiki.org. See https://www.mediawiki.org/wiki/Topic:Vp8re7r9ndwph7if. I will very thankful if someone can answer this. [07:03:03] It is related to Structured Discussions. [08:07:18] Hi there! [08:09:33] Does anybody know how to resolve this issue - PHP Fatal error: Class 'DatabaseMysql' not found in htdocs/wiki/extensions/SimpleSecurity/SimpleSecurity_body.php [08:11:56] MediaWiki 1.34.2 [08:12:54] SimpleSecurity 5.1.0, Centos 7, php 7.2 [08:14:20] hm... Latest version of SimpleSecurity supports mediaWiki 1.24... :\ [08:14:43] Is it exists some alternatives to SimpleSecurity? [08:18:46] what does it do? [08:19:02] The SimpleSecurity extension extends native MediaWiki protection to allow article's viewability to be restricted. [08:19:12] ah [09:11:38] Hello [09:12:12] In my wikipedia page i want to install fontawesome icons. [09:16:16] Hello [09:16:59] I have a wikipedia page. I want to install fontawesome icons [09:22:29] AlexeyX: I don't think anyone maintains the SimpleSecurity extension anymore, that class hasn't existed for a while now [09:23:33] AlexeyX: also, it seems that there are unfixed security issues that make it not work properly, via the linked bug ticket from the top of https://www.mediawiki.org/wiki/Extension:SimpleSecurity [09:23:46] so I wouldn't recommend continuing to use it. I think Lockdown is more widely used/maintained [10:34:33] legoktm, thank you! [10:36:27] :) [11:48:56] Hi. I'm having technical difficulties with my mediawiki. I updated and upgraded packages and restarted the server, and now I get an error when I try to access (www.fithydro.wiki). Anyone know what can be the cause based on the errrors? [11:50:16] I also installed the Scribunto extension in this period. But even after deleting it and removing the LocalSettings.php edits, I get the error [12:11:19] Marekatt: how did you install mediawiki? [12:12:40] gry: not sure what you mean. It's installed on an ubuntu virtual machine (Azure), if that's what you refer to [12:13:21] The actual installation was done by our IT help, not by me. I imagine this could be a problem with the SQL connection, but I didn't change anything concerning that in LocalSettings [12:13:59] I see [12:14:51] Is mysql even running? [12:15:02] Upgrade packages and reboot is often a good way to break things [12:15:37] Good question. Let me check real quick [12:17:16] mysqladmin: connect to server at 'localhost' failed [12:17:24] I guess this means it's not running [12:17:56] If it is indeed running on the same machine [12:18:38] Reedy: You were right. I started mysql and it works now [12:18:49] Stupid mistake, it wasn't set up to automatically launch on restart [12:19:06] I was just gonna say, you might want to reboot to check if it's a one off, or it's broken for autostart [12:20:00] I just enabled autostart. Will reboot and make sure it works now [12:22:03] Perfect, rebooted and everything is fine. Was just missing that one setting. Thanks a lot (you've helped me many times now) [12:47:38] Now I have another issue: I installed Scribunto according to the instructions. I configured localsettings and added permissions for lua. However, I don't see either Lua or Scribunto on my special:version page [13:12:13] I am told I need the sanitized-css content model, but I can't figure out how to install it... [13:13:50] Marekatt: sanitized-css is added by https://www.mediawiki.org/wiki/Extension:TemplateStyles [13:14:48] I installed that extension, but it's not there. I guess I can try to reinstall it [13:18:30] Majavah: Do I have to configure it before it will show up in special:version? I got the extension and LocalSettings config set up but TemplateStyles isn't there [13:19:27] Marekatt: no idea, but something is broken if you have it in localsettings and its not showing up in special:version [13:19:29] Aaah I was editing the wrong localsettings file... that explains a lot [13:19:41] was just about to ask about checking that :D [13:20:32] It also explains other issues I've had today '=D [15:41:38] hello [15:42:12] i'm trying to figure out how this wiki is customizing the colors for the vector theme: https://wiki.voidlinux.org/ [15:43:12] i notice that this page is empty: https://wiki.voidlinux.org/MediaWiki:Vector.css [15:43:36] and this page doesnt appear to have any configurations for the top/left bars: https://wiki.voidlinux.org/MediaWiki:Common.css [15:49:02] It's not impossible they've chaned the actual CSS files [15:49:49] https://wiki.voidlinux.org/load.php?lang=en&modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cskins.vector.styles&only=styles&skin=vector [15:56:57] Reedy: yeah i found that via the developer console [15:57:03] but i wasnt sure how to interpret that [15:57:24] i.e. does that say anything about whether the custom css is stored in a wiki page? [16:01:07] AIUI none of those listed modules are wiki page css files [16:01:17] ok [16:01:37] and if a wiki page css file were being used, it would be listed in the query string for load.php? [16:02:21] Not quite [16:02:28] it would be modules=site.styles [16:03:44] as ResourceLoaderSiteStylesModule is what includes MediaWiki:Common.css and MediaWiki:Vector.css etc [16:09:32] ahh okay [16:10:01] so that would suggest the css is hardcoded in the theme [16:10:16] [16:49:02] It's not impossible they've chaned the actual CSS files [16:10:17] Yeah [17:01:08] Hello, can I import Spanish Wikipedia into my own MediaWiki ??? [17:01:42] You were asking that question yesterday [17:02:34] Reedy I know that yes??? [17:02:55] Why do you keep asking questions you've already got answers to? [19:20:29] hello! Community Tech's work on watchlist expiry will not be completed in time for MW 1.35. What do we typically do about incomplete features? Maybe simply write in the release notes and at mw:Manual:$wgWatchlistExpiry (feature flag) that it shouldn't be used in production? [19:21:32] musikanimal: Won't be ready for the branch cut, or for the full release? [19:22:42] branch cut for sure. The email we got earlier said that means features won't be backported [19:23:06] That's right [19:23:14] But if you're finishing off features, or fixing bugs in them, that's fine [19:23:41] If you started something after the branch was cut, that wouldn't be backported without very good reason [19:27:07] got it. So the full release is aimed for August? I'm not certain we'll be done by then either, or at least not fully rolled out to our wikis. I guess we'll reevaluate as the time gets closer, and keep tagging mw-1.35-release in the meantime [19:27:42] I don't know what the date is offhand [19:29:18] I suspect stripping out the commits will be excessively time consuming... And even just removing all the code is probably icky [19:29:39] A problem with a feature flag is we're going to have people trying to use it... And as 1.35 is an LTS, that's a long time to potentially support it [19:29:48] Sure, again, we can backport for a point release so it works "eventually" [19:30:15] yeah, I don't think we can undo everything we've done for 1.35. If we need to back out I think we should just say in the docs that that feature isn't guaranteed to be stable and shouldn't be used in production [19:31:45] most people I assume we'll refer to mediawiki.org, release notes, and DefaultSettings.php about feature flags. There we can clarify $wgWatchlistExpiry is experimental [19:31:54] *will refer [19:32:00] Hopefully.. but you never know [19:32:05] Make sure you tag at least one task into the 1.35 workboard, so people know we need to re-evaluate [19:32:12] will do! [19:32:20] Like I say, we could end up saying that it's working in 1.35.1 [19:32:24] I don't think that's unreasonable [19:32:42] agreed. Thanks! [19:34:11] I think 1.35.1 is probably going to be... end of september? So might not be long enough.. Can still backport stuff and go for 1.35.2 which would be the end of the year [21:32:53] musikanimal: I'd either document it as @warning EXPERMENTAL (see other examples, means no use in prod, and might change/disappear), or if you really want to disallow it, remove the config var and change the primary ref to a hardcoded boolean false inline as a REL1_35-only patch. [21:33:31] and either way, yeah, remove from rel notes or rephrase accordingly. [21:35:53] good to know! so should we be making this decision just before the August release or by the "pencils down" date next week? [21:35:59] there's a chance we'll have a MVP completed next month. Not a very strong chance, but a chance... [22:23:59] musikanimal: fine either way, doesn't matter much :) [22:47:57] Good day