Remove /[version] from Auto-Cache Engine User-Agent #315
Labels
Milestone
Comments
Good idea! I didn't realize that wasn't being updated when WordPress is updated. Adding this to the Next Release milestone as it's an easy fix. |
Next release changelog:
|
raamdev
added a commit
that referenced
this issue
Aug 8, 2017
- **New Feature: Memcached / RAM** (Pro): Comet Cache Pro now includes support for Memcached / AWS ElastiCache to serve the cache directly from RAM. This allows for a faster cache delivery than what is possible when serving the cache via disk. Memcached / AWS ElastiCache can be configured from **Dashboard → Comet Cache Pro → Plugin Options → RAM / Memcached**. See [Issue #47](#47) - **Enhancement**: Added `Referrer-Policy` to whitelist for cachable HTTP headers. See [Issue #892](#892). - **Bug Fix** (Pro): The Cache Statistics feature was broken when the PHP `disk_total_space()` and/or `disk_free_space()` functions were disabled by the PHP configuration. Comet Cache now handles this scenario gracefully by hiding disk-related stats when those functions are not allowed. See [Issue #775](#775) - **Bug Fix** (Pro): The HTML Compressor was returning an empty string upon encountering an invalid UTF-8 sequence. See [Issue #871](#871) reported by a Comet Cache user. - **Compatibility** (Pro): Many improvements to the Pro software update system, including changes to the API Endpoints and the Proxy Fallback endpoint. See [Issue #879](#879) and [Issue #315](wpsharks/comet-cache-pro#315) for full details. - **Compatibility**: Fixed a WooCommerce compatibility issue that was generating a "Notice: id was called incorrectly. Product properties should not be accessed directly." Props @vestaxpdx. See [Issue #896](#896).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we could just remove the version from this identifier. I see what's happening now is that the option value is being saved, with a WordPress version hard-coded into this string. It makes it a bit confusing later when you upgrade WordPress; where this will still have the previous version number.
The text was updated successfully, but these errors were encountered: