[02:32:27] I have a general wiki question [02:32:39] I think I found a solution, but I'm not following it too well [02:32:54] I want to have a reference section to refer users to pages of a rulebook [02:33:12] one page might have multiple rules sections that are being referenced [02:33:46] how do I apply one tag to multiple sections without duplicating that reference in the references section? [02:37:47] `[ref content]/ref`; afterward, you can just use `` to refer to that reference without duplicating it [02:38:13] and that would be page exclusive right, now across the wiki [02:38:22] Yes [02:38:28] thank you kindly [02:53:10] Tali, I was asking this last night, but wondering if you know [02:53:50] When using the tag, is there a way to make the categories bulleted? [03:12:25] Not really familiar with CategoryTree [03:25:58] It'd probably have to be a CSS thing [03:26:25] rip me [03:26:30] Do you have an example page I could take a look at? [03:27:32] auto modded [03:27:54] You need to /auth to post links [03:28:16] Ah, I can see logs so, [03:29:09] okay I am authorized going forward I think [03:29:14] lmao [03:31:05] You don't appear in the auth logs; did you get a private message from WikiAuthBot giving you a link to verify your Discord account with your wiki account? [03:31:10] yeah [03:31:23] Did you click the link provided? [03:31:28] yeah [03:31:48] Not sure what's going on then; try authing again [04:19:57] [1/13] One thing you can try doing is something like: [04:19:57] [2/13] ```css [04:19:57] [3/13] span.CategoryTreeItem { [04:19:58] [4/13] display: list-item; [04:19:58] [5/13] list-style-position: inside; [04:19:58] [6/13] } [04:19:59] [7/13] ``` [04:19:59] [8/13] But this does funky things with spacing. On chrome (which adds extra space between the bullet and the item for no apparent reason), you may need to add this to make it look a bit nicer: [04:19:59] [9/13] ```css [04:20:00] [10/13] span.CategoryTreeItem a { [04:20:00] [11/13] margin-left: -1em; [04:20:00] [12/13] } [04:20:01] [13/13] ``` [12:26:43] While you can try some of the CSS stuff like Void suggested, if you do want more control over how it looks, https://www.mediawiki.org/wiki/Extension:DynamicPageList3 can produce similar (and lots of other kinds) of lists, but it can be quite daunting to make, the more control you want the more daunting it can be): [13:09:28] I feel so confused trying to change the wiki skin to vector. [13:10:20] You can do it via Special:ManageWiki/settings [13:41:16] rhinosf1: vector is a builtin skin and doesn't seem to be possible to enable/disable in managewiki [13:41:53] try changing the default wiki skin to vector [13:42:53] How do I do that? [13:43:10] Note: don't have mediawiki installed [13:45:10] in managewiki you can do it [13:45:41] managewiki takes the place of manually editing the files and puts it in-wiki [13:46:38] Is it called "default wiki skin"? [13:46:53] something along those lines yeah [13:47:18] sorry for not being of much help since i don't really use managewiki [13:48:59] [1/2] I don't see it [13:49:00] [2/2] Is vector just called differently? [13:49:32] Currently, it has MinervaNeue as its skin [13:57:23] minervaneue is a mobile skin [14:00:42] vector is the default skin for desktop, for mobile minervaneue is used thanks to mobilefrontend extension [14:01:54] Alright [14:03:24] So it vector already applied? [14:03:38] should be [14:03:47] Oki [14:04:35] Thanks [14:12:52] vector is applied for desktop users [15:00:32] What do I need to replace "Page" with? [15:07:32] `body` if you're using legacy Vector, `.mw-page-container` if you're using Vector 2022 [15:11:03] Thanks [15:15:09] How do I know which version I'm using? [15:31:56] @ghaztliousmoths one looks so much more bright and modern and hides loads of menus [15:33:21] I guess it's Vector 2022 if my assumption of not-modern is the 90s webpage look [15:33:55] * lastmikoi has been called out as not-modern [15:51:57] @ghaztliousmoths screnshot ? [15:52:04] Classic vector isn't 90s [15:52:09] Mediawiki isn't 90s [15:52:31] lastmikoi: not modern can be good [15:52:53] yes [16:44:25] @ghaztliousmoths that is very broken [16:44:39] That's neither behaving as it should. I think it might be a broken new. [16:44:44] What browser is that? [16:44:58] looks like chrome on android [16:45:48] @Juesto ye I need a version [16:49:15] that looks like vector 2022 on mobile [16:49:33] they tried to set the default skin to vector even for mobile [16:50:00] I'm using desktop view on mobile [16:50:10] right [16:50:23] i also forgot that by default on desktop you get vector-2022 [16:51:00] Here's a normal wiki [16:51:03] vector isnt designed to be used on mobile [16:52:07] Then what would Pikipedia seem to be using? [16:52:37] that wiki is not on miraheze [16:53:04] they're using a mobile friendly skin as well [16:53:25] I know that Pikipedia doesn't use miraheze [16:53:28] its a customized vector and minerva respectively [16:53:42] via css [16:53:44] @ghaztliousmoths what browser and version are you using? [16:54:47] Chrome version 116.0.5845.172 android [16:55:12] which android, just to rule out possible system differences [16:55:45] Samsung a13, android 12 [16:56:12] May I ask, what exactly is broken about it? [16:57:31] And would you like a link to the page? [16:58:57] @ghaztliousmoths it doesn't look to be fitting to the screen right [16:59:11] Can you paste same info in DM, I can test on the test tools [17:07:47] what's up [17:14:38] vector 2022 not looking right on mobile with request desktop site [17:17:10] mobile frontend disabled? [17:17:48] first screenshot is Timeless [17:18:57] it's mobile responsive skin, they probably use it w/ MobileFrontend [17:19:55] [1/3] also things that might affect Vector on mobile: [17:19:55] [2/3] * mobile responsiveness setting in user preferences [17:19:55] [3/3] * some settings in browser itself [17:21:20] something about fonts [17:21:49] yeah [17:22:17] how do you think it should behave on mobile? did you ever see it on mobile? [17:23:18] what? [17:23:19] Ye I've used it on mobile [17:23:48] i see [17:27:17] I've done everything on mobile [17:27:55] ah interesting, used request desktop when needed and things like that? [17:28:28] Ye [17:31:48] I've been trying to make the desktop version to become brown [17:36:40] if you're using mobile frontend, Common.css code won't work in mobile node [17:37:07] it cares only about Mobile.css [17:37:32] even if you're using request desktop site? [17:37:42] they havent changed the default mobile skin to vector [17:38:17] do you mean switching to desktop via the button at the bottom of the page, or via browser's switch? [17:38:32] they're switching via browser request desktop site [17:40:21] I could try mobile.css [17:40:37] Is it the same line of code? [17:40:49] [1/3] it makes no difference for MFE, it would show what's set for mobile mode just in bigger width [17:40:50] [2/3] if you're not using MFE, then it's just wiki being slow on update CSS, it might take around 15 min [17:40:50] [3/3] if it's still doesn't update, then you better clean cache of browser, or there's an error in the code [17:41:04] they must be using mfe [17:41:16] its there by default, no? [17:41:17] Mfe? [17:41:18] non of you answered my question [17:41:25] mobile frontend [17:41:31] an extension [17:41:55] [[mw:Extension:MobileFrontend]] [17:41:55] https://www.mediawiki.org/wiki/Extension:MobileFrontend [17:41:55]

[17:42:00] [1/2] Ahh [17:42:00] [2/2] Is it preinstalled or it needs to be downloaded? [17:42:10] wait a bit [17:42:13] both of you [17:42:17] please [17:42:17] Oki [17:42:21] in miraheze things are managed with Special:ManageWiki [17:42:40] [1/2] this extension is pre installed, yes [17:42:41] [2/2] it's also enabled by default on all new wikis [17:42:42] a set of extensions come preinstalled for you to enable/disable [17:43:19] Yep. I tried to enable pages earlier as soon as the owner gave me bureaucrat status [17:44:08] [1/2] you need to decide which skin you want to use - I guess Vector 2022? [17:44:08] [2/2] and do you want the wiki to look alright on mobile screens - in general? [17:44:40] Ehh, rather focus on how it looks on desktop [17:45:03] mobile responsiveness matters a lot for google though [17:45:24] Ah alright [17:45:42] do you plan to work from mobile on the wiki? [17:45:44] if you need to work on desktop i recommend using a desktop computer [17:46:05] request desktop is fincky [17:46:25] you can also see the desktop view link at the bottom of the mobile page, at least should [17:46:46] I do have one, it's just data being slow rn, so I can't hotspot rn [17:47:19] [1/3] Timeless and Cosmos are both mobile friendly skins which are ALSO good for admining a wiki from mobile [17:47:19] [2/3] speaking from my own experience [17:47:19] [3/3] you can even just have them as user preference option them w/o having mfe [17:47:58] Is it possible to set skins separately for mobile and desktop? [17:48:20] [1/2] yes that's mfe's main function [17:48:21] [2/2] let me word ot slowly [17:48:27] Oki [17:56:34] Cosmos is probably the best in terms of responsive and modern [17:57:21] I prefer timeless over cosmos [17:57:24] [1/6] if you want good indexing, or more - compete w/ a fandom wiki, mobile responsiveness is a must. [17:57:24] [2/6] I usually suggest people to use mobile friendly skin as default skin, and Vector as user option - and that's all w/o MFE (example - my Soft Cell wiki on Timeless, w/ old Vector as an option). [17:57:24] [3/6] if Vector, or other old skin, is a top priority for desktop, then MFE is the only proper solution. [17:57:25] [4/6] Minerva skin has to be enabled because MFE doesn't work w/o it, they're just tied, but it's simply not a good skin. [17:57:25] [5/6] instead, you still need some mobile friendly skin - I suggest Timeless (that's on Pikmin wiki screenshot you've posted) or Cosmos (replica of Wikia's Oasis, an example would be pizzatower.miraheze.org), they're both very good design wise and don't hide stuff from you like Minerva does, thus let you manage wiki pretty nicely from a phone. [17:57:25] [6/6] once you enabled needed skins, you should head to Additional settings admin menu, Styling tab - right the first setting is default (desktop) skin, and the next one is mobile skin. [18:00:22] the downside of MFE is that you need now modify Mobile.css, in addition to Commo.css and Vector/Vector-2022.css [18:00:36] and Mobile.css doesn't always work, for some reason [18:01:15] Cosmos has a bonus though - you can set it's color scheme in styling settings and it'll apply in mobile mode [18:06:01] I gotta request for timeless right? Since its not in the list of extentions [18:06:41] Timeless is part of MediaWiki [18:07:10] you should be able to pick in mobile skin option w/o enabling/requesting anything [18:08:10] now apologies, I gotta go now [18:08:30] [1/2] Alright, thanks your help ^^ [18:08:30] [2/2] Really appreciate it [18:09:16] I found it :D [18:15:57] yay [18:17:57] Oof, mobile is constantly bugging and not properly switching mobile view and desktop view [18:18:18] you're using the link in the bottom of the pages? [18:18:24] or using request desktop website? [18:18:32] [1/2] No [18:18:32] [2/2] But now it loaded in properly [18:18:45] Thanks for your help, and Void, had to disappear yesterday to do some late night work [18:19:16] there you go [18:19:25] you can use the desktop link to switch to desktop :) [18:20:06] Yay [18:20:57] does it work better now? [18:22:37] The issue with the colour being white is still present for desktop view but man, it definitely is much better to work with [18:22:42] sounds like your slow data makes your browser struggle loading [18:28:24] Yea, that's highly likely to be the reason [18:59:24] whats the limit on wikis someone can have? [19:01:25] There isn't a hard limit [19:01:56] @tatiannaz reasonable [19:02:19] abt to open fifty wikis now w [19:02:28] uuh [19:03:41]