Hello,
I have a form that saves to the DB correctly if I click 'test form' from within the CF5 wizard after saving. On the site, the same form in embedded in a page with the CF5 module and in that case, it does not save correctly. It tries to do an update rather than an insert to the DB and fails.
Here are screenshots showing the insert action, if form is submitted "on its own" (VM_TestForm.gif) and update actions if form is embedded in a web page (VM_InPage.gif) on submit.
Note that the update action, the "in page" submit, has id=2201 but the insert action, just prior to trying the "in page" submit, has id=2.
I set "Force Save" to yes subsequently in the form, and it is now inserting records even when submitted from "in page".
Also attached is a screenshot showing the DB records: 1, 2, and 2201.
So the save is happening since I set "force save" to yes, but why oh why did it try to do an Update instead of an Add when using the CF module and embedding the form in an article?
So curious, dnigra
I have a form that saves to the DB correctly if I click 'test form' from within the CF5 wizard after saving. On the site, the same form in embedded in a page with the CF5 module and in that case, it does not save correctly. It tries to do an update rather than an insert to the DB and fails.
Here are screenshots showing the insert action, if form is submitted "on its own" (VM_TestForm.gif) and update actions if form is embedded in a web page (VM_InPage.gif) on submit.
Note that the update action, the "in page" submit, has id=2201 but the insert action, just prior to trying the "in page" submit, has id=2.
I set "Force Save" to yes subsequently in the form, and it is now inserting records even when submitted from "in page".
Also attached is a screenshot showing the DB records: 1, 2, and 2201.
So the save is happening since I set "force save" to yes, but why oh why did it try to do an Update instead of an Add when using the CF module and embedding the form in an article?
So curious, dnigra