Closed nbennett25 closed 4 years ago
Hi @nbennett25. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
@nbennett25 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
It looks like one of both is a composer meta package, because only temando/module-shipping-m2
exists in the vendor
directory.
Other observations by looking at the composer.lock
file:
magento/product-community-edition
requires temando/module-shipping
temando/module-shipping
requires temando/module-shipping-m2
Strictly speaking this shouldn't be a problem but it can be a bit confusing.
In my opinion, this shouldn't cause database migration problems, so do you have more info about those @nbennett25 ?
Thanks for the clarification on the meta module.
I’m just noticing that when running setup:upgrade with 2.3.4, I’m getting the constraint violation error listed in the link above. Commenting out line 73 in the Temando_Shipping/Setup/UpgradeData.php file ($this->installer->addMappedProductAttributes();) allows the setup:install command to work as expected.
The addMappedProductAttributes() method tries to add values to the temando_product_attribute_mapping
and for whatever reason, those values already exist in the table.
Thx
On Mar 17, 2020, at 4:56 PM, Pieter Hoste notifications@github.com wrote:
It looks like one of both is a composer meta package, because only temando/module-shipping-m2 exists in the vendor directory.
Other observations by looking at the composer.lock file:
magento/product-community-edition requires temando/module-shipping temando/module-shipping requires temando/module-shipping-m2 Strictly speaking this shouldn't be a problem but it can be a bit confusing.
In my opinion, this shouldn't cause database migration problems, so do you have more info about those @nbennett25 https://github.com/nbennett25 ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/27316#issuecomment-600294481, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADE3SHBZ7YGRILVSJVYK7TTRH7PWJANCNFSM4LNXW2SQ.
The issue not reproducible on 2.4-develop , as Temando shipping module been removed from Magento 2
There seem to be multiple Temando_Shipping modules in code in 2.3.4, which causes integrity constraint violations when running bin/magento setup:upgrade, since both modules are adding the same content with data upgrades.
Related: https://community.magento.com/t5/Magento-2-x-Technical-Issues/Integrity-constraint-violation-on-setup-upgrade-Magento-2-3-3/td-p/209198
composer show: ... temando/module-shipping 1.6.2 Temando multi-carrier shipping extension for Magento 2 temando/module-shipping-m2 1.6.2 Temando multi-carrier shipping extension for Magento 2 ...
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
temando/module-shipping-m2
is installedActual result (*)
temando/module-shipping
andtemando/module-shipping-m2
are installed