[Resolved] attempting to update Types from 2.2.23 to 3.0 always goes to 2.3 instead
This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the user is trying to update to Types 3.0 from the backend but they are updated to version 2.3 instead. Solution:
This issue was actually fixed in our Types version 2.3.1 and should now give the correct update.
This support ticket is created 6 years, 7 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.
I am trying to:
Update 16 client websites to Types 3.0. Types plugins are properly registered on all sites, although I often have to click on the 'Check for updates' link on the 'wp-admin/plugin-install.php?tab=commercial' page to get rid of the prompt to register the plugins.
I expected to see:
Types updated from 2.2.23 to 3.0.
Instead, I got:
Types updated to 2.3. This has now happed on more than half of the sites I'm trying to update, and it's proving to be a huge time sink. If I update Views first, that update succeeds, but the Types update still always goes to 2.3. If I update Types first, the Views update spins forever, and Views can no longer be updated.
I get the same result regardless of whether I use the 'wp-admin/plugin-install.php?tab=commercial' page, or update using the WordPress built-in plugin update process. Please see attached screenshots from two sites where I attempted the updates. On one I did Views first and on the other I did Types first.
A related issue is that with the update of Types to 2.3, the 'wp-admin/plugin-install.php?tab=commercial' page is no longer available, but the site also does not complain about the plugins not being registered.
Not sure why your plugin is updating to version 2.3 but you can manually download version 3.0 from the downloads page below and upload to your site using FTP. https://toolset.com/account/downloads/
I'm not sure either, but it happened on 14 of 16 websites so far (haven't tried the last 2 yet)! Don't you think this is worth investigating as a possible bug in the update process? It's really a huge pain in the butt not to have the auto-update work correctly on so many sites. Now, for all those sites, I have to manually remove the offending version, upload the correct version, and fix the registration. This also means a couple of minutes of downtime for each site.
I hope you'll take this seriously and investigate further, and consider offering a fix for sites that have erroneously updated to 2.3 when they were in fact properly licensed and should have updated to 3.0.
Please see from the screenshot that, after Types erroneously goes to version 2.3 instead of 3.0, there's no longer a Registered link next to Views. Also, and as mentioned above, the 'wp-admin/plugin-install.php?tab=commercial' page no longer works.
As I explained and showed in the screenshots, regardless of whether I update from the commercial tab, or from one of the standard WordPress update tabs, I get the same result, i.e. Types updates to 2.3 every time.
I've got news from our team that this issue will be resolved in Types 2.3.1 so once that release is made then the correct plugin will be directed to customers.
I don't have an ETA on this however you can do the update manually by downloading the 3.0 plugin from our downloads page below and upload it using FTP. https://toolset.com/account/downloads/
Yes, I've run the Types 2.3.1 update on several sites and was able to update further to Types 3.0. This also resolved the issue of no longer being able to update to Views 2.6 on those sites.