MMM-Pages module all showing on one page

sdetweil

@plainbroke thx… will look at it
I added it with example params and it works with pages just fine…

{
    module: "MMM-Adventskalender",
    classes:"page1",   // on my pages def
    position: "top_center",
    config: {
        backgroundImage: "/modules/MMM-Adventskalender/images/background.jpg",
        doorMargin: 30,
        moduleWidth: 800,
        moduleHeight: 600,
        autopen: true,
        autoopenat: "10:00",
    },
},

sdetweil

@hahawoooooo weird… none of those make sense…

not found, then not executable
and css… typically that means not found

is this on a synology nas, and docker for MM??

hahawoooooo

@sdetweil I was a bit flummoxed myself, honestly. It’s on a raspberry pi, and I’m not using docker.

sdetweil

@hahawoooooo can you do

cd ~/MagicMirror/modules
ls -laF

hahawoooooo

@sdetweil Sure thing:

total 32
drwxr-xr-x 8 dtraindisplay dtraindisplay 4096 Dec 2 21:36 ./
drwxr-xr-x 16 dtraindisplay dtraindisplay 4096 Dec 2 21:15 …/
drwxr-xr-x 10 dtraindisplay dtraindisplay 4096 Dec 2 21:08 default/
drwxr-xr-x 7 dtraindisplay dtraindisplay 4096 Dec 2 21:36 MMM-CalendarExt3/
drwxr-xr-x 5 dtraindisplay dtraindisplay 4096 Dec 2 21:37 MMM-LINQConnectCalendar/
drwxr-xr-x 4 dtraindisplay dtraindisplay 4096 Dec 2 21:30 MMM-mmpm/
drwxr-xr-x 7 dtraindisplay dtraindisplay 4096 Dec 2 21:34 MMM-page-indicator/
drwxr-xr-x 5 dtraindisplay dtraindisplay 4096 Dec 2 21:34 MMM-pages/

I also tried doing a fresh install using the install script in a new folder, and I’m running into the same issue, but the console logs (ctrl+shift_I) is now showing a different output:

loader.js:179 Load script: modules/MMM-pages/MMM-pages.js
module.js:489 Module registered: MMM-pages
loader.js:152 Bootstrapping module: MMM-pages
loader.js:156 Scripts loaded for: MMM-pages
loader.js:195 Load stylesheet: modules/MMM-pages/pages.css
loader.js:159 Styles loaded for: MMM-pages
loader.js:162 Translations loaded for: MMM-pages
loader.js:179 Load script: modules/MMM-page-indicator/MMM-page-indicator.js
module.js:489 Module registered: MMM-page-indicator
loader.js:152 Bootstrapping module: MMM-page-indicator
loader.js:156 Scripts loaded for: MMM-page-indicator
loader.js:195 Load stylesheet: modules/MMM-page-indicator/page-indicators.css
loader.js:159 Styles loaded for: MMM-page-indicator
loader.js:162 Translations loaded for: MMM-page-indicator
MMM-page-indicator.js:138 [MMM-page-indicator]: MMM-pages detected. Will ignore PAGE_INCREMENT and PAGE_DECREMENT as it is already handled by MMM-pages
MMM-pages.js:117 [MMM-pages] received that all objects are created; will now hide things!
MMM-pages.js:331 [MMM-pages] resuming rotation
MMM-page-indicator.js:106 [MMM-page-indicator]: Changing maximum pages to 2
MMM-page-indicator.js:131 [MMM-page-indicator]: Setting page to 0
main.js:527 Uncaught (in promise) TypeError: searchClass.toLowerCase is not a function
at main.js:527:38
at Array.filter ()
at modulesByClass (main.js:523:31)
at Array.exceptWithClass (main.js:508:11)
at Class.animatePageChange (MMM-pages.js:234:8)
at Class.notificationReceived (MMM-pages.js:121:14)
at sendNotification (main.js:101:12)
at main.js:70:4

I also

sdetweil

@hahawoooooo interesting
Can you do

cd ~/MagicMirror/modules/MMM-pages
grep version package.json

Latest is 1.3.0
If not 1.3.0
git pull

The restart MagicMirror

plainbroke

@sdetweil
I think I found my answer, I was on version 1.0.0 of MMM-pages.
We will see what happens with Version 1.3.0 in the morning.
I did the git pull.

hahawoooooo

@sdetweil Good catch on that one - there are two MMM-Pages listed in the third party module website, and I was using your fork which is at 1.0.0. I uninstalled that version and installed the 1.3.0 version, but still having the same issue with all modules on one page.

I need to get a bit more sleep and look again just to make sure I did everything correctly after the changes.

One thing I noticed is I’m getting socket.io connection errors in the logs. where it repeatedly tries connecting and then fails. I can grab the log texts when I get back home tonight if that’s anywhere related to the problem.

sdetweil

@hahawoooooo I think this is a totally different problem…

are you using node 22.18.0 on the system?
node inside this electron version is 22.18

are you using a browser or is this the electron page started by npm start?

hahawoooooo

Node version is 22.18.0, and I’m using pm2 to start it. I changed the mm.sh file to open it via firefox.