Problem:
I would like to understand what is the difference between Toolset Layouts and Toolset Views Content Template.
Solution:
Toolset Layouts (with its Template Layouts and Content Layouts) is different from Content Templates in the editing mode mainly.
Toolset Layouts uses a Drag and Drop Bootstrap backend and front end Layout editor, based on rows and cells, whereas Content Templates either are based on HTML and ShortCodes or a Page Builder's design like Gutenberg.
Note, you can create Content Templates with Toolset Views OR Toolset Blocks, but if you use Toolset Blocks you'd not want to use Toolset Layouts generally.
Problem:
We see that we can switch screen size when editing a post with Toolset Blocks, and also several blocks offer what seem screen size dependant settings. How to use this feature?
Solution:
In all blocks Inspector, if you see the Screen Size icons, switching to another screen size and making different settings to the particular block control, will apply those settings only on the specified (current active) screen size
However, this feature does not allow to create a fully different *template* for each screen size, only single block settings can have different settings for each screen size, but you can't change a whole template layout on a specific screen size
Hence edits made IN the post editor, even if made in particular screen size will apply to ALL screen sizes!
The Single field Block allows choosing from different defined inputs, and outputs. So for example, only the Post Link will produce a link (clickable) but not the Post Title (this can be set in the Inspector of the Block)
But it does not give you the "raw" data which you can use to craft any kind of output with.
If you need more control, you'd have to use a "Fields and Text" Block.
There, you can control with much more granularity what is output and how the data is populated.
You can then use the Editor's "link" features to make your content clickable.
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].
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.
