[00:01:10] It is in Special:Log/patrol [00:01:17] Thank You [00:08:43] and also minimize the amount of emails you use things on [00:08:55] almost lost my github account because i had no idea what email i used [00:10:19] unless you have a better memory than me [00:14:11] I don't have that problem, everything uses my email that I created when I was like 9 years old [00:14:30] however, I have a different problem in that my inbox is always inundated with junk :3 [00:14:35] i have like ten emails i use 😭 [00:14:49] i dont even know why but i just do [00:15:01] i have two joke ones and like 8 ones i use for everything [00:15:37] i can never see any serious emails because of how many services im signed up to [00:15:48] thinking that recieve promotional emails is required 😭 [00:16:30] at least now i only have 3 accounts i use for emails [00:17:56] ^^^ [01:20:15] [1/3] hi guys, quick question [01:20:15] [2/3] is it possible to make a portable infobox with custom color schemes, like this one on namuwiki? [01:20:15] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1265116233431384094/image.png?ex=66a056ce&is=669f054e&hm=d67178f39c9e7286ebe841d180fdfb9eb78b992a68fb9ea7edaad0362bc24cb4& [01:20:55] Absolutely, you can also mash that up with templatestyles to create a unique style per type of infobox if wanted. [01:21:51] It'll require some CSS fiddling to get things exactly so, but https://community.fandom.com/wiki/Help:Infoboxes/CSS is a good starting resource. [01:23:23] big help, thank you so much! [01:24:02] oh but it seems that the solution suggested in that link uses wikiwide CSS? [01:24:02] Our implementation is pretty close to fandom's, but when in doubt you can always use F12 to inspect elements directly [01:24:43] Yeah, if you only want a specific type of infobox template to be affected, then you're looking at using the TemplateStyles extension. [01:25:10] can i edit a specific infobox's CSS directly? [01:25:29] Nope, infobox doesn't accept direct modification of CSS [01:26:07] i see, so i'm guessing the only way around this is to assign a class to the infobox, then modify the CSS of that class elsewhere? [01:26:43] That'd be one route to go [01:40:47] [1/4] just to confirm since this is my first time using portable infoboxes [01:40:47] [2/4] if i go down this route, that means i will need to build a portable infobox, save it as a template, then create a CSS file for that template [01:40:47] [3/4] and then when i use the template, i put `` right before the template [01:40:48] [4/4] does this sound right? [04:24:17] wdym? skin/theme? that's Vector 2022 [04:26:30] [1/2] that's correct [04:26:30] [2/2] portable infobox itself like a block element, you won't need additional wrapping [04:36:56] Perhaps, by Miraheze's 10th anniversary in 2025, there will already be more than ten thousand wikis. [06:36:28] [1/2] i see. [06:36:29] [2/2] in that case, in the separate css file, what is/are the class(es) that i will use to refer to the infobox and its elements (header, title, data row, label, etc.)? [06:40:31] [1/3] NotAcharam dropped a link in earlier message [06:40:31] [2/3] [06:40:32] [3/3] since PI was developed by Wikia/Fandom most of PI specific guides about it are on their hub wiki [06:47:25] [1/2] ah right, thanks for the help! [06:47:25] [2/2] but if i use the portable infobox builder utility, i will have to edit the template afterwards to manually insert the type/theme, i believe? [06:47:33] since i don't see anywhere on the builder to do that [06:49:18] yes, builder provides a very basic, simple infobox, which is alright for those who only start making infoboxes, afterwards you can update template code manually [06:50:24] [[Infoboxes#Portable]] [06:50:24] https://meta.miraheze.org/wiki/Infoboxes#Portable [06:50:25]

