Clicking watch link induces fade effect, but message and icon remain the same

Confirmed. This one is fixed in the next 6.x release which should be available in a day or two.

Great! Thanks for your quick reply.

Try alpha2 and let me know how it works for you.

The problem still persists in Alpha3. All caching is off, while it's a test-site.

Please download alpha4 and see if it's still there. Remember to uninstall the module as well as overwrite the old files as the database needs to be cleaned up. Thanks for your help!

Did a complete uninstall/reinstall of the module and Drupal 6.9. The problem's still there. Maybe it's a browser compatibility issue? I'm on Vista/FF3. I'll test some more on other OS/browser combo's.

Just to confirm, did you disable the module and then went to this page to uninstall the module?
admin/build/modules/uninstall

If you just disabled it, removed the files, replaced them with the new ones and re-enabled Watcher it will still use the old database schema which is the cause of the bug you reported earlier.

Running Mac OS X, everything works fine in Firefox and Safari with the latest database schema.

I did indeed uninstall and reinstall the module in the way you mentioned. Maybe it's conflicting with another module. I tested on OS X Firefox and OS X Safari, but it has the same problem. I need my testsite for a lot of other testing stuff, so I don't have time right now to try it on a clean site. Maybe this weekend.

Are any other Watcher users experiencing the same problem?

Just letting you know I take this issue seriously and want to fix it. Reason I was asking for an explicit uninstall is that the error you describe can be caused by missing fields in one of the tables.

On my local development site I uninstalled the latest version of Watcher, then reinstalled it and then, being logged in as a non-administrator user tested clicking the "You are not watching this post, click to start watching" link. I have so far been unable to recreate the problem you are describing.

What are the user permissions? I'm wondering whether there's a bug related to checking user permissions and whether the "watch" link may be visible to users who aren't actually permitted "use watcher".

I'm testing as an admin. But I'll test as a other roles (with correct permissions) as well.

But It doesn't look like a premissions issue to me. As I said in the first post, the click on the link is registered in the system, beacause the change is indeed visible when I reload the page.

Thanks for your quick replies solipsist. Maybe it is just a clash between modules. I think it's best to wait till I got time to create a clean testsite this weekend, or to get feedback from other users.

I've seen this happen on some sites, it can be caused by a misconfigured web server that doesn't return a 200 OK but an error code in response to the AJAX request when you click the link. If you have Firebug installed in Firefox, open the Net tab (enable it if necessary) and click the watch link. Let me know what Firebug tells you. Alternately, send me the URL of your site (you can use my contact form).

This is the Firebug output when clicking the link:
http://beta.xxxxxxxxx.org/user/1/watcher/toggle/12949?destination=node%2... - 200 OK

In that case I can only assume the request times out. There's a 4 second window, ample time, but if you're on a high latency connection it won't help you. You can try increasing it to more, say 10000 ms (10 s) in watcher.js and see if it helps.

Thinking of it, how long does FB report the request taking? Look at the far right end of the Net tab.

It takes between 500 and 570ms.

Alright. Try installing Watcher on a site that has no other modules installed. I suspect another module is messing with Watcher or there's a web server misconfiguration.

Ok, I installed Watcher on two other sites and this particular error isn't there. Let's close this till further notice.

@solipsist and whom ever else experiences this, for me the problem wasn't with Watcher or any other module conflicting with the AJAX operations. It was the theme. I work with zen, when I tested it with Garland, bong it worked! Now I have to find out what class or element is missing in zen.

--edit: its the drupal_rebuild_theme_registry if you're forcing a rebuild the front-end portion of this ajax or ahah call won't work. Check your template.php or if using the zen theme check the themes > configure > Theme development settings.