{{editprotected}}
The reason for G6 should say "controversial," not "controvertial." Logan Talk Contributions 07:41, 3 February 2011 (UTC)[reply]
Fixed — Martin (MSGJ · talk) 13:07, 3 February 2011 (UTC)[reply]So, the reason the script wasn't working is because hookEvent is not only deprecated, but now completely non-functional (see wikibits.js line 98). The suggested workaround is to use jQuery's $(document).ready(), but when Mr. Stradivarius tried it, it killed just about all of the other JavaScript-dependent gadgets one uses, including HotCat and Twinkle.
I was able to duplicate that problem, and it's because the CSD Helper script imports its dependent library waLib.js too late, using the importScript function from wikibits.js. The library doesn't finish loading before jQuery's document ready event is triggered, because jQuery isn't aware that wikibits.js is still loading stuff in the background. jQuery starts to run csdhelper.js, but the waLib library isn't loaded, so it gives a ReferenceError about one of the library functions not being defined, and stops. Anything else using jQuery dies at the same time (or never starts). hookEvent didn't suffer from this problem, but it's no longer an option.
However, a good rule of thumb is that a problem caused by jQuery can be fixed by jQuery, in this case, the $.getScript() function. I tested it using a copy of the script in my userspace and it all seems fine, so I've edited the live copy of the script with the fix, and everything should be fine (although of course you may need to WP:BYPASS before it works). —Darkwind (talk) 21:45, 16 November 2013 (UTC)[reply]
 | This edit request has been answered. Set the |answered=or|ans= parameter to no to reactivate your request. |
The script currently has a [[WP:ADS|advertising]] string that generates a deletion reason pointing to the disambiguation WP:ADS. It should probably point to WP:NOTADVERTISING instead, which is the actual policy. Thanks! Jo-Jo Eumerus (talk, contributions) 10:44, 28 September 2015 (UTC)[reply]
Done I used WP:PROMO instead of WP:NOTADVERTISING to save a little space in the edit summary. — Mr. Stradivarius ♪ talk ♪ 10:49, 28 September 2015 (UTC)[reply] | This edit request has been answered. Set the |answered=or|ans= parameter to no to reactivate your request. |
Could someone please fix the typo for "identical" on the F8 decline reason? Thanks! ToThAc (talk) 18:53, 4 December 2017 (UTC)[reply]
Done. Regards SoWhy 19:07, 4 December 2017 (UTC)[reply]
New proposal
Dear @Ale jrb: Thank you for having written CSDH! Here's a feature request.
When declining any nomination other than a G4 / G5 / G10 / G11 / G12 / A7 / A9 nomination:
{{oldcsd|G1|decline reason|Decliner}}On the other hand, for G4 / G5 / G10 / G11 / G12 / A7 / A9 declines, I think it'd be best not to use {{declinedsd}} or {{oldcsd}} at all. If you do use the templates, then harmful paid editors might later look and find out the decline reasons. They could gradually learn how to make their future paid articles more deletion-resistant.
Your thoughts would be welcome.
Kind regards, —Unforgettableid (talk) 06:55, 23 January 2020 (UTC)[reply]
New proposal
User:Ale jrb/Scripts/csdhelper.js sometimes uses a template to notify a nominator that their nomination was declined. The template is called User:Ale jrb/Scripts/CSDHelper. I wonder if you could please move the template to template space, so that CSDHelper users will feel more free to make changes to it?
Maybe you could call your template {{uw-csd-alt}}. This is because your template is somewhat similar to {{uw-csd}}.
Here's some template documentation that you could put on the documentation page: "This template is used by the CSDHelper user script. The script uses this template when notifying a speedy deletion nominator that their nomination was contested or declined."
Kind regards, —Unforgettableid (talk) 06:55, 23 January 2020 (UTC)[reply]
Amorymeltzer looks like you forgot to remove it from the delete reasons. --Trialpears (talk) 13:28, 14 July 2020 (UTC)[reply]
Done thanks! ~ Amory (u • t • c) 15:02, 14 July 2020 (UTC)[reply]
