Archive
Monthly
Go
|
|
DNN Blog
Mar
24
Posted by:
Joe Brinkman
3/24/2010 7:38 PM
 I am happy to announce that the DotNetNuke 5.3.1 release is now available for download. This release was focused on fixing 3 significant issues with the 5.3.0 release which caused us to remove the release from CodePlex and our DotNetNuke Support Network. It is never easy to admit that significant issues slipped through testing and made it into a release package forcing you to take drastic actions. The only thing we can do is to re-evaluate our processes and continue to find areas for improvement – obviously we have some work to do. Having just finished the sprint for 5.3.0 last week, we are finally getting around to our post-mortem on the release where we will look at what went right, and what went wrong. It is only by taking a hard look at our processes and owning up to our mistakes that we can fix the problems that allowed this to occur. We can and we will do better.
The changes for this release are outlined below.
Major Highlights
- Issue fixed where Newsletter module only sent SMTP test email.
- Issue fixed with signature change to Synchronize Folders methods.
- Fixed the issue with the email notifications where the From and To addresses were swapped.
Security Fixes
Updated Modules/Providers
The following modules and providers have been updated in the 5.3.1 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release.
Modules
Providers
As with any release, we recommend you perform a complete file and database backup before performing any upgrade on a production website and that you first conduct a trial upgrade on a staging version of the site. Following these guidelines will ensure that you are able to recover should any unforeseen problems arise during the upgrade process.
Technorati Tags: DotNetNuke, Release
16 comment(s) so far...
Re: DotNetNuke 5.3.1 Released
I think there is typo in "Updated Modules/Providers" paragraph
- (The following modules and providers have been updated in the 5.2.0 packages.) It should be 5.3.1. am I right?
By Rashid Kazi on
3/25/2010 7:28 AM
|
Re: DotNetNuke 5.3.1 Released
Happy to here good news, thanks a lot for the good effort you are doing
By jose sanguino on
3/25/2010 7:28 AM
|
Re: DotNetNuke 5.3.1 Released
Hi
I was one of the few that installed 5.3 which is running in production does this release support an upgrade 5.3.
By Dr Ocelot on
3/25/2010 7:29 AM
|
Re: DotNetNuke 5.3.1 Released
@Rashid - Thanks. Typo is fixed.
By Joe Brinkman on
3/25/2010 7:29 AM
|
Re: DotNetNuke 5.3.1 Released
@Dr Ocelot - Upgrades from 5.3 will work as usual.
By Joe Brinkman on
3/25/2010 7:30 AM
|
Re: DotNetNuke 5.3.1 Released
Smooth update except the known error in the XML module (deleted it and all went fine) - great work.
By Matt Jura on
3/25/2010 3:08 PM
|
Re: DotNetNuke 5.3.1 Released
Hi,
what's happening to the localization features then? Are they now foreseen for 5.4.0 or later? What's the estimated date?
By fprati on
3/25/2010 3:08 PM
|
Re: DotNetNuke 5.3.1 Released
This is good news indeed. BTW, I would like to be very very sure about using Telerik Controls. Where to find information, where to have wrappers, etc., etc.
By Carlos Ortiz on
3/25/2010 3:08 PM
|
Re: DotNetNuke 5.3.1 Released
Disappointed to see the custom registration page bug introduced in 5.3 wasn't fixed and is marked for 5.4. Looks like we won't be upgrading until 5.4 drops. Kind of frustrating that functionality was broken in a major release and isn't being fixed with a minor release.
By mschepker on
3/25/2010 3:07 PM
|
Re: DotNetNuke 5.3.1 Released
@mschepker - There was no time to address that issue in this quick fix. We still have an April release coming up and the fix will be addressed in that release. We cannot do one week releases where we have a ton of bug fixes. We have to pick and choose those that we can reasonably accomplish in the given amount of time. If I would have included that fix, we would have been forced to push 5.3.1 out until next week which is only 2 weeks before we deliver 5.4.
By Joe Brinkman on
3/25/2010 3:11 PM
|
Re: DotNetNuke 5.3.1 Released
Joe,
Ah, didn't realize 5.4 would be coming so quickly. I figured it was still a couple months out. That makes more sense then. Thanks for the info!
By mschepker on
4/15/2010 4:26 PM
|
Re: DotNetNuke 5.3.1 Released
BEWARE: unless I've read this post (www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2540/XML-support-for-DotNetNuke-5-3.aspx) wrong, current users of the XML module MUST upgrade that first BEFORE installing 5.3.1!
If correct, I'm suprised this was not automatically handled or noted a bit more prominently in the release notes!
By Juan de Vashon Isle on
4/15/2010 4:31 PM
|
Re: DotNetNuke 5.3.1 Released
Glad to hear you guys are keeping up with the "ton of bug fixes" Joe. Not to offend anyone, I love this CMS system, but it's posts like these that keep me from dishing out the 2k a year for a profesional membership.
By Kenneth Sim Sim on
4/15/2010 4:28 PM
|
Re: DotNetNuke 5.3.1 Released
Does there happen to be a VS2005 version of the .sln available?
(DotNetNuke_VS2008.sln)
Thanks.
By Mark Deweese on
4/15/2010 4:28 PM
|
Re: DotNetNuke 5.3.1 Released
Hi,
ist there a simple Doc on "how to update" ?
I installed DNN via MS Plattform installer.
Now I am a little lost on how to do the install.
j.
By jofeuerstein on
4/15/2010 4:28 PM
|
CodePlex source control release tagging
Thanks for this Joe - good to hear a release is on the way quickly.
DNN release stability has never been the team's strong point over the past few years I've been part of the community, but it does seem to be improving. Stability is already a damn sight better than the bug-ridden v4.4 I first experienced back in ~2006!
On the subject of release versions - we sync our local version with the CodePlex SVN tree (via Git). Up until v5.2.3 you were helpfully associating changesets that corresponded with downloadable releases - e.g., changeset 46577 (dotnetnuke.codeplex.com/SourceControl/list/changesets?page=1) is coloured yellow and includes the comment "Associated with Release: 05.02.03".
This no longer appears to be happening, meaning we have no idea what release our currently downloaded codebase corresponds to (or which changeset correponds to a particular release). This creates major headaches with knowing what release note workarounds are relevant, plus we generally replay our modifications over a particular downloadable release rather than deploying the SVN codebase directly.
Would it be possible to resume labelling changesets on CodePlex that correspond to release versions?
Many thanks, Ben
By B Johnson on
4/18/2010 6:30 PM
|
|