I apologize for the new thread but I felt some clarification of the issue was in order as the other thread was getting a bit convoluted.

The problem:
I have 8 sites with GoDaddy.  All are on shared hosting.  One site has a news module.  It works fine.  I've attempted to use the news module on some of the other sites but regardless of the news URL I use, I receive this error message while I'm logged in:

• Could Not Connect To http://sports.espn.go.com/espn/rss/ncaa/news. You Should Verify The Source Address Is Valid And That Your Hosting Provider Has Configured Their Proxy Server Settings Correctly.

Once I log out, the error changes to:

• News Feed Is Not Available At This Time. Error message:Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0,  Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

In one reply from GoDaddy, they gave a link to one of their support articles and said to insert the code (in the article) into the web.config file.  This code is supposed to set up a proxy connection. 

The irony is that the article says this isn't necessary because they (GoDaddy) to that anyway.  The fact is they don't.  I checked for this code in every web.config file of every one of my sites.  The other irony is that I tried this code anyway; it makes no difference whatsoever.

Next, they said that the news module is trying to "exceed a medium trust level" and that they do not allow this with shared hosting.  Of course, when asked to explain why the news module IS working in at least one of my shared hosting accounts, they can't say... but still insist that this is the problem.

So now my question to Lee, Joe, or anyone else out there that might know: Is the news module configured to exceed a medium trust level?  I've checked in my own limited way using VWD but don't see anything to indicate this. 

I've also posed this question to Peter Donker, project lead for the news module at DNN.  I haven't heard back from him (not sure what time zone he's in and I'm in Hawaii).

I realize some might offer the advice of dropping GoDaddy (it sounds quite appealing at the moment) but without getting into tedious details, that is not an immediate option.

Thanks again Lee And Joe, keep up the great work!

Sounds like you are getting the run around. To be honest I don't know. - If moving host is not an option, I would try: Orizonti News Feeds

and see if that solves the problem, support at orizonti is also very good.

The other option I would consider is just to move that site and future sites to a different hosting provider.

Thanks,

I've also got an error message while using the news feeds core module:

Feed 'http://news.google.com/news?hl\x3dd...ut\x3drss' could not be loaded. Error: Download error

I' ve absolutely no experience with RSS but in my dnn module some feeds work and some don't.
I' tried all the feeds in a gadget on igoogle and all feeds work properly.

what did I do wrong ?

md-pv, can you let us know which version of the news feed module you are using? The 4.0, if I remember correctly, was coded for strict compliance, but not all of the feeds (the URLs) used strict compliance of RSS when doing their feeds, so alot of people were not getting the feeds that they were prior to upgrading to the 4.00 of the module.

The latest version olf the module was supposed to have relaxed this. The latest version is 4.00.01

Here is what Peter Donker, The Lead for this module had to say when it was released:

"Newsfeeds 04.00.01 has been officially released today. The main reason for the upgrade is dealing with a growing number of feeds that were reported to us that would not show in the module. So the criteria for feeds has been relaxed somewhat in the aggregation engine. The aggregation engine needs to somehow interweave x feeds and does so using the pubDate. So for this to work the pubDate has to be understood by the aggregation engine. This was new to Newsfeeds 04.00.00. Before there was no parsing of the incoming feed and it was passed on untouched. Version 4 changed all this and as a result people started reporting feeds that were being rejected. Mostly this was because of non-standard pubDate fields in the feed. The official specification for Rss 2 stipulates that the pubDate must be RFC 822. So despite testing, it was not until after release we found that many (and among them very respectable) feed publishers were not sticking to this standard. The date restraint has been relaxed and this should help many people. Other changes include:

* Add accept and user agent for web request
* Remove email address constraints
* Add option to not use Ajax rendering in module settings
* Reorganized and rewritten Javascript to allow rendering of multiple News modules on a single page in Ajax mode
* Fix for XHTML issue (div ending with span)

I strongly urge those on 04.00.00 to upgrade. And as always: do this on your staging server first.

Peter" (taken from the DotNetNuke blog for Peter Donker at: http://www.dotnetnuke.com/Community...ased.aspx)


So, take a look and see if that does it for you.

Thanks,

Mark

Thanks, Mark!

Thanks a lot. I updated the module and everything works just fine :-)