Skip Navigation

[Resolved] How to move from Toolset Views to Toolset Blocks.

This support ticket is created 5 years, 1 month 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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 5 replies, has 3 voices.

Last updated by jarrodM 5 years ago.

Assisted by: Nigel.

Author
Posts
#1409007

I just read the update: https://toolset.com/2019/11/toolset-views-becoming-toolset-blocks/ and it seems to make sense. I used the old Toolset Blocks to build most of the views and content templates. How will all this work? I now see that Toolset Blocks is deactivated...here is a screenshot: hidden link

I just want to make sure that I know how this will work moving forward. Does that make sense? What will happen with the Views I built? Do I need to activate Toolset Blocks and update the views?

#1410743
Screen Shot 2019-12-15 at 4.01.14 PM.png

Hi, since you've already started this project and you have most of the work done, you'll continue to use the Toolset Views plugin. The Views you already created will keep working, there's nothing you need to update or migrate. There are settings in Toolset > Settings > General that allow you to use the block-style editor or the legacy editor - or even show both and allow you to choose for each element you build.

You can leave the Blocks plugin deactivated on the current site. We recommend trying out the Blocks plugin instead of Views on a new site so you can see what's possible in the new workflow. More developer-level customization is possible now with Views, but Blocks might make it easier to get a nice site up and running quickly. You may find different practical uses for the two systems in the future.

Does this help clarify? Let me know if you have any doubts.

#1412513

Yeah I think that helps. So you can't or shouldn't activate both at the same time? Even if I wanted to migrate to the Blocks version?

#1413383

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi there

Let me jump in here if I may.

The code base for the Toolset Blocks plugin and the Views 3.0 plugin are virtually the same, they just have different default settings for which UI you are presented with when creating Views, and as Christian pointed out you can effectively move between the two variants by updating the settings for which editor experience you want.

If you try to disable both Views and Toolset Blocks at the same time, one of them will automatically be disabled.

If you prefer to use Toolset Blocks plugin instead of the Views plugin (although there really is very little difference) you could de-activate Views, activate Toolset Blocks, and then go to the Toolset settings and change the editor experience to show both, so that you can continue to edit your existing Views with the classic editor you used to create them, but you can also make new Views directly in pages when editing with the block editor.

#1415371

I see what you mean. I am testing it on a development environment. Very cool. A little more restricted just because you can't use custom HTML but a much more visual and consistent editing feel. Well done! I'm sure that was an extraordinary amount of work.

#1415373

My issue is resolved now. Thank you!