Dotnetnuke 4.9.0 RC1

Dotnetnuke has postponed the release of 5.0 and now releasing 4.9.0 (yet to release, currently in RC1). One important fix is part of this release is a fix in file based caching provider.

Major Highlights

Fixed issues with the URL Rewriter. There were several issues which could result in unreachable pages using friendly URLs. We have added in validation logic to prevent pages from being created which would violate folder naming standards or which would result in two pages receiving the same Human Friendly URL.
Fixed longstanding issue in the file based caching provider. There was invalid logic in the caching provider which prevented it from working correctly. The provider has been re-written to resolve the problem and provide a stable platform for web-farm scenarios.
Fixed several dictionary errors. These errors mostly occurred under heavy load or were otherwise intermittent. Dictionary usage was evaluated throughout DNN and updated to utilize thread-safe approaches for updating and caching the dictionary.
Security issues. Will post security bulletins discussing security fixes when DNN 4.9.0 is officially released.

Following are the related bug that they fixed.

DNN-8117: Bug Performance Disk Based Module Output Caching - Content Missing
DNN-7979: Bug Performance File Based Caching Provider

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 you do not get

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

How To Create Virtual Machine Using Existing vmdk file in VMWare Workstation

vmdk file is hard disk of the VMWare virtual machine. There are many scenarios where you may need to create a new virtual machine for an existing vmdk file. This is also an alternate Method to the “ vmx is not a valid virtual machine configuration file – Could not open virtual machine ” issue. Please refer to the previous post “ Could not open virtual machine – vmx is not a valid virtual machine configuration file ” for a full list of possible resolution. This post is to describe one of the solution in more details. How To Create a new virtual machine & attach the existing .vmdk file: 1. Open VMware and select create a new virtual machine with custom (advanced) configuration option. 2. Chose “I will install the operating system later”. and chose “I will install the operating system later”. 3. Select the operating system that matches the operating system in your existing .vldk file. 4. Select a location of the new virtual machine 5. Chose “Use an exis

Laksha

Search This Blog