When you insert a Generic Select Field in Toolset Form and add an additional Custom Class, it will be added to the HTML that the Select Field generates.
You can see the in the console after saving the form and visiting it in the front end.
Types Select Fields do not allow to add a Class in the Toolset Forms Editor.
But, you can still add a class='custom-class' when in the Advanced editor, and that will as well reflect on the front end.
This would be the Form Code:
[cred_field field='select-of-types' force_type='field' class='form-control custom-class-here' output='bootstrap']
It this is not working on your end, I suggest to ensure it is not due to malformed ShortCodes, or 3rd Party code (you can temporarily disable other Plugins and use another theme to be sure).
However note, this is for select fields, as you requested.
But the ShortCode you show me is not a select field - instead it's a Taxonomy Field that accidentally is displayed as select input.
This is different.
There you can only use the wpt-form-select class which is used by all select inputs of Forms
It is closer explained here https://toolset.com/documentation/user-guides/styling-cred-forms/#hierarchical-taxonomy
But that DOC is out of date, I see.
Currently there is no class added to the Taxonomy inputs as stated there, neither to the wrapping DIV.
I've reported that to the 2nd Tier for analysis.
Right now, you can open the Browser console and analyze the Input HTML, it will tell exactly what class or name you can address, however, you cannot add your custom class to it.
You can for example use the classes wpt-form-select form-select select, or the HTML "name" attribute, which will be something like "your_taxonomy_singular_slug[]"
Example:
select[name="your_tax[]"] {
background: red;
}
I will keep you in the loop about our updates to either DOC or bug fixing in Toolset Forms to adjust the current discrepancies.
