[07:00:56] If someone could please resolve this open PR for me please, it's just adding footer icons for some wikis: https://github.com/miraheze/mw-config/pull/6500 [07:07:54] Thank you CA./ [07:08:24] No problem [07:09:39] I did notice that all the footer icon entries weren't alphabetised, did you want me to make a PR to alphabetise them? And in the case of interlanguage wikis, we can alphabetise them as a group instead? [07:10:47] I used to be more worried about the order, but now so many things are out of order and we get more PRs I don't like requesting changes just for that all the time, it matters less. You can if you really want to but it doesn't matter all that much. [07:11:05] Ah, alrighty. [07:16:30] That's more of a reason to care [07:16:45] The bigger and more people involved, the more standards and consistency have an impact [07:17:56] I stopped caring about the order a long time ago because I kept being the only one to keep fixing it and it kept getting messed up. It was to hard to maintain. [07:18:11] I probably should have written a script and put it in CI though. [07:18:20] I should do that if we really care about the order. [07:19:02] I would love to make PR's to clean it up, but if my PR's aren't merged before any others, it slowly starts becoming a mess. [07:19:18] If someone who had the ability to merge their own PR's wanted to do it, it would be easier to clean up. [07:19:25] Yes [07:19:39] Automated checks are the only way anyone is going to care about style [07:19:47] I remember why I didn't now. [07:19:59] We don't always want alphabetical order [07:20:09] some things we want grouped like this [07:20:17] Couldn't you add a PHPCS override string then? Or I guess a custom override string/rule? [07:20:28] Maybe [07:20:37] It might be complicated. [07:20:40] I will try. [07:20:45] phpcs can't do it though. [07:20:53] It doesn't have to be an immediate thing, something worked on over time would be nice. [07:21:04] Will have to be a custom script. [07:21:12] Nothing is breaking from it, it's just a pain to figure out where to put new configs and entries sometimes. [07:21:21] That is fair. [07:21:56] You can do a PR for footer icons if you want [07:22:08] I will handle the rest later. [07:22:11] Yeah, no one is going to add new ones for a big I presume. [07:22:35] It happens quite often. [07:22:47] Fairly anyway [07:23:05] That would be something nice to be able to set through ManageWiki. [07:23:23] Maybe complicated. [07:23:45] I am against doing that at this time. It is possible but it can have a lot of issues with things like licensing if we did. [07:23:50] A PortableInfobox drag and drop idea would be cool, but unnecessary maybe. [07:24:00] That is true. [07:24:15] Best not to then, unless it went into some kind of review queue. [07:24:30] But then, someone would have to screen them. [07:24:55] That is far more effort then it is worth. [07:24:58] Yeah. [07:25:23] I would rather me finally finalize getting restriction levels in ManageWiki. [07:25:31] Speaking on it though, I should scan through LocalWiki.php and LocalSettings.php and see if there are any config variables that realistically can be setup through ManageWiki. [07:25:53] There's probably not that many though. [07:26:10] We don't want literally every one there especially extremely low use ones, as to not unnecessarily bloat ManageWiki. [07:26:51] And giving people too many options could also be a bad idea. [07:28:28] ManageWiki and CreateWik might (if it passes community RfF) have some major UI changes coming soon. like within the next couple of months. [07:29:17] I have a new design for RequestWiki on beta right now, haven't decided if it still needs more UI work yet though. [07:29:32] I wonder if I can see that, lemme check. [07:30:02] Ooh, I might not have a mirabeta account anymore. [07:30:33] Oh no, I still do. [07:31:14] I like the UI Changes. [07:31:25] Yeah you do was just gonna say lol [07:31:36] Oh, my biggest annoyance with RequestWiki. [07:31:53] If I try to refresh when on the comments page, my browser asks me if I really want to refresh. [07:32:09] As if I'm editing a page and I have unsaved changes that I'll lose if I refresh. [07:32:17] I will fix that hopefully soon. [07:33:01] I also have PRs to CreateWiki and ManageWiki right now that should eliminate cache refresh delay, and immediately refresh it on all servers at once when changes are made making changes appear much faster and much more consistent. [07:33:19] Oh, and Special:Notifications is kinda broken with RequestWiki? [07:33:28] If I middle-click a notification, it sends me to `/wiki/Null`. [07:33:34] Oh fun. [07:33:45] So, I have to click on the notification. [07:33:49] Is that a beta issue or a prod issue? [07:33:51] Prod. [07:33:59] Can you create a task for that? [07:34:17] Yes, I will do that rq. [07:35:06] Thank you! [07:40:51] https://issue-tracker.miraheze.org/T15994 [07:55:05] I'll just alphabetically re-order them all, A-Z. [07:55:21] Sounds good thanks [07:55:30] Thanks for that. [07:55:32] Oh, and did we want to make people follow a format for the icons? [07:55:40] Miraheze > MediaWiki > Copyright, or nah. [07:56:00] Cause some wikis are doing Copyright > MediaWiki > Miraheze, or Miraheze > Copyright > MediaWIki. [07:56:16] No, because that order determs the display order in how they are shown. [07:56:20] I think [07:56:29] Yeah, it does. [07:56:37] I just didn't know if we cared enough about that. [07:56:57] Although, consistency really doesn't matter when we offer 30+ skins. [07:56:58] Yeah no, some wikis might do it like that on purpose, we don't need to enforce it. [08:00:15] `examplewiki` overwrites all icons, and `+examplewiki` adds onto the existing icons right? [08:33:58] Yes. [11:59:28] Can someone screenshot the UI I CBA to log in on beta lol [11:59:49] (by CBA I mean I don't know my password hehe) [12:06:33] how true is this https://meta.miraheze.org/wiki/User:123Calmer/How_not_to_screw_everything_up [12:07:27] 0% truth [12:23:56] Sure. [12:24:20] [1/2] https://cdn.discordapp.com/attachments/1006789349498699827/1546858728509149194/image.png?ex=6aa14ff4&is=6a9ffe74&hm=5e60d7644fd67409d43109c4ee6b4b3d59643cfca131bd28916eb94b81604eaf& [12:24:21] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1546858728911937588/image.png?ex=6aa14ff4&is=6a9ffe74&hm=10edbae80e43d799d2c89da248147a7add36f94dd404da5cdd9a2e13da2467df& [12:26:18] I was wondering if maybe there was at least some kind of best practice reason why direct example.com/page could maybe result in confusion that could validate even to just explain how this notion came about [12:26:55] not really worried about a userspace essay that is not particularly accurate but it seemed odd because the user's contribs are fairly neat [13:41:32] what happens if you have a wiki page called `robots.txt` [13:41:44] is I think the main problem [13:43:07] with footer icons the lines take up so much space that you'd have to ctrl+f to find anything anyway [13:43:52] I'm much more bothered about single-line configs [13:48:53] is this something I should make a note of being followed up with, that does seem relevant if there's just no handling right now [13:51:50] I have no idea, those who know mediawiki better than I do are better-equipped to answer that [14:18:59] Hmmm this looks like the Telepedia Wiki Creation Form 🤔 [14:19:06] (which I stole from Fandom anyway lol) [14:20:15] [15:05:53] It is based on Fandom UI lol I didn't even look at Telepedia actually. [15:06:23] It's only inspired by Fandom UI though quite different in the end still. [15:50:10] now that bugs me [15:56:00] If $wgArticlePath is set to / then you won't be able to create articles at index,api,rest.php etc and robots.txt / security.txt etc etc [15:56:16] And there isn't any handling of it so it could be weird [15:57:58] We proactively insert /wiki/ where we can if you forget to do it though [15:58:00] well its kind of interesting because what I'm getting from just testing on a wiki is Robots.txt is fine but it is intercepted so you can never have a robots.txt page [15:58:15] this is in context of a wiki that deliberately chose to cut the /wiki/ [15:58:21] in response to the essay I linked above [15:58:48] what I didn't try yet was what would happen if you try to create a page at the lowercase which may well just be what you wrote [15:59:14] if that's a clear cut behavior I can just fall back on what you said that it just won't be possible [15:59:31] You could probably create it via some methods [15:59:36] But it wouldn't be accessible [16:00:11] We have zero plans to support at the root path [16:00:15] Afaik [16:00:31] nor ought you, better things to do [16:00:32] I think if enough people asked then we could support alternatives to /wiki/ [16:00:38] Cc @cosmicalpha [16:01:28] We potentially could. [16:36:11] will wiki name become project namespace name by default now? [16:37:07] Most likely. [16:37:16] It can probably be changed later though. [16:39:09] a wiki created recently i know was given `Project` as the default namespace name on creation before manual change to wiki name [17:12:39] there was a phorge task about this but idr the link [17:30:02] Could we have it be made somewhat modular through a big config array for downstream? i.e have some prebuilt steps which can either be active or not [17:30:32] I'm a big fan of making all the wizards I make as modular as possible for future use and also anyone who cares to use it downstream [17:31:55] otherwise I will have to go reimplement all the classes somewhere else because I don't like forking createwiki right now when I don't have the bandwidth to properly maintain that fork lol [18:01:48] Sure. I can do that. Though it is 100% modular via hooks already. I can try to see about config though. [18:02:48] That is supposed to already be the case unless something doesn't work. [18:04:01] https://issue-tracker.miraheze.org/T15225 [18:04:15] Oh right I need to fix that. [18:04:37] Thanks! [18:07:15] If it can be hacked together by hooks then perhaps it's fine [18:09:22] btw that is a russian wiki, and its project talk ns is somehow by default named as this weird thing `Обсуждение {{GRAMMAR:genitive|Project}}`, which produces an error when you click discussion button on project pages [18:10:20] https://cdn.discordapp.com/attachments/1006789349498699827/1546945801618464909/image.png?ex=6aa1a10b&is=6aa04f8b&hm=15ac39d14c953fdc1fe90266493f10e16c3899a98133efd6b880a1b843cd9380& [18:13:16] Oh yeah I did have a fix for that but I forgot what it was. I will look again and try to fix it.