README

If you want to add a brand to your products this is the plugin to use. Use cases:

Add brand logo to your product pages
Filter by brand in the frontend or backend, i.e. product lists

Screenshots

CLICK TO SEE

Menu:

Brand admin pages:

Products admin pages:

Installation

Step 1: Download the plugin

Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:

$ composer require loevgaard/sylius-brand-plugin

This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.

Step 2: Enable the plugin

Then, enable the plugin by adding it to the list of registered plugins/bundles in config/bundles.php file of your project before (!) SyliusGridBundle:

<?php

# config/bundles.php

return [
    // ...
    Loevgaard\SyliusBrandPlugin\LoevgaardSyliusBrandPlugin::class => ['all' => true],
    Sylius\Bundle\GridBundle\SyliusGridBundle::class => ['all' => true],
    // ...
];

Step 3: Configure the plugin

# config/packages/loevgaard_sylius_brand.yaml

imports:
    # ...
    - { resource: "@LoevgaardSyliusBrandPlugin/Resources/config/app/config.yaml" }

    # If you want to see Brand column at admin products list - uncomment next line
    # - { resource: "@LoevgaardSyliusBrandPlugin/Resources/config/grids/sylius_admin_product.yaml" }

# config/routes/loevgaard_sylius_brand.yaml

loevgaard_sylius_brand:
    resource: "@LoevgaardSyliusBrandPlugin/Resources/config/routing.yaml"

Step 4: Extend services and entities

Extend `Product`

If you use annotations mapping:

<?php

declare(strict_types=1);

namespace App\Entity;

use Doctrine\ORM\Mapping as ORM;
use Loevgaard\SyliusBrandPlugin\Model\ProductInterface as LoevgaardSyliusBrandPluginProductInterface;
use Loevgaard\SyliusBrandPlugin\Model\ProductTrait as LoevgaardSyliusBrandPluginProductTrait;
use Sylius\Component\Core\Model\Product as BaseProduct;

/**
 * @ORM\Entity
 * @ORM\Table(name="sylius_product")
 */
class Product extends BaseProduct implements LoevgaardSyliusBrandPluginProductInterface
{
    use LoevgaardSyliusBrandPluginProductTrait;
}

If you use xml mapping:

<?php
// src/Model/Product.php

declare(strict_types=1);

namespace App\Model;

use Loevgaard\SyliusBrandPlugin\Model\ProductInterface as LoevgaardSyliusBrandPluginProductInterface;
use Loevgaard\SyliusBrandPlugin\Model\ProductTrait as LoevgaardSyliusBrandPluginProductTrait;
use Sylius\Component\Core\Model\Product as BaseProduct;

class Product extends BaseProduct implements LoevgaardSyliusBrandPluginProductInterface
{
    use LoevgaardSyliusBrandPluginProductTrait;
    
    // ...
}

<?xml version="1.0" encoding="UTF-8"?>

<!-- config/doctrine/model/Product.orm.xml -->

<doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
                                      http://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">

    <mapped-superclass name="App\Model\Product" table="sylius_product">
        <many-to-one field="brand" target-entity="Loevgaard\SyliusBrandPlugin\Model\BrandInterface" inversed-by="products">
            <join-column name="brand_id" on-delete="SET NULL" />
        </many-to-one>
    </mapped-superclass>

</doctrine-mapping>

Extend `ProductRepository`

<?php
# src/Doctrine/ORM/ProductRepository.php

declare(strict_types=1);

namespace App\Doctrine\ORM;

use Loevgaard\SyliusBrandPlugin\Doctrine\ORM\ProductRepositoryInterface as LoevgaardSyliusBrandPluginProductRepositoryInterface;
use Loevgaard\SyliusBrandPlugin\Doctrine\ORM\ProductRepositoryTrait as LoevgaardSyliusBrandPluginProductRepositoryTrait;
use Sylius\Bundle\CoreBundle\Doctrine\ORM\ProductRepository as BaseProductRepository;

class ProductRepository extends BaseProductRepository implements LoevgaardSyliusBrandPluginProductRepositoryInterface
{
    use LoevgaardSyliusBrandPluginProductRepositoryTrait;

    // ...
}

Configure

config/services.yaml

sylius_product:
    resources:
        product:
            classes:
                model: App\Model\Product # Or App\Entity\Product
                repository: App\Doctrine\ORM\ProductRepository

Step 5: Update your database schema

$ php bin/console doctrine:migrations:diff
$ php bin/console doctrine:migrations:migrate

Fixtures

Include prefedined brand fixtures to play with on your dev environment:

# config/packages/loevgaard_sylius_brand.yaml

imports:
    - { resource: "@LoevgaardSyliusBrandPlugin/Resources/config/app/fixtures.yaml" }

Or write your own:

Add a new yaml file to the folder config/packages and name it as you wish, e.g. my_own_fixtures.yaml.

Fill this yaml with your own brand fixtures and don't forget to declare the definition of your product(s) before this brand definition or use existing product(s) code.

# config/packages/my_own_fixtures.yaml

sylius_fixtures:
   suites:
       my_own_brand_fixtures:
            fixtures:
                loevgaard_sylius_brand_plugin_brand:
                    options:
                        custom:
                            my_brand:
                                name: 'My brand'
                                code: 'my-brand'
                                images:
                                    local_image:
                                        type: logo
                                        path: images/my-brand/logo.jpg
                                    3rd_party_plugin_image:
                                        type: black-and-white
                                        path: '@SomePlugin/Resources/images/my-brand/black-and-white.jpg'
                                products:
                                  - product_code_1
                                  - product_code_2
                                  - product_code_3

See example at src/Resources/config/app/fixtures.yaml.

Load your fixtures

php bin/console sylius:fixture:load my_own_brand_fixtures

Installation and usage for plugin development

To run test application to play with just type composer try.

Sonata blocks available

loevgaard_sylius_brand.admin.brand.create.tab_details
loevgaard_sylius_brand.admin.brand.update.tab_details
loevgaard_sylius_brand.admin.brand.create.tab_media
loevgaard_sylius_brand.admin.brand.update.tab_media

Events available

loevgaard_sylius_brand.menu.admin.brand.form to customize Brand admin form like you usually do with Product form via sylius.menu.admin.product.form event.

Testing

Play with API

Install https://stedolan.github.io/jq/ (type brew install jq at OSX terminal)

Get admin API access token:

SYLIUS_ADMIN_API_ACCESS_TOKEN=$(curl http://localhost:8000/api/oauth/v2/token \
    --silent --show-error \
    -d "client_id"=demo_client \
    -d "client_secret"=secret_demo_client \
    -d "grant_type"=password \
    -d "username"=api@example.com \
    -d "password"=sylius-api | jq '.access_token' --raw-output)

Make requests:

(GET requests indexing/showing resources shown here as an example, see tests/Controller/*ApiTest.php to discover more details about creating/updating/removing brand-related resources, creating new products with brand attached to it, uploading image files for BrandImages via API)

To Brands admin API:

curl http://localhost:8000/api/v1/brands/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

curl http://localhost:8000/api/v1/brands/setono/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

Brand images API:

curl http://localhost:8000/api/v1/brands/setono/images/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

Brand images by type API:

curl http://localhost:8000/api/v1/brands/setono/images/logo/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

curl http://localhost:8000/api/v1/brands/setono/images/<ID>/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

Brand products API:

curl http://localhost:8000/api/v1/brands/setono/products/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

Product details API:

curl http://localhost:8000/api/v1/products/setono-mug/ \
    -H "Authorization: Bearer $SYLIUS_ADMIN_API_ACCESS_TOKEN"

For XML output, add -H "Accept: application/xml" to request

Contribute

Please, run composer all to run all checks and tests before committing.

Contribute by translating

We use the same service as Sylius for translating, namely Crowdin. You can help out by translating this project into your mother tongue ;)

Thanks!

loevgaard / sylius-brand-plugin

Maintainers

Details

README

Screenshots

Installation

Step 1: Download the plugin

Step 2: Enable the plugin

Step 3: Configure the plugin

Step 4: Extend services and entities

Extend `Product`

Extend `ProductRepository`

Configure

Step 5: Update your database schema

Fixtures

Installation and usage for plugin development

Sonata blocks available

Events available

Testing

Play with API

Contribute

Contribute by translating

loevgaard / sylius-brand-plugin

Maintainers

Details

README

Screenshots

Installation

Step 1: Download the plugin

Step 2: Enable the plugin

Step 3: Configure the plugin

Step 4: Extend services and entities

Extend Product

Extend ProductRepository

Configure

Step 5: Update your database schema

Fixtures

Installation and usage for plugin development

Sonata blocks available

Events available

Testing

Play with API

Contribute

Contribute by translating

Extend `Product`

Extend `ProductRepository`