Drupal 5

Any news please !

hello

are there any news?

greetings momper

Patch for Drupal 5 attached.

Thanks for the patch. It applies, but when enabling this module there is no admin interface anywhere to enable file-based caching. In fact, there's no hook_menu() anywhere in the code.

Is anyone actually using this on D5? How about on 4.7?

Attached is a .info file. Change the file extension to ".info" and at least you can enable the module.

@christefano - there is no admin ui for this module. the instructions are in the readme. i will be trying this on 5 soon, and will submit a patch

I was wondering about the admin UI because the readme says "Enable page caching by navigating to: administer » page caching". In retrospect I guess that's the standard Drupal cache.

committed to HEAD with permission from matt. the old version was branched to 4.7

i used pieces from roberts patch, and info file from christefano.

thanks everyone.

Just wanted to note that using the HEAD version (Drupal 5 compatible) works fine, but make sure you create the cache folder otherwise you'll get errors. Also you might want to change the 'drupal_set_message' section in cache.fs.inc. At the moment it doesn't work and causes problems if your cache folder isn't correctly configured. I'm not a programmer so can't help with a patch, sorry.

Thanks for updating this module. I'd love to see this developed further, I believe flat files are the way to go for certain sites.

Ok, I noticed a problem if you switch on Drupal 5's caching system (to 'normal' caching). It throws up various errors including:
Notice: Trying to get property of non-object in htdocs/newqafac/modules/fastpath_fscache/cache.fs.inc on line 39
Should this be used with Drupal 5's caching system? And how is this module's caching enabled or disabled? In fact, how do I check to see whether its working, other than seeing the files created in the cache folder?

turn of NOTICE errors in your PHP

yes, you should enable the usual drupal page caching see "administer => performance"

you know this is working if you view a page as anonymous, then shut down your SQL server, and then refresh the page. if it works, you have success.

please file bugs/features in separate issues. this one is now closed.