NIWA Community Forums
NIWA Community => NIWA Discussion => Topic started by: HavocReaper48 on March 20, 2011, 03:33:19 PM
-
http://www.donkeykongwiki.com/Special:RecentChanges (http://www.donkeykongwiki.com/Special:RecentChanges)
Has this happened to anyone else? And can anyone assist the reverts?
-
Have you added the extension to where a user must answer a question before saving the edit?
-
Have you added the extension to where a user must answer a question before saving the edit?
Yes, but it doesn't stop human vandals.
-
Have you added the extension to where a user must answer a question before saving the edit?
Yes, but it doesn't stop human vandals.
Yeah, DKWiki has had spammer accounts before but this is the first major flesh & blood vandal wiki attack in DKWiki history since the April Fools Incident. And that was on Wikia.
-
For now, what would probably help you the most is to restrict editing temporarily to staff only.
Deriving from MediaWiki manual (http://www.mediawiki.org/wiki/Manual:User_rights), this would probably look as follows (added into LocalSettings.php), though I'm not especially familiar with administrative MediaWiki using, so you might want to check it yourself:
$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['user']['edit'] = false;
$wgGroupPermissions['sysop']['edit'] = true;
Also holy crap I haven't been here for ages. :F
-
More specifically, where do I add that coding?
Like, "MediaWiki:__"?
-
More specifically, where do I add that coding?
Like, "MediaWiki:__"?
If you don't have access to the site FTP (or physical access to the server), you can't do it. That method would involve editing a configuration file, not a database entry like a wiki page (or metapage).
-
If you have permission, you can also use Special:LockDB to shut down editing until your server admin can add that code. :)
-
Maybe there's a way to restrict making large changes, as all of those edits seem to be, to autoconfirmed users (users with 4-day-old accounts according to MediaWiki (http://www.mediawiki.org/wiki/Project:Autoconfirmed_users); according to porple (http://www.pikminwiki.com/User_talk:Porplemontage#reuploads), they need 10 edits too, though this might just be something he's configured)? That would block most of the edits, but I have no idea if it's possible... If you can't, a good start would at least be only allowing autoconfirmed users to create pages, maybe.
-
Same guy hit SmashWiki, as you may have seen; just revert, block and be sure to restrict account creation on the block form. Is there something more major that would need to be done?
-
Yeah, really the only way to stop a vandal is to restrict their access and/or just clean up after them.
Others will have more sufficient technical advice.
-
It seems that the issue has been taken care of.
-
Same guy hit SmashWiki, as you may have seen; just revert, block and be sure to restrict account creation on the block form. Is there something more major that would need to be done?
The vandal had a changing IP, so that was ineffective. Regardless, he is gone for now.
-
Same guy hit SmashWiki, as you may have seen; just revert, block and be sure to restrict account creation on the block form. Is there something more major that would need to be done?
The vandal had a changing IP, so that was ineffective. Regardless, he is gone for now.
good to hear he left..... my guess is he got bored.