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.

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

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!

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.

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'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).

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.

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.

@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.

Did anybody find a recommend solution to fix this. I'm using the acquia slate theme. I could not find a
drupal_rebuild_theme_registry call in my template.php.
Also the "Rebuild theme registry for every page" is unchecked, but the issue's still appearing.
I tried to debug the problem, an it seems, that in:

function ajaxToggleWatchFade(el, url) {

  // Fade out the element

  $(el).fadeTo(400, 0.01, function(){

  	ajaxToggleWatch(el, url)

  });

}

the

ajaxToggleWatch(el, url)

is not executed.
Thanx for your suggestions.
lg
dennis605

Don't forget to disable query logging if you are using the devel module. The ajax response fails when query logging is enabled as the JSON response gets appended with the devel queries.