Over the course of my 10 years or so of using DNN I've performed countless upgrades on many sites, and my current situation has me stuck, so I'm looking for a hand.
I have a site that is running 7.0.0, and I attempted to upgrade it to 7.3.2 using the routine ftp file method.
Just to recap exactly what I did:
1. Backed up site files
2. Backed Up DB
3. Downloaded and extracted the 7.3.2 upgrade package.
4. Set the 'AutoUpgrade' to false in the current web.config file on the site
5. Uploaded the Upgrade files to the site with the 'overwrite' option.
6. Lauched the site /Install/Install.aspx?mode=upgrade
This is where it started to get a bit hinky. Usually you see all green success and move on. In this case a number of the 7.0.x sql provider scripts failed, then some of the 7.1 scripts worked, and then again some failed, and so on through the 7.2 SQL provider scripts until it made it to the module upgrades. Then some failed, but some passed. It really seemed to have no rhyme or reason. I also was told by someone from interactive webs who was helping troubleshoot another issue on the site that it looked like my site was still using an outdated web.config file from an old 6.x installation.
Exactly what do I need to be doing during upgrades to ensure that any new items fields etc. are getting updated in the web.config? Is there a reason that the upgrade process does not handle this? I cannot attach the web.config file here but if anyone can offer insight please let me know. Or if you think looking at the actual web.config file will help reach out in response to this thread and I can arrange to get a sanitized copy for you.
Thanks!
Dustin