Skip to content
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

Comet Cache v160908-RC (Release Candidate) #828

raamdev opened this issue Sep 8, 2016 · 4 comments


Copy link

commented Sep 8, 2016

General Availability Target Date: September 14, 2016



Reporting Issues / Feedback

Please report any issues or feedback related to this Release Candidate using this GitHub issue. Please post a comment below with details.

If you are reporting a UI-related issue, please include a screenshot.

If you are reporting a bug, please provide list of steps to reproduce and if the bug is related to an existing GitHub issue, please provide a link to that GitHub issue as well.

Reported Issues to Fix

None at this time.

@raamdev raamdev added the todo label Sep 8, 2016

@raamdev raamdev added this to the Next Release milestone Sep 8, 2016


This comment has been minimized.

Copy link

commented Sep 14, 2016

Update on testing for Comet Cache v160908-RC

New Feature (Lite): The Clear Cache button is now available in the Admin Toolbar for the Lite version of Comet Cache. - Tested works as intended.

Bug Fix: In some scenarios Comet Cache might produce a false-positive "Warning: mkdir(): File exists" message when checking if the cache directory exists. - Did not encounter this issue

Bug Fix: Fixed a bug where upgrading from v160521 would result in the Client-Side Cache option being reset to the default (disabled). If you enabled the Client-Side Cache at some point, now is a good time to double-check that it's still enabled. - Tested client-side cache both options, to make sure option sticks and saves

Compatibility / Bug Fix: The automatic Clear Cache routines that cleared the entire cache automatically whenever WordPress Dashboard → Settings → General was updated, were being too aggressive and not taking into consideration other plugins that might also be using the same options-general.php URL. - Tested changing General Settings and changing settings from Autoptimize. Changing major Settings in the General tab cleared the cache. Changing settings in Autoptimize did not.

UI Enhancement: Adjusted option page font styles for WordPress v4.6 to better match existing style. - Nice font, goes with the default look of WordPress 4.6.1 Dashboard

ManageWP Compatibility (Pro): Comet Cache Pro is now compatible with ManageWP, a service that allows remote management of multiple WordPress sites. Comet Cache Pro Plugin Updates will now appear in the ManageWP dashboard and, assuming you have saved valid license credentials in Dashboard → Comet Cache Pro → Plugin Options → Update Credentials, you will be able to upgrade Comet Cache Pro remotely from the ManageWP Dashboard. - Signed up for free ManageWP account and was able to update. Noted inconsistent behavior in report here


This comment has been minimized.

Copy link
Contributor Author

commented Sep 16, 2016

I verified the new updater system works as expected on Multisite. Tested on WordPress v4.5.3


This comment has been minimized.

Copy link
Contributor Author

commented Sep 17, 2016

@jaswsinc writes...

I tested Comet Cache Lite and Comet Cache Pro on Nginx running PHP 7. No problems.
Running here w/ the HTML Compressor enabled as well. I also tested Static CDN Filters. No problems.

@raamdev raamdev closed this Sep 17, 2016


This comment has been minimized.

Copy link
Contributor Author

commented Sep 17, 2016

Comet Cache v160917 has been released and includes changes from this GitHub Issue. See the v160917 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 (#828).

@wpsharks wpsharks locked and limited conversation to collaborators Sep 17, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.