Archive
Monthly
Go
|
|
DNN Blog
Jul
22
Posted by:
Joe Brinkman
7/22/2010 9:52 AM
 Last night we posted another beta of DotNetNuke 5.5 which you can access from the beta release page on DotNetNuke.com. This is probably your last chance to provide feedback on the 5.5 release as we are nearing completion of the testing cycle. You can have a direct impact on the quality of the 5.5 release if you act today.
Since the last beta release 2 weeks ago, the DotNetNuke team has been busy cleaning up bugs and validating the user scenarios for the new Content Localization feature. During this time more than a 160 bugs and enhancements have been implemented. Many of these changes have been as the result of feedback we received from the earlier alpha and beta releases. In addition to all of the work on Content Localization we have fixed a number of longstanding bugs and made major strides on improving performance. We are hoping to be able to wrap up testing soon so that we can get a final release out to the community this summer.
Content Localization required many foundational changes to DotNetNuke so it is important that we get as much feedback as possible. If you have an existing DotNetNuke website, try to perform an upgrade on a backup copy of your site. If you are a module developer, run your module through some installation and upgrade scenarios. If you are skin designer, make sure that your skins install and work correctly. If you are new to DotNetNuke, give the beta a trial run and let us know what you think.
Once you have done your testing then let us know your results – good or bad. You can post any issues you find on our issue tracker. You can also discuss the betas on the Open Core Testing forums. Let us know what you liked, what you didn’t like or what problems you are having. Open Source works best when you get involved.
Overall, 5.5 is shaping up to be one of our most significant releases in the last 2 years and your help would be greatly appreciated in making sure this release is as solid as possible.
10 comment(s) so far...
Re: DotNetNuke 5.5 Getting Closer to Release
A quote to be saved...
"Open Source works best when the you get involved."
- Joe Brinkman
By Will Strohl on
7/22/2010 11:00 AM
|
Re: DotNetNuke 5.5 Getting Closer to Release
The Upgrade Package does not seem to contain the newer version 2010.2.713.35 (or higher) of Telerik.Web.UI.controls.
By Bruce de Beer on
7/22/2010 7:19 PM
|
Re: DotNetNuke 5.5 Getting Closer to Release
Here's a bit of feedback from me.
In the next release, I'd like to see options that are not actually available to a user, not offered.
For instance. A page admin can't add a module from the Host or Admin dropdown. So why offer the option. The Page admin has to select "Existing" and then a page.
It would be better to have a list of existing modules and offer that.
Also, If I Add a language "EN-GB", The Text/HTML module's image properties simply don't render. You have to be in the know to know to clone the Provider files with the extended name "EN-GB". This should be made automatic - or a notice put up when the language other than EN-US is selected.
Also - you need to get the designers in to spruce-up the default skin. It's boring and not pretty enough to attract people in from the competition.
I think DNN should incorporate more Silverlight.
I think the page and module visibility should be on a popup or some kind of side-panel.
On the Admin ribbon, the page "Edit" button is confusing. It should be "Settings" not Edit. Edit to even a switched-on newbie it means edit the content on a page. If I ask a customer to go to a piece of content and edit it, they click on the line and hit Edit. Except it's the page edit. The client says But I want to Edit The page. I have to explain "No that button doesn't mean Edit it means Open the settings page for the page, not the piece of content in that module".
Counter-intuitive.
Also, in the settings page, the different settings are scattered around. Then there are "Advanced" settings. They aren't really advanced, they are just tucked away to keep the page tidy. I'd like to see a search for a setting box that works like Windows 7. A list of setting links would come up from which to choose and you'd be able to work the system without having to learn the whole thing first.
Some of these are big changes, and I wouldn't expect them soon. Just some ideas for you.
By David Cuthill on
7/22/2010 7:19 PM
|
Re: DotNetNuke 5.5 Getting Closer to Release
@Bruce - See my latest Blog "Where did Telerik Go?" www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2711/Where-did-Telerik-go.aspx
@David - Thanks for the feedback. We are definitely looking at fixing some of these usability issues in upcoming releases.
By Joe Brinkman (Host) on
7/22/2010 7:21 PM
|
Re: DotNetNuke 5.5 Getting Closer to Release
Another quote to be saved...
”...more than a 160 bugs and enhancements have been implemented.”
By pontus66 on
7/23/2010 8:33 AM
|
Re: DotNetNuke 5.5 Getting Closer to Release
Does 5.5 Content Localization feature also solve the Telerik Localization dilemma? As you know you can tell RadEditor via "LocalizationPath" the way to the localization ressource files. But for controls like RadGrid there is no such way. E.g. RadGrid width Culture="de-DE" used in a module expects RadGrid.Main.de-DE.resx in App_GlobalResources – a place for ressource file which is ignored by the DNN module handling.
I just did some test with the last 5.5 Beta, but this problem seems still to exist.
By Heinz Peller on
7/23/2010 8:33 AM
|
Re: DotNetNuke 5.5 Getting Closer to Release
"During this time more than a 160 bugs and enhancements have been implemented."
160 bugs implemented!? I might wait for 5.6 I think ;-)
Seriously, well done. Sounds like it's going to be an impressive release.
By Rod Weir on
7/23/2010 8:34 AM
|
Re: DotNetNuke 5.5 Getting Closer to Release
@HeinzPeller - I don't think that 5.5 is going to solve any of the Telerik Specific localization issues. I will raise this with the team today, but I expect that is something we will have to address in 5.5.1
By Joe Brinkman on
7/23/2010 8:35 AM
|
Re: DotNetNuke 5.5 Getting Closer to Release
Does anyone know if the lack of e-mail support for 3rd party apps like Dynamic Forms and Registration have been solved in this 5.5 release? I have not had an opportunity to test and probably will not before final release.
By Dennis Kyle on
8/10/2010 4:56 PM
|
Re: DotNetNuke 5.5 Getting Closer to Release
I'm looking forward to the 5.5 release. I am already impressed with the last installation I did of 5.4, the telerick Rad Editor is a GREAT addition! Very sleek. I also like the new layout for the top admin panel.
In response to an earlier comment on this blog: @David Cuthill , so when are you going to get started on all of these changes David? I have to be honest, I am a long time user of DNN (built over 20 sites) and I find this feedback to be un-progressive, and un-helpful. I do not agree with adding more silverlight or "sprucing up" the default skin. For one the default skin looks polished as it is.
Sorry @David but these 'requests' you are asking for sound very personalized (for you) and are do not seem to account for what might be good for all users of DNN. I don't see one request in there that I would second.
To the DNN team keep up the great work, this product just keeps getting better.
By James Harrison on
8/10/2010 4:56 PM
|
|