[00:39:12] How long does T&S usually take to respond [00:40:18] usually <24h from my experience [00:40:38] Damn [00:40:58] what kind of issue have you reported [00:41:01] Well mine is waiting for about a week so I'm guessing they didn't get the email [00:41:15] Copyright [00:41:43] oh that probably takes longer but lets check [00:41:46] what did you title the email [00:42:05] or your email adr if you are bold enough [00:43:07] https://cdn.discordapp.com/attachments/407537962553966603/1409699647986864168/Screenshot_20250826_024251_K-9_Mail.png?ex=68ae549b&is=68ad031b&hm=d0ec285c1faa5c70346b16341b3864fdba8e99983f332ffc847bede3b27b6652& [00:43:22] miraheze@kocka.tech lol it's not exactly a secret [00:43:47] @Trust and Safety Non-urgent: was this received? ^ [00:44:26] I received it [00:44:54] Alright cool [01:02:16] For context, I usually review and action T&S actions weekly except when there's an urgent element to the report. In this case I was swamped with higher-priority items and wasn't able to review it fully as there's quite a lot in there to scrutinize. [01:02:32] But yes, confirming as well that I have seen it [01:09:57] I'm not exactly in a hurry but there is no receipt confirmation mechanism so I wasn't sure if my email arrived [01:11:06] I've had situations where I'd only get the bounce notification after several days [01:12:48] bounce notification by carrier pigeon [01:21:42] A simple, "yes we've received this and will look into it" could have been sent, especially if it has been seen by two people. [01:40:39] An automated reply confirming its been received cant hurt [01:56:14] That's almost certainly an actionable suggestion, I'll reach out to the workspace admins [01:57:48] I'm not sure what could have caused it then since I'm unable to reproduce it. You may want to ask other users in your community to see if they see the same anomaly. [03:12:08] [1/2] Why I can't not use Tabular.ConfigJson contentmodel? [03:12:08] [2/2] I see it can be chosen on Miraheze Common but I don't found and Data:i18n/... page on other Miraheze wikis [03:48:42] Is only we can use that on Miraheze common? [03:49:32] It may not have the extension enabled if its an extension related content model [03:49:44] i figured it out [03:50:00] Beyond that no idea [03:50:51] in most use cases Tabular.ConfigJson is supposed to be on commons or just generally elsewhere, but they wish to have it locally [03:51:48] I'm sure that I enable that feature [03:52:10] you already have everything required enabled, I'll push a config change in a moment [03:53:06] https://needforspeed.miraheze.org/wiki/Data:I18n/Uses_TemplateStyles.tab [03:57:28] [1/2] Since the data comes from c:Data:XXX, should I assume that translation data should be stored on Miraheze Commons, and that this was the original idea behind M:TNT on Miraheze Meta? [03:57:28] [2/2] Additionally I've make a counterpart of M:TNT but it use Lua table on sub-modules. [03:59:26] Oh 🤷🏼 [03:59:53] i dont particularly like this extension, bit of a mess [03:59:57] but i figured it out [04:00:06] who "they" refer to? [04:00:11] you [04:01:16] time to push to prod :3 [04:01:45] Skye why do I see fire in the DC? [04:02:15] gosh I haven't even pushed yet, please wait before screaming fire [04:03:25] Can I scream fire yet [04:03:29] feel free [04:03:35] FIRE [04:03:39] Panik [04:03:43] Is there any way for me to share the template with another wiki?(scary transclution?) [04:03:57] yessirrrrr executing the mw-config repo! 🫡 [04:04:11] Did you do rm -rf * first? [04:04:47] [1/2] @huannengqizhaban You can have Tabular.JsonConfig on your wiki now [04:04:48] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1409750399740805210/image.png?ex=68ae83df&is=68ad325f&hm=22d0452142128ca2bba22eaab3e637bfc7e56708c1142a42c7155e96cd535d7d& [04:05:14] Thank you sincerely!🌹 [04:05:37] How can I end the post? [04:06:15] the support post can just stay, no worries [04:06:52] You can archive that post [04:06:55] you meant rm -rf / on mwtask181, surely? [04:07:33] https://tenor.com/view/we-dont-do-that-here-black-panther-tchalla-bruce-gif-16558003 [04:07:50] (mostly because we dont have the discord permissions lol) [04:48:50] I think for Translation using Lua table is more easier than using Tabular.ConfigJson [07:48:13] Hey I tried to use the M:TNT again but it report Fatal exception of type "Mediawiki\Page\PageAssertionException" [07:48:36] i saw, can you post the exception code [07:49:20] I think it's better to create the Data page on Miraheze Common or Mediawiki Common, instead of local wikis [07:53:30] Done [09:04:30] nit: it's a request ID [09:04:46] It identifies all logs relating to a request [09:04:53] Not unique to the exception [09:05:03] true but rule of language barrier [09:05:10] And requests without any logs still have them [09:05:17] I know but [10:00:30] So what should we do? [10:11:49] Wait for @pskyechology to pull the traces for that ID [10:12:04] I'm away today [10:14:28] [1/2] im going home and having a well-deserved sleep [10:14:28] [2/2] if you can find someone else to convince your namespace or config to use different IDs, be my guest [10:25:30] Data page? You mean "Meta data"? [11:15:45] Data namespace [11:16:41] Why would you want a Data Namespace on Commons? Commons is a File repository [11:16:56] What you want is a Wikidata? [11:17:06] Data namespace is not a wikidata thing [11:18:10] What would you want to use that Data Namespace for? [11:19:01] It still has nothing to do with commons though [11:23:21] @skradio does JsonConfig always require the Data namespace [11:23:28] @pskyechology [11:23:45] I have no idea why it pinged ren [11:24:26] @pskyechology if it does, it should be added to https://github.com/miraheze/mw-config/blob/f510f44187acba2c5376015fb1519304387f848d/ManageWikiExtensions.php#L2527 so it installs it with the correct ID [11:24:52] The existing ones will need to be fixed in the mw_namespaces tables [11:25:03] oh boy [11:25:06] And probably one of the fix scripts [11:36:21] Could https://www.mediawiki.org/wiki/Help:Tabular_data be of use? [11:37:12] You could test that at [[mh:test:]] [11:37:13]

