Read the statement by Michael Teeuw here.
Failed to load resource
-
Has anybody seen any of these errors of late or know how I can track which module it is referring to?
I can see these but when hovering over it it just shows me http://0.0.0.0:8080/undefined
I can’t see any issues with any of the modules that I am running.
I have also noticed that this is throwing a lot of errors.
Any help, advice or direction would be greatly appreciated.
-
@mumblebaj usually the only way is to disable module one by one and hit f5 reload in the browser… do NOT stop/restart mm… just add disabled:true, one module at a time. , hit refresh
its unlikely to be the base modules…
-
@sdetweil Thanks Sam. What about the Parameter mismatch issue?
-
@mumblebaj I would grep all the source code for all the modules.looking the type “show(”
a little find, awk and grep should narrow it down pretty fast
-
@mumblebaj
Probably there would be a module which is related to the feature “hiding/showing modules”
Check what module you have;- Paging
- Hiding/Showing module by condition or schedule
- Hidden module
- Force refreshing or relocating other modules
Somewhere the module might have mistakes on call
.show(). It should have 3 parameters, but only 2 given. -
Thanks @MMRIZE. I have narrowed it down to the below from MMM-pages.
I will log an issue on the Github but I have noticed the author has requested for somebody to take over the module from him.
-
@mumblebaj
Try other equivalent modules. There are a few paging modules still. -
@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
