This bundle provides easy image manipulation support for Symfony2. For example, with this bundle, the following is possible:
<img src="{{ '/relative/path/to/image.jpg' | apply_filter('thumbnail') }}" />
This will perform the transformation called thumbnail
, which you can define
to do a number of different things, such as resizing, cropping, drawing,
masking, etc.
This bundle integrates the standalone PHP "Imagine library".
To install this bundle, you'll need both the Imagine library and this bundle. Installation depends on how your project is setup:
If you're using the bin/vendors.php
method to manage your vendor libraries,
add the following entries to the deps
in the root of your project file:
[Imagine]
git=https://github.com/avalanche123/Imagine.git
target=imagine
[AvalancheImagineBundle]
git=https://github.com/avalanche123/AvalancheImagineBundle.git
target=bundles/Avalanche/Bundle/ImagineBundle
NOTE: This location and syntax of the deps
file changed after BETA4. If you're
using an older version of the deps system, you may need to swap the order of the items
in the deps
file.
Next, update your vendors by running:
$ ./bin/vendors
Great! Now skip down to Step 2.
If you're managing your vendor libraries with submodules, first create the
vendor/bundles/Avalanche/Bundle
directory:
$ mkdir -pv vendor/bundles/Avalanche/Bundle
Next, add the two necessary submodules:
$ git submodule add git:https://github.com/avalanche123/Imagine.git vendor/imagine
$ git submodule add git:https://github.com/avalanche123/AvalancheImagineBundle.git vendor/bundles/Avalanche/Bundle/ImagineBundle
Add the following entries to your autoloader:
<?php
// app/autoload.php
$loader->registerNamespaces(array(
// ...
'Imagine' => __DIR__.'/../vendor/imagine/lib',
'Avalanche' => __DIR__.'/../vendor/bundles',
));
Finally, enable the bundle in the kernel:
<?php
// app/AppKernel.php
public function registerBundles()
{
$bundles = array(
// ...
new Avalanche\Bundle\ImagineBundle\AvalancheImagineBundle(),
);
}
Finally, add the following to your routing file:
# app/config/routing.yml
_imagine:
resource: .
type: imagine
Congratulations! You're ready to rock your images!
This bundle works by configuring a set of filters and then applying those filters to images inside a template. So, start by creating some sort of filter that you need to apply somewhere in your application. For example, suppose you want to thumbnail an image to a size of 120x90 pixels:
# app/config/config.yml
avalanche_imagine:
filters:
my_thumb:
type: thumbnail
options: { size: [120, 90], mode: outbound }
You've now defined a filter called my_thumb
that performs a thumbnail transformation.
We'll learn more about available transformations later, but for now, this
new filter can be used immediately in a template:
<img src="{{ '/relative/path/to/image.jpg' | apply_filter('my_thumb') }}" />
Or if you're using PHP templates:
<img src="<?php $this['imagine']->filter('/relative/path/to/image.jpg', 'my_thumb') ?>" />
Behind the scenes, the bundle applies the filter(s) to the image on the first request and then caches the image to a similar path. On the next request, the cached image would be served directly from the file system.
In this example, the final rendered path would be something like
/media/cache/my_thumb/relative/path/to/image.jpg
. This is where Imagine
would save the filtered image file.
The default configuration for the bundle looks like this:
avalanche_imagine:
source_root: %kernel.root_dir%/../web
web_root: %kernel.root_dir%/../web
cache_prefix: media/cache
driver: gd
filters: []
There are several configuration options available:
-
source_root
- can be set to the absolute path to your original image's directory. This option allows you to store the original image in a different location from the web root. Under this root the images will be looked for in the same relative path specified in the apply_filter template filter.default:
%kernel.root_dir%/../web
-
web_root
- must be the absolute path to you application's web root. This is used to determine where to put generated image files, so that apache will pick them up before handing the request to Symfony2 next time they are requested.default:
%kernel.root_dir%/../web
-
cache_prefix
- this is also used in the path for image generation, so as to not clutter your web root with cached images. For example by default, the images would be written to theweb/media/cache/
directory.default:
media/cache
-
driver
- one of the three drivers:gd
,imagick
,gmagick
default:
gd
-
filters
- specify the filters that you want to define and use
Each filter that you specify have the following options:
type
- determine the type of filter to be used, refer to Filters section for more informationoptions
- options that should be passed to the specific filter typepath
- override the globalcache_prefix
and replace it with this path
Currently, this bundles comes with just one built-in filter: thumbnail
.
The thumbnail filter, as the name implies, performs a thumbnail transformation on your image. Configuration looks like this:
filters:
my_thumb:
type: thumbnail
options: { size: [120, 90], mode: outbound }
The mode
can be either outbound
or inset
.
The ImagineBundle allows you to load your own custom filter classes. The only requirement is that each filter loader implement the following interface:
Avalanche\Bundle\ImagineBundle\Imagine\Filter\Loader\LoaderInterface
To tell the bundle about your new filter loader, register it in the service container and apply the following tag to it (example here in XML):
<tag name="imagine.filter.loader" filter="my_custom_filter" />
For more information on the service container, see the Symfony2 Service Container documentation.
You can now reference and use your custom filter when defining filters you'd like to apply in your configuration:
filters:
my_special_filter:
type: my_custom_filter
options: { }
For an example of a filter loader implementation, refer to
Avalanche\Bundle\ImagineBundle\Imagine\Filter\Loader\ThumbnailFilterLoader
.