Revision as of 21:24, 29 September 2008 editAnimum (talk | contribs)30,489 editsm →User:Animum/easyblock.js: reply, thanks← Previous edit | Revision as of 02:26, 30 September 2008 edit undoClueBot III (talk | contribs)Bots1,373,896 editsm Archiving 1 discussion to User talk:Animum/Archives/2008/September. (BOT)Next edit → | ||
Line 32: | Line 32: | ||
Hey. I'm very sorry, but I have a problem again. :( There is a new blocking option “''cannot edit own talk page''”. When blocking an user/an IP with your script this seems to be enabled per default. Thus I received from ] at my talk page. He advised me to have a look at ] at the ]. There it says that this new blocking option should just enabled in rare cases (i.e. continued disruptive editing during a block). So, is there any possibility to disable this new blocking option per default? That would be great. :) Thank you, —] ''•'']''•'' 13:24, 29 September 2008 (UTC) | Hey. I'm very sorry, but I have a problem again. :( There is a new blocking option “''cannot edit own talk page''”. When blocking an user/an IP with your script this seems to be enabled per default. Thus I received from ] at my talk page. He advised me to have a look at ] at the ]. There it says that this new blocking option should just enabled in rare cases (i.e. continued disruptive editing during a block). So, is there any possibility to disable this new blocking option per default? That would be great. :) Thank you, —] ''•'']''•'' 13:24, 29 September 2008 (UTC) | ||
:Ah, yes. If a parameter is not specified in the data the script sends to the servers, index.php evidently interprets it as saying "no" to the option the parameter can enable; thus, if I do not specify a value for the "wpAllowUsertalk" parameter (which determines whether the blocked user can edit his own talk page), the servers will interpret it as saying "&wpAllowUsertalk=0", which would disable editing of a user's talk page. Technical jargon aside, thanks for telling me this, and it has been {{tick|18}} '''fixed'''. —] <small>(])</small> 21:24, 29 September 2008 (UTC) | :Ah, yes. If a parameter is not specified in the data the script sends to the servers, index.php evidently interprets it as saying "no" to the option the parameter can enable; thus, if I do not specify a value for the "wpAllowUsertalk" parameter (which determines whether the blocked user can edit his own talk page), the servers will interpret it as saying "&wpAllowUsertalk=0", which would disable editing of a user's talk page. Technical jargon aside, thanks for telling me this, and it has been {{tick|18}} '''fixed'''. —] <small>(])</small> 21:24, 29 September 2008 (UTC) | ||
== Image:Magnus_logo.png listed for deletion == | |||
An image or media file that you uploaded or altered, ], has been listed at ]. Please see the ] to see why this is (you may have to search for the title of the image to find its entry), if you are interested in it not being deleted. {{#if:|{{{2}}}|Thank you.}} ] ] 01:59, 27 September 2008 (UTC) <!-- Template:Idw --> | |||
==My RfA== | ==My RfA== |
Revision as of 02:26, 30 September 2008
This talk page is automatically archived by ClueBot III. Threads with no replies in 3 days may be automatically moved. |
|
2007 2008 2009 2010 |
User:Animum/easyblock.js
Hey Animum. :) Whenever I block an IP/user with your script the user(talk)page is added to my watchlist. Is there any possibility to disable that? Best wishes, —αἰτίας •discussion• 23:00, 26 September 2008 (UTC)
- Y Done —Animum (talk) 01:40, 28 September 2008 (UTC)
- Thank you. :) —αἰτίας •discussion• 18:13, 28 September 2008 (UTC)
Hey. I'm very sorry, but I have a problem again. :( There is a new blocking option “cannot edit own talk page”. When blocking an user/an IP with your script this seems to be enabled per default. Thus I received this message from User:zzuuzz at my talk page. He advised me to have a look at this thread at the Misplaced Pages:Administrators' noticeboard. There it says that this new blocking option should just enabled in rare cases (i.e. continued disruptive editing during a block). So, is there any possibility to disable this new blocking option per default? That would be great. :) Thank you, —αἰτίας •discussion• 13:24, 29 September 2008 (UTC)
- Ah, yes. If a parameter is not specified in the data the script sends to the servers, index.php evidently interprets it as saying "no" to the option the parameter can enable; thus, if I do not specify a value for the "wpAllowUsertalk" parameter (which determines whether the blocked user can edit his own talk page), the servers will interpret it as saying "&wpAllowUsertalk=0", which would disable editing of a user's talk page. Technical jargon aside, thanks for telling me this, and it has been Y fixed. —Animum (talk) 21:24, 29 September 2008 (UTC)
My RfA
Thank you for supporting me in my RfA, which passed with a count of (154/3/2). I appreciate the community's trust in me, and I will do my best to be sure it won't regret handing me the mop. I am honored by your trust and your support. Again, thank you. –Juliancolton 18:37, 27 September 2008 (UTC) |