Problem: I have 3 CRED forms that create new posts in the same post type. I would like to automatically assign one term to each new post, and I would like that term to be different for each form. I tried using the "value" attribute of the cred_field shortcode, but it does not appear to save the correct term information.
Solution: The "value" attribute of a cred_field with single_select does not apply to taxonomy term fields. Instead, you can do something similar with the CRED API:
add_action('cred_save_data', 'auto_cred_term_action',10,2);
function auto_cred_term_action($post_id, $form_data)
{
// form #1
if ($form_data['id']==123)
{
$tag = array( 11 ); // Taxonomy term ID
$taxonomy="storytypes"; // Taxonomy name
wp_set_post_terms( $post_id, $tag, $taxonomy );
}
// form #2
if ($form_data['id']==234)
{
$tag = array( 22 ); // Taxonomy term ID
$taxonomy="storytypes"; // Taxonomy name
wp_set_post_terms( $post_id, $tag, $taxonomy );
}
// form #3
if ($form_data['id']==456)
{
$tag = array( 33 ); // Taxonomy term ID
$taxonomy="storytypes"; // Taxonomy name
wp_set_post_terms( $post_id, $tag, $taxonomy );
}
}
Remove the taxonomy cred_field shortcode from the form, and modify the form and term IDs as needed in the code above.
Problem:
The Types 3.0 beta includes repeating field groups, but the CRED beta doesn't support them.
Solution:
This will be added soon, although it doesn't make the cut for the initial release, but is a priority feature that should be included soon after.
Problem:
Display DATE field information in the theme PHP template file.
So if someone enters a course to begin on 27th September 2018 then I need to output on the front end:
• Sep
• 27
These need to be outputted separately in different places in the template. This is to allow me to display dates as in the attached screenshot.
The field (if that helps) is called 'start-date-for-course'
Solution:
I assume the field "start-date-for-course" is a custom date field created with Types plugin, please try Types function types_render_field(), for example:
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.
