Archive
Monthly
Go
|
|
DNN Blog
May
27
Posted by:
Michael Washington
5/27/2008
Being on the Core is not all fun and games and access to the DNN 5 early Beta's (grin). We run DotNetNuke sites just like everyone else and when a security release comes out we have to upgrade our sites just like everyone else.
Nice to know that when using DNN 4.6.2+ you can just drop the upgrade package on top of the site (after backing up your database and entire directory!) and it just upgrades.
This is great because I have about 20 sites to upgrade and I'm only halfway done... But hey, I'm halfway done! I got home after work and since I told my wife "I will be upgrading DotNetNuke sites all night" she isn't staring at me right now wondering why I haven't come down to dinner.
However I'm getting hungry so it's nice to know I'm halfway done...
FYI - I tried to just drop in the upgrade package on a DNN site before 4.6.2+ and I got a yellow screen of death "Could not find file 'c:\SiteUrls.config'." If performing an upgrade with a version prior to DNN 4.6.2 you have to transfer the settings from web.config to the new release.config and then rename release.config to web.config. The settings you need to transfer are the database connection strings and the machine key. Also any entries in the "codeSubDirectories" section.
18 comment(s) so far...
Re: Core members feel the pain of upgrades too
I'm always hesitant to do just a straight upgrade package without first checking to see if there are any major web.config changes.
By christoc on
5/27/2008
|
Re: Core members feel the pain of upgrades too
Chris - Micahel's point is that the upgrade process now manages web.config changes for you (since 4.6), with the new XmlMerge capability
By cnurse on
5/27/2008
|
Re: Core members feel the pain of upgrades too
XmlMerge? Please, explain
By mariette on
5/27/2008
|
Re: Core members feel the pain of upgrades too
Automatic web.config configuration and update? That's good news. Was this publicized anywhere? This is new to me also.
Great feature though.
By rodweir on
5/27/2008
|
Re: Core members feel the pain of upgrades too
New to me as well!!
By Mike Grace on
5/28/2008
|
Re: Core members feel the pain of upgrades too
Yes, please someone point us to info on this. How reliable is it? How does the system know if some manual setting change needs to be updated or not?
By ahawes on
5/28/2008
|
Re: Core members feel the pain of upgrades too
I also need to know the secret of issue.
By sunwangji on
5/28/2008
|
Re: Core members feel the pain of upgrades too
I will blog on this later this week or next week - it was mentioned in passing in one of Joe's blogs but since even some of the team leads didn't know of its existence - I guess we haven't highlighted this feature enough.
By cnurse on
5/28/2008
|
Re: Core members feel the pain of upgrades too
Is there a way to be notified of releases via email or rss?
By jay.smith on
5/28/2008
|
Re: Core members feel the pain of upgrades too
Just tried it and it works fine.
Michael, Do you know if this upgrade method will work with Version 5?
By Mike Grace on
5/28/2008
|
Re: Core members feel the pain of upgrades too
Please see a Blog post made by Charles Nurse "XmlMerge - what is it?" for a full explanation.
By AdefWebserver on
5/28/2008
|
Re: Core members feel the pain of upgrades too
From the method used in the 4.6.2 and later configurations you should be at VERY minimal risk for manual changes breaking during upgrade. The XML Merge process only updates the entries that need to be updated, therefore making it a nice clean process.
By mitchel.sellers@gmail.com on
5/28/2008
|
Upgrades the version doesn't change
Upgrade from 04.08.02 to 04.08.04, unzip the DotNetNuke_04.08.04_Upgrade.ZIP file, modify the release.config to web.config with my correct connection string and copy all file on a portal www directory but on Host>Site setting the version is allways the 04.08.02 ?
The portal run well!
rmartin
By rmartin77 on
7/9/2008
|
Re: Core members feel the pain of upgrades too
Hi guys. the last post confused me. do i have ro rename the release.config or not? i need to upgrade the 5.0.1 to 5.1.1 ? Please answer a.s.a.p.
By YANNIS MAMALIS on
7/29/2009
|
Re: Core members feel the pain of upgrades too
"I need to upgrade the 5.0.1 to 5.1.1 ?"
I'm in the same boat, and have been searching all over to find some documentation on what to do!
A-?
By Andrew on
7/29/2009
|
Re: Core members feel the pain of upgrades too
I upgraded from 4.8.4 to 5.1.1 to 5.1.2 by just unzipping the upgrade package over my existing directory. I stopped the site in IIS, unzipped the package, started the site in IIS and navigated to www.somewebsite.com/Install/install.aspx (although I believe there is an upgrade url but this still works) and the site upgraded fine without me having to make any changes to the web.config or release.config files.
As always, backup the website directory and db before any upgrade.
By Paul Sellers on
9/6/2009
|
Re: Core members feel the pain of upgrades too
i also need documentation to upgrade from 04.08.02 to 5.2.0..Please share it if you have it..
thanks
By adiga on
11/30/2009
|
Re: Core members feel the pain of upgrades too
I just followed Paul Sellers' brief tips from 09/06 and my upgrade to 5.2.2 was picture-perfect. Thanks Paul.
By rcantu on
1/31/2010
|
|