$configuration = ProjectConfiguration::getApplicationConfiguration(‘frontend’, sfContext::getInstance()->getConfiguration()->getEnvironment(), false);
$context = sfContext::createInstance($configuration);
$cache_manager = $context->getViewCacheManager();
$cache_manager->remove(‘@sf_cache_partial?module=[your_module]&action=[your_action]&sf_cache_key=[your_id]‘);

This example would clear a given partial in the frontend app from the backend app.

Hope that helps someone!
Robin

on my action I do it:


$cacheManager = $this->getContext()->getViewCacheManager();
$component_uri = "@sf_cache_partial?module=dashboard&action=_translations&sf_cache_key=40cd750bba9870f18aada2478b24840a";

$this->lastModified = $cacheManager->getLastModified( $component_uri );
$this->lifetime = $cacheManager->getLifetime( $component_uri );


and on my template I did it:

this cache was generated at , next update will be in seconds


I worked fine, but the variable sf_cache_key=40cd750bba9870f18aada2478b24840a” is hardcoded, how can I get this key dinamicaly??

thank you,

Nei

A cron job would work well for the cases where you end up with lots of old cache files sitting around; symfony won’t delete them until they need them again and see they are too old. But, it doesn’t fix the case where an object from your model is modified and you don’t those old cached files lingering around between the time it was modified and the time the cron script runs. For example, if you had a blog post and you cached the blog/show?id=xx view, and then you made an edit to the blog post content, you’d want to see your edits right away and not wait until your cache file reached the age limit.

So, the core of the issue is this: You need some way to link modifications of your model objects to a list of cached files that are affected by the change. As long as you listen in to when the object is modified, you can move the actual list of which files are modified out of the model and into some other class or even listener so keep your MVC components clean.

By the way, you write:

“say this partial is in our app’s layout folder and is called _headerNav.php.
<?php include_partial(‘global/searchTop’) ?>”

Is that a typo? Shouldn’t it be “headerNav”?

http://trac.symfony-project.org/browser/branches/1.0/lib/cache/sfFileCache.class.php#L73

Could be that the only documentation of this setting is the source code itself

- CH

What about placing some kind of comment (like PHPDoc) at the beginning of each template, stating what objects are used inside this template? Of course this has to be kept up-to-date as well, but it’s much easier IMHO than having this in a different file. And there would be one more advantage: if you remove the template, the system won’t try to remove its cache any more. So you are more able to re-use stuff as long as you use the same cache cleanup mechanism everywhere.