/div``` [01:29:15] no thanks [01:29:40] I misunderstood you then [01:29:59] i think by header i meant "heading" [01:30:10] a specified heading [01:30:18] you could do a div with big font size [01:30:19] oh cool thank u! [01:30:20] :shrug: [01:30:34] What Stack said [01:30:36] you're right [01:30:40] no problem - in general, you can use template parameters in inline html and css styling pretty freely, it can be really useful sometimes! [01:31:54] oooo ic ic, good to know! [03:09:31] [1/2] are 2k resolution image thumbnails banned or somthing [03:09:31] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1352116820261343313/image.png?ex=67dcd86b&is=67db86eb&hm=6572361f204623f25f72a19e140f3a51737e41bdd49a9dada6597d77912ddb46& [04:33:23] [1/3] can someone look over this code and tell me why it's showing up as the right when it's supposed to show up like ":bestcharacteringame: CharacterName"? the images aren't on the wiki yet so that's not an issue [04:33:23] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1352137923499266189/image.png?ex=67dcec12&is=67db9a92&hm=47cad5571f0b00c3f9adc197d8cbb065627c0afd8f9c05171670852c2893b25b& [04:33:23] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1352137923847524485/image.png?ex=67dcec12&is=67db9a92&hm=5400fcb81f0ce75a8356004002b238a44fdfb987d6c41babf40452e19c199d7a& [04:40:34] maybe remove includeonly and see if it works? [04:46:42] [1/2] nope [04:46:42] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1352141277268934676/image.png?ex=67dcef32&is=67db9db2&hm=4393bc925ff18a03d6026bfe368badd7bc309e4206afc11b6a209cac46a13c0e& [05:05:50] maybe do {{{char|}}} ? [05:13:00] nada :/ [05:51:11] link to template? [05:53:46] im importing it from a fandom wiki with some massive edits, so it may be wack [05:54:07] https://toyboxfunhouse.miraheze.org/wiki/Template:NavInput [05:59:56] fixed ! missed out a ] [06:00:01] its even in the embed lol [06:02:53] oh shit LOL [06:03:24] ta [06:20:58] Extra definitions? [07:55:06] guys guess what [07:55:13] my game failed [08:36:04] They were taken from yeah... they are from their wiki. I copied that over as it is for categorisations I guess [09:29:06] folks, only wiki owner are allow to edit MediaWiki:Common.css? [09:29:38] bureaucrat or administrator [09:29:46] well I have both of that [09:30:19] https://cdn.discordapp.com/attachments/407537962553966603/1352212650821685319/QGlvr9E.png?ex=67dd31aa&is=67dbe02a&hm=fcd4e5b61fcf16665a7a30fa8ea49f696e75724136827cf1f0af13804688bf37& [09:30:25] make sure you are logged in [09:30:29] I am [09:30:43] poked around user permissions? [09:30:54] or namespace settings [09:37:10] That kinda not work haha, that aside I just have to change url of bg to the one upload via Miraheze right? [09:38:01] the current url is upload via fandom [09:38:29] if that the case I'll just ask the owner then [10:08:21] can I change the username of the users in my wiki? [10:14:17] no since user accounts are shared across all miraheze wikis [10:14:28] they can file a global rename request if you want to though: [[Special:GlobalRenameRequest]] [10:14:29]

[12:28:53] I was meant like did you changed something in there before, potentially removing your permissions [12:48:21] no I didn't [13:02:07] do you even see Administration sidebar? [13:08:03] what is the best method of setting a global font on your wiki [13:11:57] [1/3] CSS, there's no other method? [13:11:58] [2/3] if you meant adding a custom font tho, you can import one from external resources like Google Fonts, or will have to upload font file right on the wiki (as long as it's not pirated) [13:11:58] [3/3] still has to be set up in CSS [13:12:25] sorry i mean importing google fonts or uploading it [13:12:49] long story short i used to use fandom years ago now im back but on miraheze and struggling lol [13:13:11] importing is easier, because you already know it's free and legal and you won't have to fiddle w/ files [13:13:32] yeah well, aside from pre installed fonts on Fandom it was all same [13:13:57] I was taught to weird recoding shit in CSS to have custom fonts on Fandom [13:14:44] back in Wikia days, mind you [13:14:59] its been a few years since i've used any wiki so im a little rusty [13:15:32] [1/2] but this does absolutely nothing [13:15:33] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1352269330863362159/Screenshot_2025-03-20_091523.png?ex=67dd6674&is=67dc14f4&hm=d5d101406f57568c8bf4326c92644625e1f40955b6f2b8b1fb129358fc4f3992& [13:15:52] https://discord.com/channels/407504499280707585/1351743646742872125/1351861544643985429 [13:16:33] give it a bit time or kick the cache w/ `?action=purge` in URL [13:18:12] i purged the cache and its not doing anything either [13:18:52] wait [13:19:17] [1/2] this? [13:19:18] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1352270273864400991/l2mpYqF.png?ex=67dd6755&is=67dc15d5&hm=055427c58d3ad9cd4471f226e6d1cd9c0b28d19342c436efd65d8191669a72d3& [13:19:19] you missed space break before `!important`, it would break the code [13:19:59] [1/2] yeah [13:19:59] [2/2] hmm idk what's going on then [13:20:33] you missed space break before `!important`, it would break the code [13:20:47] oh shoot [13:20:57] also which skin you're using? [13:21:53] i've heard the Previews extension has issues when displaying pages due to the TextExtract extension having caveats and this is also stated on it's documentation page, though it seems you have to have TextExtracts enabled to even use previews? [13:22:20] [1/2] https://cdn.discordapp.com/attachments/407537962553966603/1352271041870954620/image.png?ex=67dd680c&is=67dc168c&hm=a5f997e4b9168a575986f37af1440864ab52f8b39b34bf7b203a7f67990593e6& [13:22:21] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1352271042126811207/image.png?ex=67dd680c&is=67dc168c&hm=5a7f38d2628d87d976b297ddc850bcbaeb4cd581d69885689d040441e203250a& [13:22:32] timeless [13:22:46] is there a way I can disable it or not..because if they don't support using it .... how come i gotta enable it to use previews [13:24:08] [1/2] TextExtract is still on Miraheze and it used by couple of other extensions I'm pretty sure [13:24:08] [2/2] if you worry previews won't work - it works on my wiki [13:24:26] oh noo, i'm trying to troubleshoot this because it doesn't work on mine [13:24:47] [1/2] and I found this as a solution to my reservation https://issue-tracker.miraheze.org/T11755 [13:24:47] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1352271655409553408/image.png?ex=67dd689e&is=67dc171e&hm=7b3a62364721bdd880801d4005c4b1c942e6f1faa91f1abecf9310c40e7a41e5& [13:24:54] is your wiki w/ portable infoboxes? [13:25:00] uumm [13:25:14] ah, wait, wrong issue [13:25:17] nvm [13:25:38] i'm not sure if it is with portable infobox but it seems to work and not work whether there is an infobox or not [13:26:33] i come from fandom so the whole skins thing is new to me [13:27:07] [1/2] honestly, I knew a guy who made JS link previews on Fandom Dev Wiki [13:27:07] [2/2] considering how often people have troubles w/ extension I wonder if it's possible to turn into a gadget [13:27:13] on Miraheze [13:27:20] wait a second does this not also include changing the font for headers and stuff [13:27:24] poossibly...it's a bit annoying [13:28:05] [1/2] yeah, well [13:28:05] [2/2] different skins behave differently and targeting `body` won't always work for the whole wiki [13:28:26] oh boy [13:28:50] all my wikis use Timeless, I poked it quite enough if you need examples [13:29:09] I suppose you know the element inspector routine [13:29:54] yes [13:30:11] i think it just changed the font for everything but the headers [13:32:23] which wikis [13:33:15] [1/3] softcell.miraheze.org [13:33:15] [2/3] gogigantic.wiki [13:33:16] [3/3] bear in mind that Common.css is for things across all skins, and there are skin specific pages, in this case MediaWiki:Timeless.css [13:35:26] yeah ik [13:51:30] @theoneandonlylegroom thank you sm btw [13:51:59] also one other thing, how should i know which stuff should be on the common css vs the timeless css [13:55:22] [1/2] imports, including fonts, modification of elements like core MediaWiki icons, wikitable class or UI and your own styling like for templates would go to Common.css [13:55:22] [2/2] modifications of elements that belong to certain skin better go skin specific CSS [13:58:19] so i dont need to import the font again on the timeless css to use it there? [14:00:03] correct [14:00:14] just use font-family over there [14:03:46] also there's TemplateStyles extension, which would significantly unload Common.css if you style templates a lot [14:04:13] meaning certain CSS will load only if corresponding template is on the page [14:05:00] Oh nice [14:55:56] Dumb question but is one-time image usage during talks on the wiki allowed? [14:58:37] depends on individual wiki [14:58:48] but I'd avoid that [15:07:29] is there a recommended size for a wikis background image [16:12:53] If you mean the file size, the less, the better [16:13:27] And for resolution, the higher (with less lossy artifacts), the better. [16:41:42] where can i find the css required to import this template? [[dev:Template:Mbox]] [16:41:43]

[17:01:50] lmao [17:02:01] it because admin doesn't have permission in first place [17:02:19] now it working [17:03:14] that's weird [17:03:35] by default admin and sysop are able to edit it [17:17:08] the permission was split off from admin and became part of interface admin [17:17:23] so it either needs to be added back into admin or you need to be part of that group [17:59:36] [1/2] This page: https://meta.miraheze.org/wiki/Extensions [17:59:37] [2/2] Explains that there are extensions that can be enabled/disabled, but doesn't explain how to do so. [18:01:41] Interesting oversight [18:01:59] Actually I’ve also wanted to go and update the list of declined extensions and reasons why [18:06:36] Where exactly do I go and update the enabled extensions? [18:07:01] The enabled extensions list on that page? It’s maintained by a bot [18:07:11] No, on my wiki. I want to enable a new extension. [18:07:15] Oh [18:07:21] [[ManageWiki]] [18:07:22]

[18:07:34] special:ManageWiki/extensions [18:10:16] Administration sidebar, Manage this wiki's extensions [18:11:33] that’s concerning [18:19:03] [1/2] many things need to be rewritten tbh [18:19:03] [2/2] but then I look at source code and see Translate's marks 🥲 [18:20:01] It’s [18:20:02] Better [18:20:04] Then before [18:20:06] (???) [18:21:25] newcomers are still confused by logo/favicon, no mention of wordmark (no that Vector 2022 is default) + Timeless hijinks now [18:22:30] If that’s something that can be added as labels to settings, we could update that [20:23:23] is custom cursors allowed in Miraheze? [20:31:17] yes [20:31:29] just don’t make them obnoxious or hard to use [20:35:13] or else we feed them to Labster [20:38:12] the blue labster?!?! [21:58:08] [1/2] https://discord.com/channels/407504499280707585/1260019919643344897/1352255171752624221 [21:58:08] [2/2] What kind of issues does this pertain to? I have an issue with a database thing for my wiki and I am wondering if the fix includes it. [22:07:40] Special:WantedPages and the such not updating [22:10:27] :DoneMH: [22:30:38] huh, [[RfS]] gets more views then the [[Stewards]] page?? [22:30:39]

[1/2] [22:30:39]

[2/2] [22:30:43] wacky [22:41:36] trivia time what is the single most viewed page on Miraheze Meta? [23:02:09] I would guess the Main Page (Which would be the safe geuss on ANY wiki tbh) [23:08:59] That is second place actually [23:57:16] I sometimes see a >5-minute lag between editing a setting (in this case, Common.css) and when the change actually takes effect. Is that normal for Miraheze?