Closed mohitnavik closed 2 years ago
Hi @mohitnavik. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.
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, join the Community Contributions Triage session to discuss the appropriate ticket.
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-Lima. 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:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label 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.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.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.
Hi @mohitnavik ,
I have tried to reproduce the issue but issue is not reproducible to me on 2.4.4
which was upgraded from 2.4.3-p2
.
Please refer below screenshot for your reference:
Followed all the steps which you have provided in the issue .
Please provide information on which path you have saved requirejs-config.js
file.
Thanks
Hi @engcom-Lima,
Thanks for your response
Is "jquery.mobile.custom.js" file in the 2.4.4?
Did you try with new custom theme?
Thanks,
Hi @mohitnavik ,
Yes I have created custom theme as you can see my screeshot in above comment. I have checked there is no jquery.mobile.custom.js
file in 2.4.4 version.
Can you please test it in the latest 2.4-develop
if you are facing any issue let us know.
Thanks
Hi @mohitnavik ,
We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it.Please raise a fresh ticket or reopen this ticket if you need more assistance on this.
Thanks
Hi everyone. I meet the same problem. "2.4.5-p1" has the same issue. The jquery.mobile.custom.js file doesn't exist.
This is still reproducible on 2.4.4-p2 as well
Facing the same issue in 2.4.5-p1
Im also facing the same issue in magento open source 2.4.5
I have the same issue but I had a guess.
The file had been removed from magento 2.4.4 (check this https://magento.stackexchange.com/questions/355000/jquery-mobile-custom-js-file-error-after-upgrade-to-magento-2-4-4).
But if you are upgrading from an old magento the file is still located in lib/web/jquery/jquery.mobile.custom.js so it will works until you will remove the file.
In my case I had to remove the file and also remove the reference from src/app/design/frontend/XXX/YYY/web/mage/menu.js to the file in the define.
Preconditions and environment
I have upgraded Magento from 2.4.3-p2 to 2.4.4. After upgrading the magento version, I am getting "Uncaught Error: Script error for jquery/jquery.mobile.custom" error in the console.
I have custom theme and added the following in requirejs-config.js
_var config = { map: { '*': { 'rowBuilder': 'Magento_Theme/js/row-builder', 'toggleAdvanced': 'mage/toggle' } }, paths: { 'jquery/ui': 'jquery/jquery-ui', 'countdown': "js/countdown.min" }, shim: { 'countdown': { 'deps': ['jquery'] } }, deps: [ 'jquery/jquery.mobile.custom', 'mage/common', 'mage/dataPost', 'mage/bootstrap' ], config: { mixins: { 'Magento_Theme/js/view/breadcrumbs': { 'Magento_Theme/js/view/add-home-breadcrumb': true }, 'Magento_Ui/js/modal/modal': { 'MagentoUi/js/model/modal-mixin': true } } } };
I have checked and found that "lib/web/jquery/jquery.mobile.custom.js" is missing.
Steps to reproduce
Expected result
Error should not be show in console or alternate way to fix it
Actual result
Error in console: Uncaught Error: Script error for jquery/jquery.mobile.custom
Additional information
No response
Release note
No response
Triage and priority