I assume you are using Page Cache Disk:Basic since that is the only way to “Cache URIs with query string variables” (that i know of). That being said i just ran a test on my side and i was able to clear the cache perfectly fine — it purged the query string pages including one as domain.com/?utm=23u42 so not sure how you have things set up. Curious, jump into ftp and delete the cache/page folder directly.
1. Does it delete or does it refuse to?
2. What is the contents of this domain.com/?utm=23u42 vs the cached domain.com/ ? They should theoretically contain the same contents..if not i am curious what are the differences. I wonder if u’ve been infiltrated (file permissions changed to prevent deletion).
Hi Kimberly, thanks for helping me and excuse me for my slow response.
1. The “empty cache” button is working perfectly fine. When I hit the button the cache folder will be deleted entirely like it should.
2. When I make changes on domain.com/ the cache on domain.com/?utm=23u42 is not purged so updates will not show.
Maybe it has to do with the https edits I made. I implemented them because without the edits purging the cache does not work at all. Please take a look at the edits below.
I have noticed that the logic for determining if the page is HTTPS is just plain wrong in the latest version 0.9.4.1
W3\PgCache.php around like 960
if ($request_uri)
$key = substr($request_uri, strtolower(substr($request_uri, 0, 8)) == 'https' ? 8: 7);
Substring of a request uri from 0 to 8 will *never* evaluate to "https" and thus deleting keys never works for https pages.
It should be https:// or substring 0,5 instead.
Also get_post_urls function in W3\SharedPageUrls.php needs to be updated. post_permalink($post_id) needs to be changed to get_permalink($post_id), as the former has been deprecated by wordpress.
Did you test it on a http or https environment?
Please let me know if you have any suggestion.
Thanks
Tim
Ahhh you are dealing with the https issue. Yea that’s an old bug. This and your “get_post_urls” problems were discussed and fixed in the forum way back. However, to save you time a bunch of us regulars collaborate and placed a bunch of fixes (including the ones you mention) into the community-driven build here. If you’re comfy with that you can give it a try and see if that fixes your original cache delete problem. Alternatively, the issues you mentioned in your last reply are discussed in the forum — among other — (with their fixes) and you can hunt them down and do them in code manually to each file yourself.
Regards,
Kimberly
