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 ...Installation issues!!Installation issues!!
Previous
 
Next
New Post
5/15/2007 5:15 AM
 

I have just tried to upgrade from 4.4 to 4.5 and have realised a few major issues.

Firstly, i have over time chnaged the look and feel of quite a few of the integral componants such as signin/login.ascx and useraccounts.ascx/registration.ascx.  So when i upgraded all my changes where over written. This isnt a major issue becuase i had made a back up.  My question is - is there a definative list of the actual files that have been changed so i can make a dirrect comparasion without having to use a file comparasion tool.

Suggestion: Dont make changes to the look and feel of the application for upgrades.  Only the code behind should be changed.  It is clear that people who want the upgrade only require added fuctionality.

Also my second issue id that i couldnt look in to my upgrade.  Did DotNetNuke change the password!!

Please help


Class Campers -The Home of the Volkswagen camper & Bus Enthusiast
Worlds Cheapest Homes - Need a Cheap Property, cant afford a home
Beeb iPlayer - Need help with the BBC's new iPlayer software
Internet Insurance Quotes - For the the information you will ever require about Insurance
 
New Post
5/15/2007 6:12 AM
 

I would like to see this list too!

As much as possible, I try to seperate out any skinning of my site to my own custom css files.  This includes site skins and any modules that have their own module.css file. With some user controls, this is not as easy and going into your backup to figure out what you did may be necessary.  I've started keeping a running list of all changes so that when I do upgrade, I can minimize the impact to my site design.

What do you mean "couldn't look into your upgrade/"  Did you mean log in?  If so, did you copy over the machine key from your old web.config?

Paul

 
New Post
5/15/2007 6:34 AM
 

Ah

 

Thanks

yes i did mean login to my portal.  i might not of copied over the machine key.  I will give it another go

 

Cheers


Class Campers -The Home of the Volkswagen camper & Bus Enthusiast
Worlds Cheapest Homes - Need a Cheap Property, cant afford a home
Beeb iPlayer - Need help with the BBC's new iPlayer software
Internet Insurance Quotes - For the the information you will ever require about Insurance
 
New Post
5/15/2007 7:31 AM
 

albertramsbottom wrote

Suggestion: Dont make changes to the look and feel of the application for upgrades.  Only the code behind should be changed.  It is clear that people who want the upgrade only require added fuctionality.

The problem with the machine key is solved but a small note regarding the change of the look of standard components (e.g. login, ...): since we produce customized modules as well as special 'looks' (templates) of the complete portal. These systems which are under our maintenance (versions, ...) it takes us a lot of effort to recode the passages after an update. We're using an excellent graphical diff program (beyond compare) which really helps us with this jobs.

bye

 
New Post
5/15/2007 8:23 AM
 

albertramsbottom wrote

Firstly, i have over time chnaged the look and feel of quite a few of the integral componants such as signin/login.ascx and useraccounts.ascx/registration.ascx.  So when i upgraded all my changes where over written. This isnt a major issue becuase i had made a back up.  My question is - is there a definative list of the actual files that have been changed so i can make a dirrect comparasion without having to use a file comparasion tool.

Please notice, that the core team reserved to themselves, to change any portion of the core framework, that is not stated to be an interface. Adoptions of visual appearance shall be made by skins and containers, If you feel a need to modify control layout or functions, it is recommended to create a clone and modify it, as it will not get overwritten on updates.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation issues!!Installation issues!!


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