synolia/oroneo

oroneo's Issues

Prices attribute type management

In the attributes synchronization, the attribute type pim_catalog_price_collection is rejected by the validation, and supposedly not managed by the connector.

new version of oroneo ?

Hello,

I'm checking out orocommerce, and (as we already are using Akeneo v2.3), I was wondering if you are investigating using the API from Akeneo in a future version of your connector?

Also, are there plans to make a new version of the connector that will work with the latest releases of Orocommerce CE ?

If this is not the right place to ask, please let me know where I should go to.

Thanks,
Tom

Cannot change the default locale to use with attributes and options labels

There is no option to change the mapping used for the attribute and options labels.

The locale fr_FR is made mandatory and used as the desired locale, which may not be the desired one on all installs.

https://github.com/synolia/oroneo/blob/master/Migrations/Data/ORM/SetDefaultMappings.php#L55
https://github.com/synolia/oroneo/blob/master/Migrations/Data/ORM/SetDefaultMappings.php#L65

Assets collection attribute type management (Akeneo EE)

There is no management for the pim_assets_collection attribute type in the connector.

This attribute type is only present in the EE of Akeneo

The attributes import produces errors in the Oro menu

For the record, the attributes import produces errors in the Oro menu on beta 5 (reported as oroinc/orocommerce#13)

[QUESTION] The reason of using manyToMany relations instead of multi-select

Is there a special reason why the connector is using Select fields for pim_catalog_select attributes and ManyToMany fields with the LocalisedFallbackEntity for pim_ctaalog_multiselect ones ?

Was the MultiSelect type inappropriate ?

[Question] Compatibility with OroCommerce 1.0.0

Hi,

Do you have in the nearest timeline (upcoming days/weeks) plans to make Oroneo compatible with the latest stable version of OroCommerce?

Thanks,
Tomasz

Compatability with Akeneo 1.7 and Oro 1.6

Has this been tested with the versions mentioned in the title? Are the instructions up to date?

Cannot import multi-enum options

An InvalidArgumentException is thrown by the BAP when importing manyToMany enum is thrown with the message $enumCode must not be empty..

It is sent here : https://github.com/orocrm/platform/blob/master/src/Oro/Bundle/EntityExtendBundle/Tools/ExtendHelper.php#L272

At this point https://github.com/synolia/oroneo/blob/master/ImportExport/Serializer/OptionSerializer.php#L45

Here is the config I have in $config variable :

object(Oro\Bundle\EntityConfigBundle\Config\Config) {
  'id': object(Oro\Bundle\EntityConfigBundle\Config\Id\FieldConfigId) {
    'scope': 'enum'
    'className': 'Oro\\Bundle\\ProductBundle\\Entity\\Product'
    'fieldName': 'foo_field'
    'fieldType': 'manyToMany'
  }
  'values': []
}

The localized configuration fails to display

There have been a refactoring on the last commit, version 0.2.0, the localization configuration breaks :

Fatal error: Uncaught Error: Call to undefined method Oro\Bundle\LocaleBundle\Helper\LocalizationHelper::getAll() in /.../vendor/synolia/oroneo/Manager/OroFieldSelectManager.php:59 Stack trace:
#0 /.../vendor/synolia/oroneo/Form/Type/LocalizationMappingType.php(50): Synolia\Bundle\OroneoBundle\Manager\OroFieldSelectManager->getLocalizationChoices()
#1 /.../vendor/symfony/symfony/src/Symfony/Component/Form/ResolvedFormType.php(187): Synolia\Bundle\OroneoBundle\Form\Type\LocalizationMappingType->buildForm(Object(Symfony\Component\Form\FormBuilder), Array)
#2 /.../vendor/symfony/symfony/src/Symfony/Component/Form/Extension/DataCollector/Proxy/ResolvedTypeDataCollectorProxy.php(110): Symfony\Component\Form\ResolvedFormType->buildForm(Object(Symfony\Component\Form\FormBuilder), Array)

I'll look into the code