In the beta version of Types plugin, new API filter "toolset_build_intermediary_post_title", it only works with newly created intermediaries. Any previously created intermediary's title remains unchanged.
Do you have any advice on how to make this change retroactively, incase the need arises?
Solution:
You are right, the filter hook "toolset_build_intermediary_post_title" only works when you create new intermediaries, it won't work when you edit an existed intermediary, you will need to edit them one by one manually, see the workaround I mentioned in your previous thicket:
In the latest beta version of Types plugin, there is new many-to-many relationship, I am asking for / hoping for the titles of the intermediary post types to either:
A) Be accessible in the metabox when adding a relationship to posts
B) Auto generate using the parent post titles and not their post Ids
Solution:
Q1) Be accessible in the metabox when adding a relationship to posts
There isn't such a feature within Types Beta version. Currently, you can try this:
When you edit a single parent post, you can use the button "Connect existing XXX", see our document:
Q2) Auto generate using the parent post titles and not their post Ids
At the moment, we don't support that in the GUI in a very nice way, but I think we can open that to debate
and the client should be already able to use the toolset_build_intermediary_post_title filter:
/**
* toolset_build_intermediary_post_title
*
* Allow for overriding the post title of an intermediary post.
*
* @param string $post_title Post title default value.
* @param string $relationship_slug
* @param int $parent_id
* @param int $child_id
I am moving a site over from using CMB2 to take advantage of the upcoming relationships API.
It contains repeating fields but using CMB2, they are just stored as a serialized array in post meta.
From reading the documentation, it seems Toolset stores them within a hidden CPT, and all I can see is tutorials for accessing them by using a View/GUI.
I wasn't intending to use Views for this project. Do you have documentation for how to access them with API Functions?
Solution:
There isn't exact document for the Repeating Fields Groups API, but it is using child post type to store the Repeating Fields Groups , so you can use function toolset_get_related_posts() to get the child posts, then display custom field of each child post, for example:
1) Create a Repeating Fields Groups "my-fields-group" in post type "my-cpt", add some custom field into the field group
2) In the your theme file single.php, add below codes:
$child_posts = toolset_get_related_posts(
get_the_ID(), //Post to query by.
'my-fields-group', //Slug of the relationship to query by
'parent', //Name of the element role to query by.
100, //Maximum number of returned results
0, //Result offset
array(),//Additional query arguments
'post_id', //Determines return type
'child' // which posts from the relationship should be returned
);
var_dump($child_posts);
As you can see the last parameter is "child", it will be able to query the child posts of current post.
Still not able to query the intermediate post types with the Beta version of Types plugin 2.3-b4, right?
Solution:
With Types plugin version 2.3-b4, you will be able to query the intermediate post types with the Beta version of Types plugin 2.3-b4, you can download it here:
Intermediate CPT custom field slug
wpcf-purchase-link
So on my Music Release CPT theme template I want to:
1. Display the purchase link from the intermediary cpt that links the Music Release and the Music Store
2. Display the logo from the Music Store CPT linked to in the relationship, through the intermediary (music-release-music).
Solution:
Types 2.3-b3 (beta 3) indeed didn't include the new public API, it was released only yesterday with 2.3-b4, you can download it here: https://toolset.com/account/downloads/
Choose channel: Beta
- originally, it was intended to be released both 2.3-b4 and 2.2.22 at the same time, but there have been delays (glitches on the part of the beta version)
And you can use function toolset_get_related_posts(), like this:
$intermediary_posts = toolset_get_related_posts(
get_the_ID(), //Post to query by.
'music-release-music-store', //Slug of the relationship to query by
'parent', //Name of the element role to query by.
100, //Maximum number of returned results
0, //Result offset
array(),//Additional query arguments
'post_id', //Determines return type
'intermediary' // which posts from the relationship should be returned
);
I am just wondering, with Gutenberg around the corner, what the plan is for Toolset?
Do you know yet, if you will be sticking with Metaboxes underneath the primary gutenberg editor, or whether you will be converting your Types custom fields into Blocks, and using Gutenberg Block Templates attached to Post Types, as opposed to field groups?
Solution:
Toolset is fully integrated with the Gutenberg. Take a look at Toolset’s Blocks Library to learn more about each block.
Visualisation de 14 sujets : 1 à travers 14 (sur 14 au total)
Problèmes connus et leurs solutions
Nous documentons les problèmes connus et leurs solutions dans Toolset erratas. Pour gagner du temps, vérifiez d’abord dans cette rubrique si le problème auquel vous êtes confronté est un problème connu. Cette liste est volontairement courte. À chaque publication d’extensions de Toolset, nous nous efforçons de résoudre tous les problèmes connus.
Politique d’assistance
Le personnel Toolset vous guidera volontiers pour utiliser correctement les extensions Toolset, vous fournir les informations dont vous avez besoin, vous aider à résoudre les problèmes et vous conseiller quant aux meilleures pratiques.
Merci de veiller à ce que chaque ticket d’incident ne référence qu’un seul incident.
