Skip Navigation

[Resolved] Alternative to block editor for Views?

This thread is resolved. Here is a description of the problem and solution.

Problem: I would prefer to use the shortcode editor to create Views. I would prefer not to use the Blocks Editor.

Solution: You can enable the legacy Views editor and/or Block editor in Toolset > Settings > General tab > Editing Experience.

This support ticket is created 4 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 3 replies, has 3 voices.

Last updated by joonaN 4 years, 1 month ago.

Assisted by: Christian Cox.

Author
Posts
#1855843

Do I have to use the Gutenberg block editor to build Views? I absolutely, unequivocally HATE it with a passion. I can not believe anyone (WordPress.org) published this garbage software to the public and that people actually use it willingly.

I imagine that Toolset is perhaps trying to make the best of a terrible UI by releasing Toolset Blocks, but building Views this way is painful, and so full of bugs. I find it practically unusable.

Because my TS loop currently has around 200 store items in it, editing the View means that this loop is constantly regenerating in the block editor, and there is a constant "processing server request" message and the page is incredible slow to update, if it updates at all. Combine this with the most terrible system ever devised of navigating between elements on the page, and the whole thing is a mess. It is full of so many bugs and limitations I don't have time to list them all.

I loathe it and don't want to use it. But I do need to build Views.

Toolset was SOOO much better before Toolset Blocks ruined it.

#1855845

Hi, if you'd prefer not to use the Block editor to design Views and WordPress Archives, you can use the legacy Views editor even with the Toolset Blocks plugin active. Re-enable the legacy Views editor by going to Toolset > Settings > General tab. There is an option to enable both the legacy Views experience and the block editor experience in the "Editing experience" section. This will reactivate the Views menu option and give you the option to choose the legacy code editor with the customary Views shortcodes, or the Blocks editor. While the Blocks editor is great for many simple sites, the legacy Views editor is still quite powerful and useful for more advanced Users. You can choose to edit Content Templates and/or WordPress Archives in the legacy editor as well, if you want.

You can still use all the Views Shortcodes as documented here: https://toolset.com/documentation/programmer-reference/views/views-shortcodes/

Let me know if you have additional questions about that.

#1857115

Ok now I see what you mean. I was thinking I could edit my existing Block-built View in the old editor but it looks like I need to re-create it. That's still better than using the block editor.

My issue is resolved now. Thank you!

#1860101

I would just like to comment that I totally agree with Joe H.

These days I'm afraid to build anything with Toolset, because Views might not get the development attention it deserves. Building anything in Toolset Blocks offers way less control over the code, which is why I've been looking at alternative solutions ever since you stated that you would be focusing on Blocks instead of Views. I don't support this decision. As of now, there is no good option to replace Views. W4 Post List is the option best so far, and frankly, if it had better custom field support, I would've abandoned Toolset a long time ago.