[11:38:30] That's exactly what he's doing but our setup looks broken [11:39:11] I see that Data pages are stored in Commons [11:39:37] I don't think copying Wikimedia and storing them in commons is right for us [11:39:48] Much wider scope than Wikimedia for content [11:40:00] I was unfamiliar with that. Or unaware. [11:40:01] I do think we should fix it not working on your wiki though @huannengqizhaban [11:40:38] They aren't for us [11:41:02] [1/2] OK [11:41:03] [2/2] So it's OK for me to use my module as counterpart to implement translation feature? [11:41:14] Miraheze Commons seems not the right place imho. [11:41:37] I am a single admin there, and have no clue about this [11:41:40] Yes, we need to fix JsonConfig being broken on your wiki. It looks like a configuration issue on our end. [11:41:55] @rodejong it most definitely isn't the right option to do anything on commons for this [11:42:04] [1/2] Some template is better to be stored in MW common [11:42:04] [2/2] others are suitable to stored in Miraheze Common [11:42:41] I have another wiki also need to be install Tabular.ConfigJson [11:43:45] Fact is, Miraheze Commons, is not equal to Wikimedia Commons. [11:43:51] We only host files [11:44:05] Open a [[Phorge]] task please [11:44:06]

[11:44:18] Although it won't work until we fix your existing wiki too [11:44:43] It sounds more suited for dev wiki if there really is a need for global ones than commons [11:44:52] But that's honestly a separate debate to have on wiki [11:45:01] Fixing it so it at least works anywhere would be a start [12:10:15] I think it's better to save the data of utilizing template on global wiki on MH [12:16:37] This discussion can be much better articulated on wiki in a proper discussion where everyone can agree [12:38:08] Meta? [12:38:32] Yes [12:59:21] I'm so confused! [12:59:37] I'm trying to update my wiki's CSS using an extension, but when I go to apply it, it's not the same [13:00:59] ...oh, NOW it worked [13:24:29] Skye magic strikes again! [13:29:50] Is it possible to request for "shortcut links" for a wiki? (for example, st.miraheze.com linking to skibiditoilet.miraheze.com) [13:31:10] No. [13:31:19] Fair enough [13:31:36] Point is that they are not descriptive enough, and are often used for language codes [13:31:57] A subdomain needs to have a meaning [13:32:13] Oh, but if it was something like skibidi.miraheze.com would it be allowed?? [13:32:39] Yes. But we do already have a Skibidi toilet Wiki? [13:32:51] as a redirect [13:32:52] I think you misunderstood my question [13:32:57] Yeah, as a redirect [13:33:27] like fart.miraheze.org redirecting to another wiki [13:34:51] Erm... Not sure. @Sky might know that better than me [13:56:28] Currently no @bitbyte10 [13:56:50] The only time we redirect Miraheze subdomains is wiki renames [13:57:02] That's a policy matter not a technical one though [15:26:07] Hi, there's a certain format when adding a logo/favicon to a wiki. How do i add one? [15:30:43] [1/2] favicon can be an ico file, but png works too and can be the same file as logo [15:30:43] [2/2] logo image must be 135x135 px [15:31:15] [1/2] see [15:31:16] [2/2] [15:32:37] https://microscape.miraheze.org/wiki/Food [15:32:45] How do I make the description pop up? [15:35:15] [1/2] enable textextracts extension and check "Enable Auto Description" setting (in SEO tab) [15:35:15] [2/2] might take some time or a blank edit to start working [15:46:50] Do I have to request for textextracts to be activated? [15:47:30] no, if you are admin you can enable it, see Administration sidebar, Manage this wiki's extensions link [15:51:29] where's the seo tab? [15:52:09] The textextracts is enabled by default [15:53:48] Hmm strange... [16:06:51] [1/3] in Administration sidebar [16:06:51] [2/3] Manage this wiki's additional settings [16:06:52] [3/3] you'll find SEO tab, the setting is somewhere at the bottom [16:11:55] It is already enabled by default too [16:14:17] give it some time then, i guess, the page was created today [16:14:40] Alright [16:14:54] I think I might have gave the description today [16:15:02] if you click on Page information in Tools drop downs, at the very bottom should appear preview [16:15:02] Might have been just the table in the page before [16:16:20] [1/2] example [16:16:20] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1409934498153631815/Screenshot_20250826-201553.png?ex=68af2f53&is=68adddd3&hm=b59623911fd28b8c91894c4d6b5237dbc7fdb5b2e9420bc5ca3b9257e68a5b9f& [16:18:14] Hmm... it doesn't have the SEO properties yet [16:19:52] I will wait. @theoneandonlylegroom you helped me a lot [16:21:04] We don't generally permit subdomain parking in this way, no. [18:14:02] [1/2] hi is there a way to edit this a bit? i want to add rules and guidelines [18:14:02] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1409964118013902920/image.png?ex=68af4ae9&is=68adf969&hm=3060a24be7b28986224a4c10f80868efaf928d93896406e24f5028f2613478a6& [18:15:05] MediaWiki:Sidebar page [18:16:03] thanks [19:06:54] without "page" obviously 😉 [20:09:52] hi friends, how can i access the #sub parser function on a Miraheze wiki? [20:09:59] i see another miraheze wiki is using it but it wont let me D: [20:11:45] parserfunctions is enabled by default, you shold be able to use it [20:12:01] [1/2] ehh.. im trying to use it for the disambiguation template and it just does thhis [20:12:02] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1409993812373143722/image.png?ex=68af6691&is=68ae1511&hm=38feadb6a0d2384f6ee754895a99c3b32b8973367aa2393bd562b846c5669702& [20:12:04] not sure if im missing something LOL [20:12:40] [1/2] What's this "Switch to old look"? * Microscape Wiki [20:12:41] [2/2] locations|Locations [20:12:45] https://cdn.discordapp.com/attachments/407537962553966603/1409993997119783073/Screenshot_2025-08-27_at_4.12.37_AM.png?ex=68af66bd&is=68ae153d&hm=f3d732061d62a94f9e083a41be9116bb81288af9bc41f9da1e7d607544938533& [20:14:37] OH [20:16:06] [1/2] i had to enable this, it wasnt on by default HAHA [20:16:06] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1409994838740308111/image.png?ex=68af6785&is=68ae1605&hm=dfe7fb9bad4948c592822b75ad21a64c234dae235823666b3f12f241e74953ed& [20:16:07] ty skye! [20:16:57] oh huh i thought we had it on by default [20:17:00] nice that you figured it out [20:17:03] maybe on new wikis X'D [20:17:14] nah its been false for at least 3 years [20:30:22] it suggest user to switch skin (in personal settings) to old version called (legacy) Vector, current skin you're seeing is Vector 2022 [20:30:57] Can I disable this for all my users? It's sort of placed at a weird space [20:32:36] im not sure [20:32:45] perhaps it can be hidden w/ css [20:33:35] [1/7] you can save MediaWiki:Vector-opt-out as an empty page [20:33:35] [2/7] or [20:33:36] [3/7] ```css [20:33:36] [4/7] .vector-main-menu-action-opt-out a { [20:33:36] [5/7] display: none; [20:33:37]