I have no solution, but the solution so far seems like a bummer. Obviously this only affects dev, but it seems like there should be a better way.
@weaverryan On Feb 18, 2011 1:32 PM, "Lukas Kahwe Smith" <[email protected]> wrote: > > On 18.02.2011, at 20:30, Jay wrote: > >> Wow, that would mean losing a great dev resource once you decide to >> start building esi into your website. I can understand once you're >> done building it and then you can disable it on dev and enable it on >> prod, but would be nice to build ESI and have a toolbar on your dev >> env. > > > you still have the profiler. > > 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 -- 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
