I noticed that when you change the FORM from form_for(@page) to remote_form_for(@page) if you have 'wysihat_engine_pack' included in the javascript it won't work. It will fall back to regular posting.
You can see this in the demo app, just edit app/views/pages/new.html.erb and chnage from_for to remote_form_for and see that it just posts as normal.
If you remove the 'wysihat_engine_pack' from the app/views/layouts/pages.html.erb and click create, the page will not change and using firebug you can see the ajax call.
Unfortunately I don't know enough about why the wysihat-engine is taking over from the remote_form_for, though I suspect that it would relate to how it monitors the forms.
Hope this is an easy fix as I am sure others want to use remote_form_for and the wysihat engine at the same time. :-)
I noticed that when you change the FORM from form_for(@page) to remote_form_for(@page) if you have 'wysihat_engine_pack' included in the javascript it won't work. It will fall back to regular posting.
You can see this in the demo app, just edit app/views/pages/new.html.erb and chnage from_for to remote_form_for and see that it just posts as normal.
If you remove the 'wysihat_engine_pack' from the app/views/layouts/pages.html.erb and click create, the page will not change and using firebug you can see the ajax call.
Unfortunately I don't know enough about why the wysihat-engine is taking over from the remote_form_for, though I suspect that it would relate to how it monitors the forms.
Hope this is an easy fix as I am sure others want to use remote_form_for and the wysihat engine at the same time. :-)