Hi Mike,
Thanks for the response. I went back and started from scratch and got
it working. I think the problem was a jquery version issue. Good
times.<g>
Also, thanks for the explanation, that makes total sense.
Take care.
On Apr 4, 5:03 pm, "Mike Alsup" <[EMAIL PROTECTED]> wrote:
> Hi Buzz,
>
> Would you happen to have a sample page that demonstrates this problem?
> I don't think I've seen that particular error before in that part of
> the code. Regarding the dataType and target options, they are
> mutually exclusive because target only applies to a text or html
> response (dataType == null). If the dataType option is set
> (xml/script/json) then there is nothing to load in the target (and
> thus fewer hoops to jump through to manage the nested scripts).
>
> Mike
>
> On 4/4/07, Buzzterrier <[EMAIL PROTECTED]> wrote:
>
>
>
> > I am new to jquery and am trying to get the form plugin to work
> > correctly. The success callback is not getting called, and I am
> > getting the following error:
>
> > jQuery(options.target).attr("innerHTML", data).evalScripts is not a
> > function
>
> > I am at a complete loss (I must say that jquery is far harder to debug
> > than prototype). My target gets populated with the responseText, so I
> > know I am returning something. The error is at:
>
> > // perform a load on the target only if dataType is not provided
> > 213 if (!options.dataType && options.target) {
> > 214 var oldSuccess = options.success || function(){};
> > 215 callbacks.push(function(data, status) {
> > 216 jQuery(options.target).attr("innerHTML",
> > data).evalScripts().each(oldSuccess, [data, status]);
> > 217 });
> > 218 }
>
> > Also, it is not clear why dataType and target are mutually exclusive.
>
> > Any ideas?
