Second Update:
If you remove the name attribute from the button using jQuery then it
works. Just changing the name does not.
All fixed.
On Apr 14, 11:01 am, MeanStudios wrote:
> Update:
>
> I am using ExpressionEngine and am trying to edit to the publish area
> (for those of you wondering) and
Update:
I am using ExpressionEngine and am trying to edit to the publish area
(for those of you wondering) and I have no control over the name
attribute for the submit button and it's value is "submit" so I've
used jQuery to change the name of the submit button to something else
with this line of
> Cool, you should mention that on the website :)
>
> Oh wait - this would kind of be the "failure" function mentioned
> above. I actually get "parsererror" as statustext in the complete
> function. Just didn't know about it :)
You can use all of the normal "ajax" options with the Form plugin.
su
On 29 Mar., 02:46, Mike Alsup wrote:
> Well there must be more to the story than what you're telling us. The
> code you've shown above looks fine. Perhaps there is a problem with
> the json response.
Actually that was excactly the problem. It would be good to get some
kind of notification thou
> I'm trying to use the form plugin from malsup.org to submit a form
> with ajax, but it does not seem to work with options.
>
> This works:
>
> $("#loginform").ajaxSubmit(function(obj,
> statusText) {
> alert(obj);
>
5 matches
Mail list logo