Closed dphilipps closed 4 years ago
Hi @dphilipps. 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.
Please, add a comment to assign the issue: @magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
@magento give me 2.4-develop instance - upcoming 2.4.x release
Hi @dphilipps. Thank you for your request. I'm working on Magento instance for you.
Hi @dphilipps, here is your Magento Instance: https://07258af464b104e71e149da65f5c62e4-2-4-develop.instances.magento-community.engineering Admin access: https://07258af464b104e71e149da65f5c62e4-2-4-develop.instances.magento-community.engineering/admin_73a7 Login: 1362a296 Password: e13c472c0d21
I can't reproduce the issue on 2.4-devel - it works correctly.
Hi @dphilipps, unfortunately there is no ability to deploy 2.4
Magento instance. Please make sure you specify the correct Magento version/branch.
@magento give me 2.4.0 instance
Hi @dphilipps. Thank you for your request. I'm working on Magento instance for you.
Hi @dphilipps, here is your Magento Instance: https://07258af464b104e71e149da65f5c62e4-2-4-0.instances.magento-community.engineering Admin access: https://07258af464b104e71e149da65f5c62e4-2-4-0.instances.magento-community.engineering/admin_6cdd Login: 20994df8 Password: 53d2c4f66d0e
Reproduced on 2.4.0
@magento I am working on this
Hi @dphilipps! :wave:
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team
command to join Contributors team.
@magento add to contributors team
Hi @dphilipps! :wave: Thank you for joining. Please accept team invitation :point_right: here :point_left: and add your comment one more time.
@magento I am working on this
On a fresh install of Magento Open Source 2.4, when creating a FedEx shipping label from a shipment, the 'Create Packages' panel is displayed with an empty error message at the top of the screen. The 'Add products to package' button has no effect. Chrome console shows Javascript errors when the button is pressed. This is on a fresh install of Magento Opensource 2.4 built with composer including sample data however I have also reproduced it on another instance upgraded from 2.3.4 where this functionality was working as expected.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
Uncaught TypeError: Cannot read property 'select' of undefined at getItemsForPack (packaging.js:385) at HTMLSpanElement.eventListenerSykK3td404 ((index):691) at HTMLButtonElement.listenedElementSykK3td404.onclick ((index):700)
I have reproduced this issue in production mode with static content correctly deployed as well as in developer mode.
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.