This project is not covered by Drupal’s security advisory policy.

First, we had drush_ecl (which is exclusively a drush plugin). Now, we'll have ECL. This is for those that want an actual module to integrate into their drupal project for loading entities into caches.

This module warms up your content caches and can help content load faster by running through and loading any/all entity content. Once entity content is loaded, components of the content (or all of it if it can use Entitycache) can get cached thus making the latter content loads much faster. You also have capabilities to cache by entity type (such as comment, node, user, etc) and further by the bundle type (such as article, page, etc). Finally, this module also integrates with Display Cache so you can cache view modes of your entities (depending on which ones you configure to get cached).

What makes this different from drush_ecl

I'm glad you asked! The big difference is that this is a module whereas drush_ecl is *just* a drush plugin. The advantage of an exclusively drush plugin is that it is usable on *all* drupal projects (right now, drush_ecl only works with 6.x and 7.x but that is besides the point). So for those that have multiple drupal sites on a single server (doesn't have to be multisite...just hosting multiple sites on the server), then you can cache your entities without needing to install another module. However, there are a couple of downsides to an exclusive drush approach (depending on how you look at it, major/minor):

  1. No UI. This means you need to set things up as a cron task. Thus not easily usable by services like Pantheon or Aegir.
  2. Requires setting up settings.php with a base_url. So while you may still use the 'default' directory for your settings.php file, you need to set up a base url. Otherwise, what happens is that (and you may sometimes notice this with drush running cron from the server instead of hitting the url) your content that gets cached will sometimes have internal links that look like http://default/file/path. Unless the base url can be hard set (sometimes its fine, sometimes its not), this is not an ideal situation.

With that, this will be a module that you enable in your site so you can:

  • Load your entity caches via a UI.
  • Have better support with your URLs
  • Also load caches via drush (this won't interfere with drush_ecl - its going to mostly be the same code though I'd frankly recommend that if you have multiple sites on a server since running it this way does also mean you hit negative point 2 from above.

This will work best with the Entity Cache module. This module now also supports Display Cache (which I plan to also port to drush_ecl).

Also in the plans: Drupal 8 support.

Coming soon.

Project information