Hi Lukas,
I had the exact same problem as you described a few days ago. I will try
to work on it today and find a solution.
Fabien
--
Fabien Potencier
Sensio CEO - symfony lead developer
sensiolabs.com | symfony-project.org | fabien.potencier.org
Tél: +33 1 40 99 80 80
On 1/26/11 8:52 AM, Lukas Kahwe Smith wrote:
Hi,
I tried replacing the default TemplateNameParser by one that expects template
names to be in parsed for already, since for the view layer that I am working
on I need to operate on pieces of template names:
https://github.com/liip/ViewBundle/blob/serializer/View/DefaultView.php#L131
Ages ago I have written a patch that allowed this:
https://github.com/fabpot/symfony/pull/391
But that approach doesnt work anymore. In theory things should be better now
since the TemplateNameParser is now more flexible:
http://pastebin.com/PBSyaxec
But because we still have code that relies in the serialized form for the
template name we cannot actually freely define the template name format. For
example in TwigEngine:
public function supports($name)
{
return false !== strpos($name, '.twig');
}
That code will obviously fail if $name is not something like
FooBundle:Bar:index.html.twig but instead an array as it would be produced by
the default TemplateNameParser.
So I just wanted to raise awareness for this issue. I poked around briefly
trying to find a solution.
regards,
Lukas Kahwe Smith
[email protected]
--
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
