User talk:AzaToth/Archives/2009/October

Twinkle blacklist
There appears to be a problem with the twinkle blacklist. Despite the fact that the user was added to the blacklist as seen here, he is still able to use twinkle, as seen here.—  Dæ dαlus Contribs  22:22, 30 September 2009 (UTC)
 * There's no problem. Because of client side JavaScript caching, it can take time for all users to receive the new blacklist settings.  If his ability to use Twinkle does not change by tomorrow, let me know. Ioeth (talk contribs twinkle friendly) 22:48, 30 September 2009 (UTC)
 * Alright, thanks for the help.—  Dæ dαlus Contribs  23:26, 30 September 2009 (UTC)

Reply
I just checked first two articles, and they both lacked citations regarding the latest prize. Please see In_the_news: "The decision as to when an item is updated 'enough' is subjective, but a five sentence update (with at minimum three references, not counting duplicates) has generally been considered more than sufficient, while a one sentence update is considered extremely questionable." --BorgQueen (talk) 10:50, 6 October 2009 (UTC)

Nomination for deletion of Template:TestTemplatesList
Template:TestTemplatesList has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. RL0919 (talk) 16:47, 16 October 2009 (UTC)

Twinkle
Hi Aza, I notice that the WP:Twinkle and Twinkle/doc pages advise inserting "ImportScript" statements which are directed to pages in your userspace for manual or partial installation of Twinkle. I note that those pages are not protected. Is that wise? an awful lot of users could be affected.  Sp in ni ng  Spark  11:46, 17 October 2009 (UTC)
 * Which page, for instance? User:AzaToth/morebits.js? I only see pages ending in ".js" or ".css", which are automatically protected so that only admins or the user who's subpages they are can change them. Amalthea  11:53, 17 October 2009 (UTC)
 * Ah, my mistake, I did not realise (or had forgotten) that script pages were automatically protected.  Sp in ni ng  Spark  13:15, 17 October 2009 (UTC)

Twinkle
Hey, AzaToth! I found a spelling error when I was reviewing the script that requests page protection. Look at the line that says the following:

self.statelem.warn( [ htmlNode( 'strong', tag[0] ), " is alread placed on the page." ] )

Alread is a spelling mistake. It should be changed to already. Please tell me on my user talk page once you fix this error. BTW, I love twinkle! Thank you so much for creating it!  Btilm  18:23, 24 October 2009 (UTC)
 * ✅, thanks. Amalthea  23:51, 26 October 2009 (UTC)