Symfony 3.3.4 released

Warning: Symfony 3.3 is no longer supported. Consider upgrading your applications to the most recent Symfony version.

Symfony 3.3.4 has just been released. Here is a list of the most important changes:

  • bug #23413 [VarDumper] Reduce size of serialized Data objects (@nicolas-grekas)
  • bug #23385 [DoctrineBridge] Fix resetting entity managers with case sensitive id (@chalasr)
  • bug #23390 [Cache] Handle APCu failures gracefully (@nicolas-grekas)
  • bug #23371 [FrameworkBundle] 3.3: Don't get() private services from debug:router (@ogizanagi)
  • bug #23378 [FrameworkBundle] Do not remove files from assets dir (@1ed)

Want to upgrade to this new release? Fortunately, because Symfony protects backwards-compatibility very closely, this should be quite easy. Read our upgrade documentation to learn more.

Want to be notified whenever a new Symfony release is published? Or when a version is not maintained anymore? Or only when a security issue is fixed? Consider subscribing to the Symfony Roadmap Notifications.

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.


Thanks for the quick fixes!
Thanks !
Much appreciated. Thanks !
Does anyone have issues with generating doctrine entities outside a Bundle?! I've been testing with 3.3 but I can't get it to work.
Hey there, Dennis Smink

I dk if this is late but I got one solution for creating entitites after version 3.2*:

I used this workaround in the composer.json (inside your project folder):

"psr-4": {
"AppBundle\\": "src/AppBundle",
"NameBundle\\": "src/NameBundle"

And played this command on the server :
composer dump-autoload

Hope this helps! \,,/ (>.

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.