[16.0][MIG] connector_prestashop_catalog_manager: Migration to 16.0 #181
+3,878
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
============================================= Catalog Manager for Odoo PrestaShop Connector ============================================= This module is an extension for *connector_prestashop*. With it, you will be able to manage your catalog directly from Odoo: * Create/modify attributtes and values in Odoo and push then in PrestaShop. * Create/modify products and push them in PrestaShop. * Create/modify products variants and push them in PrestaShop (combinations). * Create/modify category and push them in PrestaShop. * Create/modify image and push then in PrestaShop. Known issues / Roadmap ====================== * Tests.
…om category view. Better option when you want export a lot of categories
…ort a binding without short description
…date in product_mapper, in PrestaShop this field determine the 'new' state
…t_combination from product template export mapper
…duct_template export mapper
…t a product without taxes
* Passing arguments between ConnectorUnits should be done using **kwargs, passing values in context should be discouraged * This shop_url attribute/arg is not used anywhere but a specific addon for a specific use case, it should be done in a custom extension addon. Changes that aim to make the extension more easy should be encouraged. In this regard, I extracted some methods in ProductTemplateImporter to allow the forward of custom **kwargs
This allows to drop all the "_create" overrides.
The default value of the 'Product Price' rounding is 2, which is insufficient to get back and forth from the tax included and tax excluded prices. 6 should be sufficient (e.g. from 250.00 and a tax of 8%, we get 231.481481 and from the latter we can get back our 250.00)
* [FIX] manufacturer export on template Export of manufacturer on template was broken due to a probable typo. `id_manufacturer` value was taken using `to_odoo` instead of `to_backend`. * [IMP] filter of importable orders by state If `backend_record.importable_order_state_ids` is valued we check if current order is in the list. If not, the job fails gracefully. * [FIX] combination image: do not default to `False` when missing
…tabase store to linked to ps image after export (cherry picked from commit 8e3b16b)
That may pass the prestashop id insted of the binding id to the exporter That can cause the following problems: * A job Error: Key (id_attribute_group)=(4) is not present in table "prestashop_product_combination_option" * Wrong combination or combination values export or updated * Combination or combination value never exported * Faulty value in fields 'id_attribute_group' leading to data incoherence (cherry picked from commit 767ba36)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.