Hello,
I'm using a date field in a user form and have an issue.
The way the field is working (ie : chose the year, then the month and finally the day is not always understood by users.
Sometimes, they are not defining the year and in the end, we get a wrong info.
Is there a way to have a better front end management for this kind of field :
- pre-position the initial value to undefined in order to force the user to enter all info
- instead of using the calendar view, have 3 different fields for year, month and day
Let me know
Regards
Pat
Dear Pat,
I assume we are talking about the datepicker outputted from shortcode [cred_field].
See our document:
https://toolset.com/documentation/user-guides/cred-shortcodes/#cred_field
As you see, there are't both built-in features within Toolset Forms plugin.
You can add a feature request for it, our developers will evaluate it:
https://toolset.com/forums/topic/feature-request-add-new-post-option-when-creating-a-relationship-in-toolset-forms/
Hi Luo,
If I look at the Types API, I can see that it is possible to have a style option (calendar, text). This is a pity we cannot use it inside Cred.
Another point is that in Cred, we can define a Value parameter. Would it be possible to place something there in order to get an undefined date from the beginning (ie : oblige the user to chose a complete date in the calendar then after ?).
Regards
Pat
I have already tried it in my localhost, the attribute "value" can only setup the default value of input box, it can not do what you want:
place something there in order to get an undefined date from the beginning
And according to the document I mentioned above:
https://toolset.com/documentation/user-guides/cred-shortcodes/#cred_field
date fields require a valid timestamp instead of a date string.
