By default, the Toolset Views plugin works with Gutenberg blocks. If needed, you can also enable its legacy mode which is based on shortcodes.
The legacy version of Toolset Views allows you to do a few things that are currently not possible with block-based Views. Most notably, this includes displaying nested Views, displaying a list of taxonomies, and displaying a list of users.
The best thing is that you can use both modes on the same site at the same time.
- Go to Toolset → Settings and scroll to the Editing experience section.
- Select the option to show both the legacy and Blocks interface.
Now, you can access the new Toolset → Views page which is otherwise hidden. It lists all Views on your site and allows you to create legacy Views.
As legacy Views interface uses shortcodes instead of blocks, editors are based on HTML and the editing experience is completely different.
Legacy View’s main settings
Legacy View’s Loop and Loop Item editors
- Edit the page or a post and insert the Toolset Fields and Text block.
- Click the Add Field or View button.
- In the pop-up dialog that appears, scroll to the Post View section and click the name of the legacy View you want to insert.
- In the next step, select additional View options if needed and click the Insert shortcode button.
As the legacy Views workflow is completely different than the block-based one, its documentation is not part of the regular, lesson-based Toolset documentation.
You can find it in the Toolset Views section of our legacy features documentation.
- Filtering Custom Lists of Posts
- Filtering Toolset Views by Dates
- Styling Custom Searches
- Styling Views and Archives
- Adding Custom CSS to Templates, Archives and Views
- Show all related topics...
- Passing Arguments to Views
- Display Dynamic Sources Inside all Text Blocks
- Displaying Form Data
- Displaying a List of Posts on A Map
- Creating Sliders with Dynamic Post Content
- Adding Dynamic Content to Your Homepage
- Creating a View
- Creating Responsive Columns and Grids
- Display Content Conditionally
- Using Third-Party Hidden Fields