<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"><channel><title>Cleveland Sports Radio</title><link>http://clevelandsportsradio.net</link><description>RSS feeds for Cleveland Sports Radio</description><ttl>60</ttl><item><comments>http://clevelandsportsradio.net/Home/tabid/125/articleType/ArticleView/articleId/2086/WebsiteForum-Issues.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://clevelandsportsradio.net/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=125&amp;ModuleID=599&amp;ArticleID=2086</wfw:commentRss><trackback:ping>http://clevelandsportsradio.net/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2086&amp;PortalID=3&amp;TabID=125</trackback:ping><title>Website/Forum Issues</title><link>http://clevelandsportsradio.net/Home/tabid/125/articleType/ArticleView/articleId/2086/WebsiteForum-Issues.aspx</link><description>We moved from DotNetNuke
Framework 4.9.x to 5.0.x the update was largely successful.&amp;nbsp; But some
changes we made to the existing framework over the years has caused
some outstanding issues that I'm working on fixing.&amp;nbsp; 

1.&amp;nbsp; The Forums are down because there is a display error.&amp;nbsp; I believe
that after the update to the new forum software, each user's custom
forum display settings for the forum got hosed.&amp;nbsp; If I create a NEW
forum, they display fine.&amp;nbsp; But the old forum is messed up.&amp;nbsp; I've
contacted the developer to try and locate where the user's display
settings are stored so I can debug this.&amp;nbsp; I'm waiting on a reply.

2.&amp;nbsp; If you get an error like, "Exception has been thrown by the target
of an invocation."&amp;nbsp;&amp;nbsp; when you login or try and post in the SoapBox.&amp;nbsp;
This is happening because old information remains in your browser's
cache.&amp;nbsp; If you clear your history/cache in your browser, it should fix
the problem.&amp;nbsp; 

3.&amp;nbsp; If anyone is experiencing other problems, please send me an email kbaird@vgn.us&amp;nbsp; and I'll do my best to help you out.&amp;nbsp; 

Thanks for your understanding
Kevin
</description><dc:creator>tempestb3</dc:creator><pubDate>Thu, 08 Oct 2009 14:02:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2086</guid></item></channel></rss>