The renderer type is used as the final extension in the filename, as is the case with twig templates.
Is it essential that you compress the template before it is finished rendering? I'd think it'd make more sense to compress output using a core.response (or core.view) event handler. You can see where these are called by peeking in the HttpKernel class: http://github.com/fabpot/symfony/blob/master/src/Symfony/Component/HttpKernel/HttpKernel.php ^ handleRaw() and filterResponse() methods. Events on either would conceivably allow you to modify the content of the response object. On Sep 18, 5:48 pm, Richard D Shank <[email protected]> wrote: > I'm working a custom renderer that compresses the output of the template > with lw77 before it is finished rendering. Ideally I would like to be > able to compress any output, but for now, I'm content with php. > > I'm attempting to use a php template by using this line in my controller > > return $this->render('TrackBundle:Track:index.php:lw77', > array('tracks' => $tracks, 'scores' => $scores)); > > The problem I'm facing right now is that it right now, FilesystemLoader > doesn't want to find TrackBundle:Track:index.php as the template, it > keeps looking for views/Track/index.php.lw77 > > Is this the expected behavior? If so, what is the use for .format? > > Richard -- 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
