Peter some answers and updates

Yes I use 4.0.1 thanks for asking The js error is in an older post. Yes I will try to write an XSL to get the proper date. I had hoped that it would work like the old module and other rss readers.

Regarding the js error I have found how to remove it. If I remove from my web.config the line  xhtmlConformance mode="Legacy" I cant recall why I put it there, mybee an other module needed it I will try to find out. I have never get this js error before.

 I have done a new test and it looks like all feeds are loading better now. However the load time are extrely long It takes abou 5 minuts to load the first time. Compared to the old one that took seconds. I have not yet found out how the cach parameters interact. I will continue the tests.

Jan

Jan, from your previous post it looks like you are making some progress.

I think that if you need the performance for a production site for your RSS Feeds then you should consider reinstalling the previous version until version 4.00.00 can offer the improvements that you are requiring.

It is my opinion that this thread and others have clearly expressed all the current concerns in this new version and that Peter is working at addressing these concerns. For example I have not released this version to clients at this time, they continue to use the previous version or have purchased thrid party RSS modules, My discussion in this forum is simply to report our findings and to assist with this iteration of the module, therefore in our case we do not need an urgent solution. What I can say is that this next generation of the NewsFeeds module is moving in the right direction and I'm sure that Peter is dedicated to great things for this module. Having said that, we have found that 4.00.01 is behaving better that the previous one (except the lag when updating the cache)

In summary,

Revert bsck to the previous version if you have some urgency for a production site.

Peter has responded very fast to issues raised since this modules release, and has made a beta available prior to the next release.

I don't understand your particular issues, my typical pre-production testing involves testing in a fresh install of DNN, this way I can eliminate any third party module interference. When I move (in testing environment) to a copy of a production site then I can normally be happy that the module works in a clean environment and any issue must then relate to some difference in the production version. My troubleshooting is therefore narrowed down somewhat.

cheers

Craig