Error when creating db with blog engine about refinerycms-blog

[n5ken]

Test Environment: Ubuntu 10.04.1
ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]

[joemsak]

If you generated blog before upgrading to 0997 this would be due to mis-ordered migration files. I'm actually dealing with this /right now/ on a client project. Will post findings asap

[joemsak]

I re-named my migration file timestamps so that this migration from the 0997 upgrade:

https://github.com/resolve/refinerycms/blob/master/db/migrate/20110307025652_translate_custom_title_on_pages.rb

ordered itself before my engine migration files.

Then, in development I was able to just rake db:drop, create & setup.

But on production, I ran this in console to fix "schema_migrations" without dropping the db:

ActiveRecord::Base.connection.execute("TRUNCATE TABLE schema_migrations")
Dir.open('db/migrate').each { |fname| i = fname.split('_').first.to_i; next if i == 0; ActiveRecord::Base.connection.execute("INSERT INTO schema_migrations (version) VALUES(#{i})") };nil

[n5ken]

Actually, I encountered this issue in a fresh install, tested with RefineryCMS 0.9.9.8, and here is my test steps:

1. refinerycms refinerycms998 -d mysql -u root -p root
2. uncomment the "# gem 'refinerycms-blog',         '~> 1.1'" in Gemfile
3. rails g refinerycms_blog 
4. rake db:migrate RAILS_ENV=production

the development environment is okay

[joemsak]

I just did this:

• $ gem update refinerycms
• $ refinerycms testtime
• $ cd testtime
• --- Edit gemfile (uncomment blog) ---
• $ bundle install
• $ rails g refinerycms_blog
• $ rake db:migrate

---

It worked fine, no error. I was also on:
ruby 1.9.2dev (2010-06-18 revision 28360) [x86_64-darwin10.4.0]

[n5ken]

yes, "rake db:migrate" in development environment is okay, but error with production, you can try the following command to reproduce:
rake db:migrate RAILS_ENV=production

[joemsak]

I cannot reproduce this error. Check that the blog migration happens after the 'translate custom title' one.

[n5ken]

seems this have been fixed in RefineryCMS 9.9.12, so close this issue

[refriedchicken]

I am experiencing this in production (not development) on 9.9.20

[n5ken]

As far as i know, it may be an issue of the refinery, not this plugin, anyway, i will try it on 9.9.20

[refriedchicken]

Yes, I think you are right. When I stop the seeds file from running in the migrations and then run the seeds files manually have all migrations have been run it works fine.

[parndt]

Add this to the top of your blog seeds:

Page.reset_column_information