I noticed that you have moved Toolset views into "Legacy Plugins", I assumed it was because of "Blocks" however when installing blocks there's no option for a VIEW in toolset.
We don't use BLOCks, we use classic as do many people i.e. over 1 million active installations.
Are you not going to support VIEWS long term?
We need to know because if that's the case we will move from Toolset.
We don't want to use WordPress Blocks in our developments.
Views and Blocks are essentially the same plugin, the same codebase, but they have different defaults for the UI.
With either plugin installed you can go to Toolset > Settings and choose which interface you want to use.
Views isn't going anywhere, it's a key part of our offering, but the development is focused on the block interface which is where most product innovation is happening. Some features will affect both, e.g. filtering by fields of related posts, whereas others will likely only apply to blocks, e.g. improving the styling options for the output of Views filter controls.
The topic ‘[Closed] Why is Views a legacy plugin’ is closed to new replies.
