On Apr 7, 4:26 pm, Fabien POTENCIER <[EMAIL PROTECTED]
project.com> wrote:
> Marijn wrote:
> > Hi everybody,
>
> > I just started using symfony a month ago so I figured I better move to
> > 1.1 now, I really don't feel like learning about stuff that will be
> > deprecated in a month or two ;-)
>
> > I had a simple filter that would place all my JavaScripts to the
> > bottom of the page that would set the parameterholder
> > 'javascripts_included' on the response object. But if I run that
> > filter now it says that the method setParameter is undefined. I figure
> > that would be because the response object isn't built yet..?
>
> Instead of using
>
> $response->getParameter('javascripts_included', true,
> 'symfony/view/asset')
>
> you can now use
>
> sfConfig::set('symfony.asset.javascripts_included', true)
>
Thanks for your quick reply Fabien :-)
May I conclude that:
- all the symfony parameters are moved to sfConfig..?
- sfConfig::get('symfony.asset.javascripts_included') is the
getParameter counterpart..?
In respect to beauty in code, I think this would be a nice example ;-)
Thanks,
Marijn
> Fabien
>
>
>
> > Are there changes in 1.1. regarding this which I am unaware of..?
>
> > Thanks,
>
> > Marijn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
