Acts like-taggable-on on Heroku

Question

I use acts-as-taggable-on for tagging in my development application, but when I click it on Heroku I get a nasty error:

ActionView::TemplateError (PGError: ERROR: relation "tags" does not exist : SELECT tags.*, taggings.tags_count AS count FROM "tags" JOIN (SELECT taggings.tag_id, COUNT(taggings.tag_id) AS tags_count FROM "taggings" INNER JOIN offers ON offers.id = taggings.taggable_id WHERE (taggings.taggable_type = E'Offer' AND taggings.context = E'tags') GROUP BY taggings.tag_id HAVING COUNT(*) > 0 AND COUNT(taggings.tag_id) > 0) AS taggings ON taggings.tag_id = tags.id ) on line #29 of app/views/offers/index.html.erb: 26: <div id="sidebar"> 27: <!-- <h3>Popular Tags</h3> 28: 29: <% tag_cloud(@tags, %w(css1 css2 css3 css4)) do |tag, css_class| %> 30: <% link_to tag.name, { :action => :tag, :id => tag.name }, :class => css_class %> 31: <% end %> --> 32: app/views/offers/index.html.erb:29 app/controllers/offers_controller.rb:11:in `index' /home/heroku_rack/lib/static_assets.rb:9:in `call' /home/heroku_rack/lib/last_access.rb:15:in `call' /home/heroku_rack/lib/date_header.rb:14:in `call' thin (1.2.6) lib/thin/connection.rb:76:in `pre_process' thin (1.2.6) lib/thin/connection.rb:74:in `catch' thin (1.2.6) lib/thin/connection.rb:74:in `pre_process' thin (1.2.6) lib/thin/connection.rb:57:in `process' thin (1.2.6) lib/thin/connection.rb:42:in `receive_data' eventmachine (0.12.10) lib/eventmachine.rb:256:in `run_machine' eventmachine (0.12.10) lib/eventmachine.rb:256:in `run' thin (1.2.6) lib/thin/backends/base.rb:57:in `start' thin (1.2.6) lib/thin/server.rb:156:in `start' thin (1.2.6) lib/thin/controllers/controller.rb:80:in `start' thin (1.2.6) lib/thin/runner.rb:177:in `send' thin (1.2.6) lib/thin/runner.rb:177:in `run_command' thin (1.2.6) lib/thin/runner.rb:143:in `run!' thin (1.2.6) bin/thin:6 /usr/ruby1.8.7/bin/thin:19:in `load' /usr/ruby1.8.7/bin/thin:19 

Does anyone know how to make the plugin work on Heroku PostgreSQL?

Thanks!

Answer 1

The following will reflect your dev DB before production on heroku: heroku rake db: push

but what you probably really need (ed) was to migrate heroku rake db: migrate

Good luck

Answer 2

I do not know why, but db: migrate did not work for me, instead I did db: schema: load and now it works smoothly. Give it a try.