Skip Navigation

[Resolved] Toolset Updates for legacy products not pushed anymore?

This support ticket is created 4 years 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)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by smileBeda 3 years, 11 months ago.

Assisted by: Christian Cox.

Author
Posts
#1849635

Hello there!

I have a new site to admin and as most of the sites, it uses Toolset since a few years, hence is mainly built on/with Toolset Views, and not with the new(er) Blocks.

Working myself into the site, I noticed the user still had Views 2.9.2 installed.
It surprised me, checked why comes, and saw no update push notification or else even after "check for updates" repeatedly was ever shown to the user.

I deregistered the site from the clients toolset account and registered it with mine, and checked the installer again.

At this point I noticed, Toolset Views is not anymore offered in the installer.
However Toolset WooCommerce Views is!

Now, I suspect since the Views plugin is not anymore part of the installer, it also does not anymore push updates?
Note, the existing plugin version on this site is 2.9.2, so there would still be room to update for Views 3.3.2 which is the last version of legacy Views. Of course I can install it manually, but the user himself practically never was notified about any update.

What I am faced now, generally and with this user, is (as before) again the question "will it keep working"?
Is it safe to use?
What should we do/recommend?

Since by now Views is definitely removed from the installer, and by what seems also does not push the updates it would have available - should such users start to rethink?

It is also confusing for them (the users) because they now have available (in the installer) Toolset Blocks, but not Views, but then WooCommerce Views is available - which I believe was renamed to WooCommerce Blocks officially?

So this is all a bit confusing for these users, and I am not so sure what I can tell them in regards of "don't worry keeps working".

A year ago - having Views still in the installer and blocks just in its baby shoes - I would have safely skipped this question and still many users will simply not be able to use Blocks instead of Views.
However, with Views gone from the installer and also not pushing updates to its older versions - I would like to have a confirmation to what should be done.

Keep using Views, yay or nay?

I am not talking about new sites - but about the sheer amount of existing sites built over the years with Toolset - there are ore than one would expect 🙂
I am also not talking about the fact that almost none of these users will switch to Blocks, for now.

But preparing for it is a necessary step if Toolset states clearly that this is how Toolset will proceed.
At some point an outdated and not maintained plugin will just become a security risk.
We need a message from Toolset, what we can expect about Views in the coming years, and it seems the message sent is "we moved on to Blocks", which is OK.
However the question remains how urgent is a migration, or looking even for new solutions, for existing users?

It might be a hard decision for some to take but at the end if we can base our planning on official words of Toolset, we won't plan for nothing.

I hope you understand the core concern about it.

Thanks for a answer that we can pass on to eventual customers and integrate in the decision making.

#1849891

Hello Beda,

At this point I noticed, Toolset Views is not anymore offered in the installer.
However Toolset WooCommerce Views is!

As far as the Installer goes, the intention is to move the legacy plugins like Views into a separate tab in the Installer interface. The logic behind this is that new clients are checking all the checkboxes when installing Toolset plugins, and downloading unnecessary plugins (both Blocks and Views), leading to confusion. By moving legacy plugins into a separate tab, we hope to prevent this confusion. Our developers have not yet implemented this tab, but that is on the roadmap.

However, I have also noticed that now in the Installed Plugins page, Views updates are no longer pushed and manual update of the Views plugin is necessary. Let me ask 2nd tier about this, and see if it's something we can easily fix.


What I am faced now, generally and with this user, is (as before) again the question "will it keep working"?
Is it safe to use?
What should we do/recommend?

The official answer is yes, we intend to keep supporting Views as long as our clients use it. So yes, it is safe to use and continue using for the foreseeable future.

#1884925

I think this was solved in any of the previous updates as I can now see views updates again.

Thanks also for the reassuring statement, Christian.

Regards,
Beda