Page 1 of 1
Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 7:37 pm
by richardcms
Hi,
Is is necessary to update you site with each upgrade or can a person simple go from (as an example) 1.2 to 1.3 and still have all the necessary files, avoid any errors and not have any issues?
Re: Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 7:47 pm
by RonnyK
RichardCMS,
it is off course not necessary to follow all upgrades, as sometimes things are changed that dont apply to you f.e. the 1.2.2 to 1.2.3 affected only TinyMCE. If you dont use TinyMCE, the vulnerability wasnt applicable to you. On the other hand, most upgrades have to do with fixed vulnerabilities and bug-fixes and new functionality.
Upgrading would be just overwriting the files with the full package of the latest stable, logging in in the backend afterwards will kick the upgrade process....
Ronny
Re: Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 8:07 pm
by calguy1000
Can we make a FAQ entry on this somewhere on the wiki?
How to 'Upgrade' ?
Re: Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 8:20 pm
by RonnyK
Re: Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 8:32 pm
by nivekiam
I was watching this thread in the hopes that it would answer some of my questions. Let me know if I'm going off topic and I'll start a new thread.
How does CMSms handle upgrades when you have modules that are incompatible with the new version of the core? Does it disable them, issue warnings, make it hard to remove it the offending module after the fact or does it puke and die?
Re: Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 8:40 pm
by calguy1000
CMS does nothing with handling incompatible modules between upgrading. We've really only broken module compatibility once (and that was with the 1.1 version I think)..... It's your responsibility before upgrading to make sure that the modules you already have installed will work, and/or there is a new version available, and that the upgrade sequence works for that module when you decide to go to a new version.
But if you have an incompatible version (because the MinCMSversion() and MaxCMSVersion()) data in the modules is incompatible with CMS.... then the module will be disabled in the admin, and you (should) have the ability to uninstall the module from the admin. Of course, this is only for well behaved modules.
Re: Do you have to download every update/upgrade?
Posted: Fri Jan 11, 2008 8:46 pm
by nivekiam
Perfect. Thanks. That's handled pretty similarly to what I'm use to.
Re: Do you have to download every update/upgrade?
Posted: Sat Jan 12, 2008 2:53 pm
by Pierre M.
Hello,
calguy1000 wrote:
It's your responsibility before upgrading to make sure that the modules you already have installed will work, and/or there is a new version available, and that the upgrade sequence works for that module when you decide to go to a new version.
This is nice material for the release notes template. Or should I add it to the above wiki page ?
Pierre M.