Description
Symfony 2.6.5 version changed the way errors are displayed in the browser. Lately a lot of users are complaining about this new behavior: #14337, #14199, #1396, #14111, #14073.
Symfony 2.7 beta tried to solve this problem, but the result is not completely satisfactory.
To better understand the problem, check out the different error messages that you get when your controller uses the @Security
annotation without importing its associated class.
Symfony 2.6.4
The error message is perfect.
Symfony 2.6.5 and 2.6.6
The error message is awful.
Symfony 2.7
You see 4 error messages instead of just 1. The good error is displayed at the bottom and the awful error is displayed first.
This behavior only happens in the browser. If you use Symfony 2.6.5 or 2.6.6 in the console, you get perfect error messages:
In my opinion this is a critical issue that should be fixed both for 2.6 and 2.7.