Apr 7, 2009 at 2:28 AM
Edited Apr 7, 2009 at 2:38 AM
Well I would normally say its quit easy, but changing versions on a commercial host is not fun.
First you could try to get Godaddy to update for you, we have a new IIS installer (see
www.dasblog.info ) that works quite well but its not really an upgrader application.
Normally I would say just xcopy every file in the new release over the files in the old release without touching your "contents" directory and hand comparing
and editing your "site.config" and "siteSecurity.config" in the SiteConfig directory.
But on a commercial host I would follow these steps.
1. download the files "site.config" and "siteSecurity.config" in the SiteConfig directory at your site on Godaddy to your local computer.
2. download the entire "contents" directory of your site at Godaddy to your local computer (just a backup to make sure).
3. download the web release file zip for dasBlog 2.3 and expand the files into a directory on your local system (new release)
4. edit the (new release) "site.config" file and add your domain name reference: <Root>http://mydomain.com/</Root>
5. edit the (new release) "siteSecurity.config" file and add your security information.
6. make sure that the updated "site.config" and "siteSecurity.config" are in your (new release) file structure on your hard drive
7. ftp all files and directories in your 2.3 (new release) to your godaddy site, do not include the "contents" directory.
After caching has expired your site should come back up as a dasBlog 2.3 site.
8. Log into your site and edit the configuration of the site from the menu and finish putting your site back like it was. (You may want to reference a print out of your old "site.config" file.
"Works on my Machine" but no warranties.
<edit> If your are using the Navigation or Blogroll fuctions you might want to backup and replace the new with the existing "navigatorLinks.xml" & "blogroll.opml" files.