Read the statement by Michael Teeuw here.
Default weather module not showing after MM update
-
@mumblebaj Hi, thanks for your response there are no errors on the screen when I run npm start. No loading of that module indication but there is space allocated for the weather module on the screen in the top right area. All other modules work. Everything was working before the update to the latest MM.
-
@01ZerosOnes01 I am just upgrading. Just one last check, see in the Developers window if there are any errors there.
shit + ctrl + i -
@01ZerosOnes01 I think there may be an issue with the api key for OpenWeatherMap.
-
@mumblebaj I xxx out the last few digits
-
@mumblebaj If I enter shit + ctrl + i in the terminal nothing shows up but a dialog box with Cancel and OK
-
@01ZerosOnes01 Hi. Not in the terminal from the browser window that displays the mirror. I have created an Openweathermap api key and I get an unauthorized error in the Developers window. I guess I have to wait for it to activate first. Once it is active I will see if I can spot anything.
-
@mumblebaj Okay this is what I get when I run shift + ctrl + i
Load script: modules/default/weather/weather.js
:8080/modules/default/weather/weather.js:159 Uncaught SyntaxError: Unexpected token . -
@01ZerosOnes01 said in Default weather module not showing after MM update:
@mumblebaj Okay this is what I get when I run shift + ctrl + i
Load script: modules/default/weather/weather.js
:8080/modules/default/weather/weather.js:159 Uncaught SyntaxError: Unexpected token .I’m receiving the same error after updating to 2.20.0. Here’s the text from the weather.js error line 159: " currentWeather: this.weatherProvider?.currentWeatherObject?.simpleClone() ?? null,(RED X)"
-
@Jarhead96097 Thanks for your info. Hopefully someone can come up with the fix.
-
how did u upgrade,and from what version?
I don’t see any significant code change here this release…
