Is there a quick answer to this? I just upgraded from 2.5 RC 3.1 (or so) to 3.2.0 stable, and most things seem to be working all right, but one of the weird bugs I'm finding is that inputs with type="hidden" have their value reset to "" (nothing).
What's going on? Why on earth would ChronoForms touch the field values? This is obviously an extremely crucial part of many forms so I can't imagine it's a universal problem, it must be just me. But then, what can I do to fix it?
Thanks.🙂
What's going on? Why on earth would ChronoForms touch the field values? This is obviously an extremely crucial part of many forms so I can't imagine it's a universal problem, it must be just me. But then, what can I do to fix it?
Thanks.🙂
Found a solution for the time being: it was the "Try to Republish" option. Either turn it off for the form, or add the hidden fields to the 'skip' list.
I already had some code in place to republish those fields in the event of an error in 2.5, since the data was critical and could not be re-entered by the user (since it was hidden), so for me it's okay not to republish.
I would suggest someone look into fixing this in the next release though, as hidden fields are currently getting cleared unless you skip them in the republish thing. :/ No good!
I already had some code in place to republish those fields in the event of an error in 2.5, since the data was critical and could not be re-entered by the user (since it was hidden), so for me it's okay not to republish.
I would suggest someone look into fixing this in the next release though, as hidden fields are currently getting cleared unless you skip them in the republish thing. :/ No good!
This topic is locked and no more replies can be posted.
