Problem:
The user would like to port a legacy view into blocks. And he would like to display assigned taxonomy terms for the post.
Solution:
Currently, Toolset Blocks cannot display dynamically terms data similar to how it displays post fields. To work around it we can use a "Classic" or "Fields and Text" and use the [wpv-post-taxonomy].
Problem:
The user would like to use a slider for an image repeating field. The slider duplicates images when there is a low number than the items of the slider. The user would like to disable this duplication.
Solution:
We cannot disable the duplication of images on the slider, this is expected behavior that ensures the sliding effect of images.
On the other hand, we can implement a custom function that counts the number of items on the images field and display different block for each count (1, 2, 3, >=4)
Problem:
The user would like to use the Toolset portfolio module with blocks.
Solution:
The module is built with the legacy views and is not available with blocks. To work around it, activate both the block and legacy editors for Toolset, then create the portfolio with a legacy view and use it inside blocks with a View block, a "classic" or "fields and text" block.
To enable views alongside blocks, go to Toolset->Settings->General tab, under "Editing experience", choose "Show both the legacy and Blocks interface and let me choose which to use for each item I build".
We do encourage our clients to use blocks instead of views. However, Blocks do not support all features of Views yet. We can then fallback to views. In Toolset->Settings, you can choose either one of them or both.
About Toolset elements, views are meant for displaying lists of posts, from a custom post type. Content Templates, on the other hand, are meant to display one post from a custom post type. Then you can use a view inside a content template or use a content template inside a view, and a content template inside of it, and so on.
