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

Feature Request: Support for Automatic Pro Plugin Updates #289

Closed
raamdev opened this Issue Aug 28, 2014 · 6 comments

Comments

Projects
None yet
3 participants
@raamdev
Contributor

raamdev commented Aug 28, 2014

ZenCache Pro currently has a Plugin Updater that allows the plugin to be updated through the WordPress Dashboard, but it would be really nice if there was an option for site owners to enable automatic plugin updates, thereby avoiding the need to manually update by clicking the update link.

This would work similar to the Advanced Automatic Updates plugin that allows you to automatically keep WordPress plugins up-to-date.


Related: #395 #394 #465 #289 #464 #352 #477

@mvander

This comment has been minimized.

mvander commented Aug 28, 2014

I'd love to see this feature, because many times once I setup a blog and it's running, I may not visit it again for months, and therefore not be up to date with the plugin.

@jaswrks

This comment has been minimized.

Member

jaswrks commented Aug 28, 2014

Cool idea! +1

@raamdev

This comment has been minimized.

Contributor

raamdev commented Sep 2, 2016

After the work done in websharks/comet-cache-pro#272 that switched the custom Pro Updater system to the built-in WordPress Plugin Update system, I tried enabling Automatic Plugin and Theme Updates as per the WordPress Codex by adding this filter to an MU-Plugin:

add_filter( 'auto_update_plugin', '__return_true' );
add_filter( 'auto_update_theme', '__return_true' );

I had 1 theme that needed an update, and 1 plugin (Comet Cache Pro). The theme was updated automatically, but Comet Cache Pro was not, which means there must be something about the built-in Automatic Plugin Updates system that Comet Cache Pro isn't yet compatible with.

@jaswrks

This comment has been minimized.

Member

jaswrks commented Sep 3, 2016

I just did a quick review of the routines associated with these filters and every indication that I've seen so far would suggest that this should work given the current Comet Cache dev branch. I will run some tests as well and report back.

@raamdev raamdev referenced this issue Sep 6, 2016

Closed

Feature/465 #276

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

@raamdev

This comment has been minimized.

Contributor

raamdev commented Sep 7, 2016

Next Release Changelog:

  • Enhancement (Pro): Comet Cache Pro is now fully compatible with WordPress Automatic Background Updates. If you enable automatic background updates for plugins, and you save valid Comet Cache Pro License Credentials in the Comet Cache Pro → Plugin Options → Update Credentials panel, you will automatically receive Pro plugin updates. Props @jaswsinc. See Issue #289.

@raamdev raamdev closed this Sep 7, 2016

@raamdev raamdev changed the title from Feature Request: Automatic Pro Plugin Updates to Feature Request: Support for Automatic Pro Plugin Updates Sep 7, 2016

raamdev added a commit that referenced this issue Sep 17, 2016

Phing release of v160917 with the following changes:
- **New Feature** (Lite): The Clear Cache button is now available in the Admin Toolbar for the Lite version of Comet Cache.
- **New Feature** (Pro): Comet Cache Pro is now fully compatible with [WordPress Automatic Background Updates](https://codex.wordpress.org/Configuring_Automatic_Background_Updates#Plugin_.26_Theme_Updates_via_Filter). If you enable automatic background updates for plugins, and you save valid Comet Cache Pro License Credentials in the _Comet Cache Pro → Plugin Options → Update Credentials_ panel, you will automatically receive Pro plugin updates. Props @jaswsinc. See [Issue #289](#289).
- **Bug Fix**: In some scenarios Comet Cache might produce a false-positive "Warning: mkdir(): File exists" message when checking if the cache directory exists. Comet Cache now calls `clearstatcache()` and uses `file_exists()` instead of `is_dir()` to help make this check more robust. See [Issue #786](#786).
- **Bug Fix**: Fixed a bug where the Comet Cache PHP requirements check would fail and produce a fatal error when upgrading from a version of Comet Cache that did not require an extension that is now required by newer releases. This would occur when, for example, the required PHP `mbstring` extension was missing. Props @jaswsinc for finding the bug. See [Issue #817](#817).
- **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. This bug fix also improves the reliability of all version upgrade routines that Comet Cache runs during upgrades. See [Issue #807](#807).
- **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. As a result, the entire cache was being unnecessarily cleared when the settings for those other plugins were saved. Props to @futtta from Autoptimize for reporting. See [Issue #825](#825).
- **UI Enhancement:** Adjusted option page font styles for WordPress v4.6 to better match existing style. See [Issue #271](websharks/comet-cache-pro#271).
- **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. Props @jaswsinc. See [Issue #465](#465).
- **InfiniteWP Compatibility** (Pro): Comet Cache Pro is now compatible with InfiniteWP, an application that allows you to manage multiple WordPress sites from a single location. Comet Cache Pro Plugin Updates will now appear in the InfiniteWP 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 InfiniteWP Dashboard. See [Issue #394](#394).
- **Rewritten Pro Plugin Updater**: The Comet Cache Pro Plugin Updater has been redesigned to use the built-in WordPress plugin updater system. When a Comet Cache Pro update is available, it now appears in the WordPress Updates section and in the Plugins list, like other WordPress plugins and can be updated normally like other WordPress plugins, as long as you have saved valid Comet Cache Pro license details in the new "Update Credentials" options panel. Props @jaswsinc. See [Issue #272](websharks/comet-cache-pro#272).
- **Code Style**: The `WP_CACHE` line that gets inserted into the `wp-config.php` file to enable caching now follows the [WordPress PHP Code Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/). Props @szepeviktor. See [Issue #799](#799).
- **Compatibility** (Pro): When the Autoptimize plugin is active, the Comet Cache Pro HTML Compressor panel now shows a friendly notice explaining that both the HTML Compressor and Autoptimize should not be enabled at the same time because they both address the same performance improvements. The rest of Comet Cache works great alongside Autoptimize and whether you use the HTML Compressor or Autoptimize is a matter of preference. Props to @futtta from Autoptimize for the continued collaboration.
@raamdev

This comment has been minimized.

Contributor

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

@websharks websharks 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.