2011-10-17 09:18:15 |
Sébastien BEAU - http://www.akretion.com |
bug |
|
|
added bug |
2011-10-17 09:18:28 |
Sébastien BEAU - http://www.akretion.com |
magentoerpconnect: status |
New |
Confirmed |
|
2011-10-17 09:18:32 |
Sébastien BEAU - http://www.akretion.com |
magentoerpconnect: importance |
Undecided |
Low |
|
2011-10-17 09:23:30 |
Sébastien BEAU - http://www.akretion.com |
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 |
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 |
|
2011-10-17 12:48:01 |
Sébastien BEAU - http://www.akretion.com |
magentoerpconnect: assignee |
|
Sébastien BEAU - http://www.akretion.com (sebastien.beau) |
|
2012-07-06 12:05:32 |
Alexandre Fayolle - camptocamp |
bug |
|
|
added subscriber Alexandre Fayolle @ camptocamp |
2012-07-06 14:53:38 |
Alexandre Fayolle - camptocamp |
branch linked |
|
lp:~magentoerpconnect-core-editors/magentoerpconnect/trunk-fix-876312 |
|
2012-07-06 14:53:50 |
Alexandre Fayolle - camptocamp |
magentoerpconnect: status |
Confirmed |
In Progress |
|
2012-07-06 14:53:53 |
Alexandre Fayolle - camptocamp |
magentoerpconnect: assignee |
Sébastien BEAU - http://www.akretion.com (sebastien.beau) |
Alexandre Fayolle @ camptocamp (alexandre-fayolle-c2c) |
|
2012-07-06 14:54:04 |
Alexandre Fayolle - camptocamp |
magentoerpconnect: importance |
Low |
High |
|
2012-07-09 12:21:49 |
Alexandre Fayolle - camptocamp |
magentoerpconnect: status |
In Progress |
Fix Committed |
|
2012-07-18 09:21:52 |
Matteo Parolini - Tecnica Informatica |
bug |
|
|
added subscriber Matteo Parolini - Tecnica Informatica |
2012-07-23 05:33:00 |
Launchpad Janitor |
branch linked |
|
lp:magentoerpconnect/openerp6.1-legacy-module |
|