Dear virajmody,

jQuery Allows you to return to the low level jQuery $.ajax(...) call if you need more callbacks and/or settings.

$.ajax is very simple to use.

all the high level abstraction AJAX calls like $.load(...),$.get(...), $.post(...), $.getScript(...), etc... are designed to fulfill some frequent AJAX tasks.

If you want to continue with using $.getScript(...) but with an additional callback for the error and you don't want to modify the jQuery library itself, you can use the global ajaxError callback event that has three parameter. the third one is the settings of the request that handled the error so you can test if(settings.dataType=='script' && settings.url=='...put it here') in the global ajaxError callback event to handle the getScript request that generates the error

I tried using $.ajax with dataType = "script" but that too didn't seem to invoke an error callback.

I'll try the global ajaxError callback - thanks for that suggestion.

The documentation for $.getScript should be fixed regardless, though.

I took a stab at adding error callbacks for remote scripts, which I assume would address this bug. See http://github.com/ishermandom/jquery/blob/15fc751ba6b39072c9ebf2548f2deaabe3257bc0/src/ajax.js.

I have added a reference to getScript as one of the areas of the API documentation which we need to update. Keeping this ticket open for now as there appears to have been a contribution made to address additional error callbacks that may want to be reviewed.

#4734 is a duplicate of this ticket.

(In #5048) This needs to be reverified with the new ajax module.

I've just gone through the API docs for .getScript() and also put together a a live test case here: http://jsfiddle.net/64bDU/ using jQuery 1.5.2 demonstrating that the two parameters accepted by the success callback do in fact return values and *not* null/undefined as originally posted. In the case of the first parameter (data) data is returned if available and the textStatus returns with a success message on completion. We've never claimed that error messages were available for this.

In my view, we may need to adjust the docs to clarify the limitations of .getScript(), however as the first reply correctly points out, if you need more than it provides, remember it's just a shorthand method and you can always fall back on $.ajax() for something requiring additional callbacks for errors etc.

Closing as an error callback would probably creep into the territory of stopping this being just a short convenience path to achieving $.ajax()-related functionality.

Docs updated: http://api.jquery.com/jQuery.getScript/