Read the statement by Michael Teeuw here.
Where to git clone MagicMirror 2.16
-
@plainbroke So, you may want to supply us the error messages that you are getting when you start the mirror. Either the content from the terminal when you start the mirror with npm or if you start the mirror with pm2 then pm2 log --lines 100. There are underlying issues with the modules that you have installed. To get you up and running on 2.18 then you need to provide us with the log output so we can see how to assist. Rolling back to older version of MM may not be the right thing to do. Let’s see if we can resolve the issues.
-
@mumblebaj and if you use my upgrade script, it will do all the missing require lib corrections for the active modules
-
@sdetweil That is true. But he already upgraded to latest. Not sure if your scripts will fix after the fact?
-
@mumblebaj add force instead of apply, then its a re-upgrade (npm install, not pull) … and do the whole thing
-
@plainbroke There you go. Use the upgrade script by @sdetweil with the apply option and it should sort out your modules’ missing dependencies. If you still have issues then post the logs so we can see what else is wrong.
-
@mumblebaj FORCE if already upgraded… otherwise it will say ‘already at current release’ and abort
-
@sdetweil Sorry, mind was thinking “force” but the fingers overwrote with “apply” :-)
-
@sdetweil said in Where to git clone MagicMirror 2.16:
@mumblebaj FORCE if already upgraded… otherwise it will say ‘already at current release’ and abort
Thanks guys I have slowly and I mean slowly got a few to work… I will install all of them and see what sdetweils upgrade script can do under force…
