Thanks Mitchel,

I saw Charles' post today, but I wasn't sure from his post whether he was saying you could just copy the upgrade over your site and run the install. I see from your post that this is in fact the case and that's awesome. What a timesaver.

I was under the impression that using the upgrades was fine for minor version, but that it was a good practice to use the full install for major version upgrades because of SQL updates. Does the XmlMerge resolve that issue, or am I misunderstanding a concept somewhere?

Yes, this change in the core makes it just fine to use the upgrade version for major releases as well, AS long as you are coming from 4.6.2 or later to the current version.

now, with using the upgrade package, you might need to upgrade a few modules once the upgrade is done, but that is easy!

Hi Mitchell, I too saw Charles' post (as well as your reply about running off to update your blog -- I guess you weren't kidding :-). Thanks to both of you. I don't know how this GREAT feature slipped past me. I guess I was always too nervous about using the upgrade pkg and never really looked at it in detail. Today I upgraded two DNN installs, one with 17 portals under it (of course I did a backup first!). Both upgrades went without a ripple!!! The thing I like most and always forget to do I don't have to worry aboutany more -- resetting auto-upgrade to false. Thanks.

Chuck R.

Chuck,

Don't feel bad, if you look at Michael Washington's blog he didn't know about it either....

Thanks for letting us know. I was just about to do a test run on DNN 4.8.3 and will try this out.

It is too bad the DNN's release process doesn't do a better job of notifying its customers. This feature has been available since October and few people knew it.

Thanks for making this public.
/DaveS

Do we actually need to click on http://www.mysite.com/install/install.aspx?mode=install or will an access to the home page still cause this to happen?

/DaveS

You will need to go to install/install.aspx if you have auto upgrade set to false, which I HIGHLY recommend.

<i>now, with using the upgrade package, you might need to upgrade a few modules once the upgrade is done, but that is easy! </i>

Easy for you but as a newbie I am not sure how to upgrade a module....Can anyone help? Thanks.

If you have a module listed in Module Definitions that needs an update, you can download the update from DotNetNuke.com, then simply upload it via the Module Definitions page from the "Install Module" option.

Mitch, how about turning on the app_offline.htm file first before unzipping... wouldn't that still be a good first step to make sure that it's "on" before you unzip the upgrade package over the existing site?

Hello,

I have done plenty of upgrade process these last years/months, without any problem. And today, I tried to migrate from 4.8.2 to 4.8.3
Not so easy, I have the same error message, always and always.... Any idea ??

DotNetNuke Configuration Error
Domain Name "mydomain.com/Install" Does Not Exist In The Database

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:
{...}

DV FX

Comments from the following blog entry: DotNetNuke 4.8.4 - Install/Upgrade Instructions, located at: http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/220/DotNetNuke-484--InstallUpgrade-Instructions.aspx

Comments from the following blog entry: DotNetNuke 4.8.4 - Install/Upgrade Instructions, located at: http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/220/DotNetNuke-484--InstallUpgrade-Instructions.aspx

Impressive, I just love this article as it is very useful to me

Suppose I want to upgrade DNN and also upgrade all the core modules.. How could I modify the Install package to automatically upgrade the web.config the way the Upgrade package does?

You can use the install package, the thing is you MUST remove the web.config file that is included in the install package.

Personally a streamlined upgrade, then manual updating of the additional modules is my preferred route.

I think it might be good to notify people that when you're on a hosted account, you can't just simply 'unzip' on top of your existing site.

At least this is my experience:

I had a test environment at home, i.e. Server 2003, SQL 2008, running my DNN sites. I unzipped the upgrade package over my DNN sites folder and the upgrade went without a hitch.

Then I tried doing the same thing for the production site hosted at my Provider, and after I unzipped the upgrade package on top of the site, I was missing folders and portals and ...

Obviously it didn't go well. I restored the old site (4.7) and everything is fine in that version, but I still need to figure out how to 'unzip' the upgrade on top of my production site utilizing the web tools my Hosting Provider gives me...

Jimmy,

Good point, I would highly recommend NOT using the providers zip process, and unzip locally and FTP to the server. You will want to put an App_offline.htm file up to take the site down while the files are copying.

If you want more assistance please visit the forums on this site.