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).
Hi andreabix,
Thanks - we spotted this oen a few days ago and I think Max has it fixed in the RC3 release which must be almost here.
Bob
Thanks - we spotted this oen a few days ago and I think Max has it fixed in the RC3 release which must be almost here.
Bob
I noticed that I'm still having an issue with this. FYI.
Hi MediaMisfit,
did you test this with RC3 after clearing browser cache 100% ? tell me how do you produce the bug if so!
Regards
Max
did you test this with RC3 after clearing browser cache 100% ? tell me how do you produce the bug if so!
Regards
Max
This bug still exisits. latest version downloaded. Checked the id and form element name. no date picker. made a new form. date picker works. Now need to either debug chrono forms or re build my massive form.
actually, datepickers just seem to stop working after you add a few fields. I started recreating the massive form, checked datepickers worked with just them on the form. then added 4-5 other fields (text boxes) saved and checked again, nope. not date pickers anymore.
gonna just go with text box entry of dates.
gonna just go with text box entry of dates.
oh, and the validation always fails on date text fields!
Hi asecondwill,
Please double check after you change the form by adding new fields that the "load chronoforms files" is set to yes and that you have the date field name in the auto generated tab and that you have a date field format under the general tab!
please let me know if you tested the above issues, it will help fixing the problem or finding the solution!
Regards
Max
Please double check after you change the form by adding new fields that the "load chronoforms files" is set to yes and that you have the date field name in the auto generated tab and that you have a date field format under the general tab!
please let me know if you tested the above issues, it will help fixing the problem or finding the solution!
Regards
Max
This topic is locked and no more replies can be posted.
