Open webloft opened 1 week ago
Hi @webloft. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.
@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, join the Community Contributions Triage session to discuss the appropriate ticket.
Hi @engcom-November. 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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hello @webloft,
Thank you for the report and collaboration!
Going through the issue this can be marked as a feature request.
Summary
If you have any error in your knockoutjs template you wont see the actual error given by the parser at loading the template, instead it just logs:
Failed to load the "module/components/whatever/path" template requested by "another module".
but the file can be loaded via network.
You need to intercept the Magento_Ui/js/lib/knockout/template/engine script at the point
and grab the first argument of the function to get the actual error.
You might still need the error in production mode, so it should be visible in the browsers console at any time.
Examples
-
Proposed solution
No response
Release note
No response
Triage and priority