[Resolved] Views plugin erroneously reports no valid subscription in Plugins list
This thread is resolved. Here is a description of the problem and solution.
Problem:
Views plugin erroneously reports no valid subscription in Plugins list
Solution:
Updating the Views plugin to 2.6.3 did resolve the problem on the affected sites.
Relevant Documentation:
This support ticket is created 6 years, 4 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.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Since the last set of Toolset updates, three of my four TS sites display the error shown in the attached image for the Views plugin in the Plugins list. Checking for updates on the commercial tab doesn't resolve it. Unregistering and re-entering the key doesn't resolve it. Generating and registering a new key doesn't resolve it. This is a Lifetime license, in case that makes any difference.
Well - we have published new version from almost all Toolset plugins.
Could you please update ALL Toolset plugins to it's latest official released version and try to resolve your issue.
*** Please make a FULL BACKUP of your database and website.***
You can download latest Toolset plugins from your accounts page:
=> https://toolset.com/account/downloads/
Updating the Views plugin to 2.6.3 did resolve the problem on the affected sites.
It appears possible that the problem was due to some confusion over the "Views Lite" plugin. Perhaps it, or possibly just some of its metadata, was pushed out to regular Views users with 2.6.1, when the error described started appearing. The attached images, all from the same system prior to the 2.6.3 update, suggest that the affected systems were confused over whether "Views" or "Views Lite" was installed.
In any case, the confusion seems to be over. Thanks for addressing this.