Pro upgrade notice is not dismissed when upgrading via FTP

[raamdev]

If you upgrade Comet Cache Pro via FTP, the Dashboard notice that announces a new version is available does not get automatically dismissed.

There needs to be a routine that dismisses any upgrade notice if the current version installed is detected as the latest version.

[jaswrks]

Estimate .25 days.

[jaswrks]

Related comment: https://github.com/websharks/comet-cache/issues/829#issuecomment-252807069

[jaswrks]

Next Release Changelog:

• Bug Fix: Automatically dismiss any persistent update notifications whenever a new version of the software is recompiled; i.e., don't continue to show an upgrade notice whenever the software has just been updated by a site owner. See also: issue #806 if you'd like additional details.

[jaswrks]

Noting also that these update notifications that are being cleared no longer exist in the current release of the software. The automatic clearing of these persistent notifications is to clear them on old installations of Comet Cache.

[renzms]

@jaswsinc

Built from the current dev branch and ran phing -D project_version=160701 full-build-all to backdate, but no update available shows in the header. Is this the correct way to test this?

[jaswrks]

@renzms You'd need to actually install one of the older builds where that notification was posted to the Dashboard. The newer builds, like those from the dev branch, don't do this, even if you backdate the build. It's still from the newer source code that doesn't post that notice.

[renzms]

@jaswsinc

Thanks!

@raamdev

Confirmed working in Comet Cache v161116-RC / Pro

Tested using Comet Cache 160412 / Pro and upgraded via FTP using Comet Cache v161116-RC / Pro. Update notice is removed after uploading via FTP.

[raamdev]

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 (#806).