gerryex wrote: ↑June 2nd, 2020, 9:16 pmI'm using the Yahoo.com version of the weather skin which seems to be working just fine and has the same info as your skin so at least I have my desktop weather info. But it would still be nice to be able to get the other skins based on weather.com working again.
Thanks for all your help,
Gerry
gordonpm wrote: ↑June 2nd, 2020, 10:28 pm
Still not working here either no matter how many times I clear and restart.
Varies between no information at all and partly working, but has not worked for all forecasts (Now, Tonight, Tomorrow etc) since this all began.
xenium wrote: ↑June 3rd, 2020, 11:49 am
I made a version of my Windows 10 Weather Enterprise skin that uses JSON data from the New TWC website.
The skin is in testing, it is not finished and will be available for download only when the old TWC website will no longer be available. For me my skins that use the current website still work.
But because I saw that no solution on the forum works for the skin you use, I'm sending you a PM with the skin download link.
See if it works for you
Place cursor over the weather icons for details.
Yeah, I'll also post in the near future either a method or a (basic) skin that'll work in each possible case: V2, V3 or if you're using a legit API key (the latter is more or less the same format as V3, really). The location and current conditions are already done, I just have to tweak the forecast extraction exactly the way I want to. I have the extraction done already since a couple of years back in my Feeds skin, it just needs to be adapted without any drawback to the weather skin.
So, don't worry, there are (or there will be shortly) solutions for the issue, and not just one. Whether it's the fix, the Yahoo route, Mordassius' solution or mine, the resolution will eventually be satisfactory. Me, I didn't want to settle for a format or another, but rather make the thing work irrespective of the data provided by the source, so that me (or folks using it) won't have to bother again with this whole inconvenience - and if they do, the required modifications should be superficial (i.e. not rewriting the whole skin again).
SilverAzide wrote: ↑June 3rd, 2020, 1:54 pmI can only force the issue by using a user agent string for a mobile device.
If persistent, this isn't an issue, as the real problem with this was the inconsistency. If one can force one format or another to be passed to WebParser, then at least half of the problem is gone.