Archive
Monthly
Go
|
|
DNN Blog
Dec
26
Posted by:
Joe Brinkman
12/26/2008 9:39 AM
 The DotNetNuke 4.9.1 package was released on Christmas eve. This is an special date in the history of DotNetNuke as the original release was also on Christmas eve. 4.9.1 is a minor stabilization release, although we did add a few small enhancements including the new dashboard which I will cover in depth in a separate blog. Below is a list of the major items included in 4.9.1. As always you can see a complete list with all the details of each fix/change in the ChangeLog.
Major Highlights - Fixed issue with the cache which was preventing proper operation of the scheduler.
- Fixed issue with web crawlers which could cause thrashing in the cache
- Fixed issue with the EventQueue to remove events that result in an error. This prevents an event from filling the event log with errors.
- Fixed issue with the RoleController.GetUserRoles method which introduced a breaking change in 4.9.0.
- Added a new column to the version table to distinguish between Community Edition and Professional Edition installs
- Added a new feature for logging server restarts in a web farm environment.
- Added a new admin Dashboard page. The dashboard provides a single page where hosts can view an overall snapshot of their site.
Security Fixes Updated Modules/Providers The following modules and providers have been updated in the 4.9.1 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release. Modules Providers Technorati Tags: DotNetNuke
5 comment(s) so far...
Re: DotNetNuke 4.9.1 Released
Module News 4.0.1 was included as well.
By Sebastian Leupold on
12/29/2008 3:45 PM
|
Re: DotNetNuke 4.9.1 Released
"Added a new column to the version table to distinguish between Community Edition and Professional Edition installs"
1. What is the difference between Community Edition and Professional Edition ?
2. Why was it required to be distinguished ?
By Jaydeep Bhatt on
12/29/2008 3:45 PM
|
Re: DotNetNuke 4.9.1 Released
@Jaydeep
There is a constant called AppName that will be changed (DNNCORP.CE vs DNNCORP.PRO). The purpose of doing this is to record in the db which version is being used. That is all.
Pro will be a certified build of CE.
By Charles Nurse on
3/6/2010 9:13 AM
|
Re: DotNetNuke 4.9.1 Released
In my opinion, you should take this security issue more seriously. This is a major exploit. You can log in on all sites with public registration as admin. A major message on the frontpage should be the least thing you should do. You should also consider sending an email about the exploit to everyone registered here. Bad people will be writing scripts to exploit this on dnn installations prior of 4.9.1 at the moment. I won't post the exact way to do this here, but I consider it when you don't do something to make it more well-known by everybody hosting dnn sites. I read this post on the 29th december, but looked at the source today and saw how bad it was. If this was written on the homepage, or when I had received a mail as soon as the exploit was known, I would have started upgrading all my sites immediately.
I approved this message myself.
By Paco Wensveen on
1/2/2009 11:13 AM
|
Re: DotNetNuke 4.9.1 Released
With respect to "Critical Security Fixes" - it would be helpful to the community if there was an newsletter type warning that DNN sys admins could subscribe to so that they would be notified ASAP when an issue like this comes up. I check the DNN site frequently but would have appreciated the heads up sooner rather than later and I'm sure I'm not the only one. Beyond that - I continue to be impressed by and appreciative of the core team and the other contributors for continuing to move DNN forward. Keep up the good work in the New Year!
By James Weingart on
3/6/2010 9:13 AM
|
|