This package is abandoned and no longer maintained. No replacement package was suggested.

Allows to easily use the media exposer library in a Symfony project

Installs: 2 219

Dependents: 0

Suggesters: 1

Security: 0

Stars: 8

Watchers: 30

Forks: 2

Open Issues: 0


dev-master 2012-04-24 15:50 UTC

This package is auto-updated.

Last update: 2022-09-23 13:39:39 UTC


The KnpMediaExposerBundle provides a simple integration of the MediaExposer library for your Symfony project.

The MediaExposer Library

The MediaExposer library allows you to easily expose you medias to the users of your application by computing their urls or paths.

You can find more informations on the official page.


The bundle depends on the MediaExposer library, so you need to copy it under the vendor/media-exposer directory of your Symfony project.

Grab the sources

Using the deps file

You can add the following lines to your deps file:



And run the command:

./bin/vendors install

Using git submodules

You can run the following git commands to add both library and bundle as submodules:

git submodule add vendor/media-exposer
git submodule add vendor/bundle/Knp/Bundle/MediaExposerBundle

Update your autoloader & kernel

Once you have copied the sources in your project, you must update your autoloader:

<?php // app/autoload.php

    // ... other namespaces
    'Knp\\Bundle'   => __DIR__.'/vendor/bundles',
    'MediaExposer'  => __DIR__.'/vendor/media-exposer/src'

Finally, register the bundle to your kernel:

<?php // app/AppKernel.php

public function registerBundles()
    $bundles = array(
        // ... the other bundles
        new Knp\Bundle\MediaExposerBundle\KnpMediaExposerBundle()

You can now proceed to the configuration.


To "absolutify" urls, the media exposer needs a base url that will be prepended to the relatives sources. By default, the host of the request will be used, but you can also specify it in your configuration:

# app/config/config.yml

    base_url:   'http://the-base.url'

Registering Resolvers

After the installation & configuration, the media exposer is almost ready for use. But there is still one step: registering your resolvers.

With this bundle, adding a resolver to the exposer is as simple as registering a service having the knp_media_exposer.resolver tag.

Here is an exemple of resolver service registration in yml:

        class:  'Foo\BarResolver'
            - { name: 'knp_media_exposer.resolver' }

An optional priority can also be specified:

        class:  'Foo\BarResolver'
            - { name: 'knp_media_exposer.resolver', priority: 10 }

Note: Don't forget that the highest priority is the first and the lowest is the last.


Twig integration

The bundle registers a Twig extension adding the necessary to use the Exposer in your templates.

The media_has_source function

The media_has_source function indicates whether the resolver can return a source for the given media:

{{ media_has_source(picture) }}

You can pass a hash of options as second argument:

{{ media_has_source(picture, {'foo':'bar'}) }}

The media_source function

The media_source function returns the source for the given media:

{{ media_source(picture) }}

You can specify an options hash as second argument:

{{ media_source(picture, {'foo':'bar'}) }}

If you want the Exposer to generate absolute sources (URLs), you can force it passing true as third argument:

{{ media_source(picture, {}, true) }}

The media_has_path function

The media_has_path function indicates whether the resolver can return a path for the given media:

{{ media_has_path(picture) }}

An hash of options can be passed as second argument:

{{ media_has_path(picture, {'foo':'bar'}) }}

The media_path function

The media_path function is responsible of returning a path for the given media:

{{ media_path(picture) }}

You can also specifiy options as second argument:

{{ media_path(picture, {'foo':'bar'}}

PHP templating integration

The bundle registers an extension for the PHP templating engine. You can access it using $view['media_exposer'] in your templates. It only contains proxy methods for the Exposer instances:

  • ->getSource($media [, array $options [, $forceAbsolute]])
  • ->hasSource($media [, array $options])
  • ->getPath($media [, array $options])
  • ->hasPath($media [, array $options])