Integration of Cache Expiration and Authcache Builtin Storage Backend broken

I already test the last dev version (with the committed patch) and the problem continue, only clear the anonymous cache (same with files or database)

In the Expire module I try with Internal and External, the Node Expiration actions and Rules, and all with the same result

I Think the problem is major, now I'm understanding a little more the module. I'm not an expert.

The module does not clear the cache at all, only is cleared by the Expire module when use the internal expiration option, and only the anonymous users cache.

If you put this:

dsm($cids);

at the end of authcache_builtin_expire_cache() and save some node can see that all the urls are bad formed and with the wrong key.

Tomorrow I'll continue...

Finally I get it to work...

For some reason $properties_info in authcache_enum_user_keys() is not ordered properly, so I force it to the right order, I don't know if this is the best solution but works.

function authcache_enum_user_keys() {
  $info = &drupal_static(__FUNCTION__);

  if (!isset($info)) {
    $properties_info = module_invoke_all('authcache_enum_key_properties');
    $sets = array();
    foreach ($properties_info as $key => $definition) {
      $sets[$key] = $definition['choices'];
    }

    // reorder array //----------------------------------------------------
    $temp = array();
    $temp['base_root'] = $sets['base_root'];
    $temp['roles'] = $sets['roles'];
    $temp['ajax'] = true;

    $info = array();
    module_load_include('inc', 'authcache_enum', 'authcache_enum.comb');
    foreach (_authcache_enum_cartesian($temp) as $properties) {
      // force ajax value true, i don't know why change to false at this point //----------------------------------------------------
      $properties['ajax'] = true;
      $authcache_key = authcache_user_key($properties);
      $info[$authcache_key] = $properties;
    }

    drupal_alter('authcache_enum_key_properties', $info);
  }

  return $info;
}

And the problem with the absolute urls maybe is in the Expire module side

https://drupal.org/node/2113941

I fix it with this

function authcache_builtin_expire_cache($urls) {
  global $base_root;
  if (!module_exists('authcache_enum')) {
    return;
  }

  $cids = array();

  $keys = authcache_enum_keys();
  foreach ($keys as $key) {
    foreach ($urls as $url) {
      // Expire chops the root-slash from request urls. Therefore we need to
      // add it here between the key and the url.
      $cids[] = $key . '/' . str_replace($base_root.'/', "", $url);
    }
  }
  cache_clear_all($cids, 'cache_page');
}

@RAFA3L

Regarding your array ordering issue, I think adding a call to ksort at the beginning of authcache_user_key() would solve that problem.

Also, authcache_enum_user_keys() should probably detect whether the current is the superuser or not, like authcache_key() does.

function authcache_user_key($properties, $superuser = FALSE) {
  ksort($properties);
  $data = serialize($properties);
  $hmac = hash_hmac('sha1', $data, drupal_get_private_key(), FALSE);

  // Make sure superuser has its own key not shared with anyone else (though
  // it would be better if superuser would'nt be allowed to use the cache in
  // the first place).
  if ($superuser) {
    $hmac = hash_hmac('sha1', $hmac . $data, drupal_get_private_key(), FALSE);
  }

  $abbrev = variable_get('authcache_key_abbrev', 7);
  return $abbrev ? substr($hmac, 0, $abbrev) : $hmac;
}

function authcache_enum_user_keys() {
  global $user;
  $info = &drupal_static(__FUNCTION__);

  if (!isset($info)) {
    $properties_info = module_invoke_all('authcache_enum_key_properties');

    $sets = array();
    foreach ($properties_info as $key => $definition) {
      $sets[$key] = $definition['choices'];
    }

    $info = array();
    module_load_include('inc', 'authcache_enum', 'authcache_enum.comb');
    foreach (_authcache_enum_cartesian($sets) as $properties) {
      $authcache_key = authcache_user_key($properties, $user->uid == 1);
      $info[$authcache_key] = $properties;
    }

    drupal_alter('authcache_enum_key_properties', $info);
  }

  return $info;
}

It is necessary that authcache_enum_user_keys() always returns the same results, regardless of whether the superuser is logged in or not. The solution you are proposing will return the complete set of keys prepared for superuser when uid=1 is logged in. When superuser is not logged in, it will also return the complete set of keys, however none of them prepared for superuser. An easy solution would be to simply document the fact that the superuser-feature is not compatible with expire for the moment and develop a proper solution when the need really arises.

I wasn't really planning on using the super-user feature anyway. I just wanted to point that out for consistency's sake.

You are right @znerol, I was using the 7.x-2.x-dev of the Expire module. But changing it to 7.x-1.0-beta1 or 7.x-1.x-dev (and applying the patch) doesn't fix the problem. My test site is in a subfolder "localhost/testcache" and with the "Include base URL in expires" disabled I get this cids in authcache_builtin_expire_cache, for example:

7371cb8/node/1
7371cb8/content/test-1

The subfolder is excluded.

And I notice that authcache_builtin_expire_cache get all the url nodes (with and without alias), so I think if the cids were right will clear all the pages cached and not only the updated.

The ksort call work perfect.

The patch work using Expire 7.x-1.x-dev, but now clear all the cached pages and would be only the updated node and any other indicated in rules.

Using Expire 7.x-2.x-dev work fine, only pass the selected urls, but the problem is that the option "Include base URL in expires" was discarded , as is explained here...

https://drupal.org/node/2113941

Thanks! Only one more thing...

function authcache_builtin_expire_v2_expire_cache($urls, $wildcards, $object_type, $object) {
global $base_root; // added

...

// like v1 must be
//foreach (array_keys($urls) as $path) {
foreach ($urls as $path) {

...

// This line doesn't make the url relative
//$cid = $key . url($path, array('absolute' => FALSE)); 
$cid = $key . '/' . str_replace($base_root.'/', "", $path);

With this changes work perfect

Yes! you are right! I was using an action rule to clear the cache with

[node:url]

and this is the cause of the problem, using rules doesn't pass the right path in the array keys. Using the node actions in the settings of the Expire module (without rules) all work perfect!

Thanks!!!

Hello znerol is me again...

I'm playing with the Context Mobile Detect module and I think it work fine with Authcache, but again, the problem is clearing the cache after update a node.

For example, the generated cache file using Blackberry is

...^testcache^node^1%3Fdevice%3D1%26device_type%3Dblackberry

But after update a node the cache file for the specific device is not cleared. Would be nice make it to work with Context Mobile Detect.

Sorry but I'm using the the latest builds of both Authcache and Cache Expiration with Memcached as the cache backend. If I enable 'external expiration' in Cache Expiration, when editing a node, it gives me a blank screen and does not save the node. I'm using aliases.