Now, I personally think you should also put the import itself (the importArticles version of it) into MediaWiki:Common.js and not use MediaWiki:ImportJS at all for this script. I just now wrote about it in the script's talk page.
@Marisa1980 obviously you meant MediaWiki:Common.js not MediaWiki:Common.css at the last sentence.
After removing it, what exactly do you want to use it for? The proper configuration depends on that.
Okay, the first step you should do is to delete it from your MediaWiki:ImportJS .
This script is originally meant for using it as a personal script, and while there's a way to use it globally with some configuration, it's a bad idea to put it to work globally before you have the proper configuration being set up.
You would need to explain a bit more about what you tried in order for us to be able to spot what you missed.
Yes it's normal, and on Fandom it's supposed to happen at least once in six months due to token expiration. Sometimes it can happen in a shorter period.
It does work when I try it, what exactly are you expecting it to do and it doesn't? A link to an example would be helpful.
Also, what does :not(.fandommobile-fandom-theme) exclude?
I would say that according to my experience, sometimes wikis are closed for inactivity and low content but in other cases such wikis continue to exist for years with no one bothering them. Seems like Fandom aren't putting much of effort into hunting dead wikis.
The corners are already somewhat rounded (3px), you can increase it by putting the following code in MediaWiki:Common.css :
.page__main {
border-top-left-radius: 10px;
border-top-right-radius: 10px;
}
html:not(.ve-active) .page.has-right-rail .page__main {
border-top-left-radius: 10px;
}
.page__right-rail {
border-top-right-radius: 10px;
}
You can adjust the amount of rounding by changing 10px to a different number. Make sure to change it in all occourances.
The code specifically matches how Fandom themselves currently implement the rounding, it might break if Fandom change things on their end (which they do from time to time). I'm afraid there's no good way to avoid that problem.
Can you make a screenshot and mark the exact place you want to be curved?
Yeah right. Hmm I wasn't able to find a solution but for the sake of attempting something I suggest you try to purge + null edit all the pages that link to these. Then wait for the cache of the "wanted pages" itself to be updated (last updated at March 16 as appears at the top of it).
Weird, I only see two of the three.
Can you share a link to the wiki so that we can look at it?
Since you'll need to save that link anyway, you can also save the link of the wiki you want to go into.
Not at all. It might happen if they're, for example, using the same school network or the same public wifi. It might also happen if they use the same internet provider and live in the same area - and the longer the time the more likely it is to happen.
Or you can use DISPLAYTITLE to change it to something better such as {{DISPLAYTITLE:Harry Potter Wiki}}
Simply, enabling an autoblock doesn't mean there was a sockpuppetry - the blocked user might not try to sockpuppet or ban evade.
In addition, even in case the autoblock is actually triggered and blocking someone, it might just be someone unrelated who happened to use the same IP.
All of that is explained in the replies above.
Not necceassrily, it's a measure to help prevent sockpuppeting in case it happens.
Because it also depends on the code on MediaWiki:Common.css
.pnhov {
filter: grayscale(1);
transform: scale(0.9);
transition: all .5s;
display: inline-block;
}
.pnhov:hover {
filter: grayscale(0.0);
transform: scale(1);
transition: all .5s;
}
There are no hard rules as far as I'm aware, it's about whether the wiki has a value (or it's making progress) or not.
But why would you create a wiki with only one huge page? It's not how a wiki is supposed to be structured.