This week, Symfony 2.2 continued removing any unnecessary hard dependencies between components, such as the coupling between DependencyInjection and Config components. In addition, the logging in the exception listener was refactored to allow overloading of the default behavior.
Symfony 2.0.20 and Symfony 2.1.5 have just been released and they both contain two security fixes.
Symfony 2.2 introduces some interesting security utilities.
The process for handling security issues has been improved.
Symfony 2.2 logs deprecated calls.
This week, Symfony development activity was extremely intense. Symfony 2.2 version added lots of cool features and small tweaks across all its major components.
Symfony 2.2 introduces some useful dialog helpers in the Console component to improve the interaction with the user.
Symfony 2.2 introduces many small tweaks that enhance your experience.
Symfony 2.2 introduces payment related validators.
Symfony 2.2 introduces caching for static pages.
According to our release process, we will soon reach the end of the development phase for Symfony 2.2.
This week Symfony 2.2 continued adding nice features and tweaks, such as the new fatal error pages. In addition, it was announced that the next edition of the Symfony Live conference in United States will be held at Portland and it will be co-located with two other big conferences: DrupalCon and WebVisions
Symfony Live Berlin 2012 Wrap up
Symfony 2.2 nicely displays fatal errors.
The US Symfony Live for 2013 has been announced and guess what? It’s going to be Symfo-tastic: DrupalCon Portland, Symfony Live and WebVisions will co-locate their May 2013 conference in Portland, Oregon.
This week, Symfony 2.0.19 and 2.1.4 versions were released to address a potential security vulnerability related to
Request::getClientIp() method. This security fix also made possible to tweak the algorithm used to determine the trusted client IP and added a way to configure the
X-Forwarded header names and a way to disable trusting them.