Changing compliments
-
So there’s a config and when you run the MagicMirror it says there’s a config error. And
sudo nano config.jsfrom within MagicMirror/config/ doesn’t work? Cann you go to MagicMirror/config/ and show us what it says when you put inls -l? (that’s a small letter ‘L’) which will list files with their rights/owners. -
@doubleT it does not list anything. 
-
-
@doubleT pi owns both config.js and config.js.sample
-
Weird, it sounds like there shouldn’t be a problem at all.
Do you have the possibility to edit the file externally and replace it? For example via FTP.
Btw. how do you save the file? -
@doubleT I save from the terminal with ctrl o. Have also tried ctrl x, y.
When I get to the folders through the GUI, I can change the file and save it. I have uncomment ed the calendar, and moved things around, but when I add the configure script for new compliments I get the error message need a config file. I checked it using a terminal command someone gave me here and every line that I added it did not like, even though my code was exactly like the example.
Weird. However, I am learning a lot troubleshooting this issue and I appreciate all the help.
-
I had a similar problem. It showed an error for my entire addition to the config.js. Run check:config again and pay close attention to the beginning of the output. The first error should say something about expecting a bracket of one kind and it was returned a bracket of a different kind. It will also tell you the line of the error. Now nano back into config scroll down to your addition and press ctrl + c. The bottom of your screen should give you your current line number. Find the error. Mine was a missing bracket. Fixing this error fixed the entire script. All other errors were the result of the first. Sorry if I wasn’t clear or missed something, im still a new to this too. Hope it helps.
-
@AliAS remember after locating and fixing the error to hit ctrl + o to save and ctrl + x to exit nano.
-
Another suggestion, and someone please correct me if I am wrong, you could delete the config.js file and save as or copy the config-sample.js as a new config.js file. That way you have a functioning config.js. But doing so, you would have to reconfigure all your modules. Does that sound right?
-
@AliAS said in Changing compliments:
Does that sound right?
Sure, but another idea would be to rename the non-functioning config (so you don’t lose what’s in it) and THEN make a new copy of the config.js.sample and rename it to config.js.
