Services and Subscriber

Plugin base class

Registering a custom subscriber requires to load a custom services.xml file with your plugin. This is done in your plugins base class by using the build method. Make sure to have a look at the guide about the plugin base class for further information. Registering a custom subscriber requires to load a services.xml file with your plugin. This is done by either placing a file with name services.xml into a directory called src/Resources/config/ or by overriding the method getServicesFilePath of your plugin base class.

// SubscriberPlugin/src/SubscriberPlugin.php

namespace Swag\SubscriberPlugin;

use Shopware\Core\Framework\Plugin;
use Symfony\Component\DependencyInjection\ContainerBuilder;
use Symfony\Component\DependencyInjection\Loader\XmlFileLoader;
use Symfony\Component\Config\FileLocator;

class SubscriberPlugin extends Plugin
{
    public function getServicesFilePath(): string
    {
        return 'Resources/custom_path/custom_file.xml';
    }
}

Basically, that's it already if you're familiar with Symfony subscribers. Don't worry, we got you covered here as well.

Creating the subscriber class

As mentioned above, a subscriber for Shopware 6 looks exactly the same like in Symfony itself. Therefore, this is how your subscriber could then look like:

<?php declare(strict_types=1);

namespace Swag\SubscriberPlugin\Subscriber;

use Shopware\Core\Framework\DataAbstractionLayer\Event\EntityLoadedEvent;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Shopware\Core\Content\Product\ProductEvents;

class MySubscriber implements EventSubscriberInterface
{
    public static function getSubscribedEvents(): array
    {
        // Return the events to listen to as array like this:  <event to listen to> => <method to execute>
        return [
            ProductEvents::PRODUCT_LOADED_EVENT => 'onProductsLoaded'
        ];
    }

    public function onProductsLoaded(EntityLoadedEvent $event)
    {
        // Do something
        // E.g. work with the loaded entities: $event->getEntities()
    }
}

In this example, the subscriber would be located in the <plugin root>/src/Subscriber directory.

The subscriber is now listening for the product.loaded event to trigger. Unfortunately, your subscriber is not even loaded yet - this will be done in the previously registered services.xml file.

Introducing your subscriber via services.xml

Registering your subscriber to Shopware 6 is also as simple as it is in Symfony. You're simply registering your (subscriber) service by mentioning it in the services.xml. The only difference to a normal service is, that you need to add the kernel.event_subscriber tag to your subscriber for it to be recognized as such.

<?xml version="1.0" ?>

<container xmlns="http://symfony.com/schema/dic/services"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">

    <services>
        <service id="Swag\SubscriberPlugin\Subscriber\MySubscriber">
            <tag name="kernel.event_subscriber"/>
        </service>
    </services>
</container>

That's it, your subscriber service is now automatically loaded at runtime and it should start listening to the mentioned events to be dispatched.

Source

There's a GitHub repository available, containing this example source. Check it out here.