HI - I found that with the basic config as outlined in the included README.txt still in place in settings.php, simply disabling the filecache module still continued using disk as alternative cache mechanism. I wonder if it might be a more appropriate way of sandboxing and modularizing this helpful module to allow it to be disabled (and even uninstalled).

In my particular case, what got me was running benchmarks for the client: I couldn't see any differences in jmeter load tests with filecache enabled or "disabled." :)

-Bronius

Comments

jmdeleon’s picture

jmdeleon CreditAttribution: jmdeleon commented

When using an alternate caching backend such as this (or APC), you must empty the 'cache' database table manually, with a direct SQL command (DELETE FROM `cache`;) before reverting back to the Drupal database cache.

Clearing cache with Drush then restored the site I was working on to using database cache, and got off File Cache completely. This issue describes the remedy (based on using APC as cache, but the concept is the same):

https://drupal.org/node/1341874#comment-5249602

texas-bronius’s picture

texas-bronius CreditAttribution: texas-bronius commented

Hmm - Do you think it would be sufficient, then, to perform the cache table truncate in a hook_disable (quickest and, in my case, what I'd have appreciated) or hook_uninstall (more "proper" by the definition of the hook in relation to the task performed (namely, disabling the module))? Perhaps both?

jmdeleon’s picture

jmdeleon CreditAttribution: jmdeleon commented

(Only seeing this reply now, as I've only revisited using this module)

I think a cache table truncate in a hook_disable would lead to a cleaner condition where the default database cache could be safely enabled again. Though I don't disagree with performing the truncate in both hook_disable and hook_uninstall.

Adding to my earlier comment: you can also empty the cache table from Drush with drush sqlq 'delete from cache;' before reverting to the default database cache.

delacosta456’s picture

delacosta456 CreditAttribution: delacosta456 commented

hi

i was facing this issue too ... and on my own side in addition to all this commenting the filecache's lines inserted in settings.php so that it will be ignored resolve the issue..

hope it help

thanks

  • ogi committed c40b42c on 7.x-1.x 
    Issue #2200841: Delete database cache bin when filecache bin is...

  • ogi committed 6d3b203 on 7.x-1.x 
    Issue #2200841: Delete filecache bin before first use. Delete filecache...

  • ogi committed d8a554f on 7.x-1.x 
    Issue #2200841: Document technical details about disabling filecache.

  • ogi committed 1501348 on 7.x-1.x 
    Issue #2200841: Correct documentation about disabling filecache.
ogi’s picture

ogi CreditAttribution: ogi commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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