sorry to sound extremely daft, but what should I be renaming it? Is there a preferred name or one which makes most sense?

once a new name is picked can it later be changed back to magicmirror just to keep everything standard?

Also, when you say,
mv magicmirror newname, I’m guessing the newname bit is actually what I want to call it, or do I put the new name after?
I’ve got a terrible feeling I’ll have to start the whole thing again which I definitely won’t look forward to.

Sam, scratch my last message, I was just about to turn everything off as it’s getting pretty late here.
used ctrl c to stop the MM so I could shutdown the pi and attack it another day.
pm2 restarted the MM and hey presto the mirror seems by and large back to normal.

I’m away with work for the next 3 days but will have a proper butchers (look) when I’m back home.

Thank you so much for both your patience and help.
I had genuine fears I’d have to start the entire build (modules bit) again and I was lucky I got it up and running like I did in the first place.

thank you!

@sdetweil restarted the MM with PM2, still no info being displayed in the CalendarEXT3 module.

edit to add, after letting the mirror settle down, it’s now pulling the data

@sdetweil
getting this now,
MagicMirror@raspberrypi:~/MagicMirror $ git switch _fix_clipping
Already on ‘_fix_clipping’

so assuming I can now restart mm?

@sdetweil
MagicMirror@raspberrypi:~/MagicMirror $ rm package-lock.json
rm: cannot remove ‘package-lock.json’: No such file or directory

guessing I’m not doing this right

@sdetweil do I run that in just the MagicMirror directory or the Calendar EXT3 module directory?

Below was your guidance from another of my topics with issues with this module, will it work?

(#)put package-lock.json back to last git clone state
git reset package-lock.json
(#) update the module
git pull
(#) rerun npm install with new code
npm install

had to put the # in () to stop the font going enormous

@sdetweil I’ve hit this at the 3 command,
MagicMirror@raspberrypi:~/MagicMirror $ git switch _fix_clipping
error: Your local changes to the following files would be overwritten by checkout:
package-lock.json
Please commit your changes or stash them before you switch branches.
Aborting

@sdetweil I hadn’t seen that, I was about to update the module individually then do some digging on here to see if others had had the issue.

do I use the list of commands in the link above, or the ones in this link?
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

@sdetweil This is useful to know.

Just add, I’ve had the same Issue as the last MM update, Calendar EXT3 is no longer pulling information from the base calendar module.

out of curiosity, what would I do if I needed to retrieve the back up, do I need a GitHub account?

Finally getting round to updating the base MM version.

used @sdetweil bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)”

and it did what it wanted to do.

How do I know that the second line bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply

can be run without issue?

I get this before it runs through all the package.json files for modules I’m using,

Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v20.18.1
Installed Node version: v20.8.0
Node should be upgraded.
Node.js upgrade defered, doing test run
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.8.2
Installed npm version: V10.1.0
npm should be upgraded.
npm upgrade defered, doing test run …

is it safe at this point to use the code to make the changes?
Cheers,
John.

@sdetweil so just to be clear its,
git checkout package-lock.json
git reset
git pull
npm install

within the calendar ext3 module folder?