I noticed during a page load today that tracker2_block on the dashboard of the redesign site is now being pulled from cache_block. I think this maybe a caching error down the road (as even with cache_per_role, this can't be accurate for all users...or any more than 1 user). Sadly I think this is one of the blocks we have to turn caching off for:

--- sites/all/modules/tracker2/tracker2.module	2010-09-21 23:21:53 +0000
+++ sites/all/modules/tracker2/tracker2.module	2010-09-23 20:34:28 +0000
@@ -5,6 +5,8 @@
  * Enables tracking of recent posts for users.
  */
 

 /**
  * Implementation of hook_help().
  */
@@ -74,7 +76,7 @@
   switch ($op) {
     case 'list':
       return array(
-        'user' => array('info' => t('Track posts')),
+        'user' => array('info' => t('Track posts'), 'cache' => BLOCK_NO_CACHE),
       );
 
     case 'view':

Am I totally off on this? I think the only reason this has been working on the live site is that the block cache is currently off there.

Comments

nnewton’s picture

drumm’s picture

Status: Active » Fixed

Yep. Committed and imported redesign.d.o's bzr.

Status: Fixed » Closed (fixed)
Issue tags: -drupal.org redesign, -drupal.org redesign project, -drupal.org redesign sprint 5

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