Yay I got it working thanks to your suggestions.

I replaced the default http://xoap.weather.com/ link with a custom one containing my city and license details.

Thanks!

Cr4z33. Can you show me the line (without you user ID &Key) that you changed in martins script so that I can fix mine as well?? Thanks.

I'm looking forward to just being able to use any of my 132 DX themes.I tried a dozen or so and none will fully load. I don't relish the idea of having to modify every one of them,just to have Weather dot com pull this crap again in the future. It looks like I am done with DX until this is straightened out.

Again . . I might suggest that an external file be used for scripts that may use common code. That way they could be replaced easily on the host system if needed and if all weather gadgets used the same external file it could be updated once and would work for all

That would be a wonderful thing,Zubaz. I hope that turns out to be do-able.

Redbuzzard:

Just try... now working with my own location, only 5 days forecast

http.Open "GET", "http://xoap.weather.com/weather/local/YOURLOCATIONCODE?cc=*&dayf=5&link=xoap&prod=xoap&par=YOURID&key=YOURKEY" & str_UNITS & str_RANDOM_URL, False

That does it.

Think I'll stick with Winstep and mothball DX till SD gets its act together.

Something tells me JcRabbit's way ahead on this one.

Yes... And I see only one way to get the 10 days/36 hours forecast right now .  You need retrieve the data directly from the web pages through HTML. This is a hard way but it works for me...

Thanks for proposal Vad, but i know how to do with your explanation, i just have too many widgets to re-script and, as it's told by Adni18, i think that's the real only way (for everyone already using widgets) is that Stardock should negociate codes to be used by their consumers

yes... BUT DesktopX one of SD application

Weather widgets and objects, really based martin's code..

Silica weather come with dx, I think this one Offical Stardock Weather widget..and NOT work now...

So we need SD and dx developer support in these days...

i asked about the silica widgets, apparently they are not supported as they are too outdated

Dear Zubaz,
Stardock is or was offering a weather widget with the DesktopX, many people may have buy the DesktopX only for the Silica weather widget
I don’t mean that Stardock has to buy a license for all widgets, but it may help for a solution, for example an additional script for all widgets. Stardock has many professional employees with great knowledge of scripts!

I Agree. That problem must be solved only by the authors of these widgets (certainly if they have a free time or just desire to do this).

Besides it should not be forgotten - all of these widgets was FREE OF CHARGE. So I think you have no rights to submit any claims to their authors... And more than - to Stardock.

Yeah. It seems Silica and Martin's BaseWeather are the two widgets everyone based their work off of and they require two different methods of modification as the scripts are not the same (BaseWeather is more extensive.) 

I'm working with Martin's BaseWeather and so far I got the licenseKey and PartnerID prompt working, and finally cleaned up the code for the new restrictions.

If I understood correctly, the license agreement says if you're gonna distrubute the desktop applications you have to include the 4 links provided as well as the TWC logo with an embedded link. Would it be against the rules to include the links but have a way for the user to hide them?

I'll be looking into the silica script later.

Hello.

I had the huge bad luck of downloading desktopx yesterday, when the weather services were down
and i've read all the posts and commants, but yet have found no way to fix it.

Can someone please make a tutorial of how to fix it?
I'm no good with scripts and stuff so PLEASE make it simple.

Thanks

No any problems. Just send me one of your widgets which you want to modify. Or a link where I can download it and I'll help you to solve this little problem. I'm live in Europe too and I'm a big Internationalist.

This, I think, is the bigger problem. There's no easy way to fix this on the user's end. Even if we wrote a how-to, the user would have to do this for dozens of their weather widgets. And there are several variations to the script in each widget; just going through my collection I've encountered 3 different versions.

This is one more argument that only the authors of widgets must fix this issue in their scripts and the upload an update.

So it may be a tutorial for widget developers but not for end users!