@rmcon great that you got it working on the test run, mostly currently it’s looking for mm files you might have changed for some reason, and conflict w the new release. most of the other issues I handle, upgrade node, npm and pm2 if needed. and in this release on pi0, increase swap space and increase the node heap space.

@chris_d the string of things before the { is called the selector clause. this gives u the ability to ‘select’ the html elements you want to apply the styles to I use this cheat sheet to view the different choices https://www.w3schools.com/cssref/css_selectors.php the selector can be very complex here is one from my MMM-Config module .possibly-hidden-tab div:nth-child(2) > div > div >div >ul >li:only-child >a[rel*="Item 1"] { display: none; }

@MikeBishop I’m running MMM-Calendar3 and the default modules only.

@sdetweil I may be wrong, but I doubt it - I intentionally broke one of my calendars, and CX2 did not produce an error - just reported “0 scanned, 0 selected” on the calendar. I don’t think CX2 is gonna help with this. Also, I looked through my code, and I’ve noticed that some of my shared calendars are indeed Google calendars, so I’m gonna retract that statement. My advice is to double check the settings within Google itself.

@chris_d Sometimes little bugs like that happen. Usually, it just takes a refresh to fix. Glad to see it’s working.