Planning an e107 Upgrade
e107 Wiki: English | Русский | Deutsch | Français | Magyar | Português | Български | Česky | Nederlands | Ελληνικά | Italiano | Norske | Polska | Slovenščina | Español | Svenska | Translate: Wiki | Page
Planning an e107 Upgrade
It is vital to plan properly before applying any upgrade to a Mission Critical system, and that does include e107 websites. If your website is used for critical functions in your business, then down-time may cause you loss of up-time or worse loss of income. It is YOUR responsibility to plan how you intend to upgrade your system.
The developers work hard to keep e107 up to the mark and together with the support team, we make every effort to test e107 releases, but we cannot cover every aspect the great stuff you are doing with e107.
This is probably a change from the old way of doing things, but it is fairly standard procedure in the IT world. This good advice for EVERYONE, but particularly applicable :-
You need to weigh up the risks of your installation being affected by any new code you introduce to your production system. This applies not only to e107 Core updates, this is equally applicable:-
It is YOUR system and YOUR hard work, take care and look after it properly.
Download the update file
PLEASE READ the release notes BEFORE applying any files to your site
Review the full change list here e107.org/svn_changelog.php.
Read about a specific version here e107.org/svn_changelog.php?version=1.0.4.
Check off changes that your system is using. This will give you a list of things to look at in detail when you are testing.
How urgent is it for you to apply the change, is your site under attack? Are you suffering the problems being fixed? Could you use that new feature you have been waiting for?
When the answers are NO, perhaps hold back for a while & monitor the situation.
PLEASE READ the Installation Forum
See what others are saying or encountering. Early Adopters will always be the first to encounter new problems. If you are cautious, or don't have the patience to work positively alongside support and development teams, then wait until the dust settles before considering an upgrade.
Take a full copy of the production system
Install a TEST copy in a TEST location
PLEASE READ the release notes AGAIN
Apply the Upgrade to the TEST Location
Follow any Special instructions in the Release Notes
Apply any Custom Code Extensions/Changes you have made
A note about custom code!
If you have changed any e107 base code, these changes will need to be reapplied.
Fully TEST your most Important End-to-End Processes
See Follow the menu structured pages to check each feature.
It's unlikely you will use every feature or that every feature is mission critical for you, so you do need to consider the risks at every level.
Compare any apparent changes in behaviour with your Production System.
Read the forums, see if others are finding the same as you. Remember to be nice to your fellow readers :)
Fully TEST any custom Third Party Code
Finally, and do MORE TESTING
Only Proceed to the NEXT stage when YOU are satisfied with testing YOUR new platform