Interfered with other modules' javascript

I'm getting exactly the same problem - I updated to 6.x-1.36 a couple of weeks ago and only noticed yesterday the problem editing invoices and the cart breaking. I disabled the Slideshow module altogether and those issues were fixed.

I was also having a problem with Wysiwyg, where the rich-text toolbar wouldn't display for any roles (see http://drupal.org/node/1200328) - now I've disabled Slideshow Creator it's come back.

In IE8 (before I disabled the module) I was getting this error on every page I went to (even though I only had slideshows appearing on two pages of the site):

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.1)
Timestamp: Tue, 5 Jul 2011 12:08:04 UTC

Message: 'ssc_settings' is undefined
Line: 12
Char: 3
Code: 0
URI: https://*****.com/sites/all/modules/slideshow_creator/slideshow_creator.js?m

If I put the latter URL in a browser it showed this:

/**
 * @author: Bruno Massa http://drupal.org/user/67164
 * @file slideshow_creator.js
 * The main Javacript for this module
 */
/*global Drupal, $ */

/**
 * Initialize the module's JS functions
 */
Drupal.behaviors.ssc = function(context) {
  for (var ss in ssc_settings) {
    if (ssc_settings.hasOwnProperty(ss)) {
      ssc_settings[ss].before = Drupal.ssc_before;
      $("#ssc-content-" + ss).cycle(ssc_settings[ss]);
    }
  }
};

Drupal.ssc_before = function() {
  var sscid = this.id.replace(/ssc-slide-/, "").replace(/-.*/, "");
  var slide = parseInt(this.id.replace(/ssc-slide-.*-/, ""), 10) + 1;
  $("#ssc-current-" + sscid).html(slide);
};

I will revert to the previous release for now but this is a serious bug!

Hmm, this is a big problem. The old way of doing it simply doesn't work for some sites. Drupal doesn't transmit the Drupal.settings correctly after the slideshow is loaded for the first time. Therefore I replaced it with localised javascript to put the same data into the page along with the html, which is cached correctly.

Actually I consider the fact that Drupal.settings isn't cached a bug in Drupal core, but we can't count on getting that fixed any time soon.

From your writeup I gather that you have a lot of other modules installed, and therefore the problem is some kind of interaction amongst them all. I don't really have much hope of tracking it down without help. Can you set up a simple test site with just wysiwyg and see if it messes that up without all the rest of it loaded? Or put in whatever bare minimum you have to to trigger the bug?

I have pushed a fix to the git repository for both D6 and D7, as the bug existed in both. You might like to check it out before I release yet another version. For simplicity, I attach patches for both D6 and D7. If they work for you, I'll release new versions.

The problem I found does fit your description, so I'll assume I have found the cause of your problem. It's probably best if I release a new version immediately, as we don't want that error propagating too much.

I don't know what you mean by "doesn't update automatically". There are no DB updates done by this module. I presume you have cleared all caches?

Set issue title to something meaningful.