Symfony Blog

Read release notes

Symfony 2.4 is going to be maintained for an additional 2 months.

In this Case Study, we'll reveal some architecture details of the "1 Billion Symfony2 Application". We'll show you the project big-picture then focus on features we really like in Symfony2.

This week the Validator component fixed string conversion in constraint violations, DomCrawler improved filterXPath() support for ancestors and siblings and DependencyInjection fixed a self-reference that prevented the use of the garbage collector. In addition, Twig template engine fixed some edge cases for the "starts with" and "ends with" operators. Lastly, the first official discussion about Symfony 3.0 was initiated in the Symfony repository.

Andreas Forsblom reported two potential security issues on JsTranslationBundle: a path traversal attack and a code remote injection.

Which community bundles are the most useful for your Symfony projects? Share them with us by filling in this survey.

This week Symfony increased its development activity significantly. The most important change was the introduction of SSI support. In addition, a memory leak was fixed in ValidatorBuilder and object initializers were fixed for the 2.5 version of the Validator.

After some time of reflection to decide which workshops we should (or should not) organize at SymfonyLive New York and SymfonyCon Madrid, we decided to directly ask you the question.

This week Symfony published three security releases to address a potential code injection issue in the way Symfony implements translation caching in FrameworkBundle. In addition, it fixed object initializers for Validator component and it removed spaceless blocks from Twig templates.

Symfony 2.6 adds support for embedding notes in XLIFF files. This will allow to include contextual information to improve translations.