sylake/akeneoproducerbundle

[DEPRECATED] Produces messages consumed by Sylake/SyliusConsumerBundle.

This Akeneo producer bundle is deprecated & supports Akeneo 1.7 only

AkeneoProducerBundle

Makes Akeneo produce AMQP messages pushed through RabbitMQ.

Installation

1. Require this package:

$ composer require sylake/akeneo-producer-bundle

2. Add bundles to AppKernel.php of existing Akeneo application:

protected function registerProjectBundles()
{
    return [
        new \OldSound\RabbitMqBundle\OldSoundRabbitMqBundle(),
        new \Sylake\AkeneoProducerBundle\SylakeAkeneoProducerBundle(),
    ];
}

3. Configure RabbitMQ default connection:

# app/config/config.yml

old_sound_rabbit_mq:
    connections:
        default:
            host: 'localhost'
            port: 5672
            user: 'guest'
            password: 'guest'

4. Configure locales (optional) (default: en_GB, de_DE):

# app/config/config.yml

sylake_akeneo_producer:
    locales:
        - 'en_GB'
        - 'de_DE'

Usage

1. Perform export via UI or CLI:

$ app/console akeneo:batch:create-job "Sylake - Akeneo Producer" sylake_akeneo_producer export sylake_akeneo_producer
$ app/console akeneo:batch:job sylake_akeneo_producer

You can also export just one product by its SKU by running:

$ app/console sylake:producer:export-product PRODUCT_SKU

akeneoproducerbundle's Issues

Export Products

• With images
• With categories
• With attributes
• With associations

Export Attributes

Register each item projector as a service

Is it possible have each ItemProjector registered in the container as a separate service with it's own id?

Currently ItemProjector services don't have service id's and there is no way to reuse them or make decorators for each service.

Same goes to the doctrine event listeners (CategorySavedListener etc.).

Is there a reason for this, if not could they be added?

Phpspec

We got a problem with its configuration. when I run a bin/phpspec run, it generates classes into src\ Sylake\Bundle\SylakimBundle\.... I tried to play with src_path but it doesn't change anything... Do you have a idea ?

How far is this connector?

Hi, a connection between Akeneo PIM and Sylius would be awesome.
How far is this repository in doing this?

Add LICENSE

Export Association Types

Developement tools

@jjanvier You should register it to Travis, Sensio Insight and Packagist and update the readme with the beautiful icons.

Export Categories

Add README

Update the repository and bootstrap the connector

• README
• Update namespaces
• Setup Travis-CI

Support Akeneo 2.0

Please support Akeneo 2.0 and up

Installation trouble - composer dependency resolve - guzzle

I want to run Sylakim, but i can't. Should I require package via composer to existing akeneo/pim-community-standard project?
If yes, then I've got:

Using version ^0.1.0@dev for sylake/sylakim
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for sylake/sylakim ^0.1.0@dev -> satisfiable by sylake/sylakim[0.1.x-dev].

• Conclusion: remove guzzle/common v3.7.4
  • Conclusion: don't install guzzle/common v3.7.4
  • sylake/sylakim 0.1.x-dev requires guzzlehttp/guzzle ~3.8 -> satisfiable by guzzlehttp/guzzle[v3.8.0, v3.8.1].
  • don't install guzzlehttp/guzzle v3.8.0|don't install guzzle/common v3.7.4
  • don't install guzzlehttp/guzzle v3.8.1|don't install guzzle/common v3.7.4
  • Installation request for guzzle/common == 3.7.4.0 -> satisfiable by guzzle/common[v3.7.4].

How can I solve that?

[UI] Create export profile via ui

Check that creating export profile works via UI.

Validation error on creating job

I get locale validation error when trying to create a job. My locale is en_US, but en_GB and de_de are hardcoded in Sylake\AkeneoProducerBundle\Connector\JobParameters\AkeneoProducer (https://github.com/Sylake/AkeneoProducerBundle/blob/master/src/Connector/JobParameters/AkeneoProducer.php#L53). I think locales setting should be set from active system locales or made configurable

$ app/console akeneo:batch:create-job "Sylake - Akeneo Producer" sylake_akeneo_producer export sylake_akeneo_producer

A validation error occurred with the job configuration "

• Array[filters][structure][locales][0]:
  The locale en_GB is not valid.
• Array[filters][structure][locales][1]:
  The locale de_DE is not valid.".