@sdetweil That fix helped. A minor configuration error fix helped too. I think I’ve got it back working the way I wanted it.

Ok, Sam - here’s what I got so far:

The calendar marked “No data” isn’t currently working from host, It can be ignored.
The calendar marked “Parsing” is spitting out data in debug mode, but when calendar turns around and broadcasts, it’ll broadcast zero entries. Only truly private URL has been blanked.

here’s my config - minus the calendars:

                {
                        module: "calendar", // Built in
                        //position: "top_center",  // Currently hidden
                        classes: "page1 page2 page3",
                        config: {
                                animationSpeed: 0,
                                broadcastEvents: true,
                                broadcastPastEvents: true,
                                fetchInterval: 60000, // minimum 1 minute. 
                                maximumEntries: 999999,

@sdetweil I see the problem, I think.

The logs I was using was in the console, those logs don’t show the source - PM2’s logs do.

I think something has changed in how it’s putting together the entries.

It used to be that maximumEntries: 99 - now it’s appearing to sort different or reach back further, so I need maximumEntries: 999 to see all my calendars show up.

I do have past events active - as I like to see where I had things happen, just in case I need it…

@sdetweil Don’t NPM install touch the package.json - or is it just package-lock?

Either way, @jefftse can just delete package-lock.json for that error.

What’s changed in the logic for calendar loading for 2.30?

99 entries used to be enough to display all my calendars, now I’m getting like 820 entries loading.

Curious if there’s a bug somewhere, or what. I’ve also noticed that the notices in the log indicating which calendar is loading is gone. Would be nice to have that back, at least in debug mode, so that we can tell what calendar is pushing # of entries.

Thanks!

@Niggich The default CSS keeps it tight - because that’s how I like it.

However, it’s easy to change.

in your magicmirror/css directory, there should be a file named custom.css - in that file, paste the following, and modify it to suit.

/* Month Padding */
.MMM-Multimonth .month {
  padding: 0px;
}

Cheers.

@sdetweil I’ve given up as other methods smoothed out the transitions anyway (The website that took too long to reload).

I put them both in, and that fixed it - thanks, Tom.

Tom, is it updateDomOnShow or updateDomOnResume ?

Documentation shows the latter.

@sdetweil

It shows, then resets, takes 2-3 seconds to show back up, then runs normally. The problem is that it’s just annoying to have it flash in and then blank, then come up and run.