[06:53:17] [1/6] if you need examples here's somewhat simple on one of my wikis [06:53:17] [2/6] [06:53:17] [3/6] [06:53:18] [4/6] and more over the top on Pizza Tower Wiki, it actually uses additional wrapping [06:53:18] [5/6] [06:53:18] [6/6] [07:07:13] [1/2] i see, this is very good reference, thanks! [07:07:14] [2/2] though is it wise to stash all of my different infobox themes in one CSS file? because like on namuwiki i'm trying to have each infobox look slightly different [07:16:23] [1/2] yeah, you can make a whole separate page called just "infobox", both of my examples are like that [07:16:24] [2/2] on my main wiki I use classic table infoboxes so I have like main infobox CSS which has shared styling, and each separate inbox has short individual CSS w/ coloring and small details [07:22:58] [1/2] so an infobox can have properties from two separate stylesheets, i see [07:22:58] [2/2] in that case, regardless of the number of stylesheets in use, do i still need the TemplateStyles extension? i'm a little confused about how that works anyway [07:23:42] I actually explained a bit on TemplateStyles in bottom section of Infoboxes guide [07:24:06] usually, one would put custom CSS in MediaWiki:Common.css [07:24:49] the thing about TemplateStyles it makes a portion of CSS load only if template actually appear on the page, instead of loading everywhere across the wiki [07:25:03] it make main CSS page both lighter and cleaner [07:27:06] [1/2] I'm not discouraging from using Common.css tho, I think it's fine if styling is simple, doesn't have variations, and template in question appear on large majority of articles [07:27:06] [2/2] but otherwise TS is more tidy [07:28:23] also small bonus of TS - it works in mobile mode (MobileFrontend extension) which ignores Common.css and requires filling Mobile.css [07:28:50] [1/5] i actually went to the help page for that extension earlier, and i was left with two question marks: [07:28:51] [2/5] 1. could the use of TemplateStyles accidentally affect other, non-template elements, and [07:28:51] [3/5] 2. if each infobox is different, would that mean i either need to pass in the theme as a parameter to the infobox template, or have different infobox templates for different themes? [07:28:51] [4/5] what i'm a bit confused on for question 2 is, if the former option is the way to go, can the stylesheet generated by TemplateStyles read the theme from the parameter? [07:28:51] [5/5] and for the latter option, i presume TS will generate one styles.css for each infobox? [07:32:30] ok after reading the help page again i think q1 is a non-issue, just q2 [07:41:09] [1/13] the thing about theme parameter is that it creates for PI new class w/ it, as explained in Fandom CSS guide we sent earlier [07:41:09] [2/13] so let's say you have two infobox templates, character and game [07:41:10] [3/13] to character one you give `` and game one would have `` [07:41:10] [4/13] in CSS page, let's say Infobox.css, I'd first make general styling which would be same for both templates, like spacing and fonts [07:41:10] [5/13] but colors would be different, so further I'd type [07:41:11] [6/13] `.portable-infobox.pi-theme-char .pi-secondary-background { [07:41:11] [7/13] background-color: #blue; [07:41:11] [8/13] } [07:41:12] [9/13] .portable-infobox.pi-theme-game .pi-secondary-background { [07:41:12] [10/13] background-color: orange; [07:41:12] [11/13] }` [07:41:13] [12/13] on both templates we'll link that one Infobox.css, but since we separated themes they won't mix up [07:41:13] [13/13] when page has game infobox w/ "game" theme/class, it's use orange color [07:42:43] i understand that part, but what i meant was if i did something like ``, does that work? [07:42:43] https://meta.miraheze.org/wiki/Template:theme [07:42:57] of course including the theme parameter in a call to the infobox template [07:43:06] triple brackets [07:43:10] oh right [07:43:23] it should actually but I don't remember trying that [07:43:25] but yeah that was my idea to cut down on the number of templates [07:43:27] i see [07:43:59] if that's the case i think so far i have all the information i need, thanks! [07:44:46] np :pupCoffeeMH: [09:21:37] question how do i add a header under the header a picture thats all i know how to add a header but how do to add a picture under the header [09:24:18] ``` [09:24:21] == Text== [09:24:25] [[File:Egg.png]] [09:24:25] https://meta.miraheze.org/wiki/File:Egg.png [09:24:27] ``` [09:24:42] it's hard to do multiline stuff on irc, but hopefully that helps? (assuming i understood what you meant) [09:31:34] nvm [09:31:36] thanks [09:31:38] size of headers defined by amount of `=` [09:32:17] [1/2] # How does my wiki look with all the stuff [09:32:17] [2/2] https://wiki.giantesselsie.net/ [09:32:30] [1/2] in article text the biggest is `== X ==`, big section header [09:32:31] [2/2] `=== X ===` will be smaller and becomes subsection, and so on [09:32:54] you forgot warning in message [09:33:10] /nsfw themed wiki/ [09:34:13] aside from some grammar, the main page looks okay to me [09:35:07] Question idk if it is possible i want to make a page where the public can post pictures ONLY PICTURES but not text or those stuff of they encounter with giantess dimension but i probably cant [09:35:40] as in you want people to be able to upload images but not edit pages? [09:36:11] ye but only images not add text to the page or delete the other people's images [09:36:14] do u understand [09:36:49] ik u can set the protection [09:37:05] but there is no option to allow the public to do or not able to do on the page [09:37:12] you probably could remove edit rights from users but keep upload [09:37:24] though they can set some text when uploading a file [09:37:33] those are okay [09:37:34] and i don't know if you can upload when you don't have the edit right [09:37:45] see [09:37:56] you can also only allow a certain right (or group?) to edit a namespace [09:38:01] it will be a nice feature if u guys can add a permission system [09:38:22] like the public can only upload but not removed stuff [09:38:25] or edit stuff [09:38:40] normal users can't delete any pages or files so that's already there [09:38:44] only they own stuff they can remove or edit them [09:39:16] you can prevent people from editing all namespaces except for the file namespace [09:39:28] https://files.catbox.moe/gzawct.png [09:39:48] i dont understand [09:40:39] in "Manage this wiki's namespaces", you can set it so that only users with something like editsemiprotected can edit pages [09:40:43] Also question can u check if u can see navigation tab or only explore [09:40:59] oh wait perhaps you could use an abuse filter :thinking: [09:41:11] i'm thinking about this in real time [09:41:15] lets leave it eclair [09:41:17] i only see explore [09:41:18] oh okay [09:41:27] i want that [09:41:33] navigation must be gone [09:41:48] question [09:41:53] idk if i did it right [09:42:05] or wrong but how do i set a favicon for the wiki [09:42:35] the url needs to be in the form of something like https://static.miraheze.org/... [09:43:21] you can copy the link from the "Original file" link on the file description page [09:52:37] won't removing edit right but keeping upload for users mean that only admin would be able to actually add images to articles? [09:53:12] true [09:53:18] though it's an odd thing to request in the first place [10:02:39] what can cause the error ``Le temps alloué pour l’exécution des scripts a expiré.`` (Allocated time for scripts execution expired) ? im just using an #if and calling directly the lua module behing my template provide expected output so i dont understand where it fails [10:03:29] [1/5] something doesn't add up [10:03:29] [2/5] I thought the og Anime Bath Scenes Wiki, which was shutdown by Fandom, went self-hosting, but Miraheze instance (which got reported) has an admin w/ the same username as og [10:03:30] [3/5] which one is real at this point :ThinkerMH: [10:03:30] [4/5] also one year ago Buzzfan120 tried (unsuccessfully) to take down another wiki under different clause, what a vigilant /s [10:03:30] [5/5] (the wiki still got taken down tho, per different policy) [10:03:54] *violations [10:05:18] I'm not sure what could cause this without more informations on what module and functions it call [10:06:03] [1/4] ``` [10:06:03] [2/4] {{#if: {{{2|}}} | {{#invoke:Declinaison|main|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}}} | {{#invoke:Declinaison|main|{{{1|test}}}}} }} [10:06:03] https://meta.miraheze.org/wiki/%23if:Template:_%7b%7b%7b2 [10:06:03] [3/4] ``` [10:06:03] [4/4] is the template code [10:06:17] hmm yeah, the language used in Buzzfan120's three wiki reports is a bit... strong [10:06:35] [1/2] https://languepierrick.miraheze.org/wiki/Module:Declinaison [10:06:35] [2/2] for the module [10:09:07] calling mw.loadData('Module:Declinaison/{is,get}Vowel') for every function call is a bit of a code smell to me, but i think mw.loadData is cached so it shouldn't be a problem [10:10:12] you know, the vibe of a person who "hunts down filthy content"? I feel like even if these wikis will go self-host, they might continue trying to make them do their (largely harmless, considering prohibition of nsfw and compliance w/ copyright reports) thing in peace [10:11:21] misworded lol [10:11:35] won't let them do their thing in peace [10:12:52] Oh i separated files, maybe it was not a good idea ? [10:13:41] awing_ding: you probably could try something like local isVowelData = mw.loadData('Module:Declinaison/isVowel') at the top of the page, and have the function reference from that variable (same for getVowel) [10:14:26] Oh yeah i see the problem now okay [10:21:30] it appears that i have not properly tested my code and some cases make the lua code fail lol [10:22:45] prob the while loop that never matches the end condition for some reason and run until failure [10:42:51] After checking out their reports, I can definitely see this as being what’s going on [10:46:50] how do i check the pics on my wiki [10:47:00] I don’t understand why people go out of their way to do vigilante justice like this though [10:47:57] Especially for something like wiki sites [10:48:04] i wonder how they'd react on my wiki [10:49:06] [1/2] Special:AllFiles page [10:49:06] [2/2] I suggest to check all Special pages list, there must be a link in toolbar at the bottom, it'll show you various statistics/list pages [10:50:31] I saw the file repository clause as large amount of files w/o actual substance in articles/text/presentation [10:51:06] If they want to contribute they could at least try and find more productive ways [10:51:48] I can’t imagine scouring through the wiki list for inappropriate wikis would be very efficient [10:52:12] a wiki should have proper articles, no doubt, if there's a clear attempt/desire by editor for that I wouldn't call it a file repository [10:53:15] [1/2] @theoneandonlylegroom this doesnt work [10:53:15] [2/2] https://wiki.giantesselsie.net/wiki/Special:AllFiles [10:54:05] giantesselsie: i think it's https://wiki.giantesselsie.net/wiki/Special:ListFiles ^^; [10:54:45] yeah, sorry [10:54:57] Special:NewFiles works too [10:56:29] u can check on https://wiki.giantesselsie.net/wiki/Special:SpecialPages for other special pages also [10:57:29] [1/2] I noticed this in managewiki/permissions, is this only useful for private wikis? [10:57:30] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1265261500742762517/IMG_8241.png?ex=66a0de19&is=669f8c99&hm=d7a980f5edeabdb3e69c3922e5c5e2188b9f8d17828dc7538a4836c21a88f7d9& [10:57:44] ot looks funny lol [10:58:31] mooncloud: yeah i believe [10:59:05] the wiki in question is private? [10:59:09] Public [10:59:36] I don't see this right on mine :ThinkerMH: [11:00:06] Hypothetically, would it be possible to make a wiki private and auto-assign the member role to everyone who logs in? [11:00:21] :ThinkerMH: [11:00:27] It doesn’t show up for the everyone user group but it seemingly appears for all others [11:00:44] ah [11:00:52] I noticed it today while setting up our wiki’s patroller user group [11:01:13] i assume everyone can read then [11:01:31] The read permission isn’t given to the everyone user group oddly enough [11:01:31] I guess read is to create an alternative to default Members group [11:01:43] Most likely [11:01:57] I don't feel like poking around it personally lol [11:03:05] \* can read [11:03:23] https://files.catbox.moe/8l8rlj.png [11:03:33] rip [11:03:41] discord shows poop [11:03:46] odd [11:03:51] open the link i guess [11:03:53]