Any ideas as to what might be causing this? It falls over as soon as I enable my cacherouter settings array in settings.php, which looks like this, for the record:

$conf['cache_inc'] = './sites/all/modules/contrib/cacherouter/cacherouter.inc';
$conf['cacherouter'] = array(
  'default' => array(
    'engine' => 'file',
    'shared' => TRUE,
    'prefix' => '',
    'path' => '/tmp/filecache/ecuk',
    'static' => FALSE,
    'fast_cache' => FALSE,
  ),
);

Comments

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Should note, works fine on local laptop. Breaks on CentOS 5.2 test server. =/

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Weirdness. Deleted the directory, re-created it and re-set the permissions and it worked fine. Though quite why the directory name would cause a bootstrap problem relating to a missing function, I do not know.

So mine is fixed, but I'll leave this open as I don't think I should've ever seen this error, so it's still a bug - maybe the function call will give you some clue?

crea’s picture

crea commented
Category: bug » support
Status: Active » Fixed

More likely problem with your installation. Why would Cacherouter affect core function ?

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Fair enough - I'd forgotten about this anyway. Never saw it again.

Status: Fixed » Closed (fixed)

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

butler360’s picture

butler360 commented

Well I just got the same problem after deleting the filecache folder. It does seem like this is an issue since it shouldn't cause the site to whitescreen, right? I fixed it the same way, making sure I had the right permissions. It would be nice if it failed more gracefully.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

I suppose it wouldn't be a stupid idea to see if the cache directory is writeable and revert to using standard Drupal database caching if it is not - you could set a message for admin on all pages telling them to check file permissions, as a nag, if filecache can't work, but at least the site wouldn't fail completely. Mind you, you'd have to make that check on every attempt to write to the cache, which would add an overhead, surely? I don't know how much of one.

So another way of looking at it is if you don't know what you're doing, don't play with CacheRouter - use Drupal caching as is and leave it alone.

webdevbyjoss’s picture

webdevbyjoss commented

just got the same fatal error message on my website

there should be some additional check for correct permissions in file adapter before application crash.