Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Manual Installation on GodaddyManual Installation on Godaddy
Previous
 
Next
New Post
6/21/2006 9:29 PM
 

Nothing. Is that my issue?

I figured as long as it had the original machine keys the same as the database and the connection strings the same, I wouldn't need to change it.

It shows my install as 4.3.1 now that I did what I did, but the Announcements module still shows the same behavior (i.e., bug isn't fixed, so it wasn't properly upgraded).

- Andre

 
New Post
6/22/2006 5:51 PM
 
Andre, I also upgraded and it was a snap. No problems... but I agree.... I still have a problem with Announcements, and I have the same problems with Events. I am not sure what they fixed on this upgrade.

If God does not live in Colorado, I bet he visits there a lot!!
 
New Post
6/22/2006 5:53 PM
 

Has anyone besides Andre upgraded?  If so, exactly what did you do?  I tried and got errors.  I am trying to go from 4.03 to 4.3.  Here is what I did:

I unzipped the upgrade version, and uploaded the files one by one on the root level (overwriting the old ones), except for config, changed my old webconfig to webconfig.backup, followed the directions for the machine key and such, uploaded the config, moved the siteurl and the webconfig to the root level and browsed to my site, and the permission errors that occured so many times before were there.  My only question, and this was probably a stupid mistake on my part, is should the installation date be the original one, or should I change it to the date I upgrade?  

Michelle

 
New Post
6/22/2006 11:13 PM
 

There are some additions to the web.config file in 4.3.x that where not present in 4.0.x.  I am looking at exactly what those changes are and what needs to be done.  Any upgrades to the web.config. file on Go Daddy hosting will have to be done manually.  Once I am sure of what the process is I will put up the instructions.

 
New Post
6/23/2006 12:12 AM
 

you have to remember that the 4.3.0, 4.3.1 and 4.3.? right now are release candidates, and there will be some flaws.

as for the web.config file, follow the installation guide under upgrading(page 40) from the DNN doc's.

Make a back-up copy of your existing web.config file (eg web.backup.resources). We

cannot emphasise enough how important it is that you have a backup. If you lose

the original value of the MachineKeys, then none of your users will be able to log in.

Once you are sure that you have safely backed up your web.config file, rename release.config to web.config.

Replace the following keys in your new web.config, with the values in your backup.

SiteSqlServer

InstallationDate (this will not be present in release.config, so add the key

that is in web.backup.resources to your new web.config)

Set the <connectionStrings> to the same values as you just copied from your old web.config

<add

name="SiteSqlServer"

connectionString="???????"

providerName="System.Data.SqlClient" />

Set the values of the machineKey element to the values that used to be in the

appSettings node as follows.

<machineKey

validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902"

decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"

decryption="3DES"

validation="SHA1"/>

where the “validationKey attribute should have the value that was in the

MachineValidationKey setting and the decryptionKey attribute should

have the value that was in the MachineDecryptionKey setting.

Make any other changes to web.config that you made to support additional providers etc.

and do the same with the file as you did with the install, put it in the Config folder and then drag to the root, so its keeps the same permissions as it had in the Config folder.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Manual Installation on GodaddyManual Installation on Godaddy


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out