Do the email and general options depend on the form elements being explicitly stated in the form code?
If that doesn't make sense, what I mean is that I am trying to make my form code, not explicit, I want someone in the future to be able to change it by just changing a couple numbers rather than editing the form code itself. However, recent testing of this has sent me blank emails, and sometimes, emails don't come at all.
So if I have a form field
{selection1}
does that depend on an input field being explicitly stated like so:
<input type='text' name='selection1' id='selection1' />
Rather than part of a php statement like so:
for($i=0;$i<4;$i++)
echo '<input type="text" name="selection'.$i.'" id="selection'.$i.'" />'
Thanks in advance for any input.
Post edited by: rstruber, at: 2007/12/13 07:49
Post edited by: rstruber, at: 2007/12/13 07:50<br><br>Post edited by: rstruber, at: 2007/12/13 07:51
If that doesn't make sense, what I mean is that I am trying to make my form code, not explicit, I want someone in the future to be able to change it by just changing a couple numbers rather than editing the form code itself. However, recent testing of this has sent me blank emails, and sometimes, emails don't come at all.
So if I have a form field
{selection1}
does that depend on an input field being explicitly stated like so:
<input type='text' name='selection1' id='selection1' />
Rather than part of a php statement like so:
for($i=0;$i<4;$i++)
echo '<input type="text" name="selection'.$i.'" id="selection'.$i.'" />'
Thanks in advance for any input.
Post edited by: rstruber, at: 2007/12/13 07:49
Post edited by: rstruber, at: 2007/12/13 07:50<br><br>Post edited by: rstruber, at: 2007/12/13 07:51
Hi rstruber,
Yes, ChronoForms parses the 'Form HTML' to find field names so it will only find explicit declarations.
Sorry, I can't think of any workaround to this one, it's pretty fundamental to the way the extension works.
Bob
Yes, ChronoForms parses the 'Form HTML' to find field names so it will only find explicit declarations.
Sorry, I can't think of any workaround to this one, it's pretty fundamental to the way the extension works.
Bob
This topic is locked and no more replies can be posted.