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.

Comments

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

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 Deadspin: Spor

Howto Run Your HTML Static Website Locally In IIS On Windows PC

WHAT & WHY: As a developer many time you may wish if you could run your static HTML website locally on your computer (Windows 7, Windows Vista, Windows XP, Windows 2008). Although with Static website, you could easily download and double click the index.html or home.html file to open and run other pages. But this will not give you the real world senario. For example you will not able to use a path like /images/home-page-banner.jpg. You will have to use a relative paths like ../images/home-page-banner.jpg. Following are very easy steps to do so. These steps are for Static HTML website. I will also post steps for more advance websites that uses ASP, ASP.NET, Dotnetnuke etc and uses database server.   WHAT YOU NEED: 1. IIS Server installed on your local machine 2. FTP username, password to download files form your FTP server 3. Administrative rights on local machine. Many task will display messages requesting Administrative privilege to run the task.    STEPS: 1.