Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Weather Modules GONE MAD!?Weather Modules GONE MAD!?
Previous
 
Next
New Post
5/6/2008 6:03 PM
 

Acutally www.oliverhine.com  IS having the same issue as the rest of it. It was working today around Noon ET when i submitted a feedback form but it appears he is a victim as much as us.

It's unforuntate such a wonderful module's osurce is not available but understandable......

Dean

 

 
New Post
5/6/2008 6:11 PM
 

As a follow up (for you that know your way around DNN)

I saw this entry in the change log. Probably just an alternative spot for entering the info and not being passed but MAYBE a billionth of a chance? (cuz i doubt they said in 2005 it would need to be passed?)

4/4/2005 - 11:07 PM: v1.2.2

  • Added optional Web.Config settings for weather.com license. Use appSettings "Weather.PartnerId" and "Weather.LicenseKey"
  •  
    New Post
    5/6/2008 6:22 PM
     

    I chatted with Oliver and he said he would work on getting an update posted asap.


    DotNetNuke Modules from Snapsis.com
     
    New Post
    5/6/2008 9:08 PM
     

    I just ended up here by chance when searching the web for more information on what happened today, which also affected one of my applications. Anyway, the simple solution is to omit the '&prod=xoap' part from the URL. Previously the URL I used to access the XML data feed (as per their SDK) was:

    "/weather/local/" & LocationCode & "?cc&dayf=5&unit=" & IIf(Imperial, "s", "m") & "&prod=xoap&par=<partnerID>&key=<LicenseKey>"

    replacing this by 

     "/weather/local/" & LocationCode & "?cc&dayf=5&unit=" & IIf(Imperial, "s", "m") & "&par=<partnerID>&key=<LicenseKey>"

    gets the feed back. I'm extremelly PISSED OFF with Weather.com. I called them today and they were unable to give me any info or state this simple solution, rather implying (on the phone and on their email sent barely 6 days ago!) that my application was not following their TOS (which is impossible to verify as they provide no mechanism to do so). They promised to call me back but never did.

    Now I have to make a new emergency release of my application (with half finished new features I've been working on!!!!)  to fix a problem they caused in the first place.

    You can read more about this in the Winstep Forums.

     
    New Post
    5/6/2008 11:47 PM
     

    While i eagerly await the fix to the DNN Module from http://www.oliverhine.com/, i will also try to patch what i have by using Jorge's fix.
    My question is which file is it where i need to do the replacing? Is this in the desktop module?
    Is this located in a file inside the desktop module? Is it in the Source Code and then recompile? 
    Please let me know for sure... thanks.

    ---------------------------------------------
    Also in regards to what weather.com has done. When i started noticing these problems this morning, i became very curious and then i remembered an email sent to me some time back remembering the date of May 6, 2008. THEN IT HIT ME!..... So i started this post not sure if the DNN community would grab their pitch forks and torches and rally with me.

    It appears this was the right place to post info about this and question what in the WIDE WIDE WORLD OF SPORTS was a goin' on here with the weather modules going on the Blink.

    As i mentioned in a previous post, I actually got a call from the weather.com programmers and was informed this was done on purpose because they were aware that DNN Modules and similar(they called them widgets I.E. other applications) were using their weather feeds to make nice little weather feed modules.
    Basically weather.com wasn't happy because they had no way of getting something called "Pay Per Click" feedback. They basically told me that such modules cut them out of the loop in this regard. To them they felt that their FREE url feed product was being used for profit by other programmers and they got nothing.... So what do they do? They change their feed url thus breaking EVERYTHING to get our attention. I'd just like to know who made that executive decision?

    I share the frustration everyone is having with this issue. Not very Consumer savvy if you ask me. I wasn't sure what kind of response i would get when i started this post but now after a full day... its pretty clear this little change by weather.com had some "Vista" like effects on our little DNN Community.

     
    Previous
     
    Next
    HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Weather Modules GONE MAD!?Weather Modules GONE MAD!?


    These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

    For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

    1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
    2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
    3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
    4. No Flaming or Trolling.
    5. No Profanity, Racism, or Prejudice.
    6. Site Moderators have the final word on approving / removing a thread or post or comment.
    7. English language posting only, please.
    What is Liquid Content?
    Find Out
    What is Liquid Content?
    Find Out
    What is Liquid Content?
    Find Out