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 v161116-RC (Release Candidate) #849

raamdev opened this issue Nov 16, 2016 · 2 comments


None yet
2 participants
Copy link

commented Nov 16, 2016

Target Date for General Availability Release: November 18th, 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 Nov 16, 2016

@raamdev raamdev added this to the Next Release milestone Nov 16, 2016


This comment has been minimized.

Copy link

commented Nov 16, 2016

Confirmed Working

@raamdev Everything on the check list looks good to me and is working as noted in the changelog. It wouldn't hurt though to have more eyes to catch anything I missed. 👍 🎯

  • Bug Fix: Avoid browser autocomplete in configuration fields by adding autocomplete="off" to all form tags in Comet Cache menu pages.
  • Bug Fix: Fixed a broken link to the Static CDN Filters tutorial for MaxCDN integration.
  • Bug Fix: Multisite installations inside a subdirectory were broken by Apache Optimizations via .htaccess in some scenarios. Fixed in this release.
  • Bug Fix: Don't enqueue Chart.js unnecessarily in lite version of the software.
  • Bug Fix (Pro): 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.
  • Bug Fix: Enhancing WooCommerce integration by listening to the woocommerce_product_set_stock_status hook in addition to the woocommerce_product_set_stock hook.
  • Enhancement: This version enhances the HTML comments left in the source code (HTML Debug Notes). When debug notes are enabled (i.e., HTML comments) they are now broken down into key/value pairs and tabulated for a cleaner display and easier debugging.
  • UI Enhancement: The Comet Cache UI is now fully Responsive with an improved UI on laptop and mobile devices.
  • UI Enhancement: This release improves the toggle link that allows you to see additional details whenever Comet Cache automatically clears more than one facet of the cache.
  • UI Enhancement (Pro): Following improvements to the update API in a previous release of Comet Cache that made it possible to update both the lite and pro versions of the software through normal WordPress update mechanisms, this release removes some clutter from the menu pages for Comet Cache. In short, now that we have a tighter integration with WordPress core, it's no longer necessary for Comet Cache to display update notifications in a custom way.
  • UI Enhancement (Pro): On pro version activation, display a notice that reminds site owners to configure their Pro Update Credentials so they'll be notified by WordPress about new versions of the pro software.
  • Nonce Support (Pro): In the pro version, when logged-in user caching is enabled, Comet Cache is now capable of intelligently caching pages that contain Nonce values (numbers used once). This allows for pages containing the WordPress Admin Bar to be cached without issue. It also improves compatibility with plugins like bbPress and BuddyPress, resulting in better performance and faster speeds for logged-in users.
  • i18n Compat. (Lite): This release makes all pro preview labels translatable by moving the labels that were previously defined in CSS only into HTML attribute values.
  • Performance Enhancement: For sites configured to allow query string variables into the cache, those variables are now sorted by key name internally to avoid duplicate cache files; i.e., whenever the order of query string variables changes from request to another, but with the same exact values. In short, Comet Cache now knows how to serve the same underlying cache file; i.e., from a previous request that may have had the same query string, just in a slightly different order.
  • New Pro Feature: In the pro version it is now possible to define a list of GET request variable names that should be ignored entirely by Comet Cache. See: WordPress Dashboard → Comet Cache → Plugin Options → GET Requests → List of GET Variable Names to Ignore. As an example, this new feature makes it possible for site owners to pass query string variables associated with Google Analytics (i.e., utm_* variable names) without incurring a cache performance hit.
  • HTML Compressor: Updating to the latest release of the HTML Compressor library. Comet Cache now comes with the new improved v161108 (latest release).
  • RevSlider Compat.: This release includes a built-in exclusion rule for the HTML Compressor to allow for improved compatibility with the popular RevSlider plugin for WordPress. The new built-in exclusion rule looks for and automatically bypasses an important style tag that must be preserved for the RevSlider plugin to work in all scenarios; i.e., <style id='rs-plugin-settings-inline-css'.

This comment has been minimized.

Copy link
Contributor Author

commented Nov 19, 2016

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

@raamdev raamdev closed this Nov 19, 2016

@wpsharks wpsharks locked and limited conversation to collaborators Nov 19, 2016

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