Archive
Monthly
Go
|
|
DNN Blog
May
19
Posted by:
Joe Brinkman
5/19/2010 10:53 AM
 I am pleased to announce the release of DotNetNuke 5.4.2. 5.4.2 is a monthly stabilization release which addresses a couple dozen issues with the 5.4 release. Because of the 5.4.1 release, the 5.4.2 release cycle was shortened which meant that a few high profile issues were not able to make the cutoff for this release. We expect to address those issues in the 5.4.3 release due out in June. This release also includes numerous code contributions and bug fixes submitted by the community. We will be working closely with the community on the 5.4.3 release in order to further scale the number of issues we can get addressed in that release. As usual, you can see the full list of changes for this release on the changelog.
Major Highlights
- Improved performance of Sql script for listing modules by portal.
- Improved DeleteModule method to handle instances where object may be null.
- Increased the size of the Admin - Pages list box to cater for sites with a large number of pages.
- Updated the Installation Wizard's Polish & German language packs.
- Fixed issue with emailing Vendor details to the Admin and conformation details to the Vendor.
- Fixed issue where Sitemap does not work if globalisation culture is a culture that uses comma as separator
- Fixed issue with missing type specification in SiteMapSettings.
- Fixed issue where upgrade fails when site has a non-'en-US' default language
- Fixed issue with link editor showing pages the user does not have View permissions for.
- Fixed issue with registration emails not being sent from Child Portals.
- Fixed issue with Role update email not beiung sent to the user.
- Fixed issue where default tabs for Site Settings were not created when creating settings for a new language.
- Fixed issue where localization upgrade script was incorrect and could result in error on upgrade.
- Increased the number of Users that a DNN installation can handle to 2.14 billion.
- Fixed issue where localization updates were not properly applied to individual portals.
- Fixed an Issue, where Language Editor returned to Language List on update of any file.
- Fixed issue with jQuery not loading early enough.
- Fixed issue with email sending not recognizing HTML properly.
- Fixed issue with port numbers in email address during installation.
- Fixed issue with passing connection information to Sql Module.
- Fixed issue where the User Skin object was ignoring the ShowUnreadMessages attribute
- Fixed issue where the profile ImageEditControl datatype was only added to Portal 0.
- Fixed issue with url formatting when no context exists. Adding "http" is fallback position.
- Removed "obsolete" state from DotNetNuke.Services.Mail.Mail.Sendmail.
- Fixed rare issue where the install wizard could leak useful database connection information under certain conditions.
- Fixed issue where messenging module failed to filter for dangerous html/script.
Security Fixes
Updated Modules/Providers
The following modules and providers have been updated in the 5.4.2 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release.
Modules
Providers
NOTE: 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
29 comment(s) so far...
Re: DotNetNuke 5.4.2 Released
Just a comment:
I don't understand how strictly adhering to a release schedule is more valuable than fixing "high profile" issues. Is get it done fast better than get it done right? I like the predictability and frequency, but I would trade that for more infrequent, stable releases. It seems like we're rushing DNN is being out the door to meet a self imposed deadline. End result: I have to wait for June-ish for a major issue to be corrected, one that's been around since 5.3.1 and renders my sites worthless. Seems silly IMO, and runs the risk of more problems being created than corrected.
By ech01 on
5/19/2010 12:35 PM
|
Re: DotNetNuke 5.4.2 Released
@echo1 - I understand how frustrating it can be. If we were releasing just a couple times per year then there would be a stronger case for delaying the release. But when you have an update once a month, then I believe it is more important to be predictable. Had we delayed this release to include more bug fixes, then it would likely only get you the particular fix you desire a couple weeks earlier than you otherwise would have recieved it. On the flip side, it would mean that many users would have had to wait for bugs fixes which directly impacted them.
By Joe Brinkman on
5/19/2010 12:43 PM
|
Re: DotNetNuke 5.4.2 Released
So glad you increased the number of users DNN is capable of servicing to 2.14 billion- I was about to run up against the old limit. HA! Don't I wish! What was the old limit anyway?
By Greg Brown on
5/20/2010 6:48 AM
|
Re: DotNetNuke 5.4.2 Released
Can't tell from the release notes if this version fixes the problem where the bulk emailer fails to work properly. Under 5.4.1 a bulk email would spike the CPU of the host server to around 99% until you manually restarted the application.
By Eric Failing on
5/20/2010 6:49 AM
|
Re: DotNetNuke 5.4.2 Released
I agree with joe here, however the major releases seem to be the biggest problem for getting to truely stable version. Most people I know are still on 523. Major releases every 3 months are (currently) too ambitious IMHO.
By peter schotman on
5/20/2010 6:51 AM
|
Re: DotNetNuke 5.4.2 Released
@Eric - Do you have a Gemini issue number for that problem? BTW, I am not seeing that issue here on DotNetNuke.com which is running 5.4.1.
By Joe Brinkman on
5/20/2010 6:51 AM
|
Re: DotNetNuke 5.4.2 Released
With the speed at which you update DNN, you should have a build-in module to install the updates automatically if the user wants and I am not talking about paying module on snowcovered.
By david letourneau on
5/20/2010 2:03 PM
|
Re: DotNetNuke 5.4.2 Released
David,
It's super easy to do automatic platform upgrades. On the admin page go to Tools >> Upgrade. Click the button and you will get a smooth seamless upgrade.
Wait a second, I'm thinking of WordPress.
;-)
By ech01 on
5/21/2010 5:45 AM
|
Re: DotNetNuke 5.4.2 Released
@ Joe/Eric - I would suggest this relates to this bug I reported soon after 5.4.1 was released - support.dotnetnuke.com/issue/ViewIssue.aspx?ID=12430&PROJID=2.
This kicks w3wp.exe off at 100% cpu, and causes my site to crash.
By Roger Selwyn on
5/21/2010 5:46 AM
|
Re: DotNetNuke 5.4.2 Released
I share the opinion of ech01, see first comment. I'm carefully with the installation of the updates. I thought, 5.4.2 is ready for use now. But I guess its better to wait for 5.4.3. Actually I work with 5.3.1 until 5.4.x is really ready. I would prefer a stable release schedule, not a fast. I'm sure, I'm not the only one with this opinion.
By Reto Brand on
5/21/2010 5:46 AM
|
Re: DotNetNuke 5.4.2 Released
@Reto - As a former college debater, I know that you can find a group of people with just about any opinion, but that doesn't mean much. While your opinion is valid, there are lots of factors that go into determining our release schedule.
5.4.2 is a stable release, but like all software it has outstanding issues that we have yet to address. These issues impact some people, and they don't impact others. Should everyone in the community wait until we fix the bugs that affect one subset of users? The bugs that are impacting @echo1 are not impacting DotNetNuke.com and many other customers. To characterize it as a fast, unstable release is not accurate. It is a release that addresses some issues while acknowledging there are still more to be fixed. It helps some people, but not everyone.
A customers decision to upgrade or not upgrade to a certain release should be based on whether the release provides features they want/need and whether it is stable in their environment.
By Joe Brinkman on
5/21/2010 6:00 AM
|
Re: DotNetNuke 5.4.2 Released
The bugs that are impacting @echo1 are not impacting DotNetNuke.com and many other customers.
Really? You're page hierarchy doesn't get messed up when you move a child page? It happens on every clean install and upgrade I've had since 5.3.1. The fact that it is NOT deemed a showstopper is beyond me. The entrire navigation for my site is kaput and requires manually editing the Tabs table.
support.dotnetnuke.com/issue/ViewIssue.aspx?id=12341&projid=2
While a core function of DNN (page management) broken, it's nice to know the missing release notes issue made it in the fix.
You don't have to respond Brinkman because I already know what your reply will be.
By ech01 on
5/27/2010 4:04 PM
|
Re: DotNetNuke 5.4.2 Released
@Joe - In general I agree with you, it is important to get fixes out there that benefit the majority. But hopefully not at the expense of an increasing number of unfixed major bugs.
Up until this year I've pretty much stepped my site up with each version, but I've not since somewhere around version 5.2.1. I've only recently moved to 5.4.1, and then had to do some code changes to the core messaging code to stop my site failing and to get it to send email to the right users.
My gut feeling is that whilst these are stable releases, they are getting 'less' stable, perhaps as evidenced by the request for community help in submitting patches. Perhaps caused by the bug fix team trying to keep up with the inevitable bugs introduced in new features (yep from my work on the Events module, you think you tested it but the users just don't use the features the way you planned). This is of course just a feeling, I'm sure somebody like Alex may be able to give a better view from the ebb and flow of issues arriving on Gemini.
That said, I still think DNN is evolving in the right direct, so please keep up the good work.
By Roger Selwyn on
5/27/2010 4:05 PM
|
Re: DotNetNuke 5.4.2 Released
All that said, what is the most stable version of 5.X now? I need to start a very basic new site this week for a new lawyer.
Thanks,
aresquare
By aresquare on
5/27/2010 4:08 PM
|
Re: DotNetNuke 5.4.2 Released
Update now,all success
Thanks to all Developer for DNN
By hassan izzeldin on
5/27/2010 4:09 PM
|
Re: DotNetNuke 5.4.2 Released
Hi Joe
Thank you for your answer. Don't missunderstand me. I know, you and the DNN-team makes a great job! I use DNN since Version 3.something. In the last 18 months, the development of DNN growth much faster than in earlier times. The system is more stable and faster, the skin engine is much better (CSS).
My drive to do the updates is usually of security reasons. I register sometimes automated login experiments, so I'm interested to use the newest version. I close out the source ip networks, so it's okey.
After reading the comments, I wasn't sure if it's a good idea to do the update to 5.4.2. On the other side, it's no problem. First step is allways a full backup of the site and the DB. So I can go back everytime.
Thank you for your work and have a good time!
Reto
By Reto Brand on
5/27/2010 4:05 PM
|
Re: DotNetNuke 5.4.2 Released
I and several others I know are still on 4.9.5, having had difficulties with upgrading from earlier versions of 5.x.
Is there an upgrade path to follow from 4.9.5 or should a direct upgrade now work?
By DavidT on
5/27/2010 4:08 PM
|
Re: DotNetNuke 5.4.2 Released
Good to see the new release and that it has fixed some bugs in V5. Unfortunately we tried an upgrade from 4.9 to 5 a couple of weeks ago, and although it has lots of good new features, we found a major security flaw where all users were given full edit rights to the site, so had to backtrack to 4.9 again.
It's good to see the work being done on testable modules, automated test tools etc to help move things to a more robust footing.
Tim
By Tim Thornton on
5/27/2010 4:10 PM
|
Re: DotNetNuke 5.4.2 Released
I very much agree with David's idea of an auto install for DNN system upgrades just as we have for modules. With frequent DNN updates this would make upgrading much easier to do.
By SimmoJ on
5/27/2010 4:10 PM
|
Re: DotNetNuke 5.4.2 Released
@echo1 - Re: [lack of] ease of upgrading DNN
Yeah, we know. Upgrade is not very easy or intuitive (neither is installation).
One of my very first jobs after joining DNN as a user experience developer was to do a heuristic analysis of the DNN installation and upgrade process and provide recommendations for improvement. Discussions have been held with upper management and large improvements for this area are planned for the future, a few releases down the road. (Before a new installation and upgrade process can be implemented we need to redesign the interface and interaction and I'd hope to have an opportunity to do some usability testing on early wireframes and prototypes too.)
So, it may be a bit longer yet, but the upgrade process will get better eventually - I promise!
:-j(enni)
By Jenni Merrifield on
5/27/2010 4:11 PM
|
Re: DotNetNuke 5.4.2 Released
I very much agree with David's idea of an auto install for DNN system upgrades just as we have for modules. With frequent DNN updates this would make upgrading much easier to do.
By SimmoJ on
5/27/2010 4:11 PM
|
Re: DotNetNuke 5.4.2 Released
I use DNN for a Intranet. Our needs probably differ much from a website need. For me I have to agree that a stable platform is much more important than the frequency of updates. The fewest Changes possible for internal users is very important. So I would rather have a platform that updates 2x's a year but that when I get it I know that it works.
Mike
By Mikemac on
5/27/2010 4:09 PM
|
Re: DotNetNuke 5.4.2 Released
I was going to add my 2 cents, but since Joe has played the "former college debater" card, I guess I'll pass. Good luck to you developers going up against The (Former) College Debater.
By JackAdams on
5/27/2010 4:12 PM
|
Re: DotNetNuke 5.4.2 Released
I was going to add my 2 cents, but since Joe has played the "former college debater" card, I guess I'll pass. Good luck to you developers going up against The (Former) College Debater.
By JackAdams on
5/27/2010 4:12 PM
|
Re: DotNetNuke 5.4.2 Released
I use DNN for a Intranet. Our needs probably differ much from a website need. For me I have to agree that a stable platform is much more important than the frequency of updates. The fewest Changes possible for internal users is very important. So I would rather have a platform that updates 2x's a year but that when I get it I know that it works.
Mike
By Mikemac on
5/27/2010 6:10 PM
|
Re: DotNetNuke 5.4.2 Released
I was going to add my 2 cents, but since Joe has played the "former college debater" card, I guess I'll pass. Good luck to you developers going up against The (Former) College Debater.
By JackAdams on
5/27/2010 8:24 PM
|
Re: DotNetNuke 5.4.2 Released
Obviously the platform is improving... and it's generally great. Thank you!
However, regarding the navigation problems noted above - how does something like that get released? Doesn't someone go through a set of test scripts several times, on multiple upgrades and fresh installs, prior to zipping it all up for public consumption? Basic testing should flush out these types of major bugs prior to release. How come we can't download service packs or patches?
Am I making sense?
I tend to agree that stability is far more important than monthly releases.
By Stein Langlie on
6/28/2010 7:34 AM
|
Re: DotNetNuke 5.4.2 Released
Thanks for sharing that, Jenni. It's good to see that DNN is looking to keep the product competitive with other products in the space. Certianly upgrades and particulary installs are critical as the process tempers the opinion of DNN with the admin and/or developer. It's best to keep both of these classes of users happy.
By Chris Cochran on
6/28/2010 7:34 AM
|
Re: DotNetNuke 5.4.2 Released
I can't think of a reason for an auto-updater for anything except a sandbox alpha environment. Unless I control the source, i.e. a ClickOnce kind of setup.
By Dave Scheffer on
6/28/2010 7:34 AM
|
|