Problem: I am trying to use a meta_query with the post relationships API toolset_get_related_posts, but it doesn't seem to be filtering as expected.
Solution: Some complex meta_queries, like using "IN" or "AND" with more than one term, fail with the post relationships API. Instead, you should use a standard WP_Query and add the toolset_relationships clause:
Problem: It seems like the new caching system will require manual intervention to update the cache any time content changes.
Solution: An individual View's cache is invalidated any time a post that could appear in the View results is added or edited. Manual intervention is not required here.
Problem:
We are using toolset_get_related_post and would like to specify the post status of the posts this function should return us.
How can we do this?
Solution:
toolset_get_related_post will Retrieve an ID of a single related post.
That posts post_status can be defined in the function, so if you want a specific status, you would have to specify it.
You should pass an array of post status values or a string with one or more statuses separated by commas.
The passed statuses need to be among the values returned by get_post_statuses() or added by the toolset_accepted_post_statuses_for_api filter.
Example:
$role_name_to_return = '';//parent or child
$args = array();// see args array - Additional query arguments.
$post_status = 'publish,draft';//you can only use those from https://developer.wordpress.org/reference/functions/get_post_statuses/ or passed to toolset_accepted_post_statuses_for_api
$writer = toolset_get_related_post( $post_id, array( 'one-side', 'other-side' ), $role_name_to_return, $args, $post_status );
Problem:
Toolset Maps uses a custom database table called _toolset_maps_address_cache. That table has a column named point, which is a reserved word of mySQL 5.7
This alone is not an issue because MySQL is context-sensitive in this case and understands when we are referencing the column.
However, due to a bug in mysqldump, it can happen that invalid data is used even though the table format is pretty strict, and later it can lead to issues when exporting and importing database tables to other databases.
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.
