Hello. Thank you for contacting the Toolset support.
Well - the use of constant TYPES_USE_STYLING_EDITOR with Types 3.0 is deprecated and is not going to support in future but still to have more concrete answer I've reported the issue to our next level support.
Please hold on for further updates. I will get in touch with you as soon as I know more.
The "Add Admin CSS" plugin seems to be able to substitute the existing method.
I have two questions.
Q.1
How can I delete a CSS that was set up using "fields styling editor"?
Before resetting the CSS using the "Add Admin CSS" plugin, I need to delete the old CSS set by "fields styling editor" from the WordPress database.
Q.2
How should I adjust the width and float of custom fields belonging to a specific field group with the "Add Admin CSS" plug-in?
I could not apply style if I specified as follows.
ex:
# wpcf - group - {my - field - group - name} div [data - wpt - id = "wpcf - {my - custom - field - name}"] {
width: 100px;
}
On the other hand, if I did not specify a field group, I could apply the style.
ex:
div [data-wpt-id = "wpcf- {my-custom-field-name}"] {
width: 100px;
}
Q.1
How can I delete a CSS that was set up using "fields styling editor"?
Before resetting the CSS using the "Add Admin CSS" plugin, I need to delete the old CSS set by "fields styling editor" from the WordPress database.
======>
Well - all custom styles you added to "Styling Editor" is saved in postmeta database table with key = _wp_types_group_admin_styles.
Q.2
How should I adjust the width and float of custom fields belonging to a specific field group with the "Add Admin CSS" plug-in?
=====>
Well - I tried to follow the same way and I can see its working at my end.
About:Q.2
When I set the field group name with Japanese (= multibyte character), the URL encoded HTML will be output after "# wpcf-group ***".
Please see the attached image '2018-06-11_18h22_10.png'.
In this case, I can not correctly specify the element using the field group name.
When setting field group name with English (= single byte character), CSS correctly reflected.
Therefore, I think you need slag for HTML output in the field group name (just like custom fields).
Please see the attached image '2018-06-11_18h41_17.png'.
New threads created by Minesh and linked to this one are listed below: