[00:06:47] -# i knew chrome was up to no good [00:12:44] I always knew Chrome was a virus; good thing I'm safe with Firefox [00:13:28] chrome is not the problem [00:13:34] wikitide thing is [00:16:58] [1/2] WikiTide was the name of a former wiki hosting service started by many Miraheze volunteers during the Great Schism in '23; it has since been merged into Miraheze, but the name still lives on in certain areas and also has a dubious legacy as Miraheze's would-be new name had there not been a community stir resulting in the Board cancelling any renaming plans [00:16:58] [2/2] and an extended voluntary vacation for one of our former Stewards (they returned at the end of August) [00:17:19] TL;DR: The Miraheze community is fun sometimes [00:20:02] maybe agent forgot to buy analytics.wikitide (?) and someone linked it thinking it was and i clicked on the link were Bitdefender blocked it [00:20:33] no, all analytics.wikitide.net is is Matomo [00:20:45] I'm guessing it was flagged erroneously [00:21:06] We have full control over it and it used to be located at matomo.miraheze.org [00:22:24] Actually, I think I see what happened [00:22:52] it seems the certificate for analytics.wikitide.net is invalid [00:23:31] https://discord.com/channels/407504499280707585/808001911868489748/1280670432433012747 [00:23:34] probably this [00:30:55] So... I cannot register bc of Chrome and there's no hope. [00:31:10] 🥲 [01:06:55] for future reference, wikitide.net(note net, not org) is where most of the tech infra is [01:08:04] Try clearing your cookies/cache; if that doesn't work, try using another browser [03:32:37] i jsut found out that fandom just. randomly nuked alot of personal wikis [03:35:29] hold on let me move to OT whoops [05:08:20] [1/2] Do Wiki logos HAVE to be a certain size like how Fandom forces it or is 135x135 just Miraheze's recommended? :ThinkerMH: [05:08:20] [2/2] Maybe my logo is either too big or too wide since it's horizontal lol but it's not appearing, favicon changed successfully though. Logo is still Miraheze's default [05:08:40] micor4004: recommended afaik [05:08:51] the problem is probably caching [05:09:26] Ohh, I understand! Thank you. Should I just wait, or do I have to do something like clearing cache? [05:10:04] you can try to clear your browser cache, but i'm not sure if that'd help [05:10:21] [1/2] This is the logo I used, but there's a vertical version slightly more cramped I can try to use if this is too big [05:10:21] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1280756819769430056/logoHorizontal.png?ex=66d93d3d&is=66d7ebbd&hm=c300512ebef3f8a802d3c28242cdd414b5b389cec76df2afc1bbc7c34346c31c& [05:10:34] Thank you Blank! I will try 👍 [05:12:04] i do know that robots.txt is cached for 12 hours, but i dunno about the favicon [05:12:33] miraheze is also currently migrating to cloudflare whose config i cannot see, so i have to look at their varnish config (the thing they're currently migrating from) [05:24:44] long horizontal logos on some skins are wordmark [05:25:45] logo is strictly a square, and going over 135px causes might cause funny positioning [05:26:23] there's also "apple touch icon" which is basically "favicon for mobiles" and google [05:27:54] wordmark also offers its own sizing settings [05:39:12] Welp, Usagi Shima Wiki may be getting a ton of redirect pages :p [05:40:00] It's so that it won't have issues with Indie Wiki Buddy [06:53:33] [1/2] Guys, i sent a second email verification in the moment i reported having issues, and at midnight, it arrived. Now seems im in. [06:53:33] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1280782789788307518/Screenshot_20240904_015107_Brave.jpg?ex=66d9556c&is=66d803ec&hm=c6cf4532ea2e57d6a2ab455516c3b4cbf6a027a1bf1bef9c426f2956e19b90a2& [06:54:15] Nice [08:42:16] [1/2] Anyone know any templates that can let me do something like this? Boxes with an image to the side and text next to it I mean. Or how would I make a template like this [08:42:16] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1280810148344102944/IMG_2912.png?ex=66d96ee7&is=66d81d67&hm=20b95f5607f33350577ad5c5421549912ecdd76e7efeee4c97e739b817b088be& [08:46:50] sawn.dnh: you could copy the template used from the wiki [08:47:12] a table [08:47:39] oh no [09:09:11] I cant it seems to be like, only for mods to view or something [09:09:21] weird? [09:09:33] Are tables with images something I can make out of the box or do I need to get any extensions? [09:16:16] [1/2] default functionality [09:16:16] [2/2] [09:17:00] alternatively, HTML coding, w/ div's and stuff [09:19:55] Ah thank you very much! [10:43:29] [1/2] why cant i do things? [10:43:29] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1280840653265436714/image.png?ex=66d98b50&is=66d839d0&hm=9933b831c34bf95bd486aadedce8b5a7b9b22b4c0d08c28a5457fa7f5a552422& [10:44:03] are a bureaucrat of that wiki and are logged in? [10:44:10] owner [10:44:24] and yes [10:44:24] there's no "owner" [10:44:38] admin? [10:44:39] there's bureaucrat given on creation [10:45:02] did you poked around bureau permissions? [10:45:30] because i am trying to not allow everyone (except bureau and admins) to edit [10:46:02] i think? [10:46:22] which wiki? [10:46:46] Has the image upload issue been solved yet? [10:46:54] vh3.miraheze [10:48:31] group: (everyone) [10:49:40] wait a sec, I'm getting an error [10:50:30] ? [10:50:33] oh [10:51:01] do i need to make the wiki public? or [10:51:36] [1/3] ah lmao [10:51:36] [2/3] I had different shit, VPN related [10:51:36] [3/3] but yeah, can't view private wikis either [10:51:46] oh [10:51:57] you should have changed Everyone and User groups [10:52:56] if you have changed something in bureau then idk [10:55:16] You may have to ask at [[SR]] to reset them to default if you messed up the permissions somehow [10:55:16] https://meta.miraheze.org/wiki/SR [10:56:13] hm links don't work [10:58:18] That's because Wiki-Bot ignores bot messages in Discord [10:59:01] sr? [10:59:09] whats that [10:59:11] [[SR]] [10:59:11] https://meta.miraheze.org/wiki/SR [10:59:12]

