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 Pro v161223-RC (Maintenance Release Candidate) #863

Closed
raamdev opened this Issue Dec 23, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@raamdev
Copy link
Contributor

raamdev commented Dec 23, 2016

General Availability Target: December 26th, 2016

Note: This is a release candidate for a Pro maintenance release.

Downloads

Changelog

  • Bug Fix (Pro): Resolves error Unable to determine UA info directory location when upgrading to latest release. See Issue #862.
  • Bug Fix (Pro): Enhancing compatibility with InfiniteWP, ManageWP, and other remote management tools for WordPress. See Issue #862.
  • Bug Fix (Pro): Incorrect time calculations whenever load average checks are enabled in Comet Cache configuration options. See Issue #853.
  • Cleanup: Removed an old API call that checked for a newer lite version. No longer necessary.

See also: Comet Cache Pro v161223-RC Release Announcement

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 Dec 23, 2016

@raamdev raamdev added this to the Maintenance Release milestone Dec 23, 2016

@renzms

This comment has been minimized.

Copy link

renzms commented Dec 24, 2016

@raamdev

All Fixes Confirmed Working 👍

  • Bug Fix (Pro): Resolves error Unable to determine UA info directory location when upgrading to latest release. See Issue #862.
  • Bug Fix (Pro): Enhancing compatibility with InfiniteWP, ManageWP, and other remote management tools for WordPress. See Issue #862.
  • Bug Fix (Pro): Incorrect time calculations whenever load average checks are enabled in Comet Cache configuration options. See Issue #853.

Tested Using

WordPress Version: 4.7
Current WordPress Theme: Twenty Sixteen version 1.3
Theme Author: the WordPress team - https://wordpress.org/
Theme URI: https://wordpress.org/themes/twentysixteen/
Active Plugins: Comet Cache Pro v161223-RC
PHP Version: 7.0.10-2+deb.sury.org~xenial+1
MySQL Version: 10.0.28-MariaDB-0ubuntu0.16.04.1

Tested using Single Site install and Network Installations

Bug Fix (Pro): Resolves error Unable to determine UA info directory location when upgrading to latest release. + Enhancing compatibility with remote management tools for WordPress

Infinite WP seems to have errors with its WP Dashboard Installation

screen shot 2016-12-24 at 12 14 54 pm

Used ManageWP instead to test for Remote Management upgrade

ManageWP Dashboard detects Comet Cache PRO RC available for upgrade

screen shot 2016-12-24 at 12 12 47 pm

ManageWP Dashboard after upgrading to Comet Cache Pro v161223-RC

screen shot 2016-12-24 at 12 14 02 pm

WP Dashboard Plugins list. Upon visiting, it detects Comet Cache Pro v161223-RC and clears cache

screen shot 2016-12-24 at 12 13 49 pm


Bug Fix (Pro): Incorrect time calculations

Cache Expiration Time settings

  • set at 28 days
  • Server Load average set to .01

screen shot 2016-12-24 at 12 16 14 pm

  • Time is calculated Correctly

screen shot 2016-12-24 at 12 26 22 pm

screen shot 2016-12-24 at 12 18 45 pm

@raamdev

This comment has been minimized.

Copy link
Contributor

raamdev commented Dec 26, 2016

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

@raamdev raamdev closed this Dec 26, 2016

@wpsharks wpsharks locked and limited conversation to collaborators Dec 26, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.