Fresh install of Zurb Foundation 4.2.2 gives File to import not found or unreadable: foundation.

[SimonBirrell]

This is a very fresh install, no customization, nothing.

app/assets/stylesheets/foundation_and_overrides.scss:1272
app/views/layouts/application.html.erb:18:in `_app_views_layouts_application_html_erb__1136389973384962107_70338499250200'
app/controllers/lists_controller.rb:7:in `index'

Here are my gems:

Gems included by the bundle:

• actionmailer (3.2.13)
• actionpack (3.2.13)
• activemodel (3.2.13)
• activerecord (3.2.13)
• activeresource (3.2.13)
• activesupport (3.2.13)
• addressable (2.3.4)
• arel (3.0.2)
• builder (3.0.4)
• bundler (1.2.3)
• capybara (2.1.0)
• capybara-webkit (1.0.0)
• chunky_png (1.2.8)
• coderay (1.0.9)
• coffee-rails (3.2.2)
• coffee-script (2.2.0)
• coffee-script-source (1.6.2)
• compass (0.12.2)
• compass-rails (1.0.3)
• diff-lcs (1.2.4)
• erubis (2.7.0)
• execjs (1.4.0)
• factory_girl (4.2.0)
• factory_girl_rails (4.2.1)
• ffi (1.9.0)
• formatador (0.2.4)
• fssm (0.2.10)
• guard (1.8.1)
• guard-rspec (3.0.2)
• hike (1.2.3)
• i18n (0.6.1)
• journey (1.0.4)
• jquery-rails (3.0.1)
• json (1.8.0)
• launchy (2.3.0)
• listen (1.2.2)
• lumberjack (1.0.3)
• mail (2.5.4)
• method_source (0.8.1)
• mime-types (1.23)
• mini_portile (0.5.0)
• multi_json (1.7.7)
• nokogiri (1.6.0)
• pg (0.15.1)
• polyglot (0.3.3)
• pry (0.9.12.2)
• rack (1.4.5)
• rack-cache (1.2)
• rack-ssl (1.3.3)
• rack-test (0.6.2)
• rails (3.2.13)
• railties (3.2.13)
• rake (10.1.0)
• rb-fsevent (0.9.3)
• rb-inotify (0.9.0)
• rb-kqueue (0.2.0)
• rdoc (3.12.2)
• rspec (2.13.0)
• rspec-core (2.13.1)
• rspec-expectations (2.13.0)
• rspec-mocks (2.13.1)
• rspec-rails (2.13.2)
• sass (3.2.9)
• sass-rails (3.2.6)
• slop (3.4.5)
• sprockets (2.2.2)
• thor (0.18.1)
• tilt (1.4.1)
• treetop (1.4.14)
• tzinfo (0.3.37)
• uglifier (2.1.1)
• xpath (2.0.0)
• zurb-foundation (4.2.2)

[pushcx]

Why did you close this issue?

I ask because I am experiencing the same bug.

[SimonBirrell]

It's so stupid I was kind of ashamed to admit it.

Restart your rails server and the problem goes away :-)

[pushcx]

Well, then I can only wish I had the same bug. :(