[00:00:11] [1/2] I think here has more info about it: [00:00:11] [2/2] https://portability.fandom.com/wiki/Portable_Infoboxes [00:00:59] [1/2] That is looking as a start. [00:01:00] [2/2] Good luck, you are on your way 👍 [00:19:21] shits gonna end in disaster because i dont know how to remove infoboxes [00:19:35] oh. [00:19:38] i just backspace. [00:19:42] i'm a little retarded. [00:27:09] there's stuff that is also easier to do in source editing vs the visual editor [00:28:51] HAHA [00:29:05] the second map is a placeholder [00:30:56] W [00:37:12] LET'S GET IT ON [00:37:16] LETS GOO [00:42:44] nice, grats! 😄 [00:43:08] It's not much, but its honest work [00:49:04] this [00:49:08] <:thistbh:764649024875528192> [00:49:40] i dont even wanna spam the chat but i am proud of such small work [00:50:05] It genuinely looks like you're looking at a real wikipedia article, as if Gorbachev kept the USSR afloat through the 90s [00:50:24] (also yes i took the paragraph from the USA wikipedia) [01:02:06] Very nice! [01:02:14] You're already ahead of me [01:02:34] For some reason I can't get the infobox info in a box, it just takes up the main article [01:08:56] NVM [01:09:24] Just needed to change my common css to a different one [02:00:54] your request is approved [02:56:52] Is there a way to remove the white outline around the image and to prevent it from going off page? [02:58:39] It's ok lmao [02:59:08] By the way does Miraheze have assistance in moving an entire FANDOM wiki to Miraheze? [03:00:47] For which wiki I cannot say because I still want to be in the good graces of the powers that be [03:04:16] i remember there being something about that on the meta wiki [03:04:17] hold on [03:04:41] https://meta.miraheze.org/wiki/Moving_a_wiki_to_Miraheze#Moving_from_Fandom [03:04:43] here we go [03:19:19] now i'm interested [03:19:27] also learned today there are scripts to make XML dumps of a wiki without even logging in [03:19:36] its a wee bit slow on large wikis [03:19:39] but hey [03:19:49] Will keep that in mind capn 🫡 [03:20:13] Godspeed on migration [03:20:27] After the whole World Trigger Wiki incident I don't want the same thing to happen to mine [03:20:56] Right now we're mostly lacking in manpower so migrating is still a longshot goal [03:21:40] I feel ya [03:22:12] good luck velvet [04:53:04] how do i send a message to SRE [04:54:58] [1/2] i want to send the following, but i'm guessing #sre isn't for normal text messages: [04:54:58] [2/2] Problem Report: The Lingo extension is currently disabled within Miraheze's `LocalSettings.php`, despite the extension reportedly working fine in v1.40 of MediaWiki. It's also in the Parser Functions extension menu as if nothing is wrong. I'm guessing this is an oversight, in which case could it be re-enabled in the PHP? [04:57:38] [1/4] in CSS [04:57:38] [2/4] `figure img { [04:57:38] [3/4] border: none !important; [04:57:39] [4/4] }` [05:00:50] Can you link CSS? [05:02:10] I've enabled the extension globally, looks like this was known but missed by us. Can you confirm that it is working? [05:05:13] Message here works fine, but for technical requests [[phabricator]] is preferred. #sre was previously used for discussion, but it seems we've moved most of it to #tech-community to make it easier for us to track conversations. [05:05:13] https://meta.miraheze.org/wiki/phabricator [05:05:13]

[05:20:20] [1/2] `MediaWiki:Common.css` [05:20:21] [2/2] you aren't new here, aren't you? [05:23:47] speaking of extensions 👀 isn't miraheze still using the old and unmaintained SimpleTooltip? are there plans to move to the Universal-Omega fork? [05:35:23] Thank you, I'll test it now [05:36:31] it is showing up on the `Special:Version` page [05:37:07] which page name is being used for the Terminology though? [05:37:41] because the stuff here doesn't seem to be doing anything (when hovering over the defined words on other pages) [05:40:40] [1/4] is this not meant to be at the end of `LocalSettings.php`? [05:40:40] [2/4] ```php [05:40:41] [3/4] wfLoadExtension('Lingo'); [05:40:41] [4/4] ``` [05:42:22] nvm i might just need to "edit and resave" apparently [05:43:13] oh yep it works now [05:43:17] thank you again! [05:44:20] it looks like you need to re-save every page once the extension is enabled [05:44:23] but that's fine [05:44:26] it'll sort itself out in time [07:02:49] [1/2] does anyone know how to make an image span the full width of a page? [07:02:50] [2/2] ```[[File:Title_placard.png|frameless|center|width=900px]]``` [07:02:50] https://meta.miraheze.org/wiki/File:Title_placard.png [07:03:05] im trying to make a title placard but it wont span the full width of the page [08:36:32] It's a PNG, it's inherently limited by how large the file itself is [10:37:56] hi im new to making a wiki on miraheze and id like to understand how to use monobook.css and common.css to get my wiki to be styled the way i want. i havent really used css in nearly 5 years so im quite dry on it all and i'll definitely need help with the tags and stuff because im very new to the mediawiki format of things [10:39:34] im mainly inspired by the style of croc wiki (which is why i chose this particular skin) and im clueless as to how to get everything to change the way i want it to [11:08:27] welcome to Miraheze [11:08:45] you got the wiki and set up the skin already? [11:15:40] yes i have [11:18:22] [1/4] CSS in Common page is applied to all skins (except for mobile mode), it's usually used to style templates (can be replaced by TemplateStyles extensions) or parts of MediaWiki which are same in all skins, for example thumb image or gallery [11:18:22] [2/4] to actually modify the skin is better to use skin specific CSS [11:18:22] [3/4] now, you don't usually see Monobook skin in use these days, I don't have examples on my mind, legacy Vector is more popular (being very close to Monobook as well) [11:18:23] [4/4] but the process of modifying CSS delves to poking around page's code w/ browser's element inspector, and then copy changes that click to CSS page [11:19:24] Monobook is still a very popular skin [11:20:16] you also can check Monobook.css on a wiki you look up as an example, and step by step copy and change its code [11:20:28] on your wiki ofc [11:20:32] I've been working on a variety of monobook skins, so if you need specific help with something I am happy to help [11:22:44] i did not think about inspect element [11:22:55] that opens up some possibilities LOL [11:23:36] see i did this with croc wiki but things like the wiki bg and page content bg didnt change as expected [11:23:40] so im like uhhhhh [11:23:47] what do [11:25:06] [1/2] you mean in element inspector or after editing CSS? [11:25:06] [2/2] it takes some time for CSS changes to actually start to work, otherwise an error in the code might the reason [11:25:42] after editing css, some things changed but others didnt [11:26:07] either way ill probably get more done starting from scratch since there's less confusion [11:26:30] if that fails ill go back to copypaste and alter i suppose [11:27:05] you can test changes in web tools before actually esiting CSS [11:27:55] in sidebar of element inspector, or, of you use Firefox, there's Styling tab, where you can add new CSS [11:30:13] hi [11:59:29] [1/2] Yes. Good advice. You can test the CSS changes live and running of you change the CSS on the web browser. Open the console of the web browser on "inspect element" and change the CSS. [11:59:30] [2/2] That's very helpful because the browser shows the 'square' or region of the CSS elements you are pointing [12:15:16] [1/7] i put: [12:15:17] [2/7] ```figure, figcaption { [12:15:17] [3/7] border: none !important; [12:15:17] [4/7] background-color: #001122 !important; [12:15:18] [5/7] }``` [12:15:18] [6/7] on my css but i still have a 1px white border around images. [12:15:18] [7/7] I have to find where is that 1px white border [12:15:22] Odd question, but is this good structuring? [12:15:54] Looks good. I'm happy you made a beautiful page [12:16:25] https://tenor.com/view/kuroko-railgun-toaru-kuroko-shirai-happy-gif-25276368 [12:16:25] @haya_nate43 That link is not allowed. [12:16:33] fucking embed failure [12:16:33] @haya_nate43 Watch your language. [12:49:35] https://tenor.com/view/peacemaker-vigilante-grimace-face-grimacing-gif-25645224 [12:49:53] tf is the guideline for gifs [12:49:58] some of them just don't work [12:50:29] https://tenor.com/view/cocking-pistol-john-wick-keanu-reeves-john-wick-chapter-4-jw4-gif-14490794064585307818 [12:50:35] that worked fsr [12:50:51] [1/7] @theoneandonlylegroom thanks for helping me with the images. [12:50:51] [2/7] There is a 1px solid #eaecf0 border inside the image CSS after i put the border none. [12:50:52] [3/7] The border none i put eliminates the border of the outher box of the figure, but there is another border inside the image that has a different code. I paste it here. [12:50:52] [4/7] ```figure[typeof~='mw:File/Thumb'] > a:first-child > :first-child:not(.mw-broken-media), figure[typeof~='mw:File/Frame'] > a:first-child > :first-child:not(.mw-broken-media), figure[typeof~='mw:File/Thumb'] > span:first-child > :first-child:not(.mw-broken-media), figure[typeof~='mw:File/Frame'] > span:first-child > :first-child:not(.mw-broken-media) { [12:50:52] [5/7] border: 1px solid #eaecf0; [12:50:53] [6/7] }``` [12:50:53] [7/7] Do you know if the whole paragraph is needed to revert this border or there is an abreviated form? [12:52:05] please avoid this kind of positing in general, as it's a main support channel [12:52:29] we have #offtopic anyway [12:52:33] that's right. Civism is a thing we encourage here [12:52:35] i need support for understanding the server's limitations [12:52:53] by spamming gifs? [12:53:01] the first was a reaction [12:53:11] the second was a test [12:53:28] i can delete them now [12:53:39] seeing as they passed the censor test somehow [12:53:47] ok. Then no need to put a third gif. Just use common sense and is ok 👍 [12:54:14] when common sense meets a lack of #info [12:54:38] [1/4] not sure what you mean, but I also added (just yesterday to my wiki, in fact) [12:54:38] [2/4] `figure img { [12:54:38] [3/4] border: none !important; [12:54:39] [4/4] }` [12:54:55] ok, so are you using the admins at miraheze should state rules against gifs then? [12:55:12] anyway, I have question for whether the `Popups` (aka `Previews`) extension is working atm [12:55:17] cos i enabled it on my wiki and it's not doing anything [12:55:41] it's finicky, I personally don't use it so not sure [12:56:22] [1/2] is the same issue with User kimora at [12:56:22] [2/2] that is on #support request the other day [12:56:27] i'm not really sure what else i can try to make it work [12:56:43] i'll check out that thread then, thanks [12:57:55] ok so [12:58:01] turns out it can just take a while to start working [12:58:19] like a few hours [12:58:25] so i'll just wait a bit ig [12:59:01] by the way though, I noticed that unlike a lot of other extensions, this `Popups` extension can be customised for individual wikis [12:59:47] like this [13:00:00] is it possible to get more of these for other extensions? [13:00:14] or is there a limit to what can be customised (one that can't be "fixed" by the Miraheze admin) [13:00:43] also, is there any "hub" or something for accessing these extension-specific settings [13:01:37] [1/3] rn the only ways to get to these pages are [13:01:38] [2/3] - finding the extension in the extension settings list and accessing the specific settings via an attached link if it happens to exist [13:01:38] [3/3] - entering the extension name into the url `Special:MediaWiki/settings/[extension_name]` which isn't reliable [13:07:59] it worked like a charm. Thanks 😊 👍 [13:10:31] the things that can be customized ar readily available to th end user. Thats one of the thins i like of Miraheze. They are open and put the options on the local admins to decide [13:12:16] If there is an option that local admins dont have, is because is difficult to operate, or incompatible with some settin [13:20:35] the hub of these modifications for your wiki is the ManageWiki. When you install an extension, if there are more settins, they appear there and disappear when you uninstall [13:22:55] [1/5] You can check on Mediawiki site for the total of extensions [13:22:55] [2/5] [13:22:56] [3/5] and [13:22:56] [4/5] [13:22:56] [5/5] but not all these are on Miraheze. Only the ones checked by Miraheze volunteers [13:50:00] i see, thank you [14:13:28] <.yowin> Hello there, I want to import my whole wiki from fandom to mirahaze, and they ask me the interwiki prefix, what is that ? [14:20:46] Where does it ask you that? [14:22:14] <.yowin, replying to pixldev> I have my own XML but I don't know what the "interwiki prefix" is [14:22:45] [1/2] if you trying to import via Special:Import page - it's unstable and will fail [14:22:45] [2/2] go to [[Special:RequestImportDump]] on Meta [14:22:45] https://meta.miraheze.org/wiki/Special:RequestImportDump [14:22:45]

[14:23:35] Special:Import works only w/ very small, single page files [14:24:03] <.yowin, replying to theoneandonlylegroom> That's what I am going to do I think, I wanted to try but I'm gonna do that [14:24:22] <.yowin> Thanks! [14:24:45] np [14:25:49] [1/2] interwiki prefix is a way to create ties and easy linking between your wiki and other wikis, or even different web sites [14:25:50] [2/2] if you import something from Fandom then its interwiki prefix (at Miraheze by default) is `fandom` [14:26:29] Fandom has language interwiki prefixes [14:27:16] <.yowin> [1/2] Okay I see [14:27:16] <.yowin> [2/2] But after the migration I can get rid of the fandom, or maybe not ? [14:28:55] many factors [14:29:29] Fandom can be a little bitch sometimes [14:29:32] hey legroom, finished the skin customization somehow [14:30:33] [1/2] if it's a fan wiki for something well known they won't delete it because it will generate ad revenue [14:30:34] [2/2] if it's about something very very obscure or unpopular, or the wiki is your personal kind of project, and there's very low activity and not a lot of readers, then there's a chance they'll delete it [14:30:44] Daaaaaaaaaaaaaaang [14:30:46] That’s hot [14:30:48] I managed to persuade their staff to delete mine [14:31:00] nice [14:31:00]