[10:59:48] oh [10:59:50] why I thought it doesn't ... [11:00:10] the Permissions subpage [11:00:27] it's [[SR/P]] in this case [11:00:27] https://meta.miraheze.org/wiki/SR/P [11:00:28]

[11:00:38] i'll request after i eat [11:00:43] dinner [11:00:49] enjoy your meals then [14:44:48] Idk if connection time out is ongoing issue when trying to access a wiki, but I have encountered it [15:00:06] there are various issues going on as of recently [15:01:45] this is while I saw folks saying Fandom has some server issues too, apparently? [15:13:53] my wiki says (Cannot access the database: Cannot access the database: No route to host (db181)) now rip [15:14:37] yeah, I'm rebooting cloud18 right now [15:21:49] How Do I make an infobox? [15:28:32] does the status page ever get updated lol [15:28:51] kinda doesn't really feel like it ever is [15:28:51] probably not unless there is a clear reminder to look at it, I think a portion is automated [15:28:53] Actually what's this [15:29:14] Manually-updated status page? Seriously? [15:29:21] I updated status.wikitide.net [15:29:28] Actually why does this type of outage happens? [15:29:37] outages happen for any number of reasons tbh [15:29:47] technology being technology [15:29:53] like some [15:30:20] mirahezestatus.net is old and needs to be switched to the new page [15:30:37] can it get a quick redirect fix to the new one so people don't have mixed resources? [15:31:00] Poke @cosmicalpha for that [15:31:07] They control the DNS [15:31:13] (Not us) [15:31:20] Actually its' making confusions [15:31:27] Could it be updated to mention the new one or is it just plain out of our control? [15:31:53] I can update the actual page, but can’t change it to the new page [15:32:01] updating the actual page sounds good then [15:32:05] which is the new page and which is the old page 🤔 [15:32:10] and it can go to the new page as a next step [15:32:27] this is new one https://status.wikitide.net/ [15:32:32] I assume CA can't make that fix immediately so even just a note on the old one right now would be good [15:32:43] Hi [15:33:12] Is the major otage within File Storage as shown in the status page [15:33:18] Is Mirahezee still down? [15:33:26] Yeah [15:33:40] Why? [15:34:37] This isn't Xaloria's expertise, please rely on comms from members of the @Technology Team [15:34:59] Yes actually refer to them for this [15:35:07] how do you do the sub-title things [15:35:09] I added a notice at the top of the old page [15:35:10] Try contacting them [15:36:29] for sections wth more then two words do you do an underline or space? [15:36:29] I kinda hope thkngs will be fine soon? [15:36:52] Yep, this is actively being worked by the tech team [15:36:56] Is this clouldflare domian related? [15:37:02] [1/3] to add sub-titles within your infobox on your Miraheze wiki, you'll need to modify your infobox template to include additional header and data fields for these sections. Start by editing your infobox template to add extra rows, such as section1_header and section1_data, for your sub-titles and corresponding content. For example, you might use {{Infobox | title [15:37:02] [2/3] = | image = | caption = | section1_header = Overview | section1_data = Example overview | section2_header = Details | section2_data = Example details }}. When applying this template to a page, fill in these fields with the specific information you want under each sub-title. if needed, you can further style these sections by adjusting your wiki’s CSS. This appro [15:37:02] [3/3] ach allows you to organize information clearly within the infobox. [15:37:04] thanks MacFan [15:37:28] Per staus it's major otage is in File Storage [15:37:51] Do you have any idea why it happend? [15:37:53] Xaloria, that's not the problem, please stop commenting [15:37:56] ^ [15:38:17] when dealing with section titles in your infobox template that have more than two words, you generally don’t need to use underlines or special formatting. [15:38:34] I was talking as per status [15:38:46] Just because it says major outage doesn't mean that's root cause. [15:39:12] Ohh I was unawre about thata but actually what's main otage then [15:39:13] if it want a section to have a pre-set name how do i do that, do I put it after the =? [15:39:37] mate you gonna confuse the lad because there's no infobox template by default [15:39:38] Tech team is still investigating root cause, will be communicated if/when it's appropriate. [15:40:05] Ok waiting for that [15:40:06] For now, we need to let them work. [15:40:11] pretty much [15:40:15] What do you mean "section" of a template? [15:40:19] if you want a section in your infobox to have a pre-set name, you can define this directly in your template. You would specify the name of the section within the template, and then users can fill in the content. [15:40:50] I do exeactly this with my "place" template [15:41:18] will this template word? `{{Infobox | title = | image = | caption = | continent = | header1 = | city count = |capital= |population = |income ($) = |manpower capacity = |starting conscription Law = |starting conscription Law = | header2 = Formable Details = |can form = |required to form = }}` [15:41:18] https://meta.miraheze.org/wiki/Template:Infobox_ [15:41:43] In the context of a template, a "section" typically refers to a distinct part or segment within the template where specific types of information are organized. [15:42:28] [1/2] do you have the `Template:Infobox` page on your wiki? [15:42:29] [2/2] if not, it won't work [15:42:34] Oh, so yes, my template for places have a scetion for generel info and a section for the controllers of a place. I styled the section headerss as boxes [15:42:38] what do I change then [15:42:41] it's a template [15:42:44] how do I fix it [15:42:54] I js copied what @xaloria45 said to put [15:42:58] Exactly [15:43:07] then what do I change it 2 [15:43:19] I forgot to tell but you should have Template:Infobox [15:43:23] this is the infobox template I want, I coppied what you said 2 put [15:43:34] what do I put in that?! [15:43:38] Do you have Template:Infobox [15:43:42] no [15:43:51] So create that at first [15:43:57] read through [[Infoboxes]] [15:43:57] https://meta.miraheze.org/wiki/Infoboxes [15:43:58]

