Having same problem... Can't wait for a fix????

Oh well....I guess I'm going to have to check the weather the old fashioned way....actually get up out of my chair, walk outside, look up in the sky, and feel with my senses.  Kinda trippy.  

From what I can tell....it's only the "CurrentConditions" information that is borked......I have the same issues with my Samurize configs, however all "Forecast" information still works.

This would seem to be Weather.com trying to generate some Desktop Weather revenue. Be careful of their "Free Trial"...they take your credit card info and unless you cancel prior to the end of the trial they just go ahead and bill you.

Or try using METAR information.

Does that really work?

So I'm a newbie to DesktopX issues.  been using for a long time - have only made basic edits/ additions never created an entire theme from scratch.  I typically stick to entire themes rather than loading individual widgets.  I am having the same weather widget problem as the rest of the world! 

The zipcode error comes up before the rest of my desktop loads.  I do run desktopX builder. when the desktop is running normally I can make any edits I want to the widgets and objects in the current theme and save them etc etc.

I can't get the edit menus to come up when selecting the items because of the zipcode errors!

is there any easy way to delete the weather widget from the theme before I load it on the desktop?

Thanks!

Eve...Help!!!!! 

A little hint: http://wiki.wunderground.com/index.php/API_-_XML

Don't forget: http://www.wunderground.com/members/tos.asp#api

Hi guys, I've been looking at this issue all day and it seems like the change is with the weather.com xml format requirements

If you're using the same base code as I seem to be using here, the weather widget requests data from this url:

http://xoap.weather.com/weather/local/95670?cc=*&dayf=5&unit=m&rnd=0.6765406

where it genererates bolded values on the fly.

If you type this in your browser however you always get an Missing XOAP 'link' parameter in request." error

After doing some research, it seems like weather.com is requesting that xml requests need to have a link=xoap format in it as well as a license key and a partner id.

Im  trying to find a workaround ATM and would be happy to give any info to anyone else who'll help me find the solution.

Thanks,

Homer

Well, that sinks it. It appears the url used to get the weather is no longer valid. 

^ sorry, By workarounds I meant nothing illegal, I simply meant making a base code to work with another site,  or finding someway to edit the code such that it gets the liscence for us through weather.com. They seem to offer a free service, all they want is that we sign up for it.

My only problem is that; I like to use Desktop Themes, which already have the Weather Widget coded into it. I could easily make a desktop or objects/widgets without the weather but i like to use Themes already made. Is there any possible way to take out the Weather Widget in the Theme without loading the theme? Due to the Zipcode error I cannot edit the Theme when loaded, all i get is that most ever annoying error

turn off your internet.

The base code has a simple If system.internetconnected Then

if you're not connected, you get no error

• Rename the *.desktop to *.zip
• unzip it
• delete the weather widgit
• zip it
• rename it back to *.desktop

By going to this site you can get a partner number and licence key which is free.

http://registration.weather.com/registration/xmloap/step1

I then replaced the random with

str_RANDOM_URL = "&link=xoap&prod=xoap&par=XXXXXXXXXX&key=XXXXXXXXXXXXXXXX"

where par=partner number and key=licence key provided in the email weather.com sends.  unfortunately I don't have desktopX pro to return the glow weather wiget back to  a standalone sidebar gadget.  Perhaps when starting a weather gadget it can request each person to provide their number and key then store them for later.

Ok, Now Im wondering if we can do anything to get ONE license key and partner name for use with all widgets that use this service.

That way, All we have to do is update the base code to include the partner and liscense key as you have, and make it usable for all end users who just want to download a theme with a weather widget.

(what I'm saying is that, I don't mind getting a key, but it seems kinda unnecessary to me to force EVERYONE who uses the application to get a separate liscense and key for it...)

I mean not only is that inconvenient for the users, but it's gotta be draining on weather.com's servers..

does that make sense?