Hi, yeah maybe that was the problem that sth wrong was stuck in the cache. I'm new to Symfony too but what I've learned so far is if sth goes wrong, clear the cache first, if it goes wrong again, then you have a problem ;)
Most of the time you got to clear the cache when you have new classes for example. But good that it works now :) Greetings Ben On Thu, 27 May 2010 01:12:06 -0400, Tony Peng <tpen...@gmail.com> wrote: > I started the project over from scratch and I am no longer > experiencing this problem. > > The only thing I did differently was that I executed ./symfony cc > before I created the module. Not sure if that was the problem, but > thank you comb and Garry for your help. > -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
