Page 1 of 1

Upgrading : what is kept, what is lost ?

Posted: Mon Oct 09, 2006 10:06 pm
by fredt
I'm planning upgrades from 0.13 to 1.0.2 (unless a 1.0.3 is planned for next days...). I'd like to know if current styles are left untouched during migration, or if they're updated to latest release ?

If they're left, I problably won't be able to get advantage from latest progress (in fact I think my css come from a version older than 0.13...).

If they're erased, I'll loose my changes (colours, and some behaviour...)

So, what does migration do, and what is the best upgrade path for these non-files, db-encapsulated, components (css, templates....)

TIA !

Re: Upgrading : what is kept, what is lost ?

Posted: Tue Oct 10, 2006 5:36 am
by tsw
as a basic rule everything in db is left untouched (well db schema might change but thats all)

files in uploads forlder will be left untouched

cmsms files (like file templates) might change

still TAKE A BACKUP! It gives you that nice warm feeling of secutiry when after upgrade you notice that some module you absolutely need doesnt work with 1.0 series and customer is about to hang you... :)

hope this helps

Re: Upgrading : what is kept, what is lost ?

Posted: Tue Oct 10, 2006 8:32 pm
by fredt
Yep it helps !  :)

When you say "nothing is touched"... nothing if DB exists, Table exists (so I could rename it), or TableRow_with_identical_key (item, rename some things here & there) ?

So, I won't take advantage from new css, samples... Should I create a clean install on other place, learn from it, and copy-paste-adapt... or is there some way to DIFF old vs new install ?

Fred

Re: Upgrading : what is kept, what is lost ?

Posted: Tue Oct 10, 2006 8:55 pm
by Dr.CSS
It will not add any new templates or CSS, if you need to play with or see any new stuff from fresh install go here...

http://multiintech.com/CMSMSDemo/admin/login.php

Name: adman
Password: adman