I think you will need to change spree_core to spree_frontend in that file. We will need to update the release notes with this mention.
On Tue, May 21, 2013 at 3:00 AM, ColoKoala wrote:

Following your description, I did
1. Update gemfile from *gem 'spree', '1.2.4*' to *gem 'spree', :git =>
'git://github.com/spree/spree.git', :branch => '2-0-stable' *
2. Bundle update
3. rake railties:install:migrations
4. rake db:migrate
Then I got the error at homepage:
couldn't find file 'store/spree_core'
(in D:/DevRuby/MyStore/app/assets/stylesheets/store/all.css:7)
Extracted source (around line *#7*):
4: <meta content="width=device-width, initial-scale=1.0, maximum-scale=1" name="viewport">
5: <%== meta_data_tags %>
6: <%= favicon_link_tag image_path('favicon.ico') %>
7: <%= stylesheet_link_tag 'store/all', :media => 'screen' %>
8: <%= csrf_meta_tags %>
9: <%= javascript_include_tag 'store/all' %>
10: <!--[if lt IE 9]>
The content of D:/DevRuby/MyStore/app/assets/stylesheets/store/all.css is
* This is a manifest file that'll automatically include all the
stylesheets available in this directory
* and any sub-directories. You're free to add application-wide styles to
this file and they'll appear at
* the top of the compiled file, but it's generally better to create a new
file per style scope.
*= require store/spree_core
*= require store/spree_promo
*= require_self
*= require_tree .
*= require store/spree_product_zoom
When I run "git status", the only changes are Gemfile, Gemfile.lock,
db/schema.rb, and migrations.
Apparently there should be many changes in the spree application directory
structure and file contents from 1.2.4 to 2.0.0.
Before spree comes up with an ideal automated solution, what's the best way
to solve the problem now?
Create a new store, compare the change and modify directories/files one by

Search Discussions

  • Daniel Dixon at May 24, 2013 at 12:02 am
    Another one: Make sure all of your products have a default shipping
    category. My products didn't use one before and this resulted in no
    shipping methods showing up on delivery page of the checkout page after
    upgrading to 2.0. Took a while to figure out why.

    Also, old orders may not have shipments with a shipping_location_id,
    causing an error on the views/shared/_order_details page. Run this inside
    the console:


    This assumes you've only got on Spree::StockLocation right now.

    On Tuesday, May 21, 2013 11:20:41 PM UTC-5, ColoKoala wrote:

    Yes you are right. It seems we need

    1. change spree_core to spree_frontend in
    app\assets\stylesheets\store\all.js and app\assets\stylesheets\store\all.css
    2. change spree_core to spree_backend
    in app\assets\stylesheets\admin\all.js and
    3. remove spree_promo from all above

    On Tuesday, May 21, 2013 7:41:34 AM UTC-7, Ryan Bigg wrote:

    I think you will need to change spree_core to spree_frontend in that
    file. We will need to update the release notes with this mention.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupspree-user @
postedMay 21, '13 at 2:41p
activeMay 24, '13 at 12:02a

2 users in discussion

Ryan Bigg: 1 post Daniel Dixon: 1 post



site design / logo © 2023 Grokbase