New problem after upgrade to

(Juan Manuel Formoso) #1

After creating the new discourse.conf file and configure it to my environment, I get this error when I execute rake RAILS_ENV=production multisite:migrate

==  CreateTopTopics: migrating ================================================
-- create_table(:top_topics)
rake aborted!
/discourse/app/models/top_topic.rb:6: unknown type of %string
    @periods ||= %i{yearly monthly weekly daily}
/discourse/app/models/top_topic.rb:6: syntax error, unexpected $end
    @periods ||= %i{yearly monthly weekly daily}

I’m a little lost and I’m afraid I broke something.
Is there an easy way to clone a fresh copy of latest and preserve my data in my postgres database?

(Juan Manuel Formoso) #2

It also left the database corrupted and I had to revert to an earlier backup; but I lost my local git repo and so it is now detached from the remote. I have no idea how to synch again without losing my data.

Any help would be appreciated

(Sam Saffron) #3

This is a compatibility with 1.9.3 bug @zogstrip

(Neil Lalonde) #4

I pushed a fix so that the migration will work in ruby 1.9.


Not sure what you mean, but you can start tracking master again like this:

$ git checkout -b newmaster origin/master
Branch newmaster set up to track remote branch master from origin.
Switched to a new branch 'newmaster'

If you have local changes, you can rebase them on master. Does something like that help?

(Jeff Atwood) #5