Failed to load resource

[sdetweil]

@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…

[mumblebaj]

@sdetweil Thanks Sam. What about the Parameter mismatch issue?

[sdetweil]

@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

[MMRIZE]

@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.

[mumblebaj]

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.

[MMRIZE]

@mumblebaj
Try other equivalent modules. There are a few paging modules still.

[mumblebaj]

@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

[mumblebaj]

@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?

[sdetweil]

@mumblebaj correct. easier to not make it null

[mumblebaj]

Thanks @sdetweil. I will make a change locally and test it.

[sdetweil]

@mumblebaj you shouldn’t have to do anything

[mumblebaj]

@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.

[mumblebaj]

@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. :-)

[MMRIZE]

This post is deleted!

[MMRIZE]

@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.