Events

EasyAdmin triggers several Symfony events during the execution of its requests, so you can listen to those events and run your own logic.

Events were useful in EasyAdmin versions previous to 3.0, because backends were defined with YAML config files instead of PHP code. Starting from EasyAdmin 3.0 everything is defined with PHP. That's why it's easier to customize backend behavior overloading PHP classes and methods and calling to your own services. However, the events still remain in case you want to use them.

All events are triggered using objects instead of event names defined as strings (as recommended since Symfony 4.3). They are defined under the EasyCorp\Bundle\EasyAdminBundle\Event\ namespace:

• Events related to Doctrine entities:

  • AfterEntityBuiltEvent
  • AfterEntityDeletedEvent
  • AfterEntityPersistedEvent
  • AfterEntityUpdatedEvent
  • BeforeEntityDeletedEvent
  • BeforeEntityPersistedEvent
  • BeforeEntityUpdatedEvent

• Events related to resource admins:

  • AfterCrudActionEvent
  • BeforeCrudActionEvent

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

# src/EventSubscriber/EasyAdminSubscriber.php
namespace App\EventSubscriber;

use App\Entity\BlogPost;
use EasyCorp\Bundle\EasyAdminBundle\Event\BeforeEntityPersistedEvent;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;

class EasyAdminSubscriber implements EventSubscriberInterface
{
    private $slugger;

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

    public static function getSubscribedEvents()
    {
        return [
            BeforeEntityPersistedEvent::class => ['setBlogPostSlug'],
        ];
    }

    public function setBlogPostSlug(BeforeEntityPersistedEvent $event)
    {
        $entity = $event->getEntityInstance();

        if (!($entity instanceof BlogPost)) {
            return;
        }

        $slug = $this->slugger->slugify($entity->getTitle());
        $entity->setSlug($slug);
    }
}