Topic Tag: Post-relationship

Problem:
Multiple nested relationships for sports league

Solution:
When you have complex relationship structure and having said that that may be a chance that you many need to use custom code as some point not because of how Toolset relationships are implemented, but because of the data structure based on which you want to implement the solution.

However - the best way I can suggest is you should go and create a test site using one of the our available reference sites available at discover-wp.com and try to implement your structure. This will gives you a chance to work with Toolset post relationships - how it works and also help you to check feasibility about your complex structure and you will be able to know at which point you may need custom code or not.

You can find proposed solution, in this case, with the following reply:
https://toolset.com/forums/topic/multiple-nested-relationships-for-sports-league/#post-911013

Relevant Documentation:

Problem:
Check if parent post exists with Types 3.0

Solution:
You can use [wpv-conditional] shortcode to check if parent exists or not.

For example:

[wpv-conditional if="( '[wpv-post-id item="@relationship-slug.parent"]' ne '' )"]
 
parent exists
 
[/wpv-conditional]

You can find proposed solution, in this case, with the following reply:
https://toolset.com/forums/topic/check-if-parent-post-exists/#post-911756

Relevant Documentation:
=> https://toolset.com/documentation/user-guides/conditional-html-output-in-views/

Problem:

Hi, I would like to create a Post Type for Comments so that

1) comments can be left by visitors after they are redirected to the comments page;

2) and that the comments which they had left for a specific product are displayed below on the product page of this product (I mean finally within the Post Type for this product and not where the comments themselves were left and stored)

Solution:

You can create a custom post type, for example "My comment CPT", setup one to many relationship between post type "Product" and "My comment CPT"

https://toolset.com/documentation/post-relationships/

Then setup a CRED form for user to create "My comment CPT" post:

https://toolset.com/documentation/user-guides/creating-cred-forms/

In single "Prodcut" post, display a view, list related "My comment CPT" posts.

https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/

Relevant Documentation:

https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/

Problem: I would like to get the parent post Course of the current post Product using the new Post Relationships API, but it doesn't seem to be working. I have tried both of these syntaxes:

$course = toolset_get_parent_post_by_type( $product, 'course' );

$courses = get_posts( 
        array(
            'post_type' => 'course',
            'numberposts' => -1,
            'toolset_relationships' => array(
               'role' => 'parent',
               'related_to' => $product_id,
               'relationship' => array( 'course', 'product' )
            ),
        )
    );

Solution: In this case, the relationships were created in the new system, so toolset_get_parent_post_by_type is not appropriate. The toolset_get_parent_post_by_type API is intended for use with legacy relationships, or relationships that were migrated from the legacy system. When specifying the relationship to query, the array syntax is intended for legacy relationships as well. The best approach in this case is to use the toolset_get_related_posts API, and the relationship slug instead of the post type slug array:

$product = get_post(69);
$course = toolset_get_related_post( $product, 'your-relationship-slug', 'parent');

Relevant Documentation:
https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/