MMM-Pages module all showing on one page

hahawoooooo

{  //MMM-Pages
        module: "MMM-pages",					// flip between pages - goal was to set full page calendar on one page, rest on other
        config: {
			timings: {
				default: 5000			// rotate every 5 seconds
			},
			modules: [
                                ['weather',                          // page 0	
				'MMM-CalendarExt3',
				'MMM-CalendarExt3Agenda',
				'MMM-Chores',
				'MMM-Dad-Jokes'
			   ],        				                
               ['MMM-TitanSchoolMealMenu'],        // page 1
				],
			fixed: [
					['MMM-page-indicator',						// what to show on every page
					'MMM-SmartTouch',
					'clock',
					'MMM-MagicMover',
					'MMM-Wallpaper']
				],
			hiddenPages:{					// modules to not show, or to hide in specific pages 
				"hidden": [
					'calendar', 
					'updatenotification',
					'MMM-Remote-Control'
					],      
				}
			}

hahawoooooo

Okay, I may have discovered the reason of the pages not rotating, the “searchClass.toLowerCase” not being found, and possibly a of other small strangeness I was seeing.

I was running the latest version of magic mirror without realizing you have to do a fresh wipe and re-install for major Raspberry Pi OS updates. I had put aside this project for about a year or so, and picked it back up in October without updating to Trixie.

I’m working through the OS update and restoring everything from the restore scripts to see how it runs. Fingers crossed!

sdetweil

@hahawoooooo you do NOT Have to do a wipe and install again…

generally that error message means it was trying to do a string operation (toLowerCase), but the thing was not a string (usually null )

hahawoooooo

@sdetweil said in MMM-Pages module all showing on one page:

generally that error message means it was trying to do a string operation (toLowerCase), but the thing was not a string (usually null )

That makes sense. Updating the OS fixed a few other issues, but the MMM-pages issue is still happening with the same “toLowerCase” error. I’m removing modules I’m not using and spellchecking everything to see if there’s a spelling or formatting error I’m missing in the config file in case that’s the reason for className calls to bork up somewhere.

sdetweil

@hahawoooooo I also recommend using the classes approach to config

     modules:[
              [ "page1"],
              [ "page2"],
             ],
             "fixed": ["fixed"]
      . Etc

Then for the modules you want on page1
Add

      classes:"page1",

In the config below module: line

This was so much easier for me

hahawoooooo

@sdetweil

I feel incredibly foolish - I attempted to use classes before and I couldn’t get it to work. It ends up that I had it coded as:

class:'page1',

instead of:

classes:'page1'

I swear I stared at this config file forever without seeing it!!! Thanks so much for the being patient, and I got everything working now.

sdetweil

@hahawoooooo it’s amazing what our minds see, even when it’s wrong!

Glad you found it!!