Skip to content

Upgrading a BrowserCMS project to 4.0

peakpg edited this page Feb 3, 2014 · 15 revisions

Prerequisites

Projects must first be upgrade to 3.5.4 or later. Owing to how migrations are handled, its isn't possible to upgrade directly to 4.0.

(Note: Work in progress)

Steps

1. Update the Gemfile

Use the correct version of BrowserCMS, remove any version # references to Rails and Rails related dependencies (i.e. sass-rails, coffee-rails, etc)

gem "browsercms", "4.0.0.alpha"
# gem "rails", "3.2.5" # Use BrowserCMS dependency.
gem 'sass-rails' #, '~> 3.2.3' 
gem 'uglifier', #, '~> 3.2.2'

You may want to comment out all existing BrowserCMS modules initially, since they may not have CMS 4.0 versions availalble yet Then run bundle update.

2. Add migrations

  1. Record the timestamp for the existing 3_0_0 migration (i.e. 20080815014337).
  2. Delete all the BrowserCMS migrations (3_0_0, 314, etc) from the project.
  3. Add the migrations by running rake cms:install:migrations
  4. Rename the newly generated browsercms300.cms.rb so so it matches the old timestamp of browsercms3_0_0. This will prevent the new migration from running.

Then run rake db:migrate

Clone this wiki locally