Skip Navigation

[Resolved] Split: I can not use the fields styling editor with types 3.0

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

Problem:
I can not use the fields styling editor with types 3.0

Solution:
This issue will be fixed with Types version 3.1 in near future.

Relevant Documentation:

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.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 3 replies, has 2 voices.

Last updated by goM 6 years, 2 months ago.

Assisted by: Minesh.

Author
Posts
#911785

goM

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'.

#911786

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Well - I spit this issue as new topic and I'm able to reproduce this issue and reported to our next level support for further debug.

I'll get in touch with you as soon as I know more.

#1101331

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I've got the news that this issue will be fixed with Types version 3.1 that is scheduled to release within this month.

#1101678

goM

Thank you for the information. I will wait for the release of the modified version.