* kriswallsmith/assetic/explicit-filter-config:
[AsseticBundle] added lessphp filter
[AsseticBundle] added config for image filters
[AsseticBundle] moved filters into individual config files which must be explicitly loaded
[AsseticBundle] removed configuration of default output strings
You must now explicitly load those filters you want to use in your app. Some filters have additional configuration options:
assetic:
filters:
cssrewrite: ~
yui_css: { jar: "/path/to/yuicompressor.jar" }
You can also register your own filters now by referencing a configuration file:
assetic:
filters:
my_filter:
resource: "%kernel.root_dir%/config/my_filter.xml"
foo: bar
This configuration would load the referenced configuration file and set the "assetic.filter.my_filter.foo" parameter to "bar"
* kriswallsmith/kernel/shorter-bundle-names:
updated codebase to use shorter bundle names
[HttpKernel] updated component to work with shorter bundle names
[HttpKernel] updated Bundle::getName() to validate bundle class name and rtrim "Bundle"
Controllers:
"BlogBundle:Post:show" is now "Blog:Post:show"
Templates:
"BlogBundle:Post:show.html.twig" is now "Blog:Post:show.html.twig"
Resources:
"@BlogBundle/Resources/config/blog.xml" is now "@Blog/Resources/config/blog.xml"
Doctrine:
"$em->find('BlogBundle:Post', $id)" is now "$em->find('Blog:Post', $id)"
The background is that Chrome only displays the content returned on an error page if payload is at least 512 bytes.
Prior to this change, the 404 page was just a few bytes short, resulting in the Chrome error message instead of the
real one returned by Symfony (confusing for the user).
* schmittjoh/security:
changed condition nesting
[Security] ACL: AclVoter::vote only gets an ObjectIdentity if $object is not an instance of ObjectIdentityInterface
[SecurityBundle] fixed missing argument EventDisplatcher in RememberMe service
* stealth35/use_filesystemiterator:
simplify folders deletion
work with Traversable
added FilesystemIterator namespace
tab to spaces
use FilesytemIterator insteed opendir
Quote from HTTP (bis) spec (Part 2 - 5.1.1):
The Reason Phrase exists for the
sole purpose of providing a textual description associated with the
numeric status code, out of deference to earlier Internet application
protocols that were more frequently used with interactive text
clients. A client SHOULD ignore the content of the Reason Phrase.
* weaverryan/controller-cannot-find-exception:
[FrameworkBundle] Giving a more specific message when a Bundle:Controller:Action controller class cannot be found
It's a detail, but it hits usability. For normal bundles (those without children), we're able to actually print the namespace where we're looking for the Controller. For bundles with children, this would be a very verbose message, but we can at least print all of the bundles that we looked inside of.
