[00:59:42] ---------- [01:03:24] [1/2] https://meta.miraheze.org/wiki/Help_desk?diff=prev&oldid=451751 [01:03:24] [2/2] Are there others that have issues with Dark Mode? [01:16:42] [1/4] ---------- [01:16:42] [2/4] Are there others who have difficulties uploading images? [01:16:42] [3/4] See: `Could not create directory "mwstore://miraheze-swift/local-public/5/57".` and `An unknown error occurred in storage backend "miraheze-swift"` [01:16:43] [4/4] https://meta.miraheze.org/wiki/Community_portal#Error_when_uploading_images. [01:29:29] > Are there others that have issues with Dark Mode? [01:29:29] Not the ones mentioned there, no. We fully customized our dark skin so I think it might be why [01:29:29] of course, there were still various issues to deal with, Vector 2022 defo changed in between updates [01:30:26] https://meta.miraheze.org/wiki/Help_desk?diff=prev&oldid=451751 It seems so [01:30:27] biggest issue I observer that might not be immediately obvious to users is that an option to switch dark mode for visitors/unregistered users seemingly is no longer available, According to MW docs it would require switching $wgVectorNightMode['logged_out'] = true; variable [01:31:28] I don't really have a MW installation to test if it brings back the setting though [01:48:34] @cosmicalpha maybe we should look into doing rolling releases in the future [01:57:16] Might be something to consider, yes. [02:00:02] [1/2] What can users do who have issues with Dark Mode? [02:00:03] [2/2] Seems the Css is "ruined" - Do they need to adjust their [MediaWiki:Skinname.css]? [02:00:54] Or does a Phorge ticket have to be made? [02:02:37] I mean, those issues will be likely CSS changes needed to be made, so that's MediaWiki:Skinname.css indeed [02:19:27] we can test it on an upcoming minor update or extension if we get to it [02:20:55] anyways, not sure why swift issues didn’t show up on nexttide [02:21:12] We should promote nexttide more heavily next time too [02:22:24] I think once we have the issues from the update fixed we should do a look back at how we conducted the update things we did well and things to improve on [02:22:59] yes I am getting issues right now, is it being fixed? [02:23:15] I joined just incase it was something I set up wrong with my image file on my end [02:23:58] https://issue-tracker.miraheze.org/T13136 [02:24:11] We know of it. We’re going to look into it [02:24:42] alright! [02:25:11] Our poor unpaid volunteer engineers ran out of wikijuice though so they’re all taking a nap after conducting the update and putting out the fire that was 12000% database load [02:25:20] so may take a bit for us to look into the cause [02:25:30] still not sure how that happens [02:25:37] Yeah... It's 3.25 am here 😄 [02:25:48] 👍 [02:34:40] Question: What exactly needs to change in the css? Are some codes deprecated? or have the tags changed? What do I need to explain exactly? i.e. How have the font colours changed? How has the back ground changed of an infobox? [03:19:52] [1/4] BTW, if anyone wants to do a bit of investigation into the image issues, I have an idea of how to try and narrow the issues: [03:19:52] [2/4] * Go to as many wikis affected by the image bug as possible(discord, phorge, Special:RandomWiki) [03:19:52] [3/4] * check Special:ManageWiki/core and look at the database cluster. If they all are on the same DB, good chance its a mediawiki problem and we know where to start looking. [03:19:53] [4/4] Alternatively, if you look at the url for images on a wiki and poke around maybe ping you maaay be able to find what swift container it’s on but im too tired to try and don’t remember clearly [03:20:13] im heading off and gonna do some looking tmr, feel free to give it a shot if you feel like it [05:34:19] > Internal error: Server failed to store temporary file. [05:34:21] yippee [05:35:48] huh [05:35:54] miraheze and mirabeta have separate messages [05:38:02] Yeah config is deployed manually and we never deployed any of the sitenotice commits to test151 [05:38:45] no, i mean [05:38:46] uploading a file [05:38:50] mirabeta: Internal error: Server failed to store temporary file. [05:38:54] miraheze: An unknown error occurred in storage backend "miraheze-swift". [05:39:14] btw, does logstash give any hints? [05:49:46] BlankEclair: I stumbled upon the cause when I attempted to look at graylog - the cert expired, and the renewal didn't fully deploy [05:50:06] ah :/ [05:50:17] figure we should comment that on the task? [05:50:47] CosmicAlpha is going to fix it shortly [06:00:55] MacFan4000: graylog should be working again also btw. [06:01:20] I fixed Graylog, OpenSearch, and Swift, which all had the same issues. [09:36:56] see original context, have not tested this broadly [09:38:02] Y'all use ELK ? [09:39:43] wats that [09:41:49] elasticsearch? Miraheze wikis cab have cirrussearch [09:42:18] [[mw:Extension:CirrusSearch]] [09:42:19]

