More specifically to what the anon said above, you can request for JavaScript to be enabled by contacting Fandom on your wiki here.
Maurice.136 wrote: Hey,
Community Central is typically here to help you with Fandom related things, you can contact FaceBook for those types of problems.
He's talking about his Fandom account - you can integrate it with Facebook.
Fanman, have you tried looking in your preferences for the Facebook Connect option?
I think big obtrusive popup ads which block a lot of content aren't allowed - report it at Special:Contact/bad-ad.
Ideally you should have a community consensus already such as via forum or blog post with overall view of implementing abuse filter, then go to Special:Contact/general on your wiki.
However to just accomplish the task you describe, it may not be enabled for that reason - abuse filter is usually enabled on wikis with lots of daily edits, even more so on wikis with a history of vandalism.
Godonan wrote: Okay, so the user retracted his accusations and decided it was a mistake. Howevor, I would still like this answered:
Can category creation be restricted?
Yes, with the use of abuse filter extension.
Some wikis such as the MLP Wiki don't have any fancy rules to accustom resizing - simply having a large enough background can accomplish what you seek. Theirs uses 3030x1080 dimensions.
VSTF have the ability to make themselves local administrators on a wiki they are cleaning up on, and I've seen them do that to do things they can't do as just VSTF.
So I'd say the article is correct indirectly.
Rith4life wrote: Anyways, this thread wasn't to discuss about discussions mod abilities, it is about WHAM. As soon as discussion mods have the ability to use this, Ozank, can you please inform me? Thank you.
I have a busy schedule of life but it's usually in 1-3 working days when it's done, so I'd say around Tuesday. I don't have the time to check review approvals.
Looking at Special:ListGroupRights it seems they can delete article comments, among other things, which WHAM would be useful for:
Discussions Moderators |
|
HTML5 and CSS3 have some function-esque properties but not to the extent you desire. It's not really possible to do without some JS/Lua.
By coincidence I'm the author of that version of the script. Originally I added content moderator, but I guess discussions moderator slipped my mind.
RedstoneDemigod: Good to hear that was the fix, that's what this forum is for!
Rith4life: I can see why you aren't having it load - you're not in the rollback, content moderator or admin usergroups. I have added discussions moderator though it won't work for you until Wikia review my JS edit and accept it.
Speedit wrote: I'm not seeing the two new adverts so they are probably an A/B test.
Irrespective of the ads, do please ensure that you don't block ads en-masse across the internet - because most sites run honest and good ads. Try to use a blacklist-based adblocking extension with only custom filters if you want one, to ensure that you are actually blocking ads in good faith and know what ads you're blocking. I don't use an adblocker, because most adblocker devs are just out for bribes from ad agencies.
Most people jump the gun, block all ads and force sites into the red.
I wouldn't mind most ads but the fact that rogue ads have the capability to redirect you obnoxiously to a rogue server (which is becoming more common in recent times) which could result in being affected by an exploit kit to infect your machine, coupled with the overly stupid screen covering ads disrupting your browsing experience makes me stick with NoScript.
Earlier today I decided to test one of my scripts on Chrome and I got redirected without doing anything by some rogue ad to a spammy survey site... the sad part is I never saw the ad in the first place and if I did it would immediately redirect me. This never happens to me on Firefox because I have NoScript installed on it, stopping the ad payloads arriving on my computer.
I wish there was some kind of sandbox Fandom and other big sites used that stopped ads using methods like location.replace('URL');
Dessamator wrote:
In any case, that script should be disabled until this is fixed, and should probably be reported through Special:contact/security, or maybe ask VSTF to delete (since there is no disable mechanism) the script for now.
True, but it was a dangerous gamble because someone could have set that variable through another unrelated script making it harder to detect:
var name = "wikianotifs" var a = "<scr" ... a += "ipt>..." console.log(window[name] = a )
Or even simpler, set up a script that retrieves variables from a mediawiki page, much like the ProfileTags script.
Not to mention the fact that constant reviews for minor changes such as simple text is what this thread is all about. They are quite simply unnecessary. Converting, disallowing or escaping are better alternatives.
I felt the need to join in with this conversation and say that I was making a widget on a wiki site-wide that uses an iframe and unintentionally didn't escape some of the user input which could have led to easy XSS exploitation... it's fixed now and the safe revision is live but point being Wikia are not 100% perfect with code reviews as at the time the vulnerable code was approved. I don't think Fandom regard me as a suspicious user so they probably leaned towards approving the code rather than checking it properly in the first place.
It depends on his method of changing IP. If it is simply his router assigning a different IP address in the same range, then you should opt to range ban him. If it's due to proxy/VPN, there is little you can do about those.
Quote:
Pinkgirl234 Message Wall 07:16, October 10, 2016 (UTC)
I am also putting speedydelete template to delete pointless articles I made.
As outlined in a different thread, other editors have made contributions to the articles you made. You aren't the only author to those articles now, and you do not have ownership of them.
Blindly nominating them for deletion will most likely be seen as vandalism, and I agree your block is justified.