Layout not reloaded in production. about spree_static_content HOT 5 CLOSED

Have you updated to the latest code? Perhaps you are still using an older version that still contains the page caching, which has since been removed.

from spree_static_content.

I double checked and I am using 1-3-stable branch:
(my Spree is also 1.3.0)

gem 'spree_static_content', :git => 'git://github.com/spree/spree_static_content.git', :branch => '1-3-stable'

I looked to make sure and page caching has indeed been removed in 1-3-stable. So it must be something else?

from spree_static_content.

What commit does you Genfile.lock indicate your using for the extension?
Try running bundle update spree_static_content if it does not indicate
your using the latest commit in the branch.

On Saturday, January 19, 2013, Aleksandr Melentiev wrote:

I double checked and I am using 1-3-stable branch:

gem 'spree_static_content', :git => 'git://github.com/spree/spree_static_content.git', :branch => '1-3-stable'

I looked to make sure and page caching has indeed been removed in
1-3-stable. So it must be something else?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/102#issuecomment-12464913.

from spree_static_content.

You are right, seems like master was merged into 1-3-stable only 3 days ago so I had to bundle update spree_static_content. I had to run rails g spree_static_content:install for new migrations, but was getting an error:

SQLite3::SQLException: no such table: pages: ALTER TABLE "pages" RENAME TO "spree_pages"

For some reason my table was already named spree_pages; so I had to run the add_render_as_partial_for_layout_for_spree_pages migration individually. Everything is working now.

Not sure why the table was already named spree_pages to be honest, but perhaps add a check to the migration like so, in case others updating might see same issue:

class PrefixPagesTableName < ActiveRecord::Migration
  def change
    if table_exists?(:pages)
      rename_table :pages, :spree_pages
    end
  end
end

EDIT: figured it out, it's because of #71 where a migration was renamed, so I already had it run before which renamed pages to spree_pages, but with an update it copied over the same migration with a new name, hence the error.

from spree_static_content.

I opened a PR #105 for the migration issue described above.

from spree_static_content.