The issue here is that the user has a view that lists multiple post types but want to style each post type differently
Solution:
Here is how I achieved this:
Create your view and ensure that you've selected the option "Allow multiple Post types".
Select the post types that you want to be included in the view.
Ensure that you've set the sorting option on the view. See Screenshot. You will need to do this so the posts types are listed together.
On the view loop section you will add a conditional block for your first Post Type. Setup your conditionals as per my conditional screenshot, where you will select the Post Source, in a case of a multiple post type view you can leave this unchanged as it will set the correct information once the view is displayed. However for the source you will select Post Type, then the comparison is done for a static value and just add the post type slug.
In that conditional block you will setup how you want your post type A to display.
Using the block navigator tool. Select the view loop and then add a new conditional block to that loop and repeat steps 4 and 5.
When you are finished you can double check your structure and ensure that all your conditional blocks are within the view loop
The issue here is that when the user activate our Toolset blocks plugin their post content on the frontend dissappears.
Solution:
This is actually a common issue where there is an empty content template assigned to the custom post type that is not showing on the frontend.
To verify this go to Toolset -> Content Templates and edit the template that is assigned to the post type thats not showing up.
If it is indeed empty and you don't wish to use the content template then you can go ahead and delete it.
Should you want to use the content template to customize the output of your posts on the frontend then I would recommend following the instructions in the documentation below.
Problem: I would like to display a list of custom search tag filters as formatted text links. When a User clicks one of the text links, the search results in the View should update.
Solution: Use the "radio" input type and apply custom CSS to hide the radio button and apply styles to each label element to achieve the text link "pill" effect.
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.
