[Resolved] CRED Generic fields values vanishing after validation

[Author]

Posts

[michelB]

Hello, I am having exactly the same problem as is described in here:
https://toolset.com/forums/topic/cred-generic-field-empty-after-validation-refresh/
Has this problem found any solution in the meanwhile?
Thank you very much.

[Shane]

Hi Michel,

Thank you for contacting our support forum.

So the issue here is that if the validation fails then the field data is lost ?

Please let me know.
Thanks,
Shane

[michelB]

Hi Shane, Yes exactly. This happens for generic fields. Thanks very much for your help.

[Shane]

Hi Michel,

I was able to successfully replicate the issue on a fresh install and will make a report to our team.

Hopefully we can get some more information on this soon.

Thanks,
Shane

[Shane]

Hi Michel,

Just to get some more details on this.

Is the validation for the field that the data is missing after a failed validation ? Also what type of generic field did you use.

Please let me know.

Thanks,
Shane

[michelB]

Hi Shane,
The generic field is a single checkbox. If the user checks this checkbox and submits, its value vanishes whenever validation fails for another field (a custom Type field). Validation is done via the CRED validation hook.
Thanks,
Michel

[Shane]

Hi Michel,

I tried replicating the issue again and wasn't able to.

Would you mind temporarily disabling all your non-toolset plugins and trying again ?

Once you you have done this please let me know.

Thanks,
Shane

[michelB]

I have tried to remove non-toolset plugins and to simplify my CRED form to just this generic field and I still have the same problem. For time scheduling reasons I had to work around the problem by moving the generic fields into Types customized fields. This way the value given by the user to the field persists until after the validation is performed. A better solution without having to define Types customized fields would be welcome however.

[Shane]

Hi Michel,

Would you mind providing temporary admin access to us so that we can check out the issue ? as we are not able to replicate the problem on a fresh wordpress install.

The private fields will be enabled for your next response.

Thanks,
Shane