These two versions were released on Christmas Eve.  You can download them from the DotNetNuke.com site.

I tried one upgrade to 4.9.1, and it wasn't successful.  I haven't had time to go back and try it again.  I've also seen a bug report regarding the Users Online module in 4.9.1.  The caching issue that existed in 4.9.0 seems to have been resolved, based on reports.

Version 4.9.1 was intended to be the final stabilization release for the 4.x series of DotNetNuke versions.  If you use Users Online, it probably isn't for you.


On the other hand, 5.0 is the very first version of DotNetNuke, the next generation.  As a .0 release, I would expect some rough edges. Although it is touted as suitable for live sites, I'll probably use it experimentally waiting for a point release of two.  I would expect that those will come quickly.  Use it to test the "ugradability" of your sites, and to verify that all of your modules work with it.  Check the DotNetNuke.com site for others' experiences.

But ... moving into the new year, it looks like DotNetNuke is leading the way.  I can't wait to get my hands around some of the new features.  There's even one nice new feature in 4.9.1!

Hello,

I've just been experimenting with this upgrading a fresh 4.6.2 (default installation no extra modules added) to 5.0.0 and got errors:

00:00:18.624 -   Executing Script: 04.07.00.SqlDataProvider Error! (see 04.07.00.log for more information)

Error: Violation of UNIQUE KEY constraint 'IX_FolderPermission'. Cannot insert duplicate key in object 'dbo.FolderPermission'.
The statement has been terminated.

However, if you go from 4.6.2 to 4.9.1 you get no errors

This was using DNN Blue skin which then changes to Minimal Extropy skin - when the portal loads up press CTRL + F5 to refresh the cache and get the menu to display correctly.

You can then upgrade 4.9.1 to 5.0.0 + you get no errors.

Again, you need to press CTRL + F5 to reload home page as this time the menu disappears completely - this will refresh the cache + the menu should then display.

Hope this helps,

This post is worth a read in the main dnn forums

Having upgraded, one thing that is confusing is where are the core modules installation section? in 4.9 and below we had the simple tick boxes in Module definitions to install the core modules, now they are gone, but the core module zip resource files are still in the install folder waiting to be installed.

Talk about hiding things - it took me a while even though it was staring me in the face!

In the Control Panel at the top of the page - click on Install Additional Extensions - this takes you to the tick box selection that you should all be familiar with where you can install the core modules.

It would be handy if that link was in the Extensions menu page as well!!!

It is on the Extensions page as well - named 'Batch Install Extensions' stefan blogged about it here

It looks like there is going to be a bit of learning involved here!

Yes, lots of learning, lots of new things and new ways. 

I played a little with Beta6 of DotNetNuke 5, but I may have to set up a test site.  I think that 5.0.2 is about the time that I may consider doing DotNetNuke 5 on a live site.  But, Will Morgenweck has a nice blog entry about using it now.

That's funny I was just chatting with someone and saying I would probably hold off using DotNetNuke five on a live site until version 5.0.2!

When you look through the forums there are quite a few problems people are experiencing with 5.0.0, hopefully most of those will be fixed in 5.0.1 and then others will probably be discovered in 5.0.1 which leads us to version 5.0.2 ready for use on the live websites!

I'm looking forward to digging in to version 5

I was adventurous too and tried it on a new live site. Eventually I had to delete all and reinstall, but this time v4.9.1

Though I installed it again on a test site since it looks very promising. 

My old habit to wait a while and let others find the bugs is still valid I guess.

Tiram

Hey all, I just loaded 5.0.0 and I have 1 live site on it...www.railragenyc.com strictly a blog site. Wow what a difference trying to load a skin and containers. This should be fun since i was just getting familiar with 4.9.1.

Peter

Hello Everyone,
I am upgrading from 4.7 to 4.09.01 and in my local setup which is a copy of my Server setup but in WinXP instead of Win2003. The local upgrade works just fine no errors but the test server Win2003 has a Thread abort error. I have posted it on the DNN forum with greater detail at
http://www.dotnetnuke.com/Community...fault.aspx
Have you guys experienced this or know of a solution?

Did you do the upgrade locally and then move the results to a new machine?  If so, you might want to double check that you did it all correctly.  Take a look at

• How to backup a live hosted DotNetNuke website and restore it to a localhost installation
• How to transfer a localhost DotNetNuke installation to a live website

Hmmm, your thread over there indicates that you can get to the site on your server.  Does the error repeat, or was it a one-time thing?

jncraig, well I have not tried it on the production server but on another server that is identical to production the only difference is the database on production is on another server and the clone is located locally. I have tried upgrading from scratch/fresh and rebuilding the database but I get the same results every time. I do the same locally same database and files and everything upgrades fine.

No I did not upgrade and move it over I upgraded locally and then upgraded on the clone server running win2003 with the same step following the merge method. It worked perfectly on local but not on the clone server. I have tried it several times on both and I get the same results. I am kinda of stuck.

You said that after getting the error, you navigate to the home page and login.  Does that work?  What is not working? 

When I navigate back to the home page and login everything looks like its working fine. I have not found anything that might not be working but I have not really done a thorough check. I have looked at the version under host and it states 4.09.01.