Magento 2.3.3 , PHP 7.2 FPM, NGINX , Ubuntu 18.04
we have following 3 installations
A installation migrated from 2.2 to 2.3.3 directly (migrated 1 day after release m2.3.3)
B installation directly installed 2.3.3 (installed within one week after release)
C installation 2.3.2 then migrated 2.3.3 (migrated yesterday)
disable the module temando shipping as we do not need it and the module produces for us unneccessary elements in admin sales menu
in C the module can safely be disabled without any issues, the sales admin menu points do not contain the related menu entries
the difference is
in the installations A & B when disabling temando shipping then i cannot edit products in 2 of them white screen(error 500) and following error in debug.log
[2019-11-01 09:49:37] main.INFO: Broken reference: the 'product.reviews' element cannot be added as child to 'product_tabs', because the latter doesn't exist [] []
REMARK:
i have seen that in database the Version of temando differs, perhaps its important
Schema 1.6.0 Data version 1.6.0 for A & B
Schema 1.5.0 Data Version 1.5.0 for C
Hi @itsolon. 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.3-develop instance
- upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@itsolon do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Temando_Shipping module might have added an EAV attribute already with a specific source model that no longer exists. This could generate an exception Class TemandoShippingModelSourcePackagingType does not exist when trying to edit product. To fix this, run the following SQL query in your database:
DELETE FROM `eav_attribute` WHERE `source_model` LIKE '%Temando%'
Hi @engcom-Charlie. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.3-develop
branchDetails
- Add the comment @magento give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
:white_check_mark: Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-22866
were created
Issue Available: @engcom-Charlie, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._
Temando_Shipping module might have added an EAV attribute already with a specific source model that no longer exists. This could generate an exception Class TemandoShippingModelSourcePackagingType does not exist when trying to edit product. To fix this, run the following SQL query in your database:
DELETE FROM `eav_attribute` WHERE `source_model` LIKE '%Temando%'
Worked for me, thanks a lot!!!
worked for me too! Thank you very much!
This worked for me on Magento 2.3.3 installation.
Temando_Shipping module might have added an EAV attribute already with a specific source model that no longer exists. This could generate an exception Class TemandoShippingModelSourcePackagingType does not exist when trying to edit product. To fix this, run the following SQL query in your database:
DELETE FROM `eav_attribute` WHERE `source_model` LIKE '%Temando%'
nice solution, it helped me to save a lot of time.
I found another solution: we only need to set NULL for source_model instead of deleting attributes.
Temando_Shipping module might have added an EAV attribute already with a specific source model that no longer exists. This could generate an exception Class TemandoShippingModelSourcePackagingType does not exist when trying to edit product. To fix this, run the following SQL query in your database:
DELETE FROM `eav_attribute` WHERE `source_model` LIKE '%Temando%'
Worked for me too as the others! Just 3 rows effected, saved me a headache thank you!
Hi All,
I am getting the same error so i deleted the 3 rows in the eav_attribute table using the above query.
Now i am getting this error-
Uncaught TypeError: Argument 3 passed to MagentoFrameworkViewElementUiComponentFactory::mergeMetadataElement() must be of the type array, null given, called in /home/ampscooters/public_html/vendor/magento/framework/View/Element/UiComponentFactory.php on line 385 and defined in /home/xxxxxxx/public_html/vendor/magento/framework/View/Element/UiComponentFactory.php:335
Stack trace:
Can someone help?? this is very urgent.Please
Just throwing my hat in the ring: I have seen this problem on 2.3.4. after disabling Temando_Shipping. I re-enabled it and the problem went away. Would prefer not to have that module active but it is what it is.
Experiencing same issue in 2.3.4 after disabling Temando_Shipping.
Ran the query on my magento database: SELECT * FROM eav_attribute WHERE source_model LIKE "%Temando%"
Set the 3 values to "NULL". Now I can edit products again (and leave Temando_Shipping disabled).
I experienced the same issue in 2.3.5 (Temando_ShippingRemover is disabled).
Setting the source_model for the three Temando's eav_attributes to NULL solved this issue.
Thanks to all who have pointed this out!
Most helpful comment
Temando_Shipping module might have added an EAV attribute already with a specific source model that no longer exists. This could generate an exception Class TemandoShippingModelSourcePackagingType does not exist when trying to edit product. To fix this, run the following SQL query in your database: