There’s a method on sfViewCacheManager::remove($URI) for removing an entry but it depends where you are and what you’re trying to remove.
I would assume that removing the entry would force the view to be rendered and then recached on completion. At least with the debug panel you get caching information displayed on the page elements – which should help testing J From: [email protected] [mailto:[email protected]] On Behalf Of Sid Ferreira Sent: 10 May 2009 19:39 To: [email protected] Subject: [symfony-users] Re: Cache Engine and Profile Pages nice, now all I have to do is find a way to force the 'reset' of it... On Sun, May 10, 2009 at 14:27, David Ashwood <[email protected]> wrote: Wotcha Sid, If you include the userID in the route/URL for the profile then it'll have it's own cache element. There's some detail here (http://www.symfony-project.org/book/1_2/12-Caching) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sid Ferreira Sent: 10 May 2009 15:52 To: symfony users Subject: [symfony-users] Cache Engine and Profile Pages Hi, please, Im wandering about the Cache engine about caching profile pages, wich each user has its own, does cache handle that properly? Or if I cache it the cache will make the _same_ page to anyone? Also, how to force the refresh of the cache of a page programatically? -- Sidney G B Ferreira Desenvolvedor Web --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
