Symfony Blog

A security issue has been discovered in FOSUserBundle (CVE-2013-5750).

This week, the new Expression Language component was added to the master branch of the Symfony2 repository. This component allows the use of expressions for services definition, routes, access control rules and validation constraints. It was publicly introduced this week at the Symfony Live London 2013 conference and it will be the main new feature of Symfony 2.4.

This week, the DependencyInjection component fixed some undetected circular references, the EventDispatcher events were made lighter and the Form component made a lot of tweaks and improved its code coverage. Meanwhile, the Symfony Live London 2013 conference will take place next week, where Fabien will introduce a game changing feature for the upcoming Symfony 2.4.

This week, the new Expression Language component focused all the development activity. This component provides an engine that can compile and evaluate expressions, allowing to define dynamic annotations and configuration files. Some of the most important Symfony pieces already support expressions: the service container, the security access control rules, the routing component and the validator constraints.

Symfony 2.4 adds the possibility to restrict a security firewall to specific hosts.

This week, Symfony 2.2.6 and Symfony 2.3.4 maintenance versions were released. Meanwhile, the upcoming Symfony 2.4 version, which will be released in November, continued adding cool features, such as: logs in console, better error messages, expressions for service definitions and new Request events.

Symfony 2.4 adds the ability to define an idle timeout for a Process run.

Symfony 2.4 introduces a new tag to use the stopwatch in Twig templates.

Symfony 2.4 helps you fix those class not found and undefined function PHP errors.

Read release notes