User talk:Ais523/catwatch.js

Script not working

This script looks like it would really useful, particularly in keeping track of new additions to one of the WikiProjects I'm on. But -- I can't seem to get it to work. I've tried both importing the script, & just copying & pasting the whole thing into my monobook.js file. I don't know any javascript, but I am pretty good at following the basic directions. I'm wondering if the problem might have to do with page WatchedCategories.js created by the script. When opened for editing, I get this: "Warning: There is no skin "WatchedCategories". Remember that custom .css and .js pages use a lowercase title, e.g. User:Foo/monobook.css as opposed to User:Foo/Monobook.css." Does that mean my page should be named "User:Yksin/watchedcategories.js" rather than "User:Yksin/WatchedCategories.js"? But if so, the script should create the page with that name, shouldn't it? Please advise; I'd really like to use this script. Thanks. --Yksin 21:29, 5 April 2007 (UTC)

(copied from my talk page):

I have no error messages. I get the standard stuff on my watchlist -- changes to actual pages. But, I understood that this script was intended to show when a new item was added to a particular category. So, for example, if I add Category:Alaska Natives to a particular article, the name of the article shows up on in that category and also, thanks to the script, in my watchlist as an addition to that article. But that's not happening. Perhaps I'm misunderstanding what the script is intended to do? --Yksin 18:45, 9 April 2007 (UTC)

Having finally got my hands on a copy of Firefox, it seems that the script didn't work in Firefox. I've fixed it now. --ais523 13:16, 1 May 2007 (UTC)

About the time you fixed the code that was generating that incompatability error message with java-enhanced watchlist, this script stopped working for me. Not sure if it's related.--Fuhghettaboutit (talk) 22:49, 3 April 2008 (UTC)

How to get started

How do I actually get started with the script? What do I type, and where? Do I have to specify a category to watch or how is it decided which categories are watched? Thanks, Tiddly-Tom 06:02, 3 September 2007 (UTC)

Once you install the script and clear your cache, the first time you visit your watchlist you get an alert asking if you want to set up a category to watch. Click ok, and you will be taken to this page, which will be preloaded with instructions on how to add categories to your watchlist. --Waldir ^talk 13:03, 19 April 2008 (UTC)

instructions; where's it show?

Great idea! A suggestion and a question:

It'd be good to mention in the instructions that the category names have to be in quotes (the examples that initially appear are quoted, which is how I figured out that that's what to do, but it was a bit of a guess).

It doesn't look to me like the script is working for me. I keep getting the 'you don't have a category watchlist message. I tried adding my sandbox to a would-be-watched category, but see no change in my watchlist.... but is that where I would look? I don't know where the watchlist is supposed to show up. — eitch 00:42, 3 June 2008 (UTC)

The script was broken for a while. Try bypassing your cache to see if it works then (yes, the categories appear on your watchlist). (If you use Internet Explorer, you may have to delete your temporary internet files instead; cache bypasses don't always work for this script on IE for some reason.) --ais523 11:47, 3 June 2008 (UTC)

no script

Bad script. — Preceding unsigned comment added by 86.121.112.197 (talk) 15:40, 12 February 2014 (UTC)

Scripts don't work for IPs. ₆an⁶sh₆ 18:31, 12 February 2014 (UTC)

It didn't work for me either. benzband (talk) 20:07, 12 February 2014 (UTC)

Or that. ₆an⁶sh₆ 04:11, 17 February 2014 (UTC)

Bug report and question

Great script — I wish I'd known months ago that this existed. One issue, and one question:

• After installing and visiting my watchlist, I created the WatchedCategories page as instructed. The next time I went back to my watchlist, it again asked me if I wanted to create a WatchedCategories page. So, I'm reporting the bug code as directed — responseText='/*Empty */', statusText='OK'

• The question is regarding the time stamp it uses when including the entry in the watchlist. All the other entries in my watchlist are using the local time I've set in my preferences, but these entries are using server time, which puts them out of order. Not a big deal, but just wondering if there's any way to adjust that?

Thanks for making this available — nice work! Mlaffs (talk) 21:37, 31 December 2008 (UTC)

If the first bug went away after bypassing your cache, don't worry, that's more-or-less expected. As for the second request, I think it's possible but it isn't trivial. The script would have to fetch the preferences somehow and do the maths itself, which would slow it down somewhat unless it was hardcoded in the watchlist, which would probably lead to even weirder caching problems than the ones I had to sort out earlier... --ais523 14:39, 1 January 2009 (UTC)

Good enough — I mostly wanted to make sure that I hadn't missed something in the setup instructions that was causing it to act this way. I'd added your watchlist notifier script too, so seeing the new entries in bold should make the fact that these category ones are out of order a non-issue. And one last time, thanks for building this sucker in the first place — I've been wishing for a long time now that something exactly like this existed. Apparently, I just hadn't looked hard enough or asked in the right places! Mlaffs (talk) 15:46, 1 January 2009 (UTC)

Legacy JavaScript

Hello! This script has been detected as using deprecated parameters that need to be replaced with the updated version. Examples include addOnloadHook( ... ) needs to be replaced with $( function() { ... } ); all wgGlobalVariables need to be properly gotten with mw.config.get( 'wgGlobalVariable' ); and addPortletLink needs to be called with mw.util.addPortletLink. Please see MW:ResourceLoader/Legacy JavaScript for details. Thank you. — {{U|Technical 13}} (e • t • c) 20:28, 19 January 2015 (UTC)

Request rate exceeded?

Hi,

A week or two ago I started getting "Request rate exceeded" (or "Request limit exceeded" -- I can't remember the wording) when I load my watchlist. Happened on Firefox and Chrome on two computers running Win7 and Win8. After some trial and error with my scripts I think I found that catwatch was the culprit. Don't know what else to say about that, but thought you should know :) — Rhododendrites ^talk \\ 19:11, 20 November 2015 (UTC)

Thanks Rhododendrites, you beat me to reporting this. I'm seeing the exact same issue, on Firefox running Win10. I had to comment out this script for my watchlist to return to normal. Stevie is the man! ^{Talk • Work} 19:34, 20 November 2015 (UTC)