-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Update Available" shows in header but no update shows in Plugin updater #829
Comments
I suggest that we simply remove the "(update available)" from the plugin options menu to resolve this issue. Now that we're integrating with the WordPress Update mechanism, there are already plenty of places that will indicate an update is available. I don't think it's necessary to also show it on the plugin options page. |
Next Release Changelog:
|
@jaswsinc Attempted testing this, see comment here |
Comet Cache v161119 has been released and includes changes from this GitHub Issue. See the v161119 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#829). |
While testing the new features: ManageWP Compatibility + Automatic Updates (see: Comet Cache v160908-RC (Release Candidate), I observed an inconsistency with the update notifications. In the Plugin Options of Comet Cache Pro the header would say update available, but no update for the plugin would show in the Plugin updater list. By extension, it did not appear in the ManageWP Dashboard for list of Plugins to be updated.
Steps to reproduce:
release/160908
Comet Cache Pro branch, then runphing -D project_version=160701 full-build-all
Comet Cache Pro v160701
Observed Behavior:
v160709
)."Update Available" in header:
No update in Plugins list
ManageWP Dashboard:
Check Again
via the Updates list would sometimes cause it to trigger the update, other times notExpected behavior:
The text was updated successfully, but these errors were encountered: