Skip to main content

DotNetNuke 4.9.0 Released

DotNetNuke 4.9.0 has been released. Download is available at http://www.dotnetnuke.com/tabid/125/default.aspx.

Meanwhile DotNetNuke 5.0 BETA 6 is being tested by BETA testing users but no release date has been published.

DotNetNuke 4.9.0 was initially targeted as a security fix but then become a major release including several enhancements and numerous bug fixes. Some of the highlights for this release are as bellow.

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.
  • Fixed an issue that prevented users in certain locales from adding modules to div based panes.
  • Added a new default skin that is more contemporary
  • Added a new default template that removes much of the clutter and unnecessary information.
  • Added a new Text skin object that allows you to add localized text to your skin.
  • Added a new Styles skin object that allows you to insert additional stylesheets into the page header. Stylesheets can be optionally included using IE Conditional Comments.
  • Enhanced the Search skin object to include the option to display a dropdown list of web/site search options.
  • Enhanced the Update Notification Service to display information on new language packs that are available for locales which are currently installed.
Security Fixes
Updated Modules/Providers

The following modules and providers have been updated in the 4.9.0 packages.

Modules
Providers

For a complete list of all bug fixes and enhancements, please see the official change log.

Thanks to Joe Brinkman for sharing this information.

Labels:

Comments

Post a Comment

Popular posts from this blog

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 ...
4 comments
Read More >>>

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 ...
13 comments
Read More >>>

Google Chrome Error - Ah, Snap! Something went wrong while displaying this webpage

Many users are facing following error when they try to load the new Google Chrome Browser. Due to this error they could not use Google Chrome browser on their machine. This error is coming right after they installed the Google Chrome browser. The error message says: "Ah, Snap! Something went wrong while displaying this webpage. To continue, press Reload or go to another page." Following is a screen shot of the error. Error message asks to reload the or go to another page but no matter what they do, they still see this error message. Thanks to Rupesh Bhochhibhoya for solution to this problem. As per him, this problem is most probably because of anti-virus. The solution I learn is: goto properties of browser shortcut then append --no-sandbox on target line. Like: "C:\Documents and Settings\Administrator\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --no-sandbox then you are ready to go!! Please post in the comment if you have furt...
25 comments
Read More >>>