Skip Navigation

[Resolved] Views Plugin Deprecation questions

This support ticket is created 4 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 3 replies, has 2 voices.

Last updated by Robert 4 years, 11 months ago.

Assisted by: Shane.

Author
Posts
#1623215

Tell us what you are trying to do? Well, I just updated my theme including all my views, content templates, and archive templates. Come to find out that the Views plugin has been moved to legacy support. So I am trying to understand Toolset Blocks. I see some demonstrations of blocks in action however it seems these demos still refer to the term "view" when creating a view using toolset blocks. So I need to understand that create a "view" using toolset blocks, am I still using the legacy views plugin or the toolset blocks plugin? Also, I plan to reuse those new "views" like I currently do.

Is there any documentation that you are following?
https://toolset.com/documentation/getting-started-with-toolset/create-and-display-custom-lists-of-content/
https://toolset.com/documentation/getting-started-with-toolset/

Can you help me to understand how I can properly deprecate my existing views, content and archive templates in order to use the new features of the currently toolset plugins?

#1623221

Also, if I remove the Views plugin, how do I maintain my WooCommerce views?

#1623457

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Robert,

Thank you for getting in touch.

I see some demonstrations of blocks in action however it seems these demos still refer to the term "view" when creating a view using toolset blocks.

Essentially these are still views, just created in a visual manor using the Gutenburg editor.

So I need to understand that create a "view" using toolset blocks, am I still using the legacy views plugin or the toolset blocks plugin?

The Blocks plugin and Views plugin are functionally the same, with the only difference being that Blocks is geared towards users who want to create their views completely visually. So blocks comes with the classic view editor disable by default. This can ofcourse be enabled in our Toolset settings.

The reverse is true, our views plugin comes with the blocks functionality. It's just disabled by default and can be enabled in the settings.

You can still create your views in the classic way if you enable the settings in blocks, so you won't have any issues if you switch to Blocks or use views.

Also, if I remove the Views plugin, how do I maintain my WooCommerce views?

If you remove Views and Blocks, your WooCommerce Views plugin will still function normally and your templates will remain unchanged. However as mentioned the classic view editor will be disabled by default.

You will need to go to Toolset -> Settings and scroll to editing experience to set your editor preference.

Please let me know if this clarifies things for you.

Thanks,
Shane

#1626461

My issue is resolved now. Thank you!