[09:50:13] Only mods can see the answer apparently [09:54:20] alu19_: wdym? [09:56:07] link blocked since Alu aren't verified/don't have Miraheze account [09:56:21] Yep [09:56:22] links w/o https:// should get through iirc [09:59:26] ah [10:07:56] We just copied from the URL bar tbh [10:08:01] Was just a link to ELK [17:26:39] @cosmicalpha https://github.com/Universal-Omega/Monaco/pull/35 [17:27:08] Merged [17:28:36] @cosmicalpha maybe https://github.com/Universal-Omega/Monaco/pull/33 as well (but i'm not too sure) [17:28:40] has been a long while [17:29:06] Has conflicts [17:29:13] I'll merge once resolved [17:31:47] @cosmicalpha think i fixed it already, https://github.com/Universal-Omega/Monaco/commit/7d24b887bda8b2fcaed6f6e1ff53ab15b98096fd was done a bit after [17:31:57] Ah [17:33:36] @cosmicalpha ci should be updated to run against MW 1.42 and 43 [17:34:08] hmm the extension requires MW 1.41+ anyways [17:34:14] so ci for MW 1.39 should be dropped [17:35:21] @cosmicalpha https://github.com/Universal-Omega/Monaco/pull/36 [21:21:45] [1/4] @cosmicalpha I know css is not really tech, but due to the upgrade, several users are complaining about broken css. [21:21:45] [2/4] I have asked several how to solve these issues, but so far no luck. Are you able to explain (or link to) what exactly has changed, and how I can help them get their css back in order? Do some codes need to be called in a different way? [21:21:45] [3/4] It especially is problematic with dark mode, font colours and background images. [21:21:46] [4/4] If this is out of your scope, please let me know. [21:31:02] <_arawynn> I remember seeing something about vektor.css needing to be moved to vektor-2022.css (not entirely sure if it's written like that or if it's something along those lines) [21:31:28] That's the biggest thing, there's also some different classes/IDs following the update' [21:32:27] I bet that the help pages for css haven't been updated yet, But I will look for it then. [21:35:07] You're probably better talking to @canyada @rodejong [21:35:39] Tech don't offer any guarantees about on wiki styling though [21:36:16] I haven't seen Canada here in some time though [21:38:53] [1/2] In the updates, some things have changed, It would be good to know what they are. [21:38:53] [2/2] So far no one seems to know 😢 [21:39:08] There should be a changelog [21:39:31] The vector changes weren't documented as far as I can see [21:39:49] I eventually will have to see, but not in the coming days [21:40:21] Someone go yell at wmf on idc [21:40:37] [1/2] https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Scribunto/+/1076802 [21:40:37] [2/2] It seems that "remove unused CSS styles" scribunto-dark-mode could be a the problem? [21:40:40] Please yell at the WMF if they didn't announce it [21:40:50] I'd hesitate on assignment of blame, there's a lot of places it could have been introduced. [21:40:56] Go ahead [21:41:34] were div > figure changes logged? [21:41:55] True [21:41:59] because we had to figure out [21:50:24] https://www.pro.wiki/news/what-new-features-in-mediawiki-1-43-release [21:53:11] Seriously? They needed to AI generate a picture of a field of sunflowers? [21:53:19] man [21:56:45] https://www.mediawiki.org/wiki/Heading_HTML_changes [21:57:02] I guess here are som entries to problems we might face [21:57:04] how much does a stock image of sunflowers cost, even [21:57:57] I'm sure there are plenty of public domain sunflower field photos lol [21:58:57] [1/2] yeah this similar one from [https://www.istockphoto.com/photo/field-with-yellow-sunflowers-at-sunset-in-summer-gm1298291139-391176719](istock) is 15 bucks [21:58:57] [2/2] and as you mentioned there's public domain too [22:02:20] Fuck even stock image, [[c:Category:Sunflowers]] on Commons! [22:02:21]

[22:03:14] there's a direct cat for similar images even LOL ([[c:Category:Sunflower fields]]) [22:03:15]

[22:03:34] I <3 commons [22:09:06] [1/2] MediaWiki has made template maintenance easier and more efficient with the new `EXPECTUNUSEDTEMPLATE` magic word, implemented as a behavior switch. This magic word allows editors to exclude specific templates from the list of unused templates on “Special:UnusedTemplates”, cutting down on noise and spotlighting genuinely abandoned templates. [22:09:06] [2/2] Now that really is an upgrade. [23:39:31] I wanna upgrade my main page and make it look nicer, but I dont know a lot about css to do it, would anyone be willing to take a look and offer suggestions? [23:45:11] You can get som ideas by reading https://www.mediawiki.org/wiki/Manual:CSS [23:45:56] Also this one is really good: https://www.w3schools.com/css/ [23:49:08] I read over them, but these just feel like normal css articles tbh sorrz [23:49:49] I wanna have something that like pops and is fun to use, like the old Cheese E Pedia wiki or the Pizza Tower wiki [23:50:27] rn my main page just feels like a dull navigation page, its kinda bleh and doesnt leave an impression [23:57:47] I am not well versed in css either. But I look at other wiki's and see what they are using, and then copy and paste it to my own wiki. If it works, it works, if it doesn't then I remove it again and look further. 😄 [23:58:26] The css manuals give an explanation when you look at some of the codes you come across [23:58:39] fair yee [23:58:58] I think what I lack is creativity and a good understanding of how mediawiki works mainly [23:59:19] https://animatronicvault.miraheze.org/wiki/Main_Page my main page is like Cheese E Pedia lite edition rn XD [23:59:59] Ouch...