Since you are using the Discord script, the colors should already change depending on which theme the user is viewing. If you wish to customize the colors for each theme, then you will need to write your own custom CSS for the wiki. If you are unsure which CSS rules to use, you can view the default CSS to get an idea of which rules control which parts.
Yes, exactly. You will just need to register with the new host and submit your edits again but to the new host.
And since when do wiki activities and generally spreading knowledge compete?
Since forever. Wiki platforms may be free for you to use but someone still has to pay for all the staff, setup, hosting, maintenance, electricity, etc. This is true for every wiki host; no exceptions. There are multiple different methods from which each host may choose to obtain the necessary funds but it still costs money at the end of the day. Every wiki host competes for money to keep their server running and the main manner in which they justify donors and/or advertisers giving money to their particular organization is either by having a larger reach then other hosts or by hosting unique content. Spreading knowledge so that multiple hosts have the same content dilutes the uniqueness of the individual hosts' content and reach, thus reducing funding potential, and thus reducing their ability to keep the wikis up and running.
If you truly believe you have extenuating circumstances, then you can file a support ticket with Fandom and plead your case. However, something like "I really thought I wanted this name but now I don't" or "I made a typo when entering the new name" won't cut it.
Also, keep in mind that Community Central Discussions is not how users contact Fandom. It is not like social media where you can contact the support team using their cooperate account on the platform itself. Fandom uses an older support model where you need to contact them using a separate platform. The Discussions here on Community Central are a place for users to get help from each other.
No
While it is still true that issues with the other host are best discussed with that host rather than on Fandom, I think part of the confusion is due to a lack of understanding what is meant by "migrating" and account. Since I do not know which host the wiki has moved to, I cannot speak to any host-specific features. However, in general, "migrating" an account does not mean that your data, achievements, user status, global contributions, etc. are all copy-pasted to the new host.
When wiki content is copied from one host to another, the edit history is also copied. This edit history includes the username and account number of the person who made the edit. However, the person who did so may not have an account with the new host. As such, the edits are associated to some sort of dummy account which serves as a placeholder in the system for a user that does not exist on the new host. When you "migrate" and account, what the new host does (in effect) is:
Create a new account with the same username as the account on the old host
Search through the new host's database and re-associate any edits attributed to the dummy account to the newly created account
In doing so, the person that made the edits can create an account with the new host and have credit for their edits which were made on the old host given to their account on the new host.
From the manner in which you have described the situation, it sounds like the wiki had migrated a long while before you even started editing on the Fandom wiki. If that is the case, then you would have no edits that were copied to the new host and therefore no need to "migrate" your account. All you need to do is create a new account on the other host using the same name you use here on Fandom. After than, any edits you make with the new host will be associated with your account on their servers.
If I recall correctly, users should be able to see deleted threads on their own message wall.
Edit: Looks like I was wrong. You can only deleted them, you cannot view them. Seems odd Fandom would make something like that effectively permanent.
You cannot. The only thing you can do is leave a redirect at the old page.
The answer depends on how the stub template is implemented, what kind of background you want to add, and how much you want to be able to customize it. Please provide more information. If possible please provide a link to any testing you currently have.
To deter vandals from simply creating a bunch of accounts to evade blocks.
Interesting. You might still want to report this to Fandom since I don't see why the results header should cause this issue. So I would still consider it a bug.
I am still not seeing a reason why this shouldn't work. I recommend you report this to Fandom as a bug. I have pre-filled some of the fields with my suggested values but feel free to modify as you want.
I have never used this output mode before but it looks like what you have should work. Could you link to the page the screenshot is from so we can inspect the rest of the page? It is possible something else on the page is causing this.
Even so, one thing that stands out to me trying to look through what has been posted is that there are probably some #switch that don't need to be #switch. For instance:
{{#switch:{{{Type|}}}|#default=|variant=<div style="background: red; margin-bottom: 62px;"></div>}}
Unless the intent is to add additional backgrounds as new types are added, this could just be an #ifeq.
{{#ifeq:{{{Type|}}}|variant|<div style="background: red; margin-bottom: 62px;"></div>}}
Oot42, as you well know, it happens to all of us.🤣
Just to add a bit of clarification to Oot42's comment on #ifexist being an expensive parser function. The limit is 100 expensive parser functions per page including any transcluded by templates used on the page. It is not 100 of each expensive parser function.
There are already several other threads about this issue. I believe the largest thread is the following.
Pings are broken sorta | Fandom
As SnowedLightning mentions in the last reply, Fandom is already aware of the issue and is working on a fix. This is confirmed on Fandom's official support site per the following article.
Yes, unfortunately there is no placeholder feature for galleries. Fandom's older platform used to have one for individual images but that disappeared with the platform update back in 2020-2021.
As for your original question, you should be able to do this using the #tag parser function to call the gallery tag instead of calling the gallery tag directly. That said, using #ifexist like this (or even as in your original attempt) is likely to cause issues if people try to add to the gallery from visual edit mode.
{{#tag: gallery |
File:{{#ifexist:File:Yellow Horse.png|Yellow Horse.png|Placeholder Horses.png}}{{!}}Yellow
File:{{#ifexist:File:Blue Horse.png|Blue Horse.png|Placeholder Horses.png}}{{!}}Blue
File:{{#ifexist:File:Green Horse.png|Green Horse.png|Placeholder Horses.png}}{{!}}Green
}}
Edit: It appears I misunderstood the prior discussion about placeholder images. Even the retired feature isn't really what you are looking for.
The combination of numbers is something called an IP address. It is how the internet knows where to send information. Some wikis do not require users to register an account to contribute to the wiki. If a user makes and edit without creating an account, they are referred to as an anonymous user (or "anon" for short). However, the edits they make still need to be tracked. As such, the wiki uses their IP address instead of a username.
It depends on the local wiki rules about granting user permissions as well as whether or not there are any active admins or bureaucrats. Since you haven't said which wiki this is about, that is all anyone can really tell you.
You can find a reasonably understandable explanation on the following page.