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".
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.
