Extension talk:KeepYourHandsToYourself

Hello. This looks like a pretty great extension, it's just what I need. But, if I have set$wgNamespaceAliases and changed the namespace name of "NS_USER", would it at all mess up the extension? Smaug 23:44, 30 January 2008 (UTC)
 * SOLVED. Question answered. Smaug 20:34, 26 February 2008 (UTC)

Non-existing user pages lead to action=edit...
Sorry but this needs to be fixed. Most of my users have an empty user page and all those user links lead to the edit page... COuldn't it be done that all user linsk lead to User:Foo ? --Subfader 13:22, 11 May 2008 (UTC)

How to disable autorenaming uploaded Images to User--dataname.ext
I like the facility of having Images only editable by the user who uploaded them, but I don't need it as a standard action, since most of the uploaded images are public domain. Any way to disable autorenaming? --Gara


 * You could just comment out the hook:  —Emufarmers(T 19:41, 14 June 2009 (UTC)

Need help
i not very understand how this extension work. After i apply this extension, nothings happen, others user still can edit the page that i created. Should i add anything in the page that i create? and anything should i change in KeepYourHandsToYourself.php? --ckc2009 15 September 2009

Works mostly
This extension works with 1.17.0 to prevent other users from editing another user's user page. But as for protecting an image, am not clear what "under certain circumstances" means. If I want this to work, I have to add the user name followed by two dashes. This isn't automatic. Is there a way to modify the code to automatically add the user name and two dashes?

Extension fails in 1.18.0+ due to removal of the $wgMessageCache Global Object
Per the man page for $wgMessageCache: Extensions which rely on being able to add messages to this cache directly with $wgMessageCache->addMessage are now broken. See the MessagesPreLoad hook for a possible alternative to this. As I am not familiar enough with PHP to reimplement the call to $wgMessageCache using the MessagePreLoad hook in the setupForKeepYourHandstoYourself function, I am unable to fix this myself to bring it up to speed.

However, if you otherwise control usernames and can ensure they will not have double dashes (--) in them, commenting out the contents of the setupForKeepYourHandsToYourself function bypasses the call to $wgMessageCache and appears to allow the extension to function normally in the meantime.