There is a bug in the form wizard's html code generator.
When the dafault "field_name" value for a "datepicker" type form field is changed within the form wizard, the generated html code is wrong: in the coresponding "input" tag contains the correct (new) value for the "name" attribute, instead, the "id" attributes retains the wrong (old) value.
This thing is very suble because the effect is that the form is correcly displayed in Internet Explorer (the datepicker is show) BUT THE SAME PAGE IS UNUSABLE (without datepicker) in FIREFOX!!!
Probably because i.e. uses the "name" attribute while firefox uses the "id"... I don't know really.
Workaround: edit the Form HTML generated code in the "Form code" tab by fixing the value assigned to the "id" attribute (must match the "field name" assigned in the wizard).
When the dafault "field_name" value for a "datepicker" type form field is changed within the form wizard, the generated html code is wrong: in the coresponding "input" tag contains the correct (new) value for the "name" attribute, instead, the "id" attributes retains the wrong (old) value.
This thing is very suble because the effect is that the form is correcly displayed in Internet Explorer (the datepicker is show) BUT THE SAME PAGE IS UNUSABLE (without datepicker) in FIREFOX!!!
Probably because i.e. uses the "name" attribute while firefox uses the "id"... I don't know really.
Workaround: edit the Form HTML generated code in the "Form code" tab by fixing the value assigned to the "id" attribute (must match the "field name" assigned in the wizard).