Read the statement by Michael Teeuw here.
Failed to load resource
-
@MMRIZE I am testing on MMM-pages on my Windows machine running MM in WSL. I am not getting the same behavior though. I will need to debug my PROD machine. Weird that it works fine on my one machine and throwing the errors on my other machine
-
@MMRIZE Can you help me understand the below bit of code from the core module.js.
From the above, if options is undefined then callback is assigned to options and the module carries on it’s merry way. Is my understanding correct?
-
@mumblebaj correct. easier to not make it null
-
Thanks @sdetweil. I will make a change locally and test it.
-
@mumblebaj you shouldn’t have to do anything
-
@sdetweil Well, if that was true then I should not see those errors on my MM. Which is why I am not understanding why it is throwing the errors currently.
-
@sdetweil On the other hand i agree with you completely as I don’t see the same issue on my dev machine. A bit puzzling to me. :-)
-
This post is deleted! -
@mumblebaj
As of version 2.24, Somebody added to spit this error message out when the 2nd parameter is not a callback function.However, the following codes correct the missing parameter anyway, so it is unnecessary to regard it as
ERROR, unless that self-correction logic is removed.
Even if there is a plan to drop out that correction logic, it’s still better to flag it as a “WARN” rather than an “ERROR”, I think so.Anyway, the error message is just annoying, and not related to real “ERROR” . You can ignore it.
