The manual says it's fine to turn on/leave on the existing common filter in your filters.yml in 1.3 (I realize it's going away in 1.4). But if you do that, your project bombs with an error pointing to a yml file inside Symfony itself, not your filters.yml.
See http://trac.symfony-project.org/ticket/7156#comment:3 >From the documentation: "The sfCommonFilter class is still bundled with symfony 1.3, and so you can still use it in your filters.yml if you need to." http://www.symfony-project.org/tutorial/1_4/en/upgrade I'm moving away from sfCommonFilter myself, but I'm pretty sure either the documentation or the code is wrong in 1.3. -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.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.
