Problem: I would like to be able to change the values in a custom field.
Solution:
If you just want to change the values in the field options for something like a select field or radio field, you can modify the field options directly in Toolset > Custom Fields. However, if you want to modify the value of this custom field that has already been saved with multiple posts, then it is not a simple task. A skilled developer could do this for you with a database script, or you could make the field value changes then manually edit every post that has this custom field and save the post to store the updated value(s). It's not an automated process, unfortunately.
Problem: I have a "select" custom field that includes several options. I have created a custom search View that includes this field as a filter using checkboxes. If I check any one option, the View shows the correct results. But if I check more than one option, no results are shown.
Solution: The Query Filter in this View is configured to test using the "equal to" comparison instead of the "in" comparison. Check the attached screenshot to see this configuration in the View editor screen. Your Query Filter should use "in" to check if the posts contain any of the selected values, not all of the selected values (i.e. the "equal to" option).
If you cannot see the Query Filter section in your View editor screen, scroll to the top right corner of the screen and click "Screen Options", then you can enable the Query Filter panel.
Problem: I would like to include a post date filter in a parametric search View.
Solution: At this time we do not provide a built-in front-end search control for post date. Our developers have accepted a feature request to add this type of filter, but I do not yet have a release date available for that improvement. In the meantime, you have the ability to provide front-end search controls for dates in custom fields, so you could use the save_post API to copy the publish date into a custom field as a timestamp, then insert the custom date field as a filter in your custom search View controls.
Add this custom code to your child theme's functions.php file:
function copy_custom_date_field ( $post_id ) {
// only copy over the publish date on original posts
$status = get_post_status( $post_id );
$pubdate = get_post_meta( $post_id, 'wpcf-issue-date', true);
if ( $status != 'publish' || $pubdate )
return;
$pubdate = get_the_date( 'U', $post_id );
update_post_meta( $post_id, 'wpcf-issue-date', $pubdate, '' );
}
add_action( 'save_post', 'copy_custom_date_field', 1000 );
Replace "wpcf-issue-date" in both places with the slug of your custom field, using the wpcf- prefix. So if your custom field slug is "custom-post-date" then you should use "wpcf-custom-post-date".
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
