Dotnetnuke 05.02.01 Release Updated Today

DotNetNuke Community Edition, Version 05.02.01 which was released on Dec 22, 2009 has been updated today. Major highlights of DotNetNuke Community Edition, Version 05.02.01 are:

Fixed issue where banners were not properly rotated according to the specified views/clicks
Fixed issue where upgrades could fail if the the user account did not have permission to update objects in some db schemas
Fixed issue where list values were visible outside of the Portal where they were created.
Fixed issue where caching providers were not rendering unicode characters properly.
Fixed issue with missing Telerik assembly in the source package.
Fixed issue where Ajax HostSetting was not properly set on upgrade from 4.x installations.
Fixed issues where upgrades would fail with a unique index violation
Fixed issue with the Starter Kit which was missing HTML module files
Fixed issue where page templates were not working correctly
Fixed default settings for the module and output caching providers
Fixed issue which prevented Blog module from working after some upgrades to 5.x
Fixed issue when creating a new module in the Module Definition Wizard if the .ascx extension was not specified.
Fixed issue where localization was not working if the application virtual directory name was also part of the module name.
Fixed issue where the FriendlyName for Schedule Items was not being saved.
Fixed issue where GetUserCountByPortal was making excessive database calls instead of using cached values
Added binding redirect setting in web.config to prevent versioning issues with Telerik assembly

Source:http://dotnetnuke.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=37670#DownloadId=98351

Comments

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart. Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel. I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances. RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs. 25 Best Blogs of 2009 25 Best Blogs 2008 25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog ...

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...

Laksha

Search This Blog