Such pages should better not be as article pages in the main namespace but in the Project: namespace, such as Project:Protection reasons (the Project: part is automatically replaced by the name of the wiki).
This would prevent them from appearing in these lists, from appearing in searches by default, etc.
I would use separate templates, for simplicity. For example Template:ms to seconds
<includeonly>{{#expr: {{{1}}} * 1000 }} seconds<includeonly>
Usage
{{ms to seconds | 1500}}
gives 1.5 seconds
Another example - for Template:ms to days
<includeonly>{{#expr: {{{1}}} * 1000 * 60 * 60 * 24 }} days<includeonly>
To clarify, a subpage is simply a page named after another page followed by a / and something else. No code is involved.
This template (+ module) rely on JavaScript to inject the CSS into the page. The JS part is the first section in the wiki's MediaWiki:Common.js
That makes it easy for every user to add CSS to any page, but not exactly in a good way.
Yes but you wouldn't be able to edit or post. That's what "read-only" means.
Are you looking to specifically convert from ms to minutes (or any other specific conversion)? Or to create a universal convertor that can take many different forms and units and handle everything properly?
The first one is quite simple. The second one is very hard, perhaps even impossible with Wikitext.
And the other way around too - if you put spaces they would show as underscores in the URL. Underscores and spaces are aliases to each other in MediaWiki's page names and user names.
Refactoring means changing the code to do the same but more efficiently.
Let's start off by changing the code of Template:Dia to this:
<onlyinclude><div style="width:500px; margin:12px 7px; overflow:hidden; display:flex; gap:12px; background:rgba(255, 255, 255, 0.58);">
<div style="overflow:hidden; width:90px">
[[File:Dia{{#switch: {{{character|{{{1}}}}}}
| CoinyDEL = CoinyDEL.gif
| BookAAA = BookAAA.jpg
| BraceletySign = BraceletySign.gif
| #default = {{{character|{{{1}}}}}}.png
}}|80x80px|link={{{link|{{#invoke:Dia code|code|{{{character|{{{1}}}}}}|link}}}}}|alt={{{alt|{{#invoke:Dia code|code|{{{character|{{{1}}}}}}|alt}}}}}]]
</div>
<div style="width:390px; font-size:16pt;">{{{dialogue|{{{2}}}}}}</div>
</div></onlyinclude>
{{Documentation}}
(I hope I didn't miss something important)
As for Template:DiaEmpty and some other parts, I thought it was you who said you want to leave them out.
Possibly, a page has a post-expansion limit of about 2MB.
However, you can probably save a lot of Wikitext by refactoring Template:Dia, use better constructs than a "table" and move all the styles to the wiki's CSS or to a TemplateStyles template.
Regarding leaving out Template:DiaEmptys, yes you can add a condition to prevent it from being rendered on a certain page or on the main namespace etc.
See Help:Discussions_AbuseFilter and Help:Discussions_AbuseFilter/Rule_format
I didn't use it either but it seems to be more UI-based and less tech-savy than the original AbuseFilter.
I highly doubt it would be possible to "migrate" accounts from one host to another. But anyway, it's not appropriate to go on a Fandom-owned forum and seek help for a competitor.
Not exactly a search, but you can go through your list of posts either on Discussions or on the "Activity" tab of your profile.
I don't think it's possible, that's probably not really what the extension was made to deal with.
I'm not sure what's the problem with someone deleting these messages after seeing them. The warnings are there to inform them about what they did wrong and what might happen next, not to leave a shaming note. But if you really think it should be unallowed, state it in the rules and enforce it like any other rule.
Unless you have requested a fixed IP address from your internet provider, your IP address usually changes often, so it's not possible to identify you based on IP if it was some time ago.
But anyway, are you sure you have been blocked for that? I've never heard of an IP block without blocking the account itself, unless the edit was done without logging in to any account at all.
I'm pretty sure you didn't actually want the original template to be created under the name Template:Example - that's just an example name, you choose your own. It just has to start with "Template:".
Edit: Also, you don't need to manually edit the URL, you can go through the regular "create new page" and just give it a name that starts with "Template:"
<data source="year1">
<format>{{{year1}}} {{#if: {{{year2|}}} | - {{{year2}}} }}</format>
</data>
But redirects do indeed affect the search feature, so if you type the name of the redirect page in the search box it'll give you the actual page in the search results.
You can use "forgot password" on another device, then it'll send the reset code to your school email (it probably doesn't block emails from Fandom), then you can copy it from there.
@CAMERAwMUSTACHE did you ever actually do that and turned archived comments on Talk: subpages into comments displayed in the comments section?
By my understanding of how all of this operates, I fail to see how this method would work.
So it's not an issue with the feature itself, just wanted to make sure.
You typed the correct form for the old message wall greetings, back when it was a built-in feature, but the current script-based feature indeed uses a different page.