Use plugin configuration

In our guide on how to add a plugin configuration, you can learn how to provide this possibility to use configuration options in your plugins. This guide will aid you on how to then use this configuration in your plugin.
Prerequisites
In order to add a plugin configuration, you sure need to provide your plugin first. However, you won't learn to create a plugin in this guide. Head over to our plugin base guide to create your plugin first. It is also recommended to know how to setup a plugin configuration in the first instance. In this example, the configurations will be read inside of a subscriber, so knowing the Listening to events guide will also be helpful.
Overview
The plugin in this example already knows a subscriber, which listens to the product.loaded event and therefore will be called every time a product is loaded.
<plugin root>/src/Subscriber/MySubscriber.php
<?php declare(strict_types=1);
​
namespace Swag\BasicExample\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 [
            ProductEvents::PRODUCT_LOADED_EVENT => 'onProductsLoaded'
        ];
    }
​
    public function onProductsLoaded(EntityLoadedEvent $event): void
    {
        // Do stuff with the product
    }
}
For this guide, a very small plugin configuration file is available as well:
<plugin root>/src/Resources/config/config.xml
<?xml version="1.0" encoding="UTF-8"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware/platform/master/src/Core/System/SystemConfig/Schema/config.xsd">
​
    <card>
        <title>Minimal configuration</title>
        <input-field>
            <name>example</name>
        </input-field>
    </card>
</config>
Just a simple input field with the technical name example. This will be necessary in the next step.
Reading the configuration
Let's get to the important part. Reading the plugin configuration is based on the Shopware\Core\System\SystemConfig\SystemConfigService. This service is responsible for reading all configs from Shopware 6, such as the plugin configurations.
Inject this service into your subscriber using the DI container.
<plugin root>/src/Resources/config/services.xml
<?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\BasicExample\Subscriber\MySubscriber">
            <argument type="service" id="Shopware\Core\System\SystemConfig\SystemConfigService" />
            <tag name="kernel.event_subscriber"/>
        </service>
    </services>
</container>
Note the new argument being provided to your subscriber. Now create a new field in your subscriber and pass in the SystemConfigService:
<plugin root>/src/Subscriber/MySubscriber.php
<?php declare(strict_types=1);
​
namespace Swag\BasicExample\Subscriber;
​
...
use Shopware\Core\System\SystemConfig\SystemConfigService;
​
class MySubscriber implements EventSubscriberInterface
{
    /**
     * @var SystemConfigService
     */
    private $systemConfigService;
​
    public function __construct(SystemConfigService $systemConfigService)
    {
        $this->systemConfigService = $systemConfigService;
    }
​
    public static function getSubscribedEvents(): array
    {
        ...
    }
    ...
}
So far, so good. The SystemConfigService is now available in your subscriber.
This service comes with a get method to read the configurations. The first idea would be to simply call $this->systemConfigService->get('example') now, wouldn't it? Simply using the technical name you've previously set for the configuration.
But what would happen, if there were more plugins providing the same technical name for their very own configuration field? How would you access the proper field, how would you prevent plugin conflicts?
That's why the plugin configurations are always prefixed. By default, the pattern is the following: <BundleName>.config.<configName> Thus, it would be SwagBasicExample.config.example here.
<plugin root>/src/Subscriber/MySubscriber.php
<?php declare(strict_types=1);
​
namespace Swag\BasicExample\Subscriber;
​
...
​
class MySubscriber implements EventSubscriberInterface
{
    ...
    public function onProductsLoaded(EntityLoadedEvent $event): void
    {
        $exampleConfig = $this->systemConfigService->get('SwagBasicExample.config.example');
    }
}
Add plugin configuration
Database migrations
Last updated 2 weeks ago