Radio input fields in Forms do not include the "form-control" CSS class anymore

This thread is resolved. Here is a description of the problem and solution.

Problem: Radio input fields in Forms do not include the form-control CSS class anymore.

Solution: It's expected, though we realize it may cause some problems for existing sites that used this class for style selectors. From our lead developer:
"CRED used to have a setting about loading Bootstrap markup for forms, which added a form-control CSS class to some form elements. As we added fully native Bootstrap compatibility, that option was deprecated and removed. This also meant removing the extra class when it was turned on.
Consequently, some sites that had this option turned on will not output the CSS class in question. To resolve possible styling issues, the solution is to simply add a class=”form-control” attribute to the fields that used to get this class from CRED.
Unfortunately, this might require manual editing of some of the existing forms, but we honestly think this is the best path forward."

Relevant Documentation:
https://toolset.com/documentation/user-guides/styling-cred-forms/#toolset-forms-markup-overview

This support ticket is created 6 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

This topic is split from https://toolset.com/forums/topic/unable-to-display-custom-field-value-from-parent-post/

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 2 replies, has 2 voices.

Last updated by julieP 6 years, 5 months ago.

Assisted by: Christian Cox.

Author

Posts

June 11, 2018 at 2:18 pm #911849

julieP

Hi Christian

I really appreciate the offer to look at the install. I've since taken that install offline and am working on a fresh re-build in its place (it's a dev site). I'm not importing anything I've previously captured using module manager or WordPress importer. I've set up a basic form and a view with a post edit link displaying the parent post title and this is working as expected now.

That's the good news.

I've just settled down to creating more forms and I've noticed that whereas ALL cred fields used to contain class="form-control", now they don't. It seems to be the radio fields that don't. Is this expected?

June 11, 2018 at 4:42 pm #911948

Christian Cox

It seems to be the radio fields that don't. Is this expected?
Yes, it's expected, though we realize it may cause some problems for existing sites that used this class for style selectors. From our lead developer:
"CRED used to have a setting about loading Bootstrap markup for forms, which added a form-control CSS class to some form elements. As we added fully native Bootstrap compatibility, that option was deprecated and removed. This also meant removing the extra class when it was turned on.
Consequently, some sites that had this option turned on will not output the CSS class in question. To resolve possible styling issues, the solution is to simply add a class=”form-control” attribute to the fields that used to get this class from CRED.
Unfortunately, this might require manual editing of some of the existing forms, but we honestly think this is the best path forward."

Also, please check the notes here about which types of fields accept the class attribute:
https://toolset.com/documentation/user-guides/styling-cred-forms/#toolset-forms-markup-overview

June 12, 2018 at 5:28 am #912167

julieP

Hi Christian

Thank you for this and thanks also to the developer for providing a clear explanation.