I have set up some custom fields and some of them have a description.
The description doe snot show in the cred form when I insert the according shortcode.
The tooltip in the cusstom fields setup page states that the description will show up NEXT to the field and "helps users to understand". It does not.
Have tried these but best I got was just the title, NOT the description:
[cred_field field='disclaimer' value='' urlparam='' output='bootstrap'] --> The field itself with the title
[types field="disclaimer" show_name="true"][/types] --> the title only
[types field="disclaimer" format="FIELD_NAME"][/types] --> nothing
[types field="disclaimer" format="FIELD_DESCRIPTION"][/types] --> nothing
Hi, the description is meant to be shown in wp-admin but not intended for use in CRED. If you'd like to include a message next to a CRED form field, you may add it into the auto-generated code of the CRED form.
Hmm I still dont get it. The tooltip states "the text will appear next to the field" to guide the user. But it does not appears anywhere (not in views, not in cred nor anywhere in the backend)!
You should definitely ask a devleoper about this. The tip clearly states something it does not do - or I am too blind to find any spot this text is used in.
Thanks in advance 🙂
Here are two screenshots highlighting the description in the field editor and in a post editor.
Then this definitely even more also should be available in custom CRED frontend forms...
I strongly agree with @KonstantinS88 that it should be possible to expose this description to a linked form, even if it's optional rather than enforced. If the primary purpose is to aid users in understanding what the field is for then it is just as important, if not more so to include that information in the front end editor for that field.
+ 1 to this topic!
For most Toolset applications users will be adding posts via the front end, so having the description only visible in the back end isn't useful to the front end user.
Having a simple option here to show the description on front end forms would be perfect.
Yes, we absolutely need this in the front end forms!