hi tl.
Quote:
What would be the security implications, if any, if XOOPS_TRUST_PATH = XOOPS_ROOT_PATH
In FCH, someone can see admin's cache by
XOOPS_URL/fullcache/(md5(uid))_(md5(requesturi))
Though I think it is not so severe problem...
At least, put .htaccess under fullcache/
Anyway, I will release modules using XOOPS_TRUST_PATH.
Thank you, GIJOE. Learning new things every day!
Quote:
The only issue is that my cron jobs stop to work with this hack.
As I check the cron.log, it shows "You can't use fastest cache hack".
Any way to resolve it?
I've fixed it, and released it.
If you want to change it manually
Edit line 29 of fastestcache.php
if( empty( $_SERVER['REQUEST_URI'] ) ) return ; exit( "You can't user...");
Quote:
And do you sugguest to use this hack alone or with the default cache system together?
Some kind of "block cache" will be good for performance.
But you should disable any kind of "module cache".
GIJOE, thanks for your prompt reply.
Cron jobs work again now.