[00:07:35] I thought the wiki was for that at first too [00:08:08] Yeah nah, there already is a Wiki for Welcome Home [00:08:17] Too bad it's Fandom-based. [01:14:44] Oof [01:14:50] [1/2] Thats just [01:14:50] [2/2] Oof… 🙁 [02:03:00] @rhinosf1 @pixldev @reception123 this is most likely because reopening doesn't inherently reset the inactivity timer, which causes the wiki to re-close automatically unless an edit was made [02:03:42] This is why I often make and revert a minor edit so it puts a doot on recent changes [02:06:19] It does if you reopen it from the actual wiki rather than meta also. I need to finish my log changes so changing remotely from meta can log on local wikis also, which would also fix this... [02:07:54] That'd be amazing, I guess the other workaround would be to local grant crat temporarily for the reopen but echoing log is definitely the better solution [02:08:21] Esp with how bulky my acct is on attaches, that workaround would be very slow [02:08:36] True. [02:09:15] But yeah I can try and finish that sometime soon. Would open up so Stewards can make any restricted change from meta also, not just core changes. [02:12:17] Yeah, would be lovely to nix yet another thing boosting my excessive attaches [04:16:25] Would anyone know is there is anything that causes pipe to be parsed as something else? I have an infobox (not built with Portable Infobox) that seems to have parsing issues when using | within the context of filling out infobox parameters [04:19:24] Use {{!}}, it's a magic word and it'll display a pipe but parse it like an exclamation [04:20:12] turn on the pipe escape extension instead. just learned that this will save you from excessive {{!}}s lol [04:20:47] (of course if it's just one pipe, might still be better to just {{!}} it but if it's a whole bunch...) [04:21:10] I didn't know that was a thing haha, good advice [04:21:24] yes wwr just let me know a few days ago [04:21:31] @hihello_what_are_you_doing_here >>> would that be done at the infobox template level? [04:21:31] Here is the infobox template I am building, with the specific datapints that I need: https://www.pasteboard.co/JMAbqpnR14B7.png [04:21:55] too bad i already have an entire page full of hundreds of {{!}}s that I'm now too lazy to convert back lol [04:22:38] also, no, pipe escaping should be done at the parameter level, if the issue is that you need to include the pipe in a parameter [04:23:09] Seconding emiliers [04:25:24] @hihello_what_are_you_doing_here and @emiliers : Yeah. I am trying to undrestand where the parsing problem is. Like, here is an example of that same infobox being pulled into a page (using pipes in the standard infobox syntax). https://www.pasteboard.co/2JN311wp4mqJ.png [04:25:57] though i guess in this case, since you're trying to pass an entire infobox through an if statement, then yeah, you probably need the pipe escape for the infobox pipes [04:26:19] Yeah. Im trying to figure out where I need to do the {{|}} instead of | [04:26:41] anything within the infobox row template [04:26:47] also it's an exclamation point [04:26:50] {{!}} [04:28:55] {{#if: {{{rarityofitem{{!}}}}} | {{infobox row {{!}}label=Rarity{{!}}field={{{rarityofitem}}} }} }} [04:28:55] ---- Something like that ?? [04:29:09] that line originally read {{#if: {{{rarityofitem|}}} | {{infobox row|label=Rarity|field={{{rarityofitem}}} }} }} [04:29:53] no, you don't need to pipe escape the parameter names, as in you can keep `{{{rarityofitem|}}}` as is [04:30:15] but yes to the rest [04:31:29] {{#if: {{{rarityofitem|}}} {{!}} {{infobox row|label=Rarity{{!}}field={{{rarityofitem}}} }} }} [04:33:43] no, you don't have to pipe escape the pipes for the if statement either [04:34:07] since the while point of pipe escaping is that they're mistaking these pipes for ones that belong to if [04:35:24] so {{#if {{{rarityofitem|}}} | {{infobox row {{!}} label=Rarity {{!}} field={{{rarityofitem}}} }} [04:35:53] oops forgot the second }} at the end there but hopefully it's clear what i mean [04:47:04] Yeah. I think maybe I have it : https://www.pasteboard.co/6apBgXbIoQRo.png [04:47:45] I added the second trailing }} to close it. My hope is that maybe now it will let | for infobox parameter lines will be seen like they should [04:47:45] {{Infobox Item Simple [04:47:45] | rarityofitem = Epic [04:47:45] | itemminingefficiency = Slow [04:47:45] | itemdurabilityuses = 26 [04:47:46] }} [08:40:03] [1/3] ive got a question, how do i basically make this not happen 😭 [08:40:03] [2/3] It goes off the screen, and i feel like ive tried everything make the tabs be able to be scrolled through and shorten the box for it [08:40:03] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1543178404877312070/image.png?ex=6a93ec62&is=6a929ae2&hm=f358a28a93bbbb302beb60053fdafbd606bf7e8a31e3023b81e82bae472d3211& [08:42:15] i basically want to know how to shorten the column in the table and allow the tabs to be scrolled between [09:06:39] how to set preview embed image/gif for each page on miraheze [09:06:53] like when u send Wikipedia link there's embed description with image [09:08:18] instead of it targeting random image on the wiki and setting it as embed [09:27:06] like for example I want site logo to show up on every page instead of random targeted image or gif, or vice versa [10:13:33] i think it's`$wgWikiSeoDefaultImage` and `$wgWikiSeoOverwritePageImage` in managewiki? [10:46:16] Whats the difference between
and
[10:56:31] I'll check it out in a bit, thanks [12:08:20] [1/5] how do i fix my infobox appearance, if its black instead of the one we use in main page, ill attach example from fandom as second image [12:08:20] [2/5] https://zombiestories.miraheze.org/wiki/Template:WeaponInfobox [12:08:20] [3/5] (note: the "example usage" is imported source code, the actual code is in source edit, if need this information) [12:08:20] [4/5] https://cdn.discordapp.com/attachments/407537962553966603/1543230820679032942/image.png?ex=6a941d33&is=6a92cbb3&hm=7f2d60038d4387c519d001b823e59e45d7a633d5421ab3495c47b245537e4b66& [12:08:21] [5/5] https://cdn.discordapp.com/attachments/407537962553966603/1543230821006049401/image.png?ex=6a941d33&is=6a92cbb3&hm=c42fa6f854fd9f1926df8efce44ee0ecbb55b4e1fb78965ca36bf536e08e58d6& [12:35:43] i have like 0 idea but all i want is just bring back the white borders, center main headers text and just add class [12:36:32] but everytime i add to infobox, it gives error that it isnt supported there [12:36:54] and i cant stylize them either [12:39:50] while somehow i could stylize the same templates but for homepage [12:46:46] ill prob leave it like that, since you cant edit appearance of those infoboxes [13:00:20] is there a way to report a wiki [13:00:30] How can i report a wiki [13:01:50] [[SR/WR]] [13:01:50] [13:02:03] But if it's something that should be a private report [13:02:12] (since that page is public to the internet) [13:02:17] stewards@miraheze.org [13:27:25] @unregimental ^ [13:27:32] tyvm [13:31:09] is it possible to give Special: an alias? negative namespaces are not editable in Special:ManageWiki/namespaces [13:49:54] [1/4] Hello Miraheze community! [13:49:54] [2/4] Halcyon Softworks needs YOUR help on figuring out who griefed our wiki mainpage and replaced it with a "flip you" to everyone in the HalSoft community discord server! [13:49:55] [3/4] DM me for more information. [13:49:55] [4/4] Thank you! [13:53:34] wow i love witch hunting! [13:58:12] [1/3] I've made a report but its in the public one [13:58:12] [2/3] how can i basically get it to be reviewed faster? [13:58:13] [3/3] is there any possibility? [13:59:53] My community is rather small, I'd take any help I could at this point [14:01:13] [1/2] Extra information: The griefer wishes death and torture upon me specifically out of all of the people named. (Halcyon) [14:01:13] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543259230453112942/Screenshot_2026-08-29_205042.png?ex=6a9437a8&is=6a92e628&hm=4c1c095232ac03593850d7180b058d86fe738b53e35b035898179400682fc109& [14:01:49] My mistake [14:03:26] Why not just look at the page history and then block the guy who did it [14:03:38] They were not logged in during that time. [14:03:48] You can still block them [14:04:06] Like an IP ban on Roblox or an Aternos Minecraft server? [14:04:20] Dunno how to do both. I'm an ameteur. [14:06:15] Click on their IP so it brings you to their contributions, and up towards the top there'll be a link saying "block", in there you can block them so they can't edit your wiki any more [14:07:32] [1/2] Uhh... [14:07:33] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543260821885292615/image.png?ex=6a943924&is=6a92e7a4&hm=dde38cc908c4fe4c110a900731cd03d19be5afe150fcb3f017afcb569a4a2f6e& [14:07:56] Steward bandwidth is extremely limited these days so it’s not going to be a rapid review probably, but I’ll take a look. We prioritizes by urgency so if it needs to be done ASAP it will be [14:08:44] This involves disgusting acts done by a certain wiki such as defaming minors and such [14:08:58] thats why i hope for it to be reviewed quick so action can be taken [14:09:14] Ah apologies I thought you were an administrator, you'll have to ask one to block them [14:09:45] I made the wiki, Phoenix Softworks is me .-. [14:10:22] Threatens death and torture on a known minor. Even if I hate him, he's still a HalSoft community member. We don't appreciate that [14:11:26] Still don't know who in the community made it, if they're even a HalSoftCom member [14:11:30] Did you not get admin rights when you made the wiki [14:11:40] Oh huh I guess you encountered the bug where wiki creators aren't given perms then? [14:11:57] I’ll forward this to the other stewards for review so we can see if we can action [14:11:59] Perhaps T.T [14:12:22] Thank you 🙏 [14:12:27] Yeah, I made the wiki on the same account, Phoenix Softworks [14:13:40] An account called "Halcyon Softworks" has perms it seems [14:14:13] https://cdn.discordapp.com/attachments/407537962553966603/1543262503855849603/Screenshot_20260829_091357_Firefox.jpg?ex=6a943ab5&is=6a92e935&hm=900945dec64e4b2350687f805fcfd157b0cc055b50dbc85a203b393a14c8d96c& [14:15:07] Oh, HalSoft is also me [14:15:11] I forgot the password to that [14:15:14] Keep its perms [14:15:23] I just need one for Phoe [14:16:09] memory worse than my grandma [14:16:53] You probably need to request perms be given to your current account on [[SR/P]] then, if you can't get back into the old one [14:16:53] [14:16:56] you can set a max-width for the table and for individual table cells. although the question is why do you have a tabber inside a table [14:17:15] one of them is two extra characters [14:17:51] on an unrelated note lets clear some tabs too [14:17:52] my minecraft mods T.T [14:18:26] this sounds like t&s jurisdiction tbh [14:19:14] I have 400 tabs currently open [14:19:21] whuh [14:19:24] acting like dats a flex [14:19:24] my record is 350 [14:19:48] my infinite amounts of mineraft gun mods >.< [14:44:19] @emiliers -- Im still struggling with the code to get it to parse the pipes correctly. Here is what I currently have the code set at, replacing some pipes with the double brackets and exclamaition marks (highlighted in yellow and blue : https://www.pasteboard.co/bEfJFQDtBWWX.png [14:47:10] Sadly, Im still having issues with the pipes not parsing correctly : https://www.pasteboard.co/mH6cFP_JCbLw.png [15:08:49] You think that’s bad? Rookie. [16:17:06] Brand new to all of this. I'm trying to add the PI species infobox to my wiki and I completed the steps to add the extension, no idea how to add it to a page now [16:30:03] not sure where to put this (probably SR/WR?) just came across https://meta.miraheze.org/wiki/Special:RequestWikiQueue/89580#mw-section-details this request, which appears to have the same scope as [[mh:doors]] [16:30:04] [17:02:47] got it on the spot [17:03:05] its always easiest before any editing has taken place on the new wiki which was the case this time [17:03:13] thanks for catching it [19:02:56] y'all [19:03:03] :] [19:39:20] Hello👀 [20:02:34] Could i get some help with my wiki CSS in #Global CSS Editing [20:10:57] What would happen if editing has taken place? Would your job be harder? [20:21:35] it would be harder because I don't like abruptly killing work someone has started [20:23:05] [1/2] at the very least if it was a little work I would be inclined to at least make a meta talk page message and if there was a good deal of work then the preferred approach would be controlled shutdown/merge which is more steps, and if it ran away and is a full on project despite the redundancy then the path to reconciliation can be a number of things but rarely would ever favor an abrup [20:23:05] [2/2] t "nope we're taking this, sorry, go to the other wiki" approach [20:23:40] at times we've either left it alone at that point, and especially if the older wiki is dying off, we might also favor the newer wiki and just merging off whatever of value was on the old into the new [20:24:11] because its something we have no reliable way to consistently measure its just kind of always a bit of a mess that is super easy to get into and we simply do not chase it unless it comes up [20:46:57] [1/2] Ive tried doing both and neither seemed to work [20:46:57] [2/2] As for why i have a tanner in a table, its an upgrade with multiple stages to it, and theres other upgrades on that tab in the game that im doing this for, so i wanted to keep it in one table section [20:54:52] thank you mobile frontend for not render-blocking mobile.css [20:54:59] I sure do love fouc [21:11:14] there's a setting to make it use common.css and render-block [21:11:23] something like wgmfcustomsitemodules [21:13:01] I think tabber is the wrong thing for that tbh. a list would be better [21:13:04] will prob do that (though I'll need to move stuff around) since the request time for mobile.css sucks ass anyways [21:13:30] another 450ms ❤️