XNSIO
  About   Slides   Home  
 
Managed Chaos
Naresh Jain's Random Thoughts on Software Development and Adventure Sports
      
`
 
RSS Feed
Recent Thoughts
Tags
Agile agile bengaluru 2010 Agile Coach Camp agileindia agile india agileindia2012 Agile India 2012 AgileIndia2013 Agile India 2013 Agile India 2013 Workshops agileindia2014 Agile India 2014 agile mumbai 2010 ASCI Attendees Profile Code Coverage code smells Conference Continuous Deployment Continuous Integration cyclomatic complexity Design duplicate code Evolutionary Design Extreme Programming Industrial Logic Lean Lean Startup LinkedIn Open Source pair programming post modern agile primitive obsession smell Refactoring Refactoring Teaser Scrum SDTConf simple design TDD technical debt Test Driven Development Testing unit testing user stories video
Recent Comments
«

»

How to upgrade CMS Made Simple from 1.9.x.x to 1.10.x

Recently I had the “pleasure” of upgrading from CMSMS 1.9.3 to 1.10.3.

  • Downloaded the cmsmadesimple-1.10.3-full.tar.gz
  • Unzipped it overwriting some of the existing files from the older version (1.9.3) [tar -xvf cmsmadesimple-1.10.3-full.tar.gz -C my_existing_site_installation_folder]
  • Ran the upgrade script by opening http://my-site.com/install/upgrade.php

I was constantly getting stuck at step 3, it was complaining:

Fatal error: Call to undefined method cms_config :: save () in /install/lib/classes/CMSUpgradePage3.class.php on line 30

Digging around a little bit realized cms_config is no longer available.

Then tried downloading cmsmadesimple-1.9.4.3-full.tar.gz

Luckily this time I was able to go past step 3 without any problem.

So now I was on version 1.9.4.3, but I wanted to get to 1.10.3. So

  • As per their advice, upgraded all my modules to the latest version
  • Downloaded cmsmadesimple-1.10.3-full.tar.gz,
  • Copied its contents
  • Tried to run the upgrade script.

Everything went fine, it even updated my database scheme to version 35 successfully. But then when I hit continue on step 6, it was stuck there for ever. Eventually came back with Internal Error 500. Looking at the log file, all I could see is

“2012/07/28 06:28:35 [error] 23816#0: *3319000 upstream timed out (110: Connection timed out) while reading response header from upstream”

Turns out that in 1.10, the CMSMS dev team broke a whole bunch of backward compatibility. In Step 6 of the upgrade, it tries to upgrade and install installed modules. But during this process it just conks out.

Then I tried to uninstall all my modules and run the upgrade script. Abra-kadabra the upgrade went just fine.

  • Then I had to go in and install those modules again.
  • Also had to update most of the modules to the latest version which is compatible with 1.10.
  • And restore the data used by the modules.

Only had I known all of this, it could have saved me a few hours of my precious life.

P.S: Just when I finished all of this, I saw the CMSMS dev team released the latest stable version 1.11

Related posts:

  1. Issues on Upgrading to Latest Version of CMS Made Simple I really like CMS Made Simple. Its pretty neat if you want to set up a website using a CMS...
  2. Pharma Hack: Spammy Links visible to only Search Engine Bots in WordPress, CMS Made Simple and TikiWiki Over the last 6 months, I’ve been blessed with various pharma hacks on almost all my site. (http://agilefaqs.com, http://agileindia.org, http://sdtconf.com,...
  3. Freeset’s Deployment Script At Freeset, we have two CMS Made Simple instances set up. One for development and another one for live environment....
  4. Proxy Issues while installing Rails Plugins I’m trying to install restful_authentication plugin on a rails project on a Windows platform. Every time I try “ruby script\plugin...
  5. Simple Regression Testing for Static Web Sites For Freeset, I’ve always been in the quest of Simplest Thing that Could Possibly Work. In a previous post, I...
  6. How to install Subversion on a shared host I use http://bluehost.com for hosting all my sites. So far I’m very happy with their service. The only thing I...
  7. Towards Continuous Deployment: Zero Downtime WebApp Deployment Lets assume you have a simple web application which runs on a web server like tomcat, jetty, IIS or mongrel...
  8. Automated database change management process for an Agile project This is an over simplified summary of my experiences, handling database changes on different agile projects. Most of the projects...
  9. How to move CVS repository without losing history? Log into the CVS repository server Go to the cvs root dir tar the whole cvs root dir using the...
  10. Upstream Connection Time Out Error in Nginx Currently at Industrial Logic we use Nginx as a reverse proxy to our Tomcat web server cluster. Today, while running...

This entry was posted on Monday, July 30th, 2012 at 7:30 PM and is filed under Deployment, Hosting, Tips. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.


    Licensed under
Creative Commons License