Skip Navigation

[Resolved] Unknown field name in Fields and Views

This support ticket is created 5 years, 8 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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9: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/Karachi (GMT+05:00)

This topic contains 4 replies, has 2 voices.

Last updated by Waqar 5 years, 4 months ago.

Assisted by: Waqar.

Author
Posts
#1277023
Screenshot 2019-06-26 at 10.42.00 AM.png
Screenshot 2019-06-26 at 10.49.37 AM.png

Dear Sir/Madam,

I have a custom checkbox fields "space" and only set the title and value to store for each option, I want to redefine the output value for each option from the Views but I don't understand what the string in custom value for selected and not selected mean? How can I know which option I am going to define?

Best regards,

Kelvin.

#1277293

Hi Kelvin,

Thank you for contacting us and I'd be happy to assist.

The way "custom values" section shown in your screenshot ( 1277023-Screenshot_2019_06_26_at_10.42.00_AM.png ) works, it can be used to show any new values for the checkboxes fields, which were not defined in the settings.

The fields in the first (left) column, ending with "selected" can be used to target the "checked" state, while the other fields in the second (right) column, ending with "not selected" can be used to target the "unchecked" state.

If the respective checkbox is checked, the value from the first column will be shown and otherwise, the value from the second column will be shown.

For example, suppose there are 3 options included in a "checkboxes" type field:
hidden link

This next screenshot shows how these custom value columns are shown and can be used to show new values, accordingly:
hidden link

And this is the output with the shortcodes, that is generated as a result:


[types field='company-checkboxes' state="checked" option="0"]Custom value to show when first checkbox is checked[/types]
[types field='company-checkboxes' state="unchecked" option="0"]Custom value to show when first checkbox is not checked[/types]

[types field='company-checkboxes' state="checked" option="1"]Custom value to show when second checkbox is checked[/types]
[types field='company-checkboxes' state="unchecked" option="1"]Custom value to show when second checkbox is not checked[/types]

[types field='company-checkboxes' state="checked" option="2"]Custom value to show when third checkbox is checked[/types]
[types field='company-checkboxes' state="unchecked" option="2"]Custom value to show when third checkbox is not checked[/types]

Important note: The titles of your field's options are not readable ( screenshot: hidden link ) since they include special characters from "Chinese" language. I'm going to report this behavior to the concerned team, so this can be further reviewed.

I'll keep you updated with the progress through this ticket and appreciate you brought this forward.

For now, you can fill the option values in the "custom values" section, based on the order in which these options are defined in the custom field settings.

I hope this helps and please let me know if you need any further assistance around this.

regards,
Waqar

#1280941

Dear Waqar,

Regarding the special characters from "Chinese", the u5ba2 looks like an Unicode. Hope this can be fixed soon.

Best regards,

Kelvin

#1281471

Hi Kelvin,

Yes, your observation about the Unicode is correct and we've now published this in the list of known issues:
https://toolset.com/errata/checkboxes-and-radio-options-in-non-latin-characters-are-sometimes-not-displayed-correctly-in-toolset-user-interface/

I'll update you once this gets resolved.

regards,
Waqar

#1366171

Hi Kelvin,

I'm happy to update that a fix for this issue has been included in the latest Types release ( version: 3.3.6 ).

You're welcome to update to the latest version and let us know in case the issue still persists.

regards,
Waqar