c2c-oerpscenario team mailing list archive

[Sébastien BEAU - http://www.akretion.com <sebastien.beau@xxxxxxxxxxxx>]

** Changed in: magentoerpconnect
     Assignee: (unassigned) => Sébastien BEAU - http://www.akretion.com (sebastien.beau)

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/876312

Title:
  [TRUNK] available_sort_by bug/feature magento limitation

Status in Magento OpenERP Connector:
  Confirmed

Bug description:
  Hi
  On previous version the attributs available_sort_by was uncorrectly supported. Indeed the field available_sort_by was a many2one in openerp and a multiselect in magento. Now the field is a many2many in Openerp.
  I just finish to refactor the code and and it's look like the syncronization openerp=>magento is still not correct.
  Indeed if I push the value with the data None for available_sort_by (this is mean 'use default configuration') it's work perfectly.
  But if I push with some option (for example : ['price', 'name']) Magento raise an error and tell us that the attributs available_sort_by is require. It's look like that with some version of magento the API have a bug.

  I will try to spend more time to fix it but as the refactor doesn't introduce any regression, It not a priority for the moment.
  Indeed tou can you syncronize still syncronize (as before) the category using the default configuration for default_sort_by and available_sort_by.
  If it's really important for you to have this feature working perfectly, ask us.
  Best regards

  change done on trunk rev 469 and 470

To manage notifications about this bug go to:
https://bugs.launchpad.net/magentoerpconnect/+bug/876312/+subscriptions