<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>dnnwebcontrols Issue Tracker Rss Feed</title><link>http://www.codeplex.com/dnnwebcontrols/WorkItem/List.aspx</link><description>dnnwebcontrols Issue Tracker Rss Description</description><item><title>Created Issue: Certain .JS files don't get rendered - DNN 5.x [2851]</title><link>http://dnnwebcontrols.codeplex.com/WorkItem/View.aspx?WorkItemId=2851</link><description>Hi. There is an issue I keep runningy into that is driving me crazy &amp;#58;&amp;#41; &lt;br /&gt;&lt;br /&gt;Several of our customers and now ,our site &amp;#40;recently upgraded to 5.x&amp;#41; have started having problems where some pages &amp;#40;for whatever reason very weird&amp;#41; don&amp;#39;t render ceratin .JS files. For example dnn.controls.toolbars.js along with the dnnmenu.js and a few others. This only happens when you are in view mode or unauthenticated. We have a few modules that use the dnn toolbar and this ends up rendering an error, dnn.controls.toolbars is null. We always either disable to or set the visibility to false if the user isn&amp;#39;t in edit mode, but it still renders code which throws the error. We can&amp;#39;t identify any specific settings and have the problem with about 10&amp;#37; of our customers.&lt;br /&gt;&lt;br /&gt;what causes this&amp;#63; What causes the JS file such as dnn.controls.toolbar.js to either render or not render to a DNN site&amp;#63; &lt;br /&gt;&lt;br /&gt;-Chad&lt;br /&gt;www.datasprings.com&lt;br /&gt;</description><author>datasprings</author><pubDate>Sun, 27 Sep 2009 06:05:24 GMT</pubDate><guid isPermaLink="false">Created Issue: Certain .JS files don't get rendered - DNN 5.x [2851] 20090927060524A</guid></item><item><title>Created Issue: change of treeView control in DotNetNuke.WebControls [2699]</title><link>http://dnnwebcontrols.codeplex.com/WorkItem/View.aspx?WorkItemId=2699</link><description>to let show treeView as site navigation that looks like MSDN navigation tree &amp;#40;see for example http&amp;#58;&amp;#47;&amp;#47;msdn.microsoft.com&amp;#47;en-us&amp;#47;library&amp;#47;ywdtth2f.aspx&lt;br /&gt;there is couple of ways to achieve this look but no one is possible withou treeView code modify &amp;#59;-&amp;#40;&lt;br /&gt;&lt;br /&gt;advantage of this update is that tree without folder image can have smaller padding and also saves space on screen without loose of readibility.&lt;br /&gt;&lt;br /&gt;personaly I prefer some new property ShowFolders &amp;#40;true&amp;#47;false&amp;#41;, that hides folder image for non leaf nodes. In this case leaf node image can be vertically aligned with expand collapse image &amp;#40;see attachment&amp;#41;. This solution enables nice effect where instead of simple leaf node dot image can be its original image.&lt;br /&gt;More proper solution is probably to define 2 new props ShowFolders and leafNodeExpCollapseSymbol, but this will lost beauty of solution described above.&lt;br /&gt;</description><author>asida</author><pubDate>Thu, 17 Sep 2009 09:57:36 GMT</pubDate><guid isPermaLink="false">Created Issue: change of treeView control in DotNetNuke.WebControls [2699] 20090917095736A</guid></item><item><title>Created Issue: Regex to change version in the manifest</title><link>http://dnnwebcontrols.codeplex.com/WorkItem/View.aspx?WorkItemId=1556</link><description>When you build the project, the regex in the targets file changes version fields. When reusing&amp;#47;adapting the targets file for module projects, developers will need to make this change manually and correct the other version fields in the manifests.&lt;br /&gt;&lt;br /&gt;This is not an issue with the webcontrols package, but an alternate regex may be added and commented out to allow for devs that want the targets file to work with their project modules &amp;#40;for example the silverlight template&amp;#41; and only change the version node. An alternate regex example is&amp;#58;&lt;br /&gt;&lt;br /&gt;        &amp;#60;FileUpdate Files&amp;#61;&amp;#34;&amp;#64;&amp;#40;dnnFile&amp;#41;&amp;#34; Regex&amp;#61;&amp;#34;&amp;#38;lt&amp;#59;version&amp;#38;gt&amp;#59;.&amp;#42;&amp;#34; ReplacementText&amp;#61;&amp;#34;&amp;#38;lt&amp;#59;version&amp;#38;gt&amp;#59;&amp;#36;&amp;#40;Major&amp;#41;.&amp;#36;&amp;#40;Minor&amp;#41;.&amp;#36;&amp;#40;Build&amp;#41;.&amp;#36;&amp;#40;Revision&amp;#41;&amp;#38;lt&amp;#59;&amp;#47;version&amp;#38;gt&amp;#59;&amp;#34; &amp;#47;&amp;#62;&lt;br /&gt;&lt;br /&gt;If multiple modules are integrated in the manifest, they will all use the same version number. This regex will not work in scenarios that need different versions for each module.&lt;br /&gt;</description><author>hooligannes</author><pubDate>Mon, 20 Apr 2009 20:00:16 GMT</pubDate><guid isPermaLink="false">Created Issue: Regex to change version in the manifest 20090420080016P</guid></item></channel></rss>