Problem: I have a checkboxes group custom field and I would like to display a different field if one of the checkboxes is checked. I tried nesting one Types field shortcode inside another one, but it produces inaccurate results.
Solution:
Use conditional HTML to test that checkboxes field group's selected values against a known array:
[wpv-conditional if="(CONTAINS(ARRAY([types field='pdb-areas' output='raw'][/types]),'some-value'))"]
<tr>
<td width="321"><strong><em>Markedsføring:</em> [types field="company-name-short"][/types]'s Facebook side</strong></td>
<td width="321">[types field="company-name-short"][/types] har oprettet en side på Facebook for markedsføring og for skabe et online fælleskab omkring [types field="company-name-short"][/types].</td>
</tr>
[/wpv-conditional]
Problem: I have some questions about the toolset_get_related_posts API.
- I'm querying for child posts. Why do I query_by_role "parent"?
- If the result of the API is an array with one post, how do I access that one post without a foreach loop?
- Can you update the documentation to be more helpful?
Solution:
- You should use query_by_role "parent" when the known post is the parent post and you want to retrieve child posts.
- You can access an array item by zero-based index using the syntax here:
$item = $array[0];
- I've asked for some documentation updates here and our team will make the necessary improvements.
Problem:
The issue here is that the user wasn't able to delete their custom field groups.
Solution:
In this case it seems to be a case of Ghost entries. What I would recommend that you do is to disable the Types plugin and enable it again and see if the field groups that you were trying to delete are still there.
Problem: My custom post type is a child of two parent post types. I would like to filter my View of child posts by multiple parents, but the GUI only allows one post relationship filter.
Solution: You can use the wpv_filter_query filter to extend the meta query produced by your View. Child posts are related to parent posts in the postmeta table using the key format "_wpcf_belongs" + parent post type slug + "_id". Example:
Problem: Conditionals are not behaving as expected. If I add or remove content inside the conditional tags, the behavior of the conditional is different.
Solution: Add this line to your wp-config.php file:
Problem: When editing a child post with CRED, if I deselect the parent post and submit the form I can see that _wpcf_belongs_parentslug_id = 0 in the database. However, if I perform the same change in wp-admin, _wpcf_belongs_parentslug_id is completely deleted for this post. I have a conditional set up that tests whether or not the _wpcf_belongs_parentslug_id field exists, and it's failing because 0 is not the same as not exists.
Solution: For now, it's probably best to work around this discrepancy because relationships are changing in the very near future.
Problem: I would like to create a custom search View that I can place on the single post of my top-level hierarchical post type - the Grandparent post. In that search View I want to show a filter where the User can select any posts of the second-level post - the Parent post. The matching third-level posts - the Child posts, should appear beneath the search form.
Solution: In order to accomplish a parametric search of hierarchical post types like this, you must use URL parameters to predefine any level of the hierarchical relationship. If you do not want to include these parameters in your site links, you could consider a custom approach that redirects Users from the clean URLs to the parameterized URLs.
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.
