[00:41:21] Hello? [00:43:58] nya~ [01:39:37] @pixldev the login thing still happening [01:39:59] wdym? [01:40:37] i cant log in [01:40:43] have you cleared your cache? [01:40:54] wait no [01:40:58] remove the miraheze cookies [01:41:36] yep all of the above [01:41:50] ... even removing the miraheze cookies [01:44:55] even the miraheze cookies [01:45:05] tried a diff google account [01:45:10] logged in and out of meta [01:45:22] just change browers bro 😭 [01:54:40] On the Crystalite13 account right? [01:54:51] I asked you confirm if that was the account with issues hefore [01:55:00] yes sir [01:58:18] Huh [01:58:51] Is it on all wikis [02:05:33] Hi? [02:35:37] Well, I guess I need support for posting in the support channel -- I'm getting a message saying 'this can't be sent because it contains content blocked by this server', but no clarity on what content is, uh, blocked... I'm not even attaching an image! [02:36:57] you have to verify yourself in #verify if you want to send links [02:38:24] ty! [02:39:25] you're welcome [02:48:55] only on the graceroblox.miraheze.org [03:01:22] huh, I can’t really try any of the typical pokes because its private but i don’t know of they’d work anyways [03:11:25] What happens if you log in on meta first then attempt to visit the wiki? [05:54:04] Is it possible to change the url of a wiki? [06:03:54] yes phorge [06:17:37] so this is kind of a silly question but is there some sort of CSS sandbox i can use or a way to clear CSS for myself while still keeping it visible for everyone else [06:18:20] because i just found out there's a way easier way of working on the citizen theme and i can't really do anything about it without starting from the ground up [06:26:56] Adding `?safemode=1` to your URL makes it so the page is loaded only with default CSS & JS, i.e. any MediaWiki: or User: JS and CSS code are not loaded. [06:27:48] After that you kinda had to use the Developer Console to experiment with CSS [06:27:57] yeah i've got a plugin [06:27:59] thank you very much [07:02:56] Sounds like others have already got you on the right track, but yes, a ticket on issue-tracker.miraheze.org (our phorge instance) is the right route to go if the wiki topic isn't changing at all. If the topic is changing, steward requests/misc to get teh new topic/scope approved, then off to phorge [07:03:19] And https://meta.miraheze.org/wiki/Custom_domains for non-MH URLs [07:20:06] [1/2] https://meta.miraheze.org/wiki/Help:How_to_rename_a_wiki [07:20:06] [2/2] Thought I'd write a short guide. It's shorter than I expected but at least no one needs to explain the scope change part in the future. [07:24:20] im thinking maybe we need shortcuts for these guides [09:34:48] I'm struggling to really buy our use of the help namespace for them tbh [09:35:34] a lot of the content can spin out or be side by side with mainspace as general platform guidance, and maybe end up with snazzier naming so you can do [[ rename a wiki ]] (don't, hopefully it doesn't try) [09:35:35] [09:35:40] wellp it did, oh well [09:49:18] wikiname for renaming [09:49:31] username for user renaming [09:49:48] wikilook for customization [09:52:42] or redirects can be made like meta.miraheze.org/renaming [10:08:07] [1/2] Yeah I don't really like the "how to" prefix. There's also lots of variance in quality and length among all the guides. [10:08:07] [2/2] https://meta.miraheze.org/wiki/Category:New_Admin_Guide seems to be a saner way to organize guides. But no matter how guides are presented, whoever tries to reorganize them will go through a wild ride. Unfortunately the probability of that person being me is pretty high. I guess I signed up for it when I started producing guides. [10:09:36] several have tried [12:45:02] For those interested... New proposal on [[Dev:Project:Community portal]] [12:45:03] [13:11:22] Will give me actual analysis when I’m back but do like the idea of adding more info, plus the parity with meta’s layout is nice [13:11:33] [1/2] > If you are unable to import a template from here, please create a task listing them at Miraheze's issue tracker. [13:11:34] [2/2] This is incorrect I think [13:19:13] idk if it's worth mentioning plans about default set of templates [13:21:44] Oh yeah [13:21:55] @originalauthority was working on a loadout thing in MW a while ago [13:22:23] Not sure if that’s still WIP, I think that was pre ManageWiki rewrite [13:32:06] Yeah, we haven't heard about that for a while. [13:32:59] Could you comment that on the Community portal. I am afraid I will forget that comment [14:03:56] What templates do you think should be defalt? [14:12:15] There are several. Such as Messagebox'es (such as stubs), Maintenance, {Documentation}/{Documentation Subpage}, Upload template: {Information}, User warnings, .... there are so many that many wikis use, and only need to adapted to their own liking [14:13:07] Just think when you start a new wiki, which templates/modules you import [14:13:32] Some of them are generally used by almost all wikis [14:16:11] And by using Magic words, such as ```{{SITENAME}}``` it will always take the project name; That goes also for ```[[{{SITENAME}}:Community portal]]``` for example [14:24:01] What do you think is the most over-compliated template you have seen? [14:27:43] https://rainverse.wiki/wiki/Template:Pagebox, courtesy of yours truly [14:29:11] Nah that is simple vs Wikipedia templates [14:29:23] y'know what, true [14:29:47] https://rainverse.wiki/wiki/Module:TNT [14:29:50] [1/2] I see a bunch of rather nice code. What does "-->{{DEFAULTSORT:{{#invoke: Pagebox|sortKey|sort={{{sort|}}}|chapter={{{chapter|}}}|chapter-name={{{chapter-name|}}}|sortPage={{{sortPage|}}}|page={{{page|}}}}}}}/includeonly