﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Module :: Reports</title>
    <description>Information and progress for the DotNetNuke Reports Module project.</description>
    <link>http://www.dotnetnuke.com/Community/Blogs/tabid/825/BlogId/197/Default.aspx</link>
    <language>en-US</language>
    <managingEditor>andrew@openarrow.com</managingEditor>
    <webMaster>admin1@dotnetnuke.com</webMaster>
    <pubDate>Sat, 17 May 2008 04:24:49 GMT</pubDate>
    <lastBuildDate>Sat, 17 May 2008 04:24:49 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <item>
      <title>Reports Modules - Renderers, Caching and Parameters!</title>
      <description>So, It's been a little while since I blogged, but thats because I've been working on an exciting new feature for Reports. I call them "Report Renderers".</description>
      <link>http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1076/Default.aspx</link>
      <author>andrew@openarrow.com</author>
      <comments>http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1076/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=825&amp;EntryID=1076</guid>
      <pubDate>Mon, 14 Aug 2006 04:00:00 GMT</pubDate>
      <slash:comments>8</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1076</trackback:ping>
    </item>
    <item>
      <title>Reports Module...What to do next?</title>
      <description>Recently, I've been bug fixing on the Reports module (see my previous post Re: Caching Workaround and the Reports Project Fourms). Now that most of those issues are fixed, its time to look at new features!</description>
      <link>http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1022/Default.aspx</link>
      <author>andrew@openarrow.com</author>
      <comments>http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1022/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=825&amp;EntryID=1022</guid>
      <pubDate>Mon, 17 Jul 2006 08:00:00 GMT</pubDate>
      <slash:comments>7</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1022</trackback:ping>
    </item>
    <item>
      <title>Caching workaround for Reports Module</title>
      <description>&lt;P&gt;One of the features I'm working on in the next version of Reports (actually its more of a bug fix) is to provide Administrators with the ability to disable Caching and set a Cache Timeout. Right now the module caches the results of a report with no time out, and the only way to clear the cache is to open the Module Settings and press Update which clears the cache. This has caused problems for some users so the new version should fix those problems.&lt;/P&gt;
&lt;P&gt;In the mean time, I have a one-liner code fix for anyone who wants to disable caching completely. WARNING: This has not undergone rigorous testing and you should create a backup copy of the relevant file just to be safe. Also, this change will affect all Reports modules on all Portals using the same codebase. Having said that, I've had no issues and it seems to disable caching properly. Here's the change:&lt;/P&gt;
&lt;P&gt;In App_Code/Reports/ReportsController.vb at line 145, replace the following line:&lt;BR&gt;&lt;FONT face="Courier New" color=#ff0000&gt;Dim objCache As Object = DataCache.GetCache(strCacheKey)&lt;/FONT&gt;&lt;BR&gt;With this text:&lt;BR&gt;&lt;FONT face="Courier New" color=#ff0000&gt;Dim objCache As Object = Nothing&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;This forces the module to execute the report in every request and bypasses caching. There may be a performance penalty, but if you are having problems because of caching this is a short-term workaround that should help, at least until the new version is ready.&lt;/P&gt;</description>
      <link>http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1011/Default.aspx</link>
      <author>andrew@openarrow.com</author>
      <comments>http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1011/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=825&amp;EntryID=1011</guid>
      <pubDate>Sun, 09 Jul 2006 08:00:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1011</trackback:ping>
    </item>
  </channel>
</rss>