Fix for fields shown by > or < conditionals not being saved.

Hi,

I’ve seen the same behaviour as a couple of others on this thread with later / current versions of GF.
Digging in to GF’s core, it seems that a record which doesn’t “match” according to the conditional logic rules stored in that field object won’t be saved – effectively if GF core doesn’t understand the conditional, it’s treated as hidden *even if it was visible on the POSTed form*.
The simplest solution I’ve found is to pre-test each field’s conditional via gform_pre_submission_filter and set any ‘datepicker’ conditionals that do match to equal themselves; so ‘<‘ or ‘>’ operators become “is” and the fieldId to match is overwritten with the current field’s own fieldId. Bit of a cludge but it works, so far.

Would you like to incorporate this?