Problem: I have several post types arranged in a combination of one-to-many and many-to-many Views. I would like some assistance creating a View filtered by Clients, and showing information about Tracks, Aliases, Pitches, Writers and Writer Shares.
Solution: Create a View of Pitches, filtered by parent Clients. In the View of Pitches, use a Content Template to access the parent Alias, where you can access the grandparent Track. Use the id attribute as needed to access custom field values or post information. Use a View of Writer Shares, filtered by parent Track, set by a shortcode attribute. In the Loop Output of that View, you can include information about the Writer Share and its parent Writer post. You can place this View in your Content Template to access the grandparent Track ID, and pass that into the View's shortcode attribute filter.
Problem: In the M2M betas, I am only able to connect posts in the post relationship panel of the post editor when logged in as Admin. Other roles are unable to connect posts this way.
Solution: This issue has been reported to our developers and will be addressed in a future beta release.
Problem:
After installing a Reference Site using the Framework Installer, there is a message to "Disable Framework Installer and customize this site". Is it safe to do so?
Solution:
Yes.
The Framework Installer plugin is solely for setting up the Reference Site and importing its content. Once complete it is no longer required and should be deactivated.
Problem:
A View queries intermediate posts so as to be able to display fields from a parent post. How to delete relationships or edit a relationship (e.g. assign a different parent)?
Solution:
The context of the View which queries the intermediate posts in the relationship means that you can use the normal cred_delete_post_link or toolset-edit-post-link shortcodes to delete or edit the relationship.
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.
