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
After clearing Moodle's JavaScript Cache the first page load receives this comment at the top of first.js:
// JS module 'mod_verbalfeedback/report' cannot be loaded, or does not contain a javascript module in AMD format. "define()" not found.
Somehow that leads to the web browser receiving a JavaScript error and essentially not being able to load any JS for the page. This only affects the first page load after clearing Moodle's JS Cache. Following page loads don't have this problem anymore. The above comment is also no longer returned when requesting first.js on following page loads.
This is on the one hand a bug in Moodle core, I'd argue, because it's probably not the intention that JavaScript for the whole page should be broken, even though it makes the problem more noticeable. But on the other hand it's caused by an issue in this plugin, namely that you have an AMD module with all it's code being commented out.
The text was updated successfully, but these errors were encountered:
After clearing Moodle's JavaScript Cache the first page load receives this comment at the top of first.js:
// JS module 'mod_verbalfeedback/report' cannot be loaded, or does not contain a javascript module in AMD format. "define()" not found.
Somehow that leads to the web browser receiving a JavaScript error and essentially not being able to load any JS for the page. This only affects the first page load after clearing Moodle's JS Cache. Following page loads don't have this problem anymore. The above comment is also no longer returned when requesting first.js on following page loads.
This is on the one hand a bug in Moodle core, I'd argue, because it's probably not the intention that JavaScript for the whole page should be broken, even though it makes the problem more noticeable. But on the other hand it's caused by an issue in this plugin, namely that you have an AMD module with all it's code being commented out.
The text was updated successfully, but these errors were encountered: