Cover of the book Symfony 5: The Fast Track

Symfony 5: The Fast Track is the best book to learn modern Symfony development, from zero to production. +300 pages showcasing Symfony with Docker, APIs, queues & async tasks, Webpack, SPAs, etc.

  1. Home
  2. Documentation
  3. Cookbook
  4. Profiler
  5. How to use Matchers to enable the Profiler Conditionally
WARNING:

You are browsing the documentation for Symfony 2.2 which is not maintained anymore.

Consider upgrading your projects to Symfony 5.2.

How to use Matchers to enable the Profiler Conditionally

2.2 version
Unmaintained
2.2 2.3 2.4 2.5 2.6

How to use Matchers to enable the Profiler Conditionally

By default, the profiler is only activated in the development environment. But it’s imaginable that a developer may want to see the profiler even in production. Another situation may be that you want to show the profiler only when an admin has logged in. You can enable the profiler in these situations by using matchers.

Using the built-in Matcher

Symfony2 provides a built-in matcher which can match paths and IPs. For example, if you want to only show the profiler when accessing the page with the 168.0.0.1 IP, then you can use this configuration:

  • YAML
    1
2
3
4
5
6
    # app/config/config.yml
framework:
    # ...
    profiler:
        matcher:
            ip: 168.0.0.1
  • XML
    1
2
3
4
5
6
    <!-- app/config/config.xml -->
<framework:config>
    <framework:profiler
        ip="168.0.0.1"
    />
</framework:config>
  • PHP
    1
2
3
4
5
6
    // app/config/config.php
$container->loadFromExtension('framework', array(
    'profiler' => array(
        'ip' => '168.0.0.1',
    ),
));

You can also set a path option to define the path on which the profiler should be enabled. For instance, setting it to ^/admin/ will enable the profiler only for the /admin/ URLs.

Creating a Custom Matcher

You can also create a custom matcher. This is a service that checks whether the profiler should be enabled or not. To create that service, create a class which implements Symfony\Component\HttpFoundation\RequestMatcherInterface. This interface requires one method: matches(). This method returns false to disable the profiler and true to enable the profiler.

To enable the profiler when a ROLE_SUPER_ADMIN is logged in, you can use something like:

// src/Acme/DemoBundle/Profiler/SuperAdminMatcher.php
namespace Acme\DemoBundle\Profiler;

use Symfony\Component\Security\Core\SecurityContext;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\RequestMatcherInterface;

class SuperAdminMatcher implements RequestMatcherInterface
{
    protected $securityContext;

    public function __construct(SecurityContext $securityContext)
    {
        $this->securityContext = $securityContext;
    }

    public function matches(Request $request)
    {
        return $this->securityContext->isGranted('ROLE_SUPER_ADMIN');
    }
}

Then, you need to configure the service:

  • YAML
    1
2
3
4
5
6
7
    parameters:
    acme_demo.profiler.matcher.super_admin.class: Acme\DemoBundle\Profiler\SuperAdminMatcher

services:
    acme_demo.profiler.matcher.super_admin:
        class: "%acme_demo.profiler.matcher.super_admin.class%"
        arguments: ["@security.context"]
  • XML
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
    <parameters>
    <parameter
        key="acme_demo.profiler.matcher.super_admin.class"
    >Acme\DemoBundle\Profiler\SuperAdminMatcher</parameter>
</parameters>

<services>
    <service id="acme_demo.profiler.matcher.super_admin"
        class="%acme_demo.profiler.matcher.super_admin.class%">
        <argument type="service" id="security.context" />
</services>
  • PHP
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
    use Symfony\Component\DependencyInjection\Definition;
use Symfony\Component\DependencyInjection\Reference;

$container->setParameter(
    'acme_demo.profiler.matcher.super_admin.class',
    'Acme\DemoBundle\Profiler\SuperAdminMatcher'
);

$container->setDefinition('acme_demo.profiler.matcher.super_admin', new Definition(
    '%acme_demo.profiler.matcher.super_admin.class%',
    array(new Reference('security.context'))
);

Now the service is registered, the only thing left to do is configure the profiler to use this service as the matcher:

  • YAML
    1
2
3
4
5
6
    # app/config/config.yml
framework:
    # ...
    profiler:
        matcher:
            service: acme_demo.profiler.matcher.super_admin
  • XML
    1
2
3
4
5
6
    <!-- app/config/config.xml -->
<framework:config>
    <framework:profiler
        service="acme_demo.profiler.matcher.super_admin"
    />
</framework:config>
  • PHP
    1
2
3
4
5
6
    // app/config/config.php
$container->loadFromExtension('framework', array(
    'profiler' => array(
        'service' => 'acme_demo.profiler.matcher.super_admin',
    ),
));

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.