Bruce MacKay schrieb:
> Hi Klaus,
> 
> Sorry, but I'm just not following all of this.  I've added the action 
> attribute back in - and altered the $.post statement to read 
> $.post(this.getAttribute("action"), but I don't understand your 
> advice on the "return false" with respect to the onsubmit function - 
> I cannot identify the onsubmit function.  I have "return false" at 
> the end of the $.fn.ajaxSubmit function - at least as I read it I have.
> 
> Bringing the "this.getAttribute("action")" and the "action=..." back 
> into the code is resulting in what I assume in double submitting in 
> both browsers now - FF, for example, is ending up at the ajax processing page
> 
> http://horticulture127.massey.ac.nz/degreeCdays3.asp
> 
> Sorry, but would you mind spelling this out a bit more clearly for 
> this poor horticulturist!

Bruce, I'm not to sound with jQuery's new AJAX functions, but I think 
the problem is that you apply ajaxSubmit() to an element which is not 
the form:

$(document).ready(function() {
     $("#selfreview").ajaxSubmit();
});

That attaches a submit event handler to #selfreview which is a div, but 
submit event handlers only apply to forms. Thus at the moment there does 
not happen any AJAX call at all if you submit the form.
The "return false;" statement is already correctly in place by the way, 
so if #selfreview were a form, there would be no double submit.

Try the following:

$(document).ready(function() {
     $("#selfreview form").ajaxSubmit();
});

Does it work?


-- Klaus





_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to