AdefWebserver wrote
I agree with everything Sebastian said. I do try a fresh install whenever possible. in my opinion the upgrade process is a miracle because so many things could go wrong but for the most part it works.
It's like Microsoft Windows, sometimes you need to just re-install the darn thing if you can.
One option I do is to create a new site, migrate the users over from the old site then copy over the content and the data for specific modules. For a huge site this of course is not feasible, but for 20 pages or less it's an option. However I have some sites that have been upgraded from DNN 2.0 and are running fine.
I guess I decide to start from scratch when I know I installed some module that caused problems, then I don't trust the stability of the install and therefore feel that the upgrade is going to fail.
see, none of these sites is very complex- they all use very basic modules & functionality. in fact, some of the upgrades i've gone through which have had problems are that very type- very basic without a lot of complexity. that i'm seeing so many problems is what led me to post this topic- maybe i am going about it wrong and need some tips.
i *can* and will dig in technically if i need to, but i would have guessed upgrades would have been cleaner when dealing with a simple site. maybe i'm going up too many steps at a time (4.3.4 to 4.5.3, in some cases 4.0.2 to 4.5.3). i didin't want to be digging through database tables and code when i decided on upgrading.
i'm toying with the idea of deleting and installing clean for some of the remaining sites i want to upgrade, but the problem with that is that even though they are informational, they tend to have loyal users who don't tolerate a lot of downtime.
i just wish things were a little more consistent. or maybe i need to be doing things differently or be more prepared.
i'm open to suggestions. anyone?