This thread is resolved. Here is a description of the problem and solution.
Problem:
Types fields in Toolset Forms inherit whether they are required or not from their Types setting. Is it possible to make a field required in the Form, but not in the backend?
Solution:
Only with a custom solution, either adding some JS to the form to set the field in question to be required, or using the cred_form_validate hook to perform the validation on the server when the form is submitted.
Relevant Documentation:
https://toolset.com/documentation/programmer-reference/cred-api/#cred_form_validate
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
| - | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
This topic contains 2 replies, has 2 voices.
Last updated by 6 years, 6 months ago.
Assisted by: Nigel.
I am trying to:
Set a field (radio) as required on the CRED front end side only. Not on the back end (Types Custom Field).
Link to a page where the issue can be seen:
Screen Shot
I expected to see:
Error Message
Instead, I got:
Nothing
I used:
[cred_field field='job-post-length' value='' urlparam='' output='bootstrap' required="true"]
Thank you!
