Unfortunately we had a few problems with our jQuery SDK these past two days. We are very sorry about that and have no good explanation other than human failure (my failure). Fortunately, only a small subset of customers were affected (jQuery SDK 2.6.1 in combination with use of our /file/filter robot), but still, this is not on par with the quality you've come to expect from us.

The jQuery SDK dates from before CasperJS, Travis CI, and the likes, and was in fact the first piece of software that was written for Transloadit nearly 6 years ago. It was launched without a good set of tests. Unfortunately, we failed to change that over the years as tools got better. The last few days made it painfully clear that not only our API, website, and our many other SDKs need vigorous testing, but of course also our jQuery SDK.

Not having them leaves us in a damp place of manual testing, which is prone to error and where nasty bugs like to hide the most, and slipped through the cracks this time.

Going forward we will correct this and turn weakness into strength by introducing tests to the jQuery SDK on system, implementation, and integration level using aforementioned tools. We're confident this upgrade will drastically minimize the chances of bugs like these reaching production again.

Again, we are very sorry that this has happened.

If you are running on a custom version or fork of the jQuery SDK, we kindly ask you to apply this patch manually to your setup. In the future there will be an update to the API that will break the jQuery SDK for you if you do not have this patch. This is because we currently have the logic of which result was already sent to the jQuery SDK and for which to call the onResult() callback for within the API. Of course, the API should not worry about this, as it is client-side logic. Thus, we would like to free the API from this functionality and move it into the jQuery SDK, which the above patch does with only 10% of the code used.

As always, we recommend that you use the latest jQuery version by using http://assets.transloadit.com/js/jquery.transloadit2-v2-latest.js. We will always make an effort to keep that stable. If you are using that version, you do not need to do anything about the patch.

There will be another announcement with a real deprecation date for this functionality soon, but this is to let you know in advance already, because it is related to the problems that occurred.