You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade magento to 2.4.6-p1
Removed myparcelnl/magento module
Installed myparcelnl/magento module
But setup/upgrade failes with db error related to myparcel:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mg3.catalog_product_entity' doesn't exist, query was: SELECT catalog_product_entity_varchar.entity_id, catalog_product_entity_varchar.value_id, catalog_product_entity_varchar.value, eav_attribute.attribute_id FROM catalog_product_entity AS product LEFT JOIN catalog_product_entity_varchar ON product.entity_id = catalog_product_entity_varchar.entity_id LEFT JOIN eav_attribute ON 'myparcel_fit_in_mailbox' = eav_attribute.attribute_code WHERE catalog_product_entity_varchar.attribute_id = eav_attribute.attribute_id
Plugin version
4.91
Magento version
2.4.6-p1
PHP version
8.1
What went wrong?
Upgrade magento to 2.4.6-p1
Removed myparcelnl/magento module
Installed myparcelnl/magento module
But setup/upgrade failes with db error related to myparcel:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mg3.catalog_product_entity' doesn't exist, query was: SELECT catalog_product_entity_varchar.entity_id, catalog_product_entity_varchar.value_id, catalog_product_entity_varchar.value, eav_attribute.attribute_id FROM catalog_product_entity AS product LEFT JOIN catalog_product_entity_varchar ON product.entity_id = catalog_product_entity_varchar.entity_id LEFT JOIN eav_attribute ON 'myparcel_fit_in_mailbox' = eav_attribute.attribute_code WHERE catalog_product_entity_varchar.attribute_id = eav_attribute.attribute_id
Reproduction steps
Magento installation previously contained myparcelnl/magento
Remove myparcelnl/magento (because product edit with myparcel is not possible anymore)
Run setup/upgrade - fails with db error
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: