[11.0] [MIG] connector_magento #274
Conversation
Restructure files, split large python files Fix views * Add binding on sales orders * Ensure that we always have the Connector Manager group on the Connector tabs (most are done in the parent views of connector_ecommerce) * Fixed inheritance of the delivery.carrier view Collection.work_on is now a context manager Add a base listener and use it in partner export Rewrite tests using new API and vcr.py * Use vcr.py to record the exchanges instead of a self-made recorder * Use new base Components test case classes * Separate export tests in 2 phases: trigger of the export which check that the jobs are delayed, and test the job itself in a second test Update documentation Various fixes Add dependency on product_multi_category I removed it earlier, but it is required when we import products
Fix Pylint warnings Remove deprecated select for index creation [FIX] pass http credentials to backedn component if required [FIX] change user on backend otherwise import sale order will be done on the wrong one [CHG]review product aggregation by backend to improve performance
Remove related_action from import_batch
Add Magento Enterprise Gift Cards payment line. Unpacks the giftcard code from the PHP serialized information about the giftcards using regex. Don't add a 0 amount Giftcard line. Since the value will be a string like '0.0000', the prior tests were insufficient to prevent always adding a line.
Fix failing test * Rename it because it was shadowing another test * Compute in the location's context
Add Rewards and StoreCredit payment methods. (Travis Bump)
hugosantosred
force-pushed
the
11.0-mig-connector_magento
branch
2 times, most recently
from
a059f22
to
5ff679d
Compare
connector_magento/README.rst
Outdated
|
|
||
| This is the new release of the Open-Source connector linking Odoo and | ||
| Magento also known under the name of **Magentoerpconnect**. It is | ||
| build on top of the `connector`_ framework. It is is structured so that |
|
|
| self.env[model_name].import_batch(backend) | ||
| return True | ||
| except Exception as e: | ||
| _logger.error(e.message, exc_info=True) |
There was a problem hiding this comment.
This call will fail because the Exception e doesn't have an attribute called message
There was a problem hiding this comment.
Changes Done. Now Uses the ustr method from Odoo base to print the exception as text.
hugosantosred
force-pushed
the
11.0-mig-connector_magento
branch
5 times, most recently
from
995ed4d
to
8cce753
Compare
| <field eval="False" name="doall"/> | ||
| <field ref="connector_magento.model_magento_backend" name="model_id"/> | ||
| <field eval="'_scheduler_import_sale_orders'" name="function"/> | ||
| <field eval="'()'" name="args"/> |
There was a problem hiding this comment.
change to
<field name="state">code</field>
<field name="code">model._scheduler_import_sale_orders()</field>
There was a problem hiding this comment.
Changes Done, sorry for the delay!
|
Does this connector works for Magento 2 |
|
Hi...there is some news? Could i test it on my odoo v11? |
hugosantosred
force-pushed
the
11.0-mig-connector_magento
branch
from
8cce753
to
cc5117c
Compare
hugosantosred
force-pushed
the
11.0-mig-connector_magento
branch
from
cc5117c
to
832510b
Compare
|
This one misses some commit history from 10.0 (maybe added afterwards) and Travis is red. |
|
@jesusVMayor I cannot seem to make a pull request from my version of this, but on ~line 39 of "connector_magento/models/stock_picking/exporter.py" |
[MIG] connector_magento to v11
|
@jaredkipe have you tested @jesusVMayor 's module for magento2? Is it working? If so could you provide the m2 version with whom it worked? Thanks for any feedback. |
|
May I know the status of this PR? @StefanRijnhart |
|
No plan, but it should not be too hard I think. |
|
@seyuf We have had M1 on 11 for a long time stable in production. We are currently in a AB testing situation with M1 and M2 (2.3) at the same time, there are some issues here and there that I've been fixing as we go. |
|
Hi @jaredkipe , |
|
@seyuf I wouldn't say they're all minor (but maybe you do consider it minor), like this pricing fix. hibou-io@4a08c45 We do not use MSI because we already have customizations related to combining inventory from more than one stock location as the stock qty, and advanced order planning to direct orders to closest warehouse or splitting if there are stock issues. |
Migrated connector_magento to V11
Depends on: