Problem:
The toolset_get_related_posts function of the API has a lot of possible arguments, are they all required?
Solution:
The first 3 are required for one-2-many relationships.
For m2m relationships all 8 arguments are required. (We plan to update this to make it easier to pass only certain arguments and leave others as default.)
Problem: I want to get the parent post ID. Post relationships created in the new M2M system use dashes in their slugs, but post relationships migrated from the legacy system use underscores in their slugs. I would like to be able to programmatically determine the relationship slug to get related posts, but the naming convention is inconsistent.
Solution: Use the toolset_get_relationship API to inspect new or legacy migrated relationships, and use the toolset_get_related_posts API to get related posts from either migrated or new relationships.
function be_get_parent_id($atts){
//Get current post object and ID
global $post;
$post_id_current = $post->ID;
$a = shortcode_atts( array(
'postid' => $post_id_current,
'parent' => '',
), $atts );
//get post type
$post_id_current = $a['postid'];
$post_type_current = get_post_type($post_id_current);
//The Post relationship slug to check - NOTE THE NEW SYNTAX WITH - HERE
$relationship_to_query = $a['parent']."-".$post_type_current;
//Set the role the other post type has:
$role = "parent";
//Get related posts with new API, if none, it'll return 0, if any, the ID (hence not 0)
// try legacy method, fallback to new method
$related_post = toolset_get_related_post( $post_id_current, array($a['parent'], $post_type_current), $role);
if (! $related_post ){
$related_post = toolset_get_related_post( $post_id_current, $relationship_to_query, $role);
}
return $related_post;
}
add_shortcode( 'be-get-parent-id', 'be_get_parent_id' );
There are some PHP warning when send submit the Toolset form for editing user with email notification settings:
PHP Warning: array_key_exists(): The first argument should be either a string or an integer in /home/aaronmckeon/public_html/wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/models/CRED_Fields_Types_Utils.php on line 30
Solution:
It is fixed in the latest version of CRED beta plugin 2.0 RC, please update all Toolset plugins to the latest beta version and test again, you can download them here:
Problem: I would like to make a single select taxonomy field optional in my CRED form by inserting a placeholder option before the term options.
Solution: There's not an option to do this in the GUI, but you could use some JavaScript to insert the placeholder option programmatically. Another ticket I worked on recently discussed this approach in some detail: https://toolset.com/forums/topic/cred-module-edit-post-choice-taxonomy-does-not-work/
This ticket also includes some backend validation messages that you may or may not want to include. Let me know if you have questions about this approach.
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.
