Since update to the version 1.4 Ajax does not work any more

I changed line 292 in rate.module from:

drupal_add_js(drupal_get_path('module', 'rate') . '/rate.js', array('scope' => 'footer'));

to

drupal_add_js(drupal_get_path('module', 'rate') . '/rate.js', array('scope' => 'footer', 'group' => JS_DEFAULT,  'weight' => 200));

Just for testing, but did not help. The I commented the line out and added the line

scripts[] = rate.js

to rate.info.
Now it works again. I know that this is not a good solution, because now the JS is loaded every time on every page. But I am a bit helpless at that point not having any idea what could be the cause of that strange issue.

With the above described workaround Ajax does not work if content was loaded via Ajax it self.

I actually fond out that skipping the 'scope' brings drupal_add_js() back to work. I don't have an idea why. So for rate widget I changed line 292 in rate.module in:

drupal_add_js(drupal_get_path('module', 'rate') . '/rate.js', array('group' => JS_DEFAULT));

It looks to me like a Drupal bug. The problem is, that AJAX loaded widgets keep refuse working. I get the error:

TypeError: Drupal.settings.rate.basePath.match is not a function
Source: .../rate/rate.js?md0yni
line: 31 

The cause of that error seems to be that the code form line 286-291 is not being executed or perhaps not at the right moment?

  drupal_add_js(array(
    'rate' => array(
      'basePath' => url('rate/vote/js'),
      'destination' => $dest['destination'],
    )
  ), array('type' => 'setting'));

Does anybody know where o what could cause that strange behavior?

Thanks XmhO, it works. But apart from the fact, that your solution is much more elegant then mine, both do the same: Deleting or changing the scope. Bu why have we to do so? And why does it not work with AJAX loaded content? XmhO, do you have a widget witch is loaded with AJAX? Just to tray whether or not you experience the same problem? Thank you so far!

Thank you mauritsl. Reverting this two lines solves the first issue: The rate.js is loaded with the right weight again. But I still get an JavaScript error when I click on a rate widget which was loaded via AJAX because of the fact that Drupal.setting.rate.basePath seems not to be set.
Maybe that is a different issue? Could that have something to do with the function drupal_get_destination()? Maybe it does not return a result when the script is called via AJAX?
Thank you very much for your help!

I hunted it down. The problem is, that for some reason the JavaScript variable set in line 286 in rate.module "Drupal.settings.rate.basePath" and "Drupal.settings.rate.destination":

  drupal_add_js(array(
    'rate' => array(
      'basePath' => url('rate/vote/js'),
      'destination' => $dest['destination'],
    )
  ), array('type' => 'setting'));

becomes an Array instead of a string when the content containing the widget is loaded via Ajax. The cause of that problem may be an bug in drupal_add_js() core function because of the fact that documentation says if a setting value is set more than once it will be overwritten. How ever, in this case it is not, but becomes an array which looks like:

0 => "rate/vote/js",
1 => "rate/vote/js",
2 => "rate/vote/js",

I added, just for testing, these to lines to line before line 31 in rate.js:

Drupal.settings.rate.basePath = Drupal.settings.rate.basePath instanceof Array ? Drupal.settings.rate.basePath[0] : Drupal.settings.rate.basePath;
Drupal.settings.rate.destination = Drupal.settings.rate.destination instanceof Array ? Drupal.settings.rate.destination[0] : Drupal.settings.rate.destination;

Now it works again. I know it is a dirty workaround but I could not find the real cause of the problem. Would be glad to know whether or not someone can reproduce the described problem.

But the problem occurs only with content loaded via AJAX, I can't imagine the real cause but I did not had that issue with the former versions of Rate Widget. One could set a View's load more behavior to AJAX for testing.