|
|
Sep
30
Posted by:
Joe Brinkman
9/30/2009 11:22 PM
With the month of September coming to a close it is time once again for another DotNetNuke Stabilization release. DotNetNuke 5.1.3 resolves almost 40 issues with the previous release and further stabilizes the 5.x codebase. Given the stability of the recent 5.x releases it should not come as any surprise that the fixes in this release tend to be narrow edge cases or resolved problems where well known workarounds were available. We also added a minor modification that improves the ability of administrators to email event logs to their support providers. This will allow system integrators, hosters and consultants providing DotNetNuke customer support to get a better snapshot of errors that the user is experiencing without relying on the user to accurately cut and paste error messages. The changes outlined below were incorporated in these releases. As usual, the complete details for all of the changes can be found in the ChangeLog. Major Highlights - Added the ability to specify a subject line when emailing event viewer logs
- Modified the event viewer to include event logs as email attachments when emailing the event logs
- Added the ability to use dictionary objects for token replacement in system messages
- Fixed an issue which caused an error whenever edititng the Site Settings.
- Fixed issue which caused an error trying to retrieve a role group by name
- Fixed an issue which prevented a skin from being able to be re-installed or uninstalled.
- Fixed issue where Html module was displaying unpublished content
- Fixed issue where URLs for pages within the site were always being created as relative which is a change from previous versions.
- Removed solution explorer page from the Admin menu and removed the Marketplace feed from the OPML file.
- Fixed issue with upgrading DotNetNuke 4.x skins when upgrading site to DotNetNuke 5.x
- Fixed issue which resulted in incorrect URL for SiteMap in a child portal
- Fixed issue which caused error when deleting files from the Host file manager.
Security Fixes Updated Modules/Providers The following modules and providers have been updated in the 5.1.3 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release. Modules - HTML 05.01.04
- Form and Lists 05.00.03
- Forum 04.05.03
Providers - AspNetMembershipProvider 05.01.03
- DNNMembershipProvider 05.01.03
- FileBasedCachingProvider 05.01.03
Technorati Tags: DotNetNuke, Release
4 comment(s) so far...
Re: DotNetNuke 5.1.3 Released
Hi Joe
Does the 5.1.3 upgrade zip file include the updates for previous levels? I am on 5.1.1 at the moment, so can I skip directly to 5.1.3 or do I have to install the upgrade to 5.1.2 first? Also, I cannot find any instructions for doing DNN upgrades, what is the upgrade process please?
Best wishes, John
By SimmoJ on
10/1/2009 10:12 PM
|
Re: DotNetNuke 5.1.3 Released
Simmo, you can easily skip a few versions during upgrades, e.g. upgrading from DNN 5.0 to 5.1.4 - and of course from 5.1.1 to 5.1.4
By Sebastian Leupold on
3/6/2010 9:20 AM
|
Re: DotNetNuke 5.1.3 Released
@John: Yes, you are covered! DNN releases are typically 'rollups' so incorporate ALL changes and modifications up until some (unfortunately unspecified) previous release. I think versions older than (4.3???) may require manual merging of your old config.xml file with the new one (i.e., release.config).
Joe: THANKS for delineating what Module/Provider versions are included in this version! I've never known how to sleuth this out in the past. Super helpful!
By Juan de Vashon Isle on
3/6/2010 9:20 AM
|
Re: DotNetNuke 5.1.3 Released
Here is some guidance in the forum: web3.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/334206/scope/posts/Default.aspx
I am about to try this myself, but am worried about having to re-do web.config, 3rd party modules, icons.... I was hoping the upgrade would just replace code that is in place, but it looks like it also rewrites your database, so you have to backup and then restore. I am going to wait a bit to see what other people say before having to do a lot of rework.
By john dukovich on
3/6/2010 9:20 AM
|
|
|