Checkbox custom fields not staying selected in wp-admin post editor

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

Problem: Checkbox custom fields are not staying selected in the post editor, and sometimes I see an error related to a parent post field even though I did not modify that field.

Solution: Update to the latest version of Types.

This support ticket is created 6 years, 6 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
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)

Tagged: Types plugin

This topic contains 16 replies, has 3 voices.

Last updated by Christian Cox 6 years, 4 months ago.

Assisted by: Christian Cox.

← 1 2

Author

Posts

July 15, 2018 at 3:37 pm #947800

Christian Cox

There are two different ways to display custom field values. The first way uses the Types field shortcode like this:

[types field="order-events-set-2-presenter-4" output="raw"][/types]

The second way uses the wpv-post-field shortcode like this:

[wpv-post-field name="wpcf-order-events-set-2-presenter-4"]

The main things to note about this field are:
- you must use the wpcf- prefix with your field slug
- the raw value will be returned with no additional formatting applied

We have documentation available here:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-post-field

Types 3.0.4 is now available for download or automatic update.

July 15, 2018 at 4:02 pm #947807

lauraS

Thank you for this response. I was able to get it to work properly with that documentation.

Have a great day!

August 13, 2018 at 12:58 pm #1081363

Christian Cox

Our developers have let me know that the issue with Types fields shortcodes displaying empty space instead of 0 will be resolved in Types 3.1, due in the next few weeks.

← 1 2