Not wanting to sound lazy but there's 43 pages off stuff about fixing this issue. I run modern gadgets as it does everything I want. I'll have to have a think about where I got modern gadgets from to contact the developer.
If someone can point me to a one click solution though, I'd be most appreciative of that.
patoriku66 wrote: ↑January 15th, 2022, 4:08 am
Not wanting to sound lazy but there's 43 pages off stuff about fixing this issue. I run modern gadgets as it does everything I want. I'll have to have a think about where I got modern gadgets from to contact the developer.
If someone can point me to a one click solution though, I'd be most appreciative of that.
The files you need to edit are located in Skins\ModernGadgets\WeatherMeter\Includes.
The file names are:
AstroMeasures.inc
WeatherComJSONMeasures.inc
Open the files in a text editor, replace the APIKey value in those files to apiKey=21d8a80b3d6b444998a80b3d6b1449d3
patoriku66 wrote: ↑January 15th, 2022, 4:08 amNot wanting to sound lazy but there's 43 pages off stuff about fixing this issue.
Just so you know, the 43 pages are an aggregate of various issues with getting weather stuff in skins over time, with this particular issue only the latest of those. The answer to your question is literally mentioned on the 42nd page.
jsmorley wrote: ↑January 10th, 2022, 8:48 pm
I think you will find that if you change the API Key to 21d8a80b3d6b444998a80b3d6b1449d3, it will begin to work again.
Perhaps this might prevent problems if the APiKey is changed in the future.
I take it that you adapted this a bit to specifically suit jsmorley's .inc files, didn't you? if so, good idea, it didn't cross my mind, unfortunately.
I do have the same problem, when trying to get the weather info from the JSON embedded in the weather.com's page source instead of the separate JSON file. It appears one has to try various flags and such to get a proper response (one that can be parsed) on the weather.com webpage source...
EDIT: The weather.com's webpage source appears fine in the browser (Chrome here) though, and the embedded JSON is still there, so it's not a matter of weather.com changing the page source format, but rather of page source accessibility.