Right now the recommended release of expire is still 7.1.

Is 7.2 more stable than 7.1. I'm encouraged as it has documentation #1959788: Expire module exposes an API but does not document it.

This might just be an oversight, but it would be useful to get more information.

Comments

spleshka’s picture

See 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.

bibo’s picture

So, 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.

bibo’s picture

So, 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

spleshka’s picture

@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.

helmo’s picture

Title: When will the 7.2 branch be the recommended release? » When will the 7.x-2.x branch be the recommended release?
Status: Active » Fixed

Calling this fixed, the 2.0-rc2 release is done and now the recommended release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.