Any news about this pull request / CLI cache warmup alternatives? - we
need it to for our functional tests

On Mar 2, 11:34 pm, [email protected] wrote:
> there is a pull request for this one, you can merge remote repo to
> have it fixed temporaryhttps://github.com/symfony/symfony/pull/144
> --
> Aurelijus Valeiša
> +370-618-19765http://www.Aurelijus.eu
>
>
>
>
>
>
>
> On Tue, Mar 1, 2011 at 10:09 PM, Martijn <[email protected]> wrote:
> > Hi,
>
> > The problem is the combination of cache and the "FrameworkBundle
> > \Templating\TemplateNameParser". The parser ensures correct template
> > names. But the "TwigBundle\CacheWarmer\TemplateCacheCacheWarmer" uses
> > hash keys from templates.php (stored in the cache directory) as
> > template names.
>
> > How should we solve this?
>
> > As workaround you could edit templates.php to return correctly
> > formatted keys.
>
> > Martijn
>
> > On Feb 23, 2:45 pm, Ruudk <[email protected]> wrote:
> >> In my cache/dev/templates.php I see this:
>
> >> 'a6425a46d30cbcf531a85c01282dda4a' =>
> >> '/www/sparkling/vendor/symfony/src/Symfony/Bundle/FrameworkBundle/Resources
> >>  /views/Exception/error.atom.twig',
>
> > --
> > If you want to report a vulnerability issue on symfony, please send it to 
> > security at symfony-project.com
>
> > You received this message because you are subscribed to the Google
> > Groups "symfony developers" 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-devs?hl=en

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" 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-devs?hl=en

Reply via email to