I really don't understand why so many people are bashing Stardock over this one.

First and foremost, Stardock already did what they could when they partnered with Accuweather  some time ago and *hosted* the weather feed themselves. This means Stardock is the company providing and paying for the bandwidth used by their Accuweather widgets, not Accuweather.

Second, DX widget authors are the *only* people responsible for choosing to use Weather.com over Accuweather.

Third, ALL applications using Weather.com's feed were affected, (and this is the important part) REGARDLESS of them following Weather.com's rules or not!!! Weather.com couldn't care less if you're one of the 'good' or the 'bad' guys, they knew this change would affect us ALL and they went ahead anyway!

Weather.com unilaterally and without warning CHANGED the format of the request string (they did the same last year, but at least then they sent out a warning before to everyone who had a valid license key).

Since most of us are using hard coded request strings (Winstep Xtreme included, but I changed that now) the only way to solve this is by issuing a new release. Fool me once...

Sorry JcRabbit, but on wc site, you not seen any accuweather widget.

There is 1 custom gadget, and come few with mycolors, BUT those gadgets.

Currently we not have free sample for build custom accuweather Dxwidget..

Good work! This fixed the prob for me.

Thanks for your input!!!

The short answer is no. You would have to redesign your widget to The Weather Channel standards (logos, adverts, etc.) Also, if you have hard coded your personal ID and license key into the widget, you can not redistribute it as that would be in violation of the license agreement.

If you use the solution that doesn't call for an ID or key, you MIGHT be able to reupload. I'm not entirely sure. Just bear in mind that it is not the official TWC method and will likely be prohibited in future, then you'd have to re-do your widgets all over again.

I apologize for the tone of my posts yesterday.  I think when stuff like this happens, we all go through an adjustment reaction, and we each have to find our own way of dealing with it. 

I tried Neophil78's solution, and obviously I'm doing something wrong, because the change did not fix the problem for me.  I've never built anything in DesktopX, I really don't even know how to begin with it, so my personal answer to this dilemma is to cease using DesktopX.  The clocks never stayed in the place I put them, so I quit using the clocks long ago, and have replaced that feature with ClocX; I've been using Rainlendar instead of the calendars; and now I'm going phase over to Rainmeter for the weather feature on my desktop, and just skin this stuff myself using the simple code and .pngs I invent myself.  DesktopX is just too complicated for me, and I have enough things I MUST attend to in my life right now--I don't need another thing to distract me from my the things I have to get accomplished.

Thanks for all who tried to help with this issue.  I appreciate your time and willingness to assist.

Vadim

What method use on update?

xml feed?

Vad_M--have you updated the SD Desktop weather widget, and if you have, are you going to upload it?

We don't know. Since that fix technically uses a different feed than the one licensed (I think) it may or may not fall under the license agreements.

Err on the side of caution. If that method is in violation of TWC's license, and you re-upload using it, TWC will have a right to hold you liable.

My honest advice is to just post a notice on your skins informing users that it doesn't work at the present time, until a more long-term solution presents itself. Or you could just take down your skins. It sucks, but those are our options.

As I said before, these fixes are primarily for end-users who have already downloaded the widgets. We authors have a much more difficult time on our hands in terms of how best to proceed.

the only major cahnge was to replace xoap with xml in any addresses that refence the TWC site. I found 2 references in my implemntation of Vienna. One was in the script for weather_image and one was under the script for weather_location.

Depending on how your widget is setup, you may have more or less references and in differnt places. just open the object list and sort by name and look at the scripts for all of the weather objects. most of them won't have scripts, but for the ones that do just look for xoap and replace it with xml.

I am not sure WHY this works, or if it will continue to work. As others have said, chances are TWC will identify this leak and patch it up shortly.

Vad, thank you