How to upgrade from 1.9 to 1.10
The following procedure must be followed exactly if you do not want to lose your website.
1. First determine if the upgrade is required. I do not yet consider 1.10 to be stable because bugfixes are still being released (as of spring 2012). More importantly, a pool of how-to information about the upgrade has not developed yet (other than this article).
3. Create a comprehensive backup of your website, as described elsewhere on my website.
4. Read 1.10 release notes. After I have read the release notes, I noticed the following MAJOR changes from the 1.9 series:
a) The full TinyMCE module will now be available from the module manager as a third party module. It has been replaced with MicroTiny.
b) The NuSOAP module has been removed as a core module.
c) The Printing module was replaced with CMSPrinting
d) The tag has been depreciated. You must edit every single of your templates, and replace with . You must do the same if you install any of the templates from the CMSMS website's collection of templates.
e) Failure to login now issues a login failed event to allow for custom handling (email notifications maybe) of failed login events. If you have not renamed the admin directory for security purposes, I would use this to warn you of any hacking attacks.
f) The tag has been improved to combine all stylesheets into one cached .css file by default, thus under normal circumstances reducing the number of requests to the server required by the browser to render a page.
g) The config.php file has been shortened to just a few lines. All other options are loaded to their default values. If you need to change one of the config.php values (such as to set those values to your old config.php values), you can add the parameter to the shortened config.php manually. Some options have changed. Read the documentation.
REQUIRED UPGRADE PROCEDURE:
1. Back up your website as I have described elsewhere.
2. Upgrade your website to 188.8.131.52.
3. Backup your website again.
4. Read the release notes.
5. Read thru release notes of every module, and upgrade all modules to the version which can run with 184.108.40.206. THIS IS NOT THE SAME AS THE LATEST VERSION OF THE MODULE AS SHOWN BY THE BUILT-IN MODULE MANAGER. YOU MUST GO TO THE FORGE TO ACCESS MODULE RELEASE NOTES AND PREVIOUS VERSIONS.
6. Verify website functionality after upgrade to 220.127.116.11 and module upgrade.
7. Look at all of the third party plugins you have installed into your sites plugins directory and ensure that they should be compatible with CMSMS 1.10 (you may need to refer to the information below or to the forum for this).
8. Look at all of your User Defined Tags (UDT's) to insure that they are be compatible with CMSMS. Read the technical information in the release notes to see what has changed.
9. Ensure that each module that your site requires is compatible with CMSMS 1.10. If your site is using some older or less used modules, you may have to contact the modules author or inquire in the CMSMS forum to see if the module is compatible.
NOTE: the CMSMS development team has not tested any third-party modules for compatibility with CMSMS 1.10, and do not consider it to be one of their responsibilities. CMSMS developers have never tried to keep third-party modules up to date with every CMSMS release. Therefore, if you use anything other than core modules, then no one promises that your website will not break due to incompatibility with your outdated third-party modules.
10. DO NOT EVER upgrade a CMSMS site by overwriting the files with an upgrade. ALWAYS create a clone of your database, and then install the updated CMSMS version into a new folder on your server. Point the new installation to the database clone.
This way, you will preserve the old version of your website should you need to revert to it.
Install all of the necessary modules to your new installation. Your template and module functionality should work now, minus the files in /uploads which you have not yet transferred from the old installation.
Copy files in /uploads to the new installation folder if your website functions well with the new CMSMS version. Do not use FTP. Use your hosting control panel file management utility or SSH.
DO NOT delete old CMSMS installation and database.
˅˅˅ Additional valuable information is available at one of the links below: ˅˅˅
Did you like the article? Let Google Search know by clicking this button:
Page last modified 20-Aug-12 22:26:22 EDT