COmanage Developers List

[Scott Koranda <>]

> > On 10/12/11 11:30 AM, Scott Koranda wrote:
> > 
> > >It does now. Changing the log level causes the cache to be
> > >thrown away and recreated. Once that is done the cm_users view
> > >is available inside the cache.
> > 
> > Since cm_users is created manually, I'm not surprised the cache is
> > invalid. I wouldn't object to clearing the cache as part of 'cake
> > setup', as long as we document why we're doing it.
> > 
> > I guess considering the other bad-cache issue (CO-171), perhaps we
> > should contemplate just turning off caching entirely. I'm still
> > leaning towards documented workarounds to clear the cache in
> > appropriate places, though. Perhaps add a clear_cache() function to
> > utils.php and call it from setup and wherever is appropriate for
> > CO-171?
> > 
> > You should put this issue in JIRA and relate it to 171.
> > 
> 
> Done. JIRA is
> 
> https://bugs.internet2.edu/jira/browse/CO-191
> 
> The diff is below. Can I commit?
> 
> Scott
> 
> Index: setup.php
> ===================================================================
> --- setup.php (revision 100)
> +++ setup.php (working copy)
> @@ -188,6 +188,13 @@
>        $grm_id = $this->CoGroupMember->id;
>  
>        $this->out(_txt('se.done'));
> +
> +      // Clear the models in the cache since the cm_users view
> +      // was just created and will not otherwise appear in the cache.
> +      //
> +      // See https://bugs.internet2.edu/jira/browse/CO-191
> +      clearCache(false, 'models');

Actually this *has* to be

      clearCache(null, 'models');

Don't blame me...it's a cake function, their API. false will
not work.


> + 
>      }
>    }
> -?>
> \ No newline at end of file
> +?>