Problem: I have some post relationships custom code in place on my site, and the migration process indicates that it may cause problems.
Solution: It's a good idea to check with support for migrating relationship code. This code should be okay, because we built in backwards compatibility for this particular case.
Problem: I have a Form that triggers an email notification. I send the notification to an email address that is stored in a parent post's custom field, by using the CRED API cred_notification_recipients. Since updating to Types 3.0, the email notifications are not sent as expected.
Solution: Update the code to work with the new Post Relationships API, and ensure the child post status is not "private".
Problem: I would like to send a CRED notification to an email address that is stored in a custom field on the CRED post's parent post. How can I access that parent post field in the CRED notification recipients configurations?
Solution:
The most flexible, preferred method today is to use the CRED API hook cred_notification_recipients to modify the "to", "cc", or "bcc" of the notification email.
Within the callback, you can figure out the parent post by calling get_post_meta on the child post, and accessing a hidden field that relates a parent post ID to the child post. The name of that field follows the format "_wpcf_belongs_" + parent post type slug + "_id". So if your parent post type slug is "event", then the postmeta key is "_wpcf_belongs_event_id" and the code is:
again on the parent post to retrieve the email field value. Types fields use the prefix "wpcf-" in the postmeta table, so if your email field slug is "email-address-of-organizer" then the code would look like this:
Now the variable $email_of_organizer contains the email address from the parent post. Use that to modify the code sample on the API documentation page to fit your needs.
Problem: I would like to use a CRED generic field to display users, and modify the author of the created post to match the selected user.
Solution: Using a View to create options for a generic field is not a supported feature of Views. The steps other users have had luck with are described below, but not guaranteed to work.
add_action('cred_save_data', 'my_save_data_action',10,2);
function my_save_data_action($post_id, $form_data)
{
// if a specific form
if ($form_data['id']==131)
{
$my_post = array(
'ID' => $post_id,
'post_author' => $_POST['change_post_author']
);
// Update the post in the database
wp_update_post( $my_post );
}
}
Problem:
One Post Type has 2 kind of repeatable Fields assigned.
You want to display the First repeating instance of Field A along line with the first repeating instance of Field B
(etc)
An example can be wpcf-name and wpcf-phone
Solution:
1. You set up 2 Repeatable Fields, "phone" and "name"
2. Pay attention that each item has a pendant, means, when you add a Phone go ahead and add a Name as well.
3. Once you populated this data, create a View and query the Post type in question.
4. In the Loop, use the Wizard to create a Table and use the below approach to insert your above created Fields:
Sort child posts by custom fields of parent post type.
Solution:
There isn't such kind of built-in feature within Toolset plugins, Toolset Blocks/Views plugins are using WordPress class WP_Query to query posts, see WP document:
‘meta_value‘ – Note that a ‘meta_key=keyname‘ must also be present in the query.
That means you can only sort the results by custom fields of post type(“Institutional position”) you are querying, you can not sort the result by custom fields of other post type(“People”).
As a workaround, you can try with a nested views, for example:
Problem:
Include parent custom field value in form notification
Solution:
You can use the Toolset form hooks to add parent field using custom place holder:
- cred_body_notification_codes
- cred_subject_notification_codes
Problem: I would like to include the parent post title in an email notification triggered by a Form that creates private child posts. Unfortunately the %%PARENT_POST_TITLE%% placeholder is not working as expected.
Solution: The best solution here is to create custom placeholders using the Forms API, and use the post relationships API in those placeholders to display information from the parent post.
Then in your notification you can use them like other placeholders:
Parent post title: %%FIXED_PARENT_TITLE%%
Parent post link: %%FIXED_PARENT_LINK%%
In your case you would change @book-chapter_parent to match your post relationship slug. Yours would be @tessuti_richiesta-info_parent. Notice that the "dot" usually seen in the post relationship slug is replaced with an underscore here.
Problem:
I want to grant or revoke access to certain content on a single post and user basis.
Is this possible using Toolset?
Solution:
Partially it is natively possible using Access, but for example, to allow or disallow access to single fields by posts by users, you'll need some custom code.
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.
