Problem: I have a one-to-many hierarchical relationship of post types with grandparent, parent, and child posts (Make > Model > Version). On the single Version post page, I would like to display the Version information, as well as breadcrumb links to the single Model and single Make pages for its parent and grandparent posts. On the parent single Model page, I would like to show a View of all the Versions that belong to this parent. The breadcrumbs on this page should include a link to the grandparent Make post. On the single grandparent Make page, I would like to include a View that shows all the Version posts belonging to the grandparent Make.
Solution: Create a Content Template for Version posts. Include information about the Version by adding Field shortcodes. Create another View that will be used to display breadcrumb links. Add links to the parent and grandparent single post pages. Place this View in your Content Template.
Use a post relationship filter to create a View of Version posts. Filter to show posts that are children of the current post. In the Loop Output section, include links to each Version single post page. Create another View that shows links to the grandparent Make single post. Use this View to display breadcrumbs. Place both these Views in your Content Template for Model single posts.
Repeat this process for the grandparent Make Content Template, but remove the filter and update the breadcrumb structure to match your hierarchy.
Problem: I would like to be able to set certain posts as "featured posts", so they will appear at the top of sorted results lists.
Solution: Use a custom field to store a value of 1 for all posts, or 2 if the post is "featured". Use the cred_save_data hook to add this value automatically when posts are created by CRED. Filter based on this custom field.
Problem:
Set checked by default (on new post) is not working for CRED Add new post form.
Solution:
As of today, this is a known bug appeared in CRED v1.9.1 and is reported to be fixed soon. As a temporary solution you can Downgrade to Toolset CRED v1.9 to resolve the issue.
Problem:
I have two types of packages - for 15 days and for 30 days.
Each package is another CRED form. I also created 2 forms for creating posts - one for 15 days, another for 30 days.
You need to be able to view a link to one of these forms depending on the package purchased earlier
Solution:
1) When user submit the CRED form A, add a custom field into the package post, setup the field value as "15 days", same as above:
When user submit the CRED form B, add a custom field into the package post, setup the field value as "30 days" https://toolset.com/documentation/programmer-reference/cred-api/#cred_save_data
2) In the single package post, use shortcode [wpv-conditional] to check the field value, then display the what you want
Problem:
Parametric search query takes time even for a few minutes.
Solution:
Updated the Toolset plugins resolved the issue. And make sure that URL parameter prefixes for your View are same as generated by Toolset Views plugin (you can create a new test custom search view to match that).
Problem: I would like to automatically remove all "payment" taxonomy terms from a post when a User edits this post with CRED.
Solution: Use the cred_save_data hook and the wp_set_object_terms function to remove any terms from the 'payment' taxonomy associated with the post being edited.
add_action('cred_save_data', 'my_save_data_action_remove_options',10,2);
function my_save_data_action_remove_options($post_id, $form_data)
{
if ($form_data['id']==2226){
wp_set_object_terms( $post_id, null, 'payment' );
}
}
Problem:
Address field is not working in CRED form and displaying error messages:
“ There is a problem with Array field. Please check CRED form. ”
Notice: Undefined variable: command_field in /home/c///public_html/wp-content/plugins/cred-frontend-editor/application/controllers/field_translation/command/CRED_Translate_Command_Factory.php on line 30
Notice: Array to string conversion in /home/c///public_html/wp-content/plugins/cred-frontend-editor/application/models/field/field.php on line 375
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.
