Updating Pageflow

When moving your project to a newer version of the Pageflow gem, there are a couple of steps you need to perform to upgrade your application.

Read the CHANGELOG

Pageflow is still in a 0.x version. We plan to follow semantic versioning once we have reached 1.0. For now we'll increase the patch level for bug fix releases and the minor version whenever (possibly breaking) functional changes or enhancements occur.

Please always carefully review the CHANGELOG for additional instructions before updating.

Increasing the Gem Version

cd my_pageflow_app
$EDITOR Gemfile # Increase Pageflow version
bundle update pageflow

If the Pageflow entry inside the Gemfile does not have a version constrains (i.e. it just says gem 'pageflow'), you call bundle update pageflow without editing the Gemfile.

Database Migrations

You need to make sure the most recent migrations are applied to your database. Here's the full process:

bundle exec rake railties:install:migrations 

This copies new migrations from Pageflow and its plugins to the db/migrate directory inside your app. Then run:

bundle exec rake db:migrate

Changing the asset version

New versions contain updated locale files for i18n-js. The most bulletproof way to incorporate all new translations is to change your asset version. This will recompile all assets once you deploy.

# config/initializers/assets.rb

# When updating Pageflow, update the assets version as well. It will force a refresh for i18n-js.
Rails.application.config.assets.version = '1.x'

Here x is a placeholder for the number you are supposed to increase.

Now restart your app.