[15:43:58] and put what in it [15:44:22] lets start at the beginning with this, see canada's link for an overview [15:44:39] I can't stop by for long and can only interject, but that's definitely the point to begin [15:45:18] Yes and after making Template:Infobox you would then do what I told you to do? [15:45:27] ima use the Portable Infobox Builder [15:45:28] Xaloria, slow down [15:45:33] please [15:45:34] ok [15:45:36] Also, if you want to use FANDOM infoboxes, you would need an exterson [[PortableInfobox]] [15:45:36] https://meta.miraheze.org/wiki/PortableInfobox [15:45:37]

[15:45:38] this is the simplest way to go I think [15:45:45] it's js loading a bit slow [15:45:54] it will give you a graphical build and yes, it can be slow on initial load [15:46:06] keep in mind it creates new boxes and can't be used to edit existing [15:46:12] Usually only the first load is slow, it gets faster on repeat visits. [15:46:13] https://cdn.discordapp.com/attachments/407537962553966603/1280916840515637370/image.png?ex=66d9d245&is=66d880c5&hm=abbcdc2b738d3b4cec3775bee02fe495cb333300be71521fac8d1759eaa24221& [15:46:25] (And hitting refresh never hurts. 🙂 ) [15:46:44] if it's going off past a minute, f5 yeah [15:47:00] unfortunately the current outages must be considered, right now is worse for loading than most times [15:47:25] Hey actually wanted know how can i hide logs edits from recent changes like if made any changes in logs it doesn't shows in recent changes [15:47:51] if you know you're doing stuff that will spam recent changes, give yourself the bot right until you've done it [15:48:08] Are custom domains broken? AllTheTropes seems to be down (it’s not loading), but other Miraheze wikis not using custom domains work just fine. [15:48:12] if you've already made a change and need to hide it, that can be done in the page history [15:48:26] Are custom domains broken? AllTheTropes seems to be down (it’s not loading), but other Miraheze wikis not using custom domains work just fine. [15:48:27] and that hide will then apply to recent changes as well [15:48:36] Ok [15:48:41]