Error upgrading from a pinned version to 3.0.1

[trevor...@gmail.com]

I'm upgrading from a pinned version of refinerycms to version 3.0.1: https://github.com/refinery/refinerycms/compare
I followed http://www.refinerycms.com/guides/upgrading-to-the-latest-stable-version
After running "rails generate refinery:cms --update" I got the following output:

me@ubuntu:~/dev/agrifeeds$ rails generate refinery:cms --update

setting api_version is deprecated and will be removed shortly, only v2 is supported
        gsub  Gemfile
      append  .gitignore
      insert  app/assets/stylesheets/application.css
   identical  app/views/sitemap/index.xml.builder
   identical  config/database.yml.mysql
   identical  config/database.yml.postgresql
   identical  config/database.yml.sqlite3
   identical  app/decorators/controllers/refinery/.keep
   identical  app/decorators/models/refinery/.keep
        rake  railties:install:migrations db:create db:migrate db:seed
Copied migration 20160202231039_translate_refinery_images.refinery_images.rb from refinery_images
Copied migration 20160202231040_add_translated_title_to_refinery_resources.refinery_resources.rb from refinery_resources
Copied migration 20160202231041_update_slug_and_title_in_refinery_page_parts.refinery_pages.rb from refinery_pages
Copied migration 20160202231042_fix_slug_format_in_refinery_page_parts.refinery_pages.rb from refinery_pages
NOTE: Migration 20100913234705_create_refinerycms_authentication_schema.rb from refinery_authentication_devise has been skipped. Migration with the same name already exists.
NOTE: Migration 20120301234455_add_slug_to_refinery_users.rb from refinery_authentication_devise has been skipped. Migration with the same name already exists.
NOTE: Migration 20130805143059_add_full_name_to_refinery_users.rb from refinery_authentication_devise has been skipped. Migration with the same name already exists.
NOTE: Migration 20150503125200_rename_tables_to_new_namespace.rb from refinery_authentication_devise has been skipped. Migration with the same name already exists.
agrifeeds_development already exists
setting api_version is deprecated and will be removed shortly, only v2 is supported
== 20160202231039 TranslateRefineryImages: migrating ==========================
== 20160202231039 TranslateRefineryImages: migrated (0.1200s) =================

== 20160202231040 AddTranslatedTitleToRefineryResources: migrating ============
== 20160202231040 AddTranslatedTitleToRefineryResources: migrated (0.0359s) ===

== 20160202231041 UpdateSlugAndTitleInRefineryPageParts: migrating ============
== 20160202231041 UpdateSlugAndTitleInRefineryPageParts: migrated (0.1809s) ===

== 20160202231042 FixSlugFormatInRefineryPageParts: migrating =================
== 20160202231042 FixSlugFormatInRefineryPageParts: migrated (0.1027s) ========


-- DEPRECATION WARNING --
The use of 'Change Refinery::Pages.default_parts= from ["Body", "Product Desc", "Column 2", "Nutritional Analysis"] 
to [{:title=>"Body", :slug=>"body"}, {:title=>"Product Desc", :slug=>"product_desc"}, {:title=>"Column 2", :slug=>"column_2"}, 
{:title=>"Nutritional Analysis", :slug=>"nutritional_analysis"}]' is deprecated and will be removed at version 3.2.0.
rake aborted!
ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR:  missing FROM-clause entry for table "title"
LINE 1: ..."refinery_page_parts"."refinery_page_id" = $1 AND "title"."t...
                                                             ^
: SELECT  DISTINCT "refinery_page_parts"."id", position AS alias_0 FROM "refinery_page_parts" 
LEFT OUTER JOIN "refinery_page_part_translations" ON "refinery_page_part_translations"."refinery_page_part_id" = "refinery_page_parts"."id" 
WHERE "refinery_page_parts"."refinery_page_id" = $1 AND "title"."title" = 'Body' AND "title"."slug" = 'body'  ORDER BY position ASC LIMIT 1
<snip stack trace>

Poking around the site on my dev instance everything seems to be working... Anything specific I should be checking or need to manually fix?

[Philip Arndt]

Seems like everything worked, except the db:seed command, which is okay. You should be relatively fine given the commit you upgraded from. :)

Just check that all the files that it mentioned that it changed in the stack trace are okay. In production you'll only need to run:

rake db:migrate

Not any other db tasks.