I have a form which consists of many inputs and a few CKeditors.
The form is submitted via ajax, but if the user has not filled in a required part of the form, the form shows up again so that they can finish.
As of right now, I have a generic javascript ajax form submit function that I use for the entire site. This form submit function right now will always destroy all CKEditors in the div being updated before it is updated. That way when a new CKEditor appears with the same name, there won't be a problem.
Is that normal to get this error when submitting via ajax before destroying the editor? Is there a better way to do this?
The form is submitted via ajax, but if the user has not filled in a required part of the form, the form shows up again so that they can finish.
As of right now, I have a generic javascript ajax form submit function that I use for the entire site. This form submit function right now will always destroy all CKEditors in the div being updated before it is updated. That way when a new CKEditor appears with the same name, there won't be a problem.
Is that normal to get this error when submitting via ajax before destroying the editor? Is there a better way to do this?
Re: Ajax submit best practices
In short... When submitting via ajax, and it's possible for a ckeditor with the same name to show up again, do I always have to destroy the editors before submitting to prevent a javascript error? Or is there a better way??
Re: Ajax submit best practices
Re: Ajax submit best practices
Becuase that's how an ajax update works. It updates the entire div with all of the inputs, replacing them with the new div coming from the server.
Anyway, I figured it out. Before adding the editor, if an editor object exists, I do destroy(true). That way, it doesn't try to update the nonexistant textarea element in the DOM.
Re: Ajax submit best practices