Closed (fixed)
Project:
Block Cache Alter
Version:
6.x-1.3
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
30 Apr 2009 at 18:38 UTC
Updated:
20 May 2009 at 18:00 UTC
After applied the rules for cache for each block, for second option of cache expired (node, comment, user, login/logout) doesn't being save into database.
When I reconfigure the same block after Submit, the this option become empty and I need to re-set again. I don't know either the setting before have been save into the database or not.
*ps: does this module create a table in database?
Comments
Comment #1
swentel commentedThe module doesn't create a table in the database, all is stored in the variable table. I'll have look this weekend to see if I can reproduce the problem.
Comment #2
parasolx commentedthanks for that effort. i'll wait for new patches.
Comment #3
swentel commentedOk, I tried to reproduce and the only time I manage to loose the settings is when I fill in the Cache lifetime option too. If this is not empty, it will save this value into the database, otherwhise the other values, see code excerpt underneath.
So as far as I know, everything should work fine.
Comment #4
swentel commentedHmm, wrong status
Comment #5
parasolx commentedso thats mean if the cache lifetime is set for custom value, then the setting is not save in database.
while if let it by zero then it should save?
Comment #6
swentel commentedYep, that's the catch, you can only choose either between cache lifetime OR on actions, not both.
Comment #7
parasolx commentedIC... then it should be update in manual guidance for other references
Comment #8
swentel commentedI updated the documentation in the Drupal 6 branch for some more clarification about this and updated the project page too.