Closed (fixed)
Project:
Cache Expiration
Version:
7.x-2.0-beta2
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2014 at 15:43 UTC
Updated:
1 Apr 2014 at 11:21 UTC
Jump to comment: Most recent
Comments
Comment #1
spleshkaSee https://drupal.org/comment/7630533#comment-7630533 for more details. I can make 7.x-2.x branch recommended, but we need to fix something there.
Comment #2
bibo commentedSo, drush integration is the main concern blocking the release?
I do love drush, and have actually written some simple custom varnish purging logic as a drush extension. Such as, purge everything regardless of domain name (which can be useful when using cdn or domain).
In any case, I would love seeing a recommended 7.2-release, regardless if it has full drush support. Then we could probably replace cache_actions (which hasnt seen much progress for a while) with expire on many projects.
Comment #3
bibo commentedSo, based on the digging what I've been doing, the actual problem with the 2.x-series is the API change that adds hostname to the purges - which works with Database-page_cache, but breaks with Varnish-page_cache?
In other words, this issue is the blocker, or am I wrong?
#2113941: hook_expire_cache() should not give absolute URLs but internal Drupal paths.
There are also MANY related issues in the Varnish-issue queue:
#1847672: VarnishCache::clear() has different behaviour than DrupalDatabaseCache::clear().
#1286854: Cache purge by cid key from cache_page table
#2185281: Site aliases aren't purged
#1849506: Varnish purge cache - Configuration
Comment #4
spleshka@bibo, you are right. We need to solve issue with absolute urls first, then we can release and least first 7.x-2.x-rc.
Comment #5
helmo commentedCalling this fixed, the 2.0-rc2 release is done and now the recommended release.