wpsharks / comet-cache

An advanced WordPress® caching plugin inspired by simplicity.
https://cometcache.com
GNU General Public License v3.0
77 stars 18 forks source link

Clear Cache not clearing cache directories #868

Closed raamdev closed 7 years ago

raamdev commented 7 years ago

We have several reports of Comet Cache Lite v161221 not deleting directories in wp-content/cache/comet-cache/cache/http/example-com/* when you click the 'Clear Cache' button. Cache files get deleted, but any and all directories remain. Comet Cache Lite v160917 and v160706 are also reported as having this issue.

I have not been able to reproduce this, but there are at least three confirmed reports of this issue:

Users have double-checked permissions and even installed other caching plugins to see if those plugins delete directories fine (they do). Please see the above links for the details of each report.

renzms commented 7 years ago

@raamdev

Unable to reproduce error

Tested using Comet Cache Lite v161221, with single site and multisite.

Using PHP 5.4/7

Comet Cache Lite v161221 clears files and directories properly.

screen shot 2016-12-29 at 12 58 31 am

screen shot 2016-12-29 at 1 04 23 am

eurobank commented 7 years ago

Doesn't work for me also. CloudLinux Shared Hosting with PHP 7, using LiteSpeed webserver (if this makes any difference).

Directories remain.

Tested with other cache plugins and works as expected.

raamdev commented 7 years ago

After extensive tests, we discovered the bug that was causing this issue; see https://github.com/websharks/comet-cache-pro/commit/3db638daf2df16e3a4e9da5aa7729bfc1d1b07ac. A fix for this issue will go out with the next release.

renzms commented 7 years ago

Confirmed working in Comet Cache™ Pro v170201-RC

Clear button clears out all empty directories

raamdev commented 7 years ago

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