Default weather module not showing after MM update

01ZerosOnes01

@mumblebaj If I enter shit + ctrl + i in the terminal nothing shows up but a dialog box with Cancel and OK

mumblebaj

@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.

01ZerosOnes01

@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 .

Jarhead96097

@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)"

01ZerosOnes01

@Jarhead96097 Thanks for your info. Hopefully someone can come up with the fix.

sdetweil

@01ZerosOnes01 @Jarhead96097

how did u upgrade,and from what version?

I don’t see any significant code change here this release…

01ZerosOnes01

I keep the mirror updated so I am assuming it was updated from the last version.
I updated by first issuing git stash then git pull && npm install --only=prod --omit=dev
followed by git stash apply

All other default and third party modules work.

Thank for your help it is appreciated.

mumblebaj

@01ZerosOnes01 I had my API authorized and the module works just fine with your location data. The only change I made was not add quotes around the locationID.

locationID: 4891010,

Jarhead96097

@sdetweil I also upgraded from 2.19.0, which had been upgraded from 2.18.0. No problems before today.

Jarhead96097

@mumblebaj Well, unfortunately, removing the quotes around locationID did not resolve the issue on my configuration. I still receive “Uncaught SyntaxError: Unexpected token” in weather.js:159.