Upgrading a BrowserCMS project

This page covers how to upgrade a BrowserCMS project. It is valid for upgrading projects from 3.3.x to later versions of 3.3.x. See below for a list of instructions for older versions.

Instructions

1. Update your project's Gemfile

gem 'browsercms', '3.3.3' # Set to the new version of the gem

2. Update scripts

In your project, run the following scripts from the commandline:

$ bundle install
$ rails g browser_cms:cms
$ rake db:migrate

This will install the new version of the gem, copy the migrations into the project, and then update the database.

Instructions for Older Versions

If you need instructions for how to upgrade earlier versions of BrowserCMS, see the following list:

• Upgrading to 3.3.x from 3.1.x (aka Rails 2 to Rails 3)
• Upgrading to 3.1.5 (from 3.1.x)
• Upgrading to 3.1.x (from earlier versions)

Troubleshooting

If you get

Message
undefined method `id' for nil:NilClass

on the Sitemap, or

Message
undefined method `name' for nil:NilClass

on any of the core content library types,search your sections table for any unjoined section nodes that do not have parent sections. The immediate fix is to delete these sections. The following query should help you locate problem section_nodes

SELECT * FROM section_nodes left  join sections on section_nodes.node_id = sections.id WHERE section_nodes.node_type = "Section"

This stack trace may point to the following line in the cms section.rb file

      section.full_path = root? ? section.name : "#{name} / #{section.name}"