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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Upgrade from 4.3.7 ---> 4.4.1   --  WOWUpgrade from 4.3.7 ---> 4.4.1 -- WOW
Previous
 
Next
New Post
2/8/2007 3:04 PM
 
I still have all of my core modules installed that existed in 4.3.5 and I noticed that page load times were cut by almost 50% with the new version.  I am very impressed.

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
2/8/2007 7:21 PM
 
BentAngle wrote

The way the upgrade process works, you should be able to upgrade to 4.4.1 from any dnn version (not including dnn1)  just by getting the lastest upgrade.

I can tell you from my MANY MANY efforts - upgrading in this fashion will not work and I can confirm after speaking with core team members who have done this have failures and had to use their knoweldge of the core code to get themselves out of it and upgrading a dnn 2 site for one experienced core team member took about 2 days... now, if he's having problems, has access to his server via remote desktop,  I can't see in a month of sundays where others can just pick up think that taking their DNN 2 site on a hosted environment will be able to upgrade to the latest version of DNN. What normally happens in builds is that there is a focus in a particular area, for example in this build - 4.4.1 was compression, once it was the membership management, etc.. and there have been builds which focus on upgrading.  Not that it shouldn't upgrade, but it simply doesn't. 

I have been working with DNN for over three years now and the nature of my business is based on building sites for clients and often have seen the necessity to make decisions on upgrading or moving clients from 'child portals' to stand alone ecommerce portals, upgrading from earlier versions of DNN to move into later versions that meet client requirements.

To be honest, upgrading requires preparation and experimentation and sure you can work in a hosted environment but if you do - you really should be looking at having the full build locally to test thoroughly. Sometimes I have to attempt upgrades 1/2 dozen times and that has to be evaluated to whether you should be doing a completely new build and just importing the users.. it's quite a challenge in my opinion, juggling things and where your expectations of what it should do and what it does can find you rather disillusioned with the whole process.

Having said that - on Tuesday, have succesfully upgraded a website running catalook from 3.2.2 to 4.4.1 - and will be documenting and taking screen shots on how I did it and post on my website for you to learn from.  I am attempting now a 3.1.1 >> 4.4.1 upgrade based on what I learnt from it and will share with you.  This is also another Catalook site where I want to use different payment gateways so have to upgrade, it is a deep site with a mix of articles modules from ventrian and the photo gallery too.

There is one thing I also believe that makes upgradeability possible - the modules you are using.  And I have alot of experience with modules in general having had to provide solutions for clients - have around 1,000 modules in my 'kitty' and know from good and quite horrible experiences as to what works and what doesn't, so over time have split my business model up into 'segments' that allow me to provide a range of solutions that are workable for both clients and me.  And that includes a range of  'customised' builds where we strip out the problems before they occur. 

So, by all means - dont' take my advice - try until the cows home home - but I've never met a single person who's been able to upgrade without taking a few steps... and if they are out there.. then please post here.. because it's very disheartening to read 'experts' saying - sure it will work but not knowing their 'secret herbs and spices' to make it actually work.

Part of the reason I think it's good to do things in small steps is that you can often catch the 'culprits' rather than wait until trying to sort the mess out and redoing again. And then it goes back to me thinking ... wow, if I was on a shared hosting envrionment how would I go about this.. so, after I get the upgrades explained, if I have time - will try my best to 'pretend' I'm a hosted person and do a 'step by step' upgrade to see how that goes.  I cannot guarantee any promises of success there but hey it's worth a try.

So, step by step I think will get you there with less headache. 

Nina Meiers 


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
2/8/2007 8:17 PM
 

I have to disagree with Nina on this one.  Users in this thread have already stated that they have SUCCESSFULLY upgraded with no problems.  So a statement like "upgrading in this fashion will not work" is as misleading as "you should be able to upgrade to 4.4.1 from any dnn version (not including dnn1)  just by getting the lastest upgrade."

DNN is tested quite extensively IN EVERY RELEASE to ensure a smooth upgrade when using the core DNN application and DNN sponsored projects.  However, that is as far as we go.  We do not test every vendor's modules to ensure they also support a smooth upgrade process.  Some vendor's may take a little longer to get out updated versions of their products that support the latest DNN version (in most cases, upgrades are not required).  So when Nina says that upgrading DNN is not possible, that is false.  It is possible depending on the modules you are using and the version you are trying to upgrade from/to.  Also, when we release DNN 3 we made a conscious decision to implement dozens of breaking changes all at once.  This means that upgrades from versions prior to 3.0 will require extensive testing on your part.

In the end, DNN is no different than any other mission critical platform.  In this I agree with Nina that you should test your upgrades in a development/test environment and not on your production server.  This will ensure that you end up with a smooth process with no surprises.  While we are comfortable with the DNN upgrade process, your mileage may vary depending on your specific configuration.


Joe Brinkman
DNN Corp.
 
New Post
2/8/2007 9:17 PM
 

At least we can agree on something.. a local installation if you are running a business site that relies on DNN is very important and even more important if you don't have access to the server via Remote desktop and rely on third parties to manage your database. 

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
2/8/2007 9:26 PM
 
Something all users should do is uninstall all modules they are not using.  Any DLL in the bin folder is loaded upon site request...so a simple thing to improve speed  is to uninstall the modules you are not using.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Upgrade from 4.3.7 ---> 4.4.1   --  WOWUpgrade from 4.3.7 ---> 4.4.1 -- WOW


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