Migration error when upgrading from 515839e73b to HEAD #366
Comments
|
Did you also run rake db:migrate? On Monday, January 7, 2013, Adinda Praditya wrote:
|
|
The error is the output of |
|
Can you run |
|
Here you go: |
|
I am experiencing this as well. |
|
@sheam thanks for the confirmation. Hopefully one of us will be able to reproduce this soon :) in the mean time if you find any workaround please let us know as it helps with debugging the issue. Thanks! |
|
I just confirmed that the issue does not occur with rails 3.2.3, but it does occur with 3.2.11. The issue occurs during rake db:seed, on the following lines of my seeds.db file: forem_forums = Forem::Forum.create([ Perhaps there is a better way to seed the DB? |
|
Can you double check that you're running friendly_id version 4.0.9? |
|
yep. [497]$ bundle show friendly_id |
|
I notice the forem version is (1.0.0.beta1) from git://github.com/radar/forem.git (at master) , should I try a different version? |
|
The latest should show as 1.0.0.beta1. We don't really use the version in Forem. :) |
|
Ignoring the seed error (as I am just creating forums), if I start the app, and try to go to the forums index I get the dreaded: NoMethodError in Forem/forums#index Showing /Users/sheam/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/bundler/gems/forem-9b9c15ecbbbb/app/views/forem/categories/_category.html.erb where line #1 raised: undefined method `can_read_forem_forums?' for #User:0x007f915b79ace0 This does not happen with rails 3.2.3 either. |
|
@sheam: That seems like a completely different error, like the decorators that add that method to the User class aren't being loaded. Could you please open a new issue with some steps to reproduce it within a new app? |
|
I'm reproducing this issue with |
|
Please try |
|
OK Confirm. This was caused by friendly_id not being version 4.0.9.. see my successful reproduce: |
|
Now I get no such column: name. I am guessing this is because 'title' go renamed to 'name'. I have to run, but will a migration which renames the 'title' column to 'name' fix this? Or do I have to run rails g forem:install again to regenerate my forem models. If I have to run form:install again, are there files I should delete beforehand? |
|
@sheam How are you getting that error? Do you have an app we could use to reproduce it? |
|
I get the error during the seeding of the DB. In my schema.rb, the form_forums table has a title, and not name. I think you guys have renamed title column to name a few month ago. I do not want my code public at this point, but if I can zip up my working directory and send it to you I will. Or if you have a place to upload it to... I don't think you would reproduce the error by getting a fresh copy of my code from bit bucket, as the problem now seems to have to do with the upgrade. But I can also send you a fresh copy. |
|
Hmm okay. I think best for you is just to manually change forem_forums to have name and not title thus solving this issue for you. I don't think that others will get this, personally. :-) |
|
class RenameTitleToNameInForemForums < ActiveRecord::Migration This fixed the migration issue. I am bug free, going to try and deploy to heroku now. Thanks for the amazing response time guys. |
|
I am experiencing this issue as well. Upgrading Forem gem. I tried deleting the initializer, just in case, but still a no-go. Rails 3.2.11 and 3.2.13.rc1 were both tested producing the following errors: Please help |
|
Hi, seems no one is keen to help with this.. I figured out this issue, and would suggest that you fix the project... The Everything is working fine now. |
|
@funkdified We are actually keen to help out on this problem. The issue is that if we can't reproduce it on our machines, then we can't verify that it's actually fixed. So if you can give us some easy steps to reproduce a problem accurately on our machines, we can identify the problem and then fix it. Thank you. |
|
@radar Oops, sorry to sound so negative, just saw your response and realized I sounded bad! I think I was just frustrated. Anyway, hope what I said was helpful. |
|
@radar I followed funkdified's suggestion about the migrations, and it solved this issue for me. When I ran but this would error out (I think the auto_subscribe migration had already succeeded, and is not a part of the problem): I changed the timestamp in the Perhaps when I upgraded forem, I upgraded too many versions at once? thus the Hope this helps reproduce the bug. |
|
I just had this issue as well for Rails 4, and the above solution fixed it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm trying to upgrade from 515839e to HEAD (03725d7). After restarting the rails app, noticed there's a change in database structure, so I run
rake forem:install:migrationsand added some new migration files. The problem comes when I ran migration. I get this error:Did I miss something? Thanks for the great work!
The text was updated successfully, but these errors